hyperkitty won't list more than 5 posts and shows empty grey Activity Summary box
Hi,
On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example). Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers.
Regards,
Cyprian
On 08/04/2017 02:54 AM, Cyprian Laskowski wrote:
Hi,
On our new installation of Mailman 3, which seems to be otherwise working fine (thanks!), the "More..." link doesn't work, such that the list continues to only show 5 posts, even though it's clear that hyperkitty is aware of more (if I click on August, for example).
This is <https://gitlab.com/mailman/hyperkitty/issues/134>. The fix is a one-liner at <https://gitlab.com/mailman/hyperkitty/commit/2034b937c438f66b465d86bebbbc120...>
Also, nothing is shown in the grey box under Activity Summary (the <svg class="chart-data"> element), although I'm not sure what's supposed to be shown there. The public archived list is here: http://seznami.cjvt.si/hyperkitty/list/test@seznami.cjvt.si/. I'd appreciate any pointers.
The box is a bar graph of posts by day. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/> for what it should look like. I'm not sure why it's empty in your case. Do you have cron running all the Django minutely, quarter-hourly, ... tasks?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks for the quick and helpful reply. (However, please note that until now I was under the impression that there had been no response yet to my question, since my post appears to indicate having 0 comments at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2017/8/).
Yes, the one-liner did indeed help the "More ..." problem. :)
As for the bar graph, it's showing a bar now, probably correct. But I have not seen anything about django cronjobs in the MM3 documentation, haven't set any up, can't find any in our (Ubuntu 16.04) system and haven't done anything to fix this in-between (although I have restarted mailman-core and mailman-suite a few times). Could you point me in the right direction?
On 08/09/2017 12:56 PM, cyp@trojina.si wrote:
Thanks for the quick and helpful reply. (However, please note that until now I was under the impression that there had been no response yet to my question, since my post appears to indicate having 0 comments at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2017/8/).
Yes, I see that. It was apparently an issue with caching. I recently enabled memcached on the server for django and apparently there was an issue with that. I just did what @abompard suggested at <https://gitlab.com/mailman/hyperkitty/issues/131#note_30244378> and that seems to have fixed it, at least for the moment.
Yes, the one-liner did indeed help the "More ..." problem. :)
As for the bar graph, it's showing a bar now, probably correct. But I have not seen anything about django cronjobs in the MM3 documentation, haven't set any up, can't find any in our (Ubuntu 16.04) system and haven't done anything to fix this in-between (although I have restarted mailman-core and mailman-suite a few times). Could you point me in the right direction?
This is what I have in Mailman's crontab on lists.mailman3.org
@hourly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs hourly @daily /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs daily @weekly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs weekly @monthly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs monthly @yearly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs yearly 0,15,30,45 * * * * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs quarter_hourly
- /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs minutely
Send periodic digests.
# I like 03:30 so they go overnight, but since we're 'global' and on UTC, # maybe 07:30 is good. 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send
I don't recall exactly where I saw that that was needed, but you can find it (except for the periodic digests bit) at <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>. Note that that suggests a system crontab with the web server user rather than the 'mailman' user's crontab.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi,
On Wed, 9 Aug 2017 13:42:20 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 08/09/2017 12:56 PM, cyp@trojina.si wrote:
Thanks for the quick and helpful reply. (However, please note that until now I was under the impression that there had been no response yet to my question, since my post appears to indicate having 0 comments at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/2017/8/).
Yes, I see that. It was apparently an issue with caching. I recently enabled memcached on the server for django and apparently there was an issue with that. I just did what @abompard suggested at <https://gitlab.com/mailman/hyperkitty/issues/131#note_30244378> and that seems to have fixed it, at least for the moment.
Yes, the one-liner did indeed help the "More ..." problem. :)
As for the bar graph, it's showing a bar now, probably correct. But I have not seen anything about django cronjobs in the MM3 documentation, haven't set any up, can't find any in our (Ubuntu 16.04) system and haven't done anything to fix this in-between (although I have restarted mailman-core and mailman-suite a few times). Could you point me in the right direction?
This is what I have in Mailman's crontab on lists.mailman3.org
@hourly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs hourly @daily /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs daily @weekly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs weekly @monthly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs monthly @yearly /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs yearly 0,15,30,45 * * * * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs quarter_hourly
- * /opt/mailman/mailman-bundler/bin/mailman-web-django-admin runjobs minutely
Send periodic digests.
# I like 03:30 so they go overnight, but since we're 'global' and on UTC, # maybe 07:30 is good. 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send
I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as well?
I don't recall exactly where I saw that that was needed, but you can find it (except for the periodic digests bit) at <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>. Note that that suggests a system crontab with the web server user rather than the 'mailman' user's crontab.
-- thanks, Abhilash Raj
On 08/09/2017 02:35 PM, Abhilash Raj wrote:
Hi,
On Wed, 9 Aug 2017 13:42:20 -0700 Mark Sapiro <mark@msapiro.net> wrote:
# Send periodic digests. # I like 03:30 so they go overnight, but since we're 'global' and on UTC, # maybe 07:30 is good. 30 7 * * * /opt/mailman/mailman-bundler/bin/mailman digests --send
I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as well?
It's only that one and whether it's needed or not depends on list configuration. The list has attributes digest_send_periodic and digest_size_threshold. When a post is received it is added to the list's digest mbox, and if that causes the size of the mbox to reach digest_size_threshold K bytes, a digest is sent. Additionally, if digest_send_periodic is true, a digest is sent periodically whether or not it has reached digest_size_threshold.
However, the sending of periodic digests depends on cron running something periodically to actually trigger the sending.
Note: I've just looked at the code and there seems to be an issue with using 'mailman digests --send' to send the periodic digests. It appears that if a list's digest mbox has any messages, 'mailman digests --send' will send a digest even if digest_send_periodic is false. I've just reported <https://gitlab.com/mailman/mailman/issues/384> for this issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, 9 Aug 2017 15:45:48 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 08/09/2017 02:35 PM, Abhilash Raj wrote:
Hi,
On Wed, 9 Aug 2017 13:42:20 -0700 Mark Sapiro <mark@msapiro.net> wrote:
[...]I wasn't aware that Core needed cron jobs too, is that true for 3.1 release as well?
It's only that one and whether it's needed or not depends on list configuration. The list has attributes digest_send_periodic and digest_size_threshold. When a post is received it is added to the list's digest mbox, and if that causes the size of the mbox to reach digest_size_threshold K bytes, a digest is sent. Additionally, if digest_send_periodic is true, a digest is sent periodically whether or not it has reached digest_size_threshold.
However, the sending of periodic digests depends on cron running something periodically to actually trigger the sending.
Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks?
I am thinking mostly about the container images because the mailman-core container runs nothing else other than Core. I'd have to another cron for this which isn't a lot of overhead but since mailman-web container already has periodic tasks, it would be great if I could trigger it from there.
Note: I've just looked at the code and there seems to be an issue with using 'mailman digests --send' to send the periodic digests. It appears that if a list's digest mbox has any messages, 'mailman digests --send' will send a digest even if digest_send_periodic is false. I've just reported <https://gitlab.com/mailman/mailman/issues/384> for this issue.
Also, it seems that Postorius doesn't have any way to set
digest_send_periodic and only has a setting to set the max_threshold for the
digest. I opened another issue
(https://gitlab.com/mailman/postorius/issues/211) to add this feature.
-- thanks, Abhilash Raj
On Aug 9, 2017, at 16:00, Abhilash Raj <maxking@asynchronous.in> wrote:
Can this be done using the REST API? If not, maybe we should do that so that Postorius can take of the periodic tasks?
It certainly could. Right now you can do effectively mailman digests —send —bump through the REST API, so if you wanted to leave the periodicity to Postorius, that would work right now. If we added the —periodic option to the CLI, then we should also add it to the REST API. The one thing is that —periodic and —send should be mutually exclusive for both.
I’ve updated the issue with those comments.
Cheers, -Barry
On Aug 9, 2017, at 15:45, Mark Sapiro <mark@msapiro.net> wrote:
However, the sending of periodic digests depends on cron running something periodically to actually trigger the sending.
Right. There will eventually be additional recurring tasks for Core too though, such as processing the bounce database for disables and unsubs, pulling messages from NNTP, and possibly others as time goes on.
I’ve always thought about handling these as commands that cron would run, much as in Mailman 2, but it would also be possible to implement a runner, or runners, to do those jobs. I can see advantages and disadvantages with either approach.
Note: I've just looked at the code and there seems to be an issue with using 'mailman digests --send' to send the periodic digests. It appears that if a list's digest mbox has any messages, 'mailman digests --send' will send a digest even if digest_send_periodic is false. I've just reported <https://gitlab.com/mailman/mailman/issues/384> for this issue.
Yep, thanks for the bug report. mailman digests —periodic seems like the right approach.
Cheers, -Barry
I don't recall exactly where I saw that that was needed, but you can find it (except for the periodic digests bit) at <http://docs.list.org/en/latest/config-web.html#scheduled-tasks-required>;.
Thank you, I missed that.
participants (5)
-
Abhilash Raj -
Barry Warsaw -
cyp＠trojina.si -
Cyprian Laskowski
-
Mark Sapiro