I am still have the authentication problems with qrunner and, since nobody seems to know what the problem is or how to fix it, thought that I would ask what exactly does qrunner do? I can tell that the cron.d/mailman script is calling /usr/lib/mailman/cron/qrunner, but what does this script do?
Since I only have a rudimentary programming knowledge, I would greatly appreciate your help on this.
Robert Lydiate icon@accesscomm.ca
At 00:26 28/11/2002, fish wrote:
I am still have the authentication problems with qrunner and, since nobody seems to know what the problem is or how to fix it, thought that I would ask what exactly does qrunner do? I can tell that the cron.d/mailman script is calling /usr/lib/mailman/cron/qrunner, but what does this script do?
MM processes incoming mail in several stages.
The Python scripts in $prefix//scripts are called by your Mail Transfer program to accept incoming posts. The scripts take the incoming mail and enqueue it (on MM 2.0.13 in the qfiles directory). The qrunner from $prefix/cron, as is implied by its name, is executed frequently and takes mail from the input queue, processes it, and sends out the resulting mail to the list members etc.
If the qrunner is not working right then Mailman will not do its job.
Sorry I cannot help with your base problem but I use neither debian nor exim and you need help not guesses.
Since I only have a rudimentary programming knowledge, I would greatly appreciate your help on this.
Robert Lydiate icon@accesscomm.ca
Thanks Richard,
I understood, from the name, that qrunner processed queue's, and that if it was having a problem that mailman probably wouldn't work right. My question now is, though, if my logs are saying that qrunner is having authentication problems, then should my list mail be working. Right now, I am hosting 5 lists, all of which are working and mail is getting to them. This means, to me, that qrunner is running properly. I am assuming that it is the /etc/cron.d/mailman script that is calling qrunner every minute or so, which is where the authentication problem is.
So, if that script is running, amd mail is getting delivered, what is the authentication problem, and how do I stop it so that I can have my rapidly shrinking hard drive space back that is being eaten up by these large log files.
Robert Lydiate icon@accesscomm.ca
-----Original Message----- From: mailman-users-bounces+fish=livingsky.net@python.org [mailto:mailman-users-bounces+fish=livingsky.net@python.org]On Behalf Of Richard Barrett Sent: Thursday, November 28, 2002 6:09 AM To: fish; mailman-users@python.org Subject: Re: [Mailman-Users] qrunner problems
I am still have the authentication problems with qrunner and, since nobody seems to know what the problem is or how to fix it, thought that I would ask what exactly does qrunner do? I can tell that the cron.d/mailman
At 00:26 28/11/2002, fish wrote: script is
calling /usr/lib/mailman/cron/qrunner, but what does this script do?
MM processes incoming mail in several stages.
The Python scripts in $prefix//scripts are called by your Mail Transfer program to accept incoming posts. The scripts take the incoming mail and enqueue it (on MM 2.0.13 in the qfiles directory). The qrunner from $prefix/cron, as is implied by its name, is executed frequently and takes mail from the input queue, processes it, and sends out the resulting mail to the list members etc.
If the qrunner is not working right then Mailman will not do its job.
Sorry I cannot help with your base problem but I use neither debian nor exim and you need help not guesses.
Since I only have a rudimentary programming knowledge, I would greatly appreciate your help on this.
Robert Lydiate icon@accesscomm.ca
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: fish@livingsky.net Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/fish%40livingsky.net
At 13:16 28/11/2002, fish wrote:
Thanks Richard,
I understood, from the name, that qrunner processed queue's, and that if it was having a problem that mailman probably wouldn't work right. My question now is, though, if my logs are saying that qrunner is having authentication problems, then should my list mail be working. Right now, I am hosting 5 lists, all of which are working and mail is getting to them. This means, to me, that qrunner is running properly. I am assuming that it is the /etc/cron.d/mailman script that is calling qrunner every minute or so, which is where the authentication problem is.
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.
So, if that script is running, amd mail is getting delivered, what is the authentication problem, and how do I stop it so that I can have my rapidly shrinking hard drive space back that is being eaten up by these large log files.
Robert Lydiate icon@accesscomm.ca
-----Original Message----- From: mailman-users-bounces+fish=livingsky.net@python.org [mailto:mailman-users-bounces+fish=livingsky.net@python.org]On Behalf Of Richard Barrett Sent: Thursday, November 28, 2002 6:09 AM To: fish; mailman-users@python.org Subject: Re: [Mailman-Users] qrunner problems
I am still have the authentication problems with qrunner and, since nobody seems to know what the problem is or how to fix it, thought that I would ask what exactly does qrunner do? I can tell that the cron.d/mailman
At 00:26 28/11/2002, fish wrote: script is
calling /usr/lib/mailman/cron/qrunner, but what does this script do?
MM processes incoming mail in several stages.
The Python scripts in $prefix//scripts are called by your Mail Transfer program to accept incoming posts. The scripts take the incoming mail and enqueue it (on MM 2.0.13 in the qfiles directory). The qrunner from $prefix/cron, as is implied by its name, is executed frequently and takes mail from the input queue, processes it, and sends out the resulting mail to the list members etc.
If the qrunner is not working right then Mailman will not do its job.
Sorry I cannot help with your base problem but I use neither debian nor exim and you need help not guesses.
Since I only have a rudimentary programming knowledge, I would greatly appreciate your help on this.
Robert Lydiate icon@accesscomm.ca
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@accesscomm.ca
A search threw up the following link which seems to be relevant
http://mail.python.org/pipermail/mailman-users/2001-November/015556.html
Best of luck
At 19:06 28/11/2002, fish wrote:
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@accesscomm.ca
At 19:06 28/11/2002, fish wrote:
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?
I wouldn't do that if I were you. All it will do is increase the latency before incoming mail goes out. Fix the basic problem; see my earlier post.
Robert Lydiate icon@accesscomm.ca
participants (2)
-
fish -
Richard Barrett