[Mailman-Users] qrunner problems

[fish]

Richard wrote:
> If I understand you correctly, you say cron is executing the
> qrunner, which
> is sending out mail to your lists subscriber, but you are getting 'error'
> messages logged each time.
>
> You might get more help if you  repost to mailman-users list giving an
> example of exactly what is being logged into which log file.
>
> >

Ok.

fish:/var/log# tail syslog
Nov 28 13:04:01 livingsky CRON[3946]: Authentication service cannot retrieve
authentication info.
Nov 28 13:04:01 livingsky /USR/SBIN/CRON[3950]: (list) CMD
(/usr/bin/python -S /usr/lib/mailman/cron/qrunner)
Nov 28 13:05:01 livingsky /USR/SBIN/CRON[3964]: (list) CMD (   [ -x
/usr/bin/python -a -f /usr/lib/mailman/cron/qrunner ] && /usr/bin/python
/usr/lib/mailman/cron/qrunner)
Nov 28 13:05:01 livingsky CRON[3961]: Authentication service cannot retrieve
authentication info.
Nov 28 13:05:01 livingsky CRON[3962]: Authentication service cannot retrieve
authentication info.
Nov 28 13:05:01 livingsky /USR/SBIN/CRON[3968]: (list) CMD
(/usr/bin/python -S /usr/lib/mailman/cron/gate_news)
Nov 28 13:05:01 livingsky /USR/SBIN/CRON[3966]: (list) CMD
(/usr/bin/python -S /usr/lib/mailman/cron/qrunner)
Nov 28 13:06:01 livingsky /USR/SBIN/CRON[3973]: (list) CMD (   [ -x
/usr/bin/python -a -f /usr/lib/mailman/cron/qrunner ] && /usr/bin/python
/usr/lib/mailman/cron/qrunner)
Nov 28 13:06:01 livingsky CRON[3971]: Authentication service cannot retrieve
authentication info.
Nov 28 13:06:01 livingsky /USR/SBIN/CRON[3975]: (list) CMD
(/usr/bin/python -S /usr/lib/mailman/cron/qrunner)

fish:/var/log#less auth.log (edited)
Nov 28 13:04:01 livingsky PAM_unix[3945]: (cron) session opened for user
list by (uid=0)
Nov 28 13:04:01 livingsky PAM_unix[3947]: (cron) session opened for user
list by (uid=0)
Nov 28 13:04:04 livingsky PAM_unix[3945]: (cron) session closed for user
list
Nov 28 13:04:04 livingsky PAM_unix[3947]: (cron) session closed for user
list
Nov 28 13:05:01 livingsky PAM_unix[3960]: (cron) session opened for user
list by (uid=0)
Nov 28 13:05:01 livingsky PAM_unix[3963]: (cron) session opened for user
list by (uid=0)
Nov 28 13:05:01 livingsky PAM_unix[3967]: (cron) session opened for user
list by (uid=0)
Nov 28 13:05:05 livingsky PAM_unix[3960]: (cron) session closed for user
list
Nov 28 13:05:05 livingsky PAM_unix[3963]: (cron) session closed for user
list
Nov 28 13:05:05 livingsky PAM_unix[3967]: (cron) session closed for user
list
Nov 28 13:06:01 livingsky PAM_unix[3970]: (cron) session opened for user
list by (uid=0)
Nov 28 13:06:01 livingsky PAM_unix[3972]: (cron) session opened for user
list by (uid=0)
Nov 28 13:06:03 livingsky PAM_unix[3970]: (cron) session closed for user
list

Since the mailman cron is the one being started just before the
authentication message (as happens in all cases of the authentication
error), I am presuming that they are related.

I did double check to make sure that mail to my mailing lists was being
delivered, and have received replies to several messages sent out through
the lists, and the logs show that mail is being delivered to the various
addresses on the lists.

Another question that I have is how do I change /etc/cron.d/mailman to run
every 15 minutes (or more, it isn't a busy server) instead of every minute?


Robert Lydiate
icon at accesscomm.ca