The issue I'm having is that my mailman server is no longer sending email out. There was an issue with it earlier in the day where VCS shut it down because of the disk set monitor script was not completing.
I'm running: mailman-2.1.9-4.el5
This was working up till today. I did some googling and there are qrunner processes running: [root@request1 mailman]# ps -ef | grep qrunner mailman 13235 13231 0 16:26 ? 00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 13236 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13237 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13238 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13239 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13240 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13241 13231 0 16:26 ? 00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13242 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
check_perms says everything is ok
crond is running
mailmanctl is running
I'm running postfix 2.3.3
Any help is much appreciated!
Troy
Troy Campbell wrote:
The issue I'm having is that my mailman server is no longer sending email out. There was an issue with it earlier in the day where VCS shut it down because of the disk set monitor script was not completing.
I'm running: mailman-2.1.9-4.el5
This was working up till today. I did some googling and there are qrunner processes running: [root@request1 mailman]# ps -ef | grep qrunner mailman 13235 13231 0 16:26 ? 00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 13236 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13237 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13238 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13239 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13240 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13241 13231 0 16:26 ? 00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13242 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
Good.
check_perms says everything is ok
Good
crond is running
Irrelevant for non-digest mail delivery with Mailman 2.1.x
mailmanctl is running
Good.
I'm running postfix 2.3.3
Any help is much appreciated!
See the FAQ at <http://wiki.list.org/x/A4E9>.
What's in Mailman's queues (/var/spool/mailman/* in RHEL)?
What's in Mailman's logs, particularly smtp, smtp-failure and error?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Things magically started working after about an hour and a half so it must have been something else this time. Anyway, much appreciate your timely reponse!
Regards, Troy
-----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: Thursday, July 01, 2010 6:09 PM To: Troy Campbell; mailman-users@python.org Subject: Re: [Mailman-Users] Problem sending emails out
Troy Campbell wrote:
The issue I'm having is that my mailman server is no longer sending email out. There was an issue with it earlier in the day where VCS shut it down because of the disk set monitor script was not completing.
I'm running: mailman-2.1.9-4.el5
This was working up till today. I did some googling and there are qrunner processes running: [root@request1 mailman]# ps -ef | grep qrunner mailman 13235 13231 0 16:26 ? 00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 13236 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13237 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13238 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13239 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13240 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13241 13231 0 16:26 ? 00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13242 13231 0 16:26 ? 00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
Good.
check_perms says everything is ok
Good
crond is running
Irrelevant for non-digest mail delivery with Mailman 2.1.x
mailmanctl is running
Good.
I'm running postfix 2.3.3
Any help is much appreciated!
See the FAQ at <http://wiki.list.org/x/A4E9>.
What's in Mailman's queues (/var/spool/mailman/* in RHEL)?
What's in Mailman's logs, particularly smtp, smtp-failure and error?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Troy Campbell