Hyperkitty archives - new list not archived
Hi!!
I'm running mailman 3.2 on Ubuntu server 18.04. Installed it via pip inside a conda virtual environment.
I'm having problems related to hyperkitty on which I'd really appreciate some help. When I try to access the archives of a mailing list named 'test-nov' it redirects me to 'example.com/hyperkitty/list/test-nov@example.com/', where a 404 appears and a 'No archived mailing-list by that name.' message is thrown by hyperkitty.views.mlist.overview.
I'm not very experienced with django, so I could have made a mistake on any configuration. I have not configured an MX for my mail server yet, so I'm able to send emails but I can't recieve emails for my lists. Is this somehow related to a misconfigurated MTA?
Which logs should I take into account?
Regards, Vincent.
On 12/3/18 9:15 AM, vaarcilal@eafit.edu.co wrote:
I'm having problems related to hyperkitty on which I'd really appreciate some help. When I try to access the archives of a mailing list named 'test-nov' it redirects me to 'example.com/hyperkitty/list/test-nov@example.com/', where a 404 appears and a 'No archived mailing-list by that name.' message is thrown by hyperkitty.views.mlist.overview.
Are you running the Django periodic tasks? See <http://docs.mailman3.org/en/latest/config-web.html#scheduled-tasks-required>, In particular, I think the hourly "new_lists_from_mailman" job is what you need.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks! Now a well rendered page from Hyperkitty is shown. Big header: "Page not found". In red: "This page either doesn't exist, or it moved somewhere else." Is this normal since the list is new and it has no messages?
The cron jobs seems to be OK. It has been like this for 2 hours. Here are the last logs from syslog:
Dec 11 18:55:01 hostname CRON[114841]: (www-data) CMD (django-admin runjobs minutely --pythonpath /path/to/project --settings settings) Dec 11 18:55:01 hostname CRON[114842]: (www-data) CMD (django-admin runjobs minutely --pythonpath /path/to/project --settings settings) Dec 11 18:56:01 hostname CRON[114855]: (www-data) CMD (django-admin runjobs minutely --pythonpath /path/to/project --settings settings) Dec 11 18:56:01 hostname CRON[114856]: (www-data) CMD (django-admin runjobs minutely --pythonpath /path/to/project --settings settings) Dec 11 18:57:01 hostname CRON[114871]: (www-data) CMD (django-admin runjobs minutely --pythonpath /path/to/project --settings settings) Dec 11 18:57:01 hostname CRON[114872]: (www-data) CMD (django-admin runjobs minutely --pythonpath /path/to/project --settings settings)
On 12/11/18 11:04 AM, vaarcilal@eafit.edu.co wrote:
Thanks! Now a well rendered page from Hyperkitty is shown. Big header: "Page not found". In red: "This page either doesn't exist, or it moved somewhere else." Is this normal since the list is new and it has no messages?
The cron jobs seems to be OK. It has been like this for 2 hours. Here are the last logs from syslog:
Have the 'hourly' cron jobs run? The hourly new_lists_from_mailman job should make the list available in HyperKitty even if there are no posts.
You could also try manually running
django-admin runjob new_lists_from_mailman
If that fixes it, there may be some issue with how cron is running these jobs.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks!! That fixed it. More precisely: django-admin runjob new_lists_from_mailman --pythonpath /path/to/project --settings settings
I ran this command as the user on which mailman's conda environment is installed, even though in the docs is specified it should be run as www-data, since I'm running ubuntu. Does this mean I can just put this commands in my-user's cron file?
On 12/12/18 8:57 AM, vaarcilal@eafit.edu.co wrote:
I ran this command as the user on which mailman's conda environment is installed, even though in the docs is specified it should be run as www-data, since I'm running ubuntu. Does this mean I can just put this commands in my-user's cron file?
Yes. Things should probably be run as the user that owns the conda environment.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
vaarcilal＠eafit.edu.co