[Mailman-Users] mailman no longer working

Mark Sapiro msapiro at value.net
Sun Oct 8 03:51:41 CEST 2006


Noah wrote:
>
>Mark Sapiro wrote:
>>
>> When Mailman encounters an unanticipated exception in handling a
>> message, it logs the error and puts the message aside in the shunt
>> queue. After the underlying cause is addressed, it may be appropriate
>> to run bin/unshunt to reprocess the messages, but not before the
>> underlying problem is addressed and fixed and maybe not at all.
>>
>>
>>   
>okay thanks
>>   
>>> here is a snippet of the file namesin qufiles/shunt
>>>
>>> 1160196209.4276011+2cb7b1389cc59eb383e0a179f1b59eed1b376aa5.pck
>>> 1160196209.4734559+63faff22811443c4c89098dd10ce9417852920e3.pck
>>> 1160196209.5072241+8105afad74a5cdbaac7821626a483cc674b0c9ad.pck
>>> 1160196209.5556359+bd6f797928d52cc8b9f899655a246c819334adae.pck
>>> 1160196209.590873+2a5f1aa36e17e8a79dc08ef16d37118ff6c57ecb.pck
>>> 1160196209.6326721+af3f4018e49a1aa658dd00ab9647f740e1bfa5ef.pck
>>> 1160196209.6745429+7b4a363c5d6b3424f8a354cb96ee264e0140ad33.pck
>>> 1160196209.716466+e9179b50c745d1dd1568c6cf975e87d9db67fe15.pck
>>> 1160196209.771184+a3664c9dd86d55f567e79a8b61d83ddc7563f3db.pck
>>> 1160196209.8121741+b8f598a5f14355e5acba3f962bb3f4d4ce8b2883.pck
>>> 1160196209.8540821+dd989c817f5b59f1eadc8545012d0793f54c4b74.pck
>>> 1160196209.89591+a031c30d55c9ef0922bdd64a0a02cd37bbb21a24.pck
>>> 1160196209.946244+3655a069af376348d0051aac1171ce9c7cdebf38.pck
>>> 1160196209.979713+53463a27f773583ad8151955523618248804031d.pck
>>> 1160196210.0325711+98d2a68cfa8244cb7ff465f0538d4f95d3d97b0d.pck
>>> 1160196210.0694251+c5a913922860b2bb9ca7700b261dea17e3cc2c14.pck
>>>     
>>
>>
>> Is this the beginning or the end? The nnn.nnn at the beginning of the
>> name is a time stamp - floating point seconds since the start of the
>> epoch. The above range from 'Fri Oct  6 21:43:29 2006' to 'Fri Oct  6
>> 21:43:30 2006'.
>>   
>
>okay here is the start of the qfiles/shunt directory = so around October 
>6th at 21:33
>
>--- snip ---
>
># ls -l  | less
>total 274700
>-rw-rw----  1 root  mailman    10210 Oct  6 21:33 
>1160195625.999362+c89e0d7b8e07710
>e7c154543027c12dad2a60f9a.pck
>-rw-rw----  1 root  mailman     3121 Oct  6 21:33 
>1160195626.0452521+2066b799fc17b7
>a02e64ac7f7e7c0e8298caf329.pck
>-rw-rw----  1 root  mailman   254315 Oct  6 21:33 
>1160195626.111922+0e86b9e8b76c77e
>eae51676ddda24eb4784112f4.pck
>-rw-rw----  1 root  mailman     3280 Oct  6 21:33 
>1160195626.1932449+07084c71555a8c
>29767428f9983cd83ff54f29e0.pck
>-rw-rw----  1 root  mailman    18023 Oct  6 21:33 
>1160195626.2369709+8a099a228d5aa6
>2cecb29f6e24620ac1c7a5a1f1.pck
>-rw-rw----  1 root  mailman     4231 Oct  6 21:33 
>1160195626.2888789+abd785fe25c7d4
>504fc6d102f3f218dda7dda24f.pck
>-rw-rw----  1 root  mailman  1339443 Oct  6 21:33 
>1160195626.407881+0cb3adf00e340e3
>3efd319c679074ef2351d4d1e.pck
>-rw-rw----  1 root  mailman    41846 Oct  6 21:33 
>1160195626.633749+1b24da7f45e5dba
>f4d6d25ebf8443b43c9bd20be.pck
>-rw-rw----  1 root  mailman     2973 Oct  6 21:33 
>1160195626.695061+3aac5e546d276b5
>6779ed08af756d1d2baed00b6.pck
>-rw-rw----  1 root  mailman    41388 Oct  6 21:33 
>1160195626.746171+2a1736ceae5ff7b
>7d8ba19cab30b570987b10385.pck
>-rw-rw----  1 root  mailman     8894 Oct  6 21:33 
>1160195626.8063321+e67b6bf18cc5c1
>35fac6903815b4f7e554087fac.pck
>-rw-rw----  1 root  mailman    44829 Oct  6 21:33 
>1160195626.8536539+3e4e1eeecc6a2c
>a0444aa03c51fed2099f4d680b.pck
>-rw-rw----  1 root  mailman     3162 Oct  6 21:33 
>1160195626.8973761+8afa4edfeafd77
>c29f7b64a1dfa9304b0d51e949.pck
>-rw-rw----  1 root  mailman     2362 Oct  6 21:33 
>1160195626.9391079+47c40f250f06ec
>cbdb28ac8abe034e1390005eca.pck
>-rw-rw----  1 root  mailman    42127 Oct  6 21:33 
>1160195626.993763+0d551742b9149fb
>61b2d1b31fab5f435869bc17c.pck
>-rw-rw----  1 root  mailman     1665 Oct  6 21:33 
>1160195627.054147+8c2ad33a86933c5
>c5d7c47408a96d3bef13ea520.pck
>-rw-rw----  1 root  mailman     1955 Oct  6 21:33 
>1160195627.0825861+7f05bcbdd780d0
>b61ce59f05842ebb3be37d0740.pck
>-rw-rw----  1 root  mailman     1612 Oct  6 21:33 
>1160195627.1322341+d803fa8078f5ef
>0a38b4e894aaba8f74db900110.pck
>-rw-rw----  1 root  mailman    11844 Oct  6 21:33 
>1160195627.1798019+bebaed1a8cb75f
>a2f22d184574a4af895500fa2b.pck
>-rw-rw----  1 root  mailman    42152 Oct  6 21:33 
>1160195627.2235739+47763a52ea557f
>2308a292a53b189b425d17efd1.pck
>-rw-rw----  1 root  mailman    42179 Oct  6 21:33 
>1160195627.2690489+e2fdc1d15ca33f
>4fe59872a0eaf9f25729435633.pck
>-rw-rw----  1 root  mailman     6434 Oct  6 21:33 
>1160195627.3298931+094a7d137dc73d
>84fe6c6b09a4ca54dc6137224d.pck
>-rw-rw----  1 root  mailman     6464 Oct  6 21:33 
>1160195627.372112+3bad6533f7c966c
>69d17d479b8d258504e25f3a2.pck
>-rw-rw----  1 root  mailman     9185 Oct  6 21:33 
>1160195627.4168611+9b02b5f80ab201
>ee4cf0ddc16974171a62be7f1b.pck
>
>
>---- snip -----
>> There should be an entry in Mailman's error log for each one of those
>> with a full traceback and ending with a line
>>
>> SHUNTING: filebase
>>   
>> Where filebase is the filename as above without the .pck extension.
>>
>> What do the tracebacks and errors say?
>>
>>   
>
>well here are the errors that have ended up in 
>/usr/local/mailman/logs/error  I dont see anything in the date range of 
>october 6th.  so what else can I try?
>
>---- snip ---
>
># grep "SHUNT" error
>Feb 11 11:47:03 2006 (67129) SHUNTING: 
>1139687222.191267+a408a7c3791d970391e2ee859e7ee1aee4e511ec
>Feb 19 23:23:04 2006 (88962) SHUNTING: 
>1140420182.7228961+3cca5db88da3b3ffe735834b1101f27b97a626a2
>Mar 07 12:45:22 2006 (96045) SHUNTING: 
>1141242240.8385019+b94b2e966cad393acbb1b8727f5596b971c5db35
>Mar 11 08:09:47 2006 (1215) SHUNTING: 
>1142093385.240932+63ea006aaf597383a233e9b93899daec9bb5f4c9
>Mar 15 07:27:58 2006 (63110) SHUNTING: 
>1142436477.7204449+451ae4e6b12ffc224ba7d6c1d0cd3ca51180c90b
>Mar 20 12:05:03 2006 (32271) SHUNTING: 
>1142885102.207798+68a0d57e24ffed593bfc41d7f04b5abad8565522
>Mar 24 12:02:38 2006 (79703) SHUNTING: 
>1143230556.5646989+07333452c2faa25964fda992b6ffe1facd7ef738
>Mar 30 10:59:09 2006 (43059) SHUNTING: 
>1143745147.5963349+fa1dd3bcc355fc953e1cc2c56a4ee61696889596
>Apr 02 14:30:30 2006 (39135) SHUNTING: 
>1144013428.959239+eaf23aaa2eeda1fbea24bd6168a1671b127bf608
>
>---- snip ---


I am puzzled. As I read the code, it is not possible to create the
shunt queue entry without also logging the error and the SHUNTING
message. Ordinarily, I would suggest that you might be logging to a
different set of log files in a different directory, but an earlier
post showed error log entries with timestamps Oct 06 21:56:25 2006 and
later. Is it possible you have more than one Mailman installation?


>> Also, you can probably examine those files with bin/show_qfiles or
>> bin/dumpdb and see if the message might indicate some kind of loop.
>>
>>   
>I can see the qfile but it looks like a regular post.  so I am not sure 
>what is going on here.


Well, there seem to be 14,000 of them in a 10 minute period. I don't
think they can all be regular posts unless something is looping on the
same post, but that shouldn't be because once the post is shunted, it
isn't processed further.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan




More information about the Mailman-Users mailing list