I'm running Mailman 2.1.15 on a Ubuntu server, feeding into Courier MTA, running Python 2.7.3. I track security updates and install them promptly when they're issued by Ubuntu. Yesterday I updated the Linux kernel from 3.2.0-58-generic (x86_64) to 3.2.0-59-generic and Mailman quit working. List posts made it through to the archives, and were apparently queued within Mailman, but wouldn't go out. The mail server was working OK for non-list email. Today I backed out the kernel update and posts to lists sent yesterday and today are going out without problems.
I can find nothing in the Mailman logs, or in the mail server logs, indicating a problem.
This is the first time I've ever had a problem with a server kernel update breaking something related to mail. Has anyone else seen this problem? Does anyone have any insight into how to address it?
-- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com |
On 02/20/2014 10:07 AM, Lindsay Haisley wrote:
I'm running Mailman 2.1.15 on a Ubuntu server, feeding into Courier MTA, running Python 2.7.3. I track security updates and install them promptly when they're issued by Ubuntu. Yesterday I updated the Linux kernel from 3.2.0-58-generic (x86_64) to 3.2.0-59-generic and Mailman quit working. List posts made it through to the archives, and were apparently queued within Mailman, but wouldn't go out. The mail server was working OK for non-list email. Today I backed out the kernel update and posts to lists sent yesterday and today are going out without problems.
What's in Mailman's 'post' and 'smtp' logs for these messages. Are they timestamped before or after you backed out the update. If before, they were queued in the MTA. If after, they were in Mailman's 'out' queue.
If the latter, what's in Mailman's 'qrunner' log related to OutgoingRunner.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Feb 20, 2014, at 12:07 PM, Lindsay Haisley wrote:
I'm running Mailman 2.1.15 on a Ubuntu server, feeding into Courier MTA, running Python 2.7.3. I track security updates and install them promptly when they're issued by Ubuntu. Yesterday I updated the Linux kernel from 3.2.0-58-generic (x86_64) to 3.2.0-59-generic and Mailman quit working. List posts made it through to the archives, and were apparently queued within Mailman, but wouldn't go out. The mail server was working OK for non-list email. Today I backed out the kernel update and posts to lists sent yesterday and today are going out without problems.
I'm really quite surprised about this. From the kernel version numbers, I'm guessing you're running Ubuntu 12.04 LTS? I have my personal Mailman server running on that OS, and just performed a kernel update. I'm about to reboot it into the new kernel, so I'll send a test message out and see if it works. Very odd that a kernel update alone would cause the problem. Can you send mail normally (i.e. outside of Mailman) and connect to your port 25? I guess the one difference between our setups is that I use Postfix.
-Barry
On Thu, 2014-02-20 at 14:39 -0500, Barry Warsaw wrote:
I'm really quite surprised about this. From the kernel version numbers, I'm guessing you're running Ubuntu 12.04 LTS?
You are correct about the Ubuntu release on the box.
My next step would be to reinstall the new kernel version and test this issue in a controlled way, but before I do so I'd like to have some diagnostic code or configs in place which will track and log the intimate details of the relationship between Mailman and the MTA. Any suggestions will be appreciated!
I'm also going to post to the very active courier-users list and see if anyone else is having this or similar problems.
-- Lindsay Haisley | "Everything works if you let it" FMP Computer Services | 512-259-1190 | --- The Roadie http://www.fmp.com |
participants (3)
-
Barry Warsaw -
Lindsay Haisley -
Mark Sapiro