On Thu, Aug 24, 2017, at 10:09 AM, Abhilash Raj wrote:
On Thu, Aug 24, 2017, at 09:42 AM, Cameron Smith wrote:
Abhilash,
I think the location of the message, in the error log, is correct: in the uwsci-cron.log, the entries show that the “minutely” jobs run for 32-33 seconds, whereas the entries in the error log show the jobs as running for only 2 seconds, suggesting an error. (As an aside, what is “minutely” doing that takes 32-33 seconds?)
Just as an FYI, my test server running the container images also has minutely jobs taking 2 seconds and older entries in uwsgi-cron.log being 32-33 seconds.
Note that this change in time could be something that was changed in Hyperkitty 1.1.1, I haven't yet read the changelog to infer that part yet. Since this problem started happening once you upgraded to 0.1.1 images, which use HK 1.1.1.
Yeah, if there are no entries going to uwsgi-cron at all, it looks like there is some configuration problem in log routing. T this1 is the uwsgi configuration that is supposed to route the cron related logs to uwsgi-cron.log.
Also, I am not exactly sure of what jobs run "minutely", 2 is the place where all of them are defined if you want to dive in yourself. Jobs (class) have a method "when" which defines when they run like "hourly", "daily" etc.
How best can I diagnose the problem? If need be, I can simply tear down the whole system, including deleting /opt/mailman on the host, start again and see if the problem persists. I think it would, however, be more helpful if we could figure out what has gone wrong.
I am not sure what exactly is the problem, opening an issue with Hyperkitty3 might be worth it to see if the devs have ideas about it. If this is a problem with Hyperkitty, I'd assume it would also be visible on the archives on this list, which runs on Mailman 3 (and not using containers AFAIK).
On 2017.08.20, at 14:34 , Abhilash Raj <maxking@asynchronous.in> wrote:
On Sun, 20 Aug 2017 08:38:53 -0700 Cameron Smith <ccsmith@cetsi.com> wrote:
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)
This seems like a bug in the uwsgi configuration, it should actually go to uwsgi-cron.log. I have opened a new bug1 to track this problem.
Cameron Smith
-- Abhilash Raj maxking@asynchronous.in
Mailman-users mailing list mailman-users@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- Abhilash Raj maxking@asynchronous.in