Heya, folks.
I've got a mailman install which had been working happily, and then yesterday, began silently queuing messages without sending them on.
Sendmail logs show that the messages get handed off to mailman correctly, and now there are both .db and .msg files sitting in the ~mailman/qfiles directory, starting yesterday. Nothing in the logs directory has been updated since March 30, and since I'm the only active admin on this installation, it seems unlikely that something there has changed.
Anyone got any pointers for how to debug this sort of thing? I'd love to resume traffic to the affected list...
Thanks
Adam
-- "What do you say to a man who's killed a lion with <adam@baz.org> his bare hands and is sleeping with your wife?" <adam hirsch> - Derek Mason, asked about his wife's affair with a Masai warrior
Adam Hirsch (adam@baz.org) wrote:
I've got a mailman install which had been working happily, and then yesterday, began silently queuing messages without sending them on.
Further testing shows that the mailman installation can send out mail (I had it send me my password for the list in question), but list mail is simply sitting in the queue, without being sent.
I'm even more baffled, now. It's clearly not sendmail, and it's clearly not the entire mailman installation. Anyone know of something that could make all standard list mail come to a screeching halt while leaving administrative mail alone?
Adam
-- Writing a novel is like driving a car at night. You can only see as far as your headlights, but you can make the entire journey that way. <adam hirsch> <adam@baz.org> - E.L. Doctorow
Did you run #crontab <srcdir>/cron/crontab.in?
Sounds to me like qrunner isnt running out of cron.
--Neil
On 03 Apr 2001 12:50:57 -0400, Adam Hirsch wrote:
Adam Hirsch (adam@baz.org) wrote:
I've got a mailman install which had been working happily, and then yesterday, began silently queuing messages without sending them on.
Further testing shows that the mailman installation can send out mail (I had it send me my password for the list in question), but list mail is simply sitting in the queue, without being sent.
I'm even more baffled, now. It's clearly not sendmail, and it's clearly not the entire mailman installation. Anyone know of something that could make all standard list mail come to a screeching halt while leaving administrative mail alone?
Adam
-- Writing a novel is like driving a car at night. You can only see as far as your headlights, but you can make the entire journey that way. <adam hirsch> <adam@baz.org> - E.L. Doctorow
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users
Neil Cooler (ncooler@nandomedia.com) wrote:
Did you run #crontab <srcdir>/cron/crontab.in?
Sounds to me like qrunner isnt running out of cron.
Bingo. One of the machine admins upgraded vixie-cron, and concurrent with that, mailman's cron jobs stopped running. Now, to figure out why.
Adam
-- Microeconomics concerns things that economists are specifically wrong about, while macroeconomics concerns things economists are wrong about generally. Or, to be more technical, microeconomics is about money you don't have, and macroeconomics is about money the government is out of. -P.J. O'Rourke <adam@baz.org> \\ adam hirsch // http://web.baz.org/~adam/
participants (2)
-
Adam Hirsch -
Neil Cooler