Docker Installation of Mailman -- The Hyperkitty Chronicles
Using Maxking's docker project to install mailman3, I have a fairly functional mailman3 installation. However Hyperkitty is not archiving or showing list participants like:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/
This is my page:
https://mailman3.emwd.com/hyperkitty/list/testlist@mailman3.emwd.com/
The docker documents really don't say much about getting HK up and running.
Brian
On 12/22/18 6:08 AM, brian@emwd.com wrote:
Using Maxking's docker project to install mailman3, I have a fairly functional mailman3 installation. However Hyperkitty is not archiving or showing list participants like: ...
Check your list's Settings -> Archiving in Postorius and make sure policy is public or private and HyperKitty is active.
Also, make sure the cron jobs are running. I'm not sure how this is set up in the Docker container, but see http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi Mark,
Merry Christmas (or Happy Holidays!).
I have the list settings set to Public archives and hyperkitty checked in the Active archivers box.
As for the cron jobs. I am not sure how to change the following to reflect my setup:
# This goes in /etc/cron.d/mailman
# Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory
@hourly apache django-admin runjobs hourly --pythonpath /path/to/project --settings settings @daily apache django-admin runjobs daily --pythonpath /path/to/project --settings settings @weekly apache django-admin runjobs weekly --pythonpath /path/to/project --settings settings @monthly apache django-admin runjobs monthly --pythonpath /path/to/project --settings settings @yearly apache django-admin runjobs yearly --pythonpath /path/to/project --settings settings
- apache django-admin runjobs minutely --pythonpath /path/to/project --settings settings 2,17,32,47 * * * * apache django-admin runjobs quarter_hourly --pythonpath /path/to/project --settings settings
For instance, I am using nginx not apache. I also do not know what the /path/to/project should be using maxking's setup. I also am not sure how to call django-admin from the command line. I get the following:
# django-admin -bash: django-admin: command not found
Brian
On December 22, 2018 10:00:49 AM EST, brian@emwd.com wrote:
Hi Mark,
Merry Christmas (or Happy Holidays!).
Thank you.
I have the list settings set to Public archives and hyperkitty checked in the Active archivers box.
As for the cron jobs. I am not sure how to change the following to reflect my setup:
I think we need to wait for Abhilash to answer this as I don't know enough about the Docker setup.
-- Mark Sapiro mark@msapiro.net Sent from my Not_an_iThing with standards compliant, open source software.
On Sat, Dec 22, 2018, at 7:01 AM, brian@emwd.com wrote:
Hi Mark,
Merry Christmas (or Happy Holidays!).
I have the list settings set to Public archives and hyperkitty checked in the Active archivers box.
As for the cron jobs. I am not sure how to change the following to reflect my setup:
# This goes in /etc/cron.d/mailman
# Replace "apache" by your webserver user ("www-data" on Debian systems) and # set the path to the Django project directory
@hourly apache django-admin runjobs hourly --pythonpath /path/to/project --settings settings @daily apache django-admin runjobs daily --pythonpath /path/to/project --settings settings @weekly apache django-admin runjobs weekly --pythonpath /path/to/project --settings settings @monthly apache django-admin runjobs monthly --pythonpath /path/to/project --settings settings @yearly apache django-admin runjobs yearly --pythonpath /path/to/project --settings settings
- apache django-admin runjobs minutely --pythonpath /path/to/project --settings settings 2,17,32,47 * * * * apache django-admin runjobs quarter_hourly --pythonpath /path/to/project --settings settings
uwsgi handles all the cron jobs in the container images, you don't need to setup anything. See here1.
For instance, I am using nginx not apache. I also do not know what the /path/to/project should be using maxking's setup. I also am not sure how to call django-admin from the command line. I get the following:
# django-admin -bash: django-admin: command not found
If you do need to run django-admin commands, you have to do that
inside the container images. So, try this to enter the container:
$ docker exec -it mailman-web bash
Then to run commands:
$ python manage.py <subcommands>
-- thanks, Abhilash Raj (maxking)
On Sat, Dec 22, 2018, at 6:08 AM, brian@emwd.com wrote:
Using Maxking's docker project to install mailman3, I have a fairly functional mailman3 installation. However Hyperkitty is not archiving or showing list participants like:
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/
This is my page:
https://mailman3.emwd.com/hyperkitty/list/testlist@mailman3.emwd.com/
The docker documents really don't say much about getting HK up and running.
You don't need to do anything to make HK work.
What do you see in the logs? Check /opt/mailman/web/logs/ for Mailman-Web logs and /opt/mailman/core/var/logs for the logs of Core.
There must be some errors showing up, causing emails to not be archived.
Brian
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/
-- thanks, Abhilash Raj (maxking)
Abhilash Raj wrote:
What do you see in the logs? Check /opt/mailman/web/logs/ for Mailman-Web logs and /opt/mailman/core/var/logs for the logs of Core.
This is what I found but sporadic:
ERROR 2018-12-22 13:54:07,233 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:07,252 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:07,686 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:07,721 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 13:54:08,447 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS.
There must be some errors showing up, causing emails to not be archived.
I am not seeing any other errors.
- Do I need mailman-hyperkitty.cfg setup in the /opt/mailman/core directory?
- What ownership/group does the file structure need to be in the /opt/mailman directory? I am wondering if the hyperkitty issue has something to do with permissions?
It seems HK should work out of the box with your docker setup if I read your documentation correctly. Is that correct?
At this moment I am dead in the water. Is there anyway to try to test the archiving and see if the logs shows an error using the tail -f command?
Brian
Are the cron jobs supposed to be showing up in the /opt/mailman/web/logs/uwsgi-error.log? I am seeing:
Sat Dec 22 22:02:44 2018 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 3242) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 3242 exited after 5 second(s) Sat Dec 22 22:03:44 2018 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 3248) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 3248 exited after 5 second(s) Sat Dec 22 22:04:44 2018 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 3254) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 3254 exited after 5 second(s) Sat Dec 22 22:05:44 2018 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 3260) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 3260 exited after 5 second(s) Sat Dec 22 22:06:44 2018 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 3266) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 3266 exited after 6 second(s) Sat Dec 22 22:07:44 2018 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 3272) [uwsgi-cron] command "./manage.py runjobs minutely" running with pid 3272 exited after 5 second(s)
Brian
Ok I was able to trigger an error when posting to the list in the mailmanweb.log:
ERROR 2018-12-22 22:12:01,813 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 22:12:01,830 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 22:12:03,243 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 22:12:03,251 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 22:12:03,350 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS. ERROR 2018-12-22 22:12:03,419 34 django.security.DisallowedHost Invalid HTTP_HOST header: 'mailman-web:8000'. You may need to add 'mailman-web' to ALLOWED_HOSTS.
Brian
I solved the problem and now Hyperkitty is working.
I added "mailman-web" to the "/opt/mailman/core/mailman-hyperkitty.cfg" file. Now my archives are working!!!! It looks like I have a fully functional Mailman3 installation at this point. I have some minor issues/questions but I will start a separate thread(s) for them. Probably on Monday.
Thank you Abhilash Raj. You have been a big help.
Brian
participants (3)
-
Abhilash Raj -
brian＠emwd.com -
Mark Sapiro