Update: I removed all the 120 or so files from the qfiles directory, with the exception of the original newsletter posting to the list, and the newsletter started going out almost immediately to the 1880 subscribers. So what was it about those files that caused Mailman to choke? I've saved them for later examination, but it was necessary to use the steam-shovel approach since the two-day delay in sending out his newsletter was causing the client to go into cardiac arrest. Any thoughts?
.\\ichelle > One thing I've had to do before is to ps jax |grep qrunner, kill any >running qrunner processes, and then cd to the locks dir, and delete any >remaing locks, so a clean instance of qrunner can start next time the cron >is processed. Probably not the best thing to do, but I have had to do it >before. > > -Richard Idalski Okay, I tried that but it didn't seem to help, so I rebooted the system. Still no joy. From the qrunner log: Dec 26 15:11:02 2001 (855) Could not acquire qrunner lock Dec 26 15:12:02 2001 (879) Could not acquire qrunner lock Dec 26 15:13:02 2001 (886) Could not acquire qrunner lock Dec 26 15:14:02 2001 (896) Could not acquire qrunner lock Dec 26 15:14:24 2001 (898) Could not acquire qrunner lock Dec 26 15:15:03 2001 (914) Could not acquire qrunner lock Dec 26 15:16:01 2001 (929) Could not acquire qrunner lock Dec 26 15:17:02 2001 (933) Could not acquire qrunner lock And new locks have been created: /usr/local/mailman/logs# ls -al ../locks/ total 4 drwxrwsr-x 2 mailman mailman 512 Dec 26 15:28 . drwxrwsr-x 18 mailman mailman 512 Oct 31 14:55 .. -rw-rw-r-- 2 mailman mailman 69 Dec 27 00:57 qrunner.lock -rw-rw-r-- 2 mailman mailman 69 Dec 27 00:57 qrunner.lock.straylight.primelogic.com.71237 The strange thing is, Mailman's three lists were working perfectly until the 24th. I ran check_perms to see if permissions had gotten changed somehow, but they're okay. But there's something I'm not comprehending here. A working system shouldn't just suddenly stop working. .\\ichelle >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]On Behalf Of Michelle Brownsworth >Sent: Wednesday, December 26, 2001 4:31 PM >To: [EMAIL PROTECTED] >Cc: Richard Idalski >Subject: RE: [Mailman-Users] Mailman not sending out mail > > >>Is anything showing up in mailman's error log? $prefix/mailman/logs/error. >>There could be something there to shed some light on this. As far as, >>getting rid of the extra postings, if they're still floating around the >>qfiles dir, just delete the corrosponding .msg, and .db files for the extra >>posting... be sure to leave at least one set however so it does go out. >> >> >> -Richard Idalski > > >Nope, not a thing in the error log; that was the first place I >looked. Thanks for the tip about the qfiles dir, though. > >.\\ichelle > > >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED]]On Behalf Of Michelle Brownsworth >>Sent: Wednesday, December 26, 2001 4:02 PM >>To: [EMAIL PROTECTED] >>Subject: [Mailman-Users] Mailman not sending out mail >> >> >>Gentle friends, >> >>I'm having a problem with Mailman 2.06, running on FreeBSD >>4.4-RELEASE. It has been working perfectly up until now, serving >>three lists. All of a sudden it won't send out mail posted to a >>list, although the wrapper receives it. Here's the most recent post >>made by the moderator of the largest (1500) list: >> >>Dec 25 20:41:05 straylight sendmail[48896]: fBQ4f4U48896: >>from=<[EMAIL PROTECTED] >>>, size=66192, class=0, nrcpts=1, >>>msgid=<[EMAIL PROTECTED]>, proto=ES >>MTP, daemon=MTA, relay=imo-d05.mx.aol.com [205.188.157.37] >>Dec 25 20:41:06 straylight sendmail[48897]: fBQ4f4U48896: >>to="|/usr/local/mailma >>n/mail/wrapper post fishlink", >>ctladdr=<[EMAIL PROTECTED]> (1/0 > >), delay=00:00:02, xdelay=00:00:01, mailer=prog, pri=95692, >>dsn=2.0.0, stat=Sent >> >>The cron jobs seem to be running every minute: >> >>68546 ?? I 0:00.00 cron: running job (cron) >>68550 ?? Is 0:00.01 /bin/sh -c /usr/local/bin/python -S >>/usr/local/mailman/cron/qrunner >>68554 ?? I 0:00.67 /usr/local/bin/python -S >>/usr/local/mailman/cron/qrunner >> >>But I'm getting this message in /usr/local/mailman/logs: >> >>Dec 25 20:48:01 2001 (48945) Could not acquire qrunner lock >>Dec 25 20:49:02 2001 (48948) Could not acquire qrunner lock > >Dec 25 20:50:02 2001 (48956) Could not acquire qrunner lock >>Dec 25 20:51:02 2001 (48960) Could not acquire qrunner lock >>Dec 25 20:52:01 2001 (48968) Could not acquire qrunner lock >>Dec 25 20:54:02 2001 (48977) Could not acquire qrunner lock >>Dec 25 20:55:03 2001 (48986) Could not acquire qrunner lock >> >>Lock files are being created: >> >>/usr/local/mailman/locks# ls -al >>total 4 >>drwxrwsr-x 2 mailman mailman 512 Dec 26 12:07 . >>drwxrwsr-x 18 mailman mailman 512 Oct 31 14:55 .. >>-rw-rw-r-- 2 mailman mailman 69 Dec 26 21:52 qrunner.lock >>-rw-rw-r-- 2 mailman mailman 69 Dec 26 21:52 >>qrunner.lock.straylight.primelogic.com.68866 >>/usr/local/mailman/locks# ls -al >>total 4 >>drwxrwsr-x 2 mailman mailman 512 Dec 26 12:46 . >>drwxrwsr-x 18 mailman mailman 512 Oct 31 14:55 .. >>-rw-rw-r-- 2 mailman mailman 69 Dec 26 22:28 qrunner.lock >>-rw-rw-r-- 2 mailman mailman 69 Dec 26 22:28 >>qrunner.lock.straylight.primelogic.com.69414 >> >>Oddly, the times on the lockfiles are off, set in the future. Here's >>the current time: >> >>/usr/local/mailman/locks# date >>Wed Dec 26 12:47:11 PST 2001 >> >>I removed the locks as a test but they were recreated with different >>numeric extensions. >> >>/usr/local/mailman/logs/post has no entries corresponding to the post >above. >> >>Also, if the problem is solved the list owner will not want all three >>of his attempts to post to be delivered. Is there a means to delete >>the last two attempts so his subscribers won't be spammed with the >>same newsletter? >> >>Hope someone can shed some light, because I'm at a loss here. >> >>.\\ichelle >>--------------------- >>Michelle Brownsworth >>System Administrator >>PrimeLogic Corporation >>http://www.primelogic.com >> >>------------------------------------------------------ >>Mailman-Users maillist - [EMAIL PROTECTED] >>http://mail.python.org/mailman/listinfo/mailman-users >> >> >>------------------------------------------------------ >>Mailman-Users maillist - [EMAIL PROTECTED] >>http://mail.python.org/mailman/listinfo/mailman-users > > >------------------------------------------------------ >Mailman-Users maillist - [EMAIL PROTECTED] >http://mail.python.org/mailman/listinfo/mailman-users ------------------------------------------------------ Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
