[Mailman-Users] problem with mailman and qmail-ldap
- mailman 2.1.5-9 - apt-get - Linux Debian testing. - MTA : qmail with ldap. My problem is : I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. The problems had began when i updated the libc6 four days ago. The version the libc6 is 2.3.5-6. What is my problem ? Thanks you Gabriel -- 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] problem with mailman and qmail-ldap
gabo wrote: I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. This seems to indicate that the mail reaches Mailman and is queued, but there is some problem with one or more of the qrunners. Look at the Mailman logs 'error' and 'qrunner' to see if qrunners are dying and what might be causing it. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] problem with mailman and qmail-ldap
Mark Sapiro wrote: gabo wrote: I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. This seems to indicate that the mail reaches Mailman and is queued, but there is some problem with one or more of the qrunners. Look at the Mailman logs 'error' and 'qrunner' to see if qrunners are dying and what might be causing it. nothing abount this in the error and qrunner log, only shuting and smtp cannot connection, error messages. Nov 01 12:03:20 2005 (21469) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 223, in _dispose res = Results(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File /usr/lib/python2.3/email/Header.py, line 144, in make_header h.append(s, charset) File /usr/lib/python2.3/email/Header.py, line 272, in append ustr = unicode(s, incodec, errors) UnicodeDecodeError: 'ascii' codec can't decode byte 0xda in position 14: ordinal not in range(128) Nov 01 12:03:20 2005 (21469) SHUNTING: 1130857400.1742439+75ef1b3c5e1079f2ee995e954fd2a65f7e650a65 Nov 01 17:24:53 2005 (21472) Cannot connect to SMTP server server.xxx.xxx.xxx on port 25 qrunner log: Nov 02 06:25:05 2005 (11143) RetryRunner qrunner caught SIGHUP. Reopening logs.Nov 02 15:02:25 2005 (11136) ArchRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:25 2005 (11136) ArchRunner qrunner exiting. Nov 02 15:02:25 2005 (11139) IncomingRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:25 2005 (11139) IncomingRunner qrunner exiting. Nov 02 15:02:25 2005 (11140) NewsRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:25 2005 (11140) NewsRunner qrunner exiting. Nov 02 15:02:26 2005 (11141) OutgoingRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11141) OutgoingRunner qrunner exiting. Nov 02 15:02:26 2005 (11142) VirginRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11142) VirginRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master watcher caught SIGTERM. Exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11136, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11139, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11140, sig: None, sts: 15, class: NewsRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11141, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Nov 02 15:02:26 2005 (11137) BounceRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11138) CommandRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11138) CommandRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11138, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11142, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Nov 02 15:02:26 2005 (11143) RetryRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:26 2005 (11143) RetryRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11143, sig: None, sts: 15, class: RetryRunner, slice: 1/1) Nov 02 15:02:26 2005 (11137) BounceRunner qrunner exiting. Nov 02 15:02:26 2005 (11135) Master qrunner detected subprocess exit (pid: 11137, sig: None, sts: 15, class: BounceRunner, slice: 1/1) Nov 02 15:02:26 2005 (26683) ArchRunner qrunner started. Nov 02 15:02:27 2005 (26684) BounceRunner qrunner started. Nov 02 15:02:27 2005 (26685) CommandRunner qrunner started. Nov 02 15:02:27 2005 (26686) IncomingRunner qrunner started. Nov 02 15:02:27 2005 (26687) NewsRunner qrunner started. Nov 02 15:02:27 2005 (26688) OutgoingRunner qrunner started. Nov 02 15:02:27 2005 (26689) VirginRunner qrunner started. Nov 02 15:02:27 2005 (26690) RetryRunner qrunner started. Nov 02 15:02:29 2005 (26684) BounceRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:29 2005 (26684) BounceRunner qrunner exiting. Nov 02 15:02:29 2005 (26685) CommandRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:29 2005 (26685) CommandRunner qrunner exiting. Nov 02 15:02:29 2005 (26686) IncomingRunner qrunner caught SIGTERM. Stopping. Nov 02 15:02:29 2005 (26686) IncomingRunner qrunner exiting. Nov 02 15:02:29 2005
Re: [Mailman-Users] problem with mailman and qmail-ldap
gabo wrote: Mark Sapiro wrote: gabo wrote: I have run mailman with an qmail-ldap server.Once or twice per day, mailman not delivery mail. The mails are received in qmail-ldap server and it calls /var/lib/mailman/mail/mailman post listname. I checked it, qmail receive the mail, however the mailman not send. Then i restart mailman and all mails received are sending. This seems to indicate that the mail reaches Mailman and is queued, but there is some problem with one or more of the qrunners. Look at the Mailman logs 'error' and 'qrunner' to see if qrunners are dying and what might be causing it. nothing abount this in the error and qrunner log, only shuting and smtp cannot connection, error messages. log messages snipped The next time this occurs, look in qfiles/* and see where the undelivered messages are. Don't worry about shunted messages in qfiles/shunt, or the archive/, bad/, bounces/, commands/, news/ or virgin/ queues either. Undelivered messages that will be delivered automatically following a mailmanctl restart will almost certainly be in one of in/, out/ or retry/. Once you've located the messages, check the state of the corresponding runner. A command like $ ps -fwu mailman or whatever the equivalent is on your system normally gives something like: UIDPID PPID C STIME TTY TIME CMD mailman 1564 1 0 Jul02 ?00:00:00 /usr/bin/python /var/mailman/bin/mailmanctl -s -q start mailman 1565 1564 0 Jul02 ?00:33:00 /usr/bin/python /var/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 1566 1564 0 Jul02 ?00:00:53 /usr/bin/python /var/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 1567 1564 0 Jul02 ?00:00:23 /usr/bin/python /var/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 1568 1564 0 Jul02 ?00:03:31 /usr/bin/python /var/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 1569 1564 0 Jul02 ?00:00:09 /usr/bin/python /var/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 1570 1564 0 Jul02 ?00:08:01 /usr/bin/python /var/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 1571 1564 0 Jul02 ?00:01:32 /usr/bin/python /var/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 1572 1564 0 Jul02 ?00:00:00 /usr/bin/python /var/mailman/bin/qrunner --runner=RetryRunner:0:1 -s If the specific qrunner isn't there, that's the problem. Maybe some system log can help determine why it died. If it is there, maybe you have tools to help figure why it isn't doing what it should be. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
