Hmm… something is definitely not right.
/opt/mailman/web/logs/uwsgi-cron.log has not been updated since Aug 11, which is when I installed the container images 0.1.1. However, /opt/mailman/web/logs/uwsg-error.log is being updated every minute with entries similar to this:
Sun Aug 20 13:40:00 2017 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 123) [uwsgi-cron] command “./manage.py runjobs minutely" running with pid 123 exited after 2 second(s)
In addition (and possibly related) to this, HyperKitty is “losing” messages; threads with multiple messages will suddenly lose all but the top message. A new subscriber will be told that there are unread messages, but none but the top message will appear. Actually, this isn’t entirely true: all of the messages in *one* of the threads have suddenly reappeared for no apparent reason…
On 2017.08.19, at 00:04 , Abhilash Raj <maxking@asynchronous.in> wrote:
On Wed, 16 Aug 2017 09:18:59 -0700 Cameron Smith <ccsmith@cetsi.com> wrote:
Mailman 3, container images 0.1.1
HyperKitty 1.1.1 is showing incorrect numbers for the number of participants and the number of discussions.
(All messages referred to below were submitted in August.)
In one list, I have two threads. In one thread, I have three messages, each from a different email address, all submitted via email (as opposed to replying from within HyperKitty). The month page (clicking on “August”) of that list however, shows that thread as having one participant and no messages. Opening the list shows the same stats: “1 participants”, “0 comments”; all three messages are displayed.
The other thread in the same list also shows one participant and no messages; it has two messages in it, one submitted via email, the other submitted via HyperKitty by a different subscriber. Opening the list shows both messages.
The front page of that list shows zero participants and two discussions.
A second list also has two threads with three email-submitted messages from different addresses. The monthly stats show one thread as having one participant and one message, the other as having one participant and zero messages. The front page shows one participant and one discussion.
Statistics are generated by routine tasks which are usually meant to be run as cron jobs. In the docker container, uwsgi is responsible to run them.
If you are using the standard directory structure mentioned in the documentation for Mailman 3, you will find the logs for cron at /opt/mailman/web/logs/uwsg-cron.log
It should tell if you if the log daemons are running as they are supposed to.
I am not sure which job exactly is supposed to generate stats, but if you see the logs running with
manage.py runjobs minutelyevery minute, then probably the problem lies somewhere else.Cameron Smith
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
Cameron Smith