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?)
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.
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