On Wed, Mar 1, 2023 at 6:13 PM Mark Sapiro <mark@msapiro.net> wrote:
On 2/28/23 21:33, Odhiambo Washington wrote:
Now that I have the error message - mail was generated at 0600hrs - what should I grep for in mailmanweb.log to ascertain when the cron job
started?
You could look in /etc/crontab to see what time the cron.monthly jobs are run or you could look in syslog for 'cron\.monthly'.
In FreeBSD we have the /var/log/cron. Mar 1 00:00:00 gw /usr/sbin/cron[66206]: (mailman) CMD (/opt/mailman/mm/bin/django-admin runjobs monthly)
So the job was started at 00:00, and the email was generated at 06:00: 2023-03-01 06:00:52 1pXCi4-000N2h-2D <= mailman@gw.kictanet.or.ke U=mailman P=local S=1466 T="Cron <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly" from <mailman@gw.kictanet.or.ke> for mailman
That is 6hrs and the lock was still there. Given that my search engine is whoosh and my archive is heading to 3GB, I should probably try setting the value to 10hrs for a start?
PS: Is there any documentation (for laymen) on how to set up an alternative search engine for MM3?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)