Hi,
I assume micro instance has been used for obvious reason to leverage AWS Free tier.
Unfortunately it wouldn't work for Mailman 3 w. Hyperkitty because of large memory footprint of the applications.
However, Postorius-only version works just fine on micro instance.
I'm providing free AMIs for both cases with zero-configuration needed (but without SES integration) in AWS Marketplace, links could be found on page https://mailman3.com/aws/
Best regards, Danil Smirnov
ср, 10 апр. 2019 г., 19:29 Abhilash Raj <maxking@asynchronous.in>:
On Tue, Apr 9, 2019, at 2:34 PM, roger.hislop@is.co.za wrote:
Hi all -- really need some help. I'm tech literate, but definitely not a sysadmin or dev.
I'm following the tutorial at "Olay's Farmland" at https://www.olay.xyz/2018/01/01/deploy-mailman-3-on-aws-using-docker/ which seems to be a clone of the same content here https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/
The right place to get help regarding these guides would be the author of the posts, which AFAIK, have no affiliation with Mailman Core Team.
On a (very) quick glance, it seems fine.
Easy enough to get most of the way ... set up EC2 instance, configure SES and add DNS settings with DKIM etc. Set up Postfix, test it. All working groovy.
I run through the how to all the way through setting up the containers and firing it up. This is where things start to get funky.
Once the docker-compose is run, I run "curl http://172.19.199.3:8000/postorius/lists/" to test. First time it said it couldn't connect to database. So I nuked and restarted from scratch. Second time it said the same thing... was reading around the place and tried again, and then reran that curl and it worked -- gave me html from a page. But the VM started running slowly --taking forever to follow keypresses.
Eventually became unresponsive. So I rebooted the machine via AWS console, and docker ps showed only the postgres db running. docker-compose ps shows Name Command State Ports
docker-mailman_database_1 docker-entrypoint.sh postgres Up 5432/tcp mailman-core docker-entrypoint.sh maste ... Exit 255 8001/tcp, 8024/tcp mailman-web docker-entrypoint.sh uwsgi ... Exit 255 8000/tcp, 8080/tcp
So rebuilt the container -- same thing. It looks and feels like its running out of memory.
I used the compose file from
https://gist.githubusercontent.com/Yexiaoxing/833bfcc5d3e4e0c06a8b7f0bac7c4c... (with appropriate edits).
How much memory do yo have in your VM? Have you tried using a bigger VM?
thanks Abhilash
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/