[Mailman-Users] Cull_Bad_Shunt

[Mark Sapiro]

On 09/28/2016 01:29 PM, Mark Graves wrote:
> I'm using Mailman v2.1.21 on openSUSE Leap 42.1 and received the following email from Cron Daemon:
> 
> [Mailman] Cron <mailman at listserv> /usr/bin/python -S /usr/lib/mailman/cron/cull_bad_shunt
> 
> 
> Traceback (most recent call last):
> 
>   File "/usr/lib/mailman/cron/cull_bad_shunt", line 126, in <module>
> 
>     main()
> 
>   File "/usr/lib/mailman/cron/cull_bad_shunt", line 121, in main
> 
>     os.remove(pathname)
> 
> OSError: [Errno 2] No such file or directory: '/var/lib/mailman/qfiles/shunt/1474407372.553232+5932f7df2b1dccdd77f92f45a8271e33e8f945d8.pck'
> 
> 
> Just passing it along in case it's a bug.


This can occur only if some other process removed the
/var/lib/mailman/qfiles/shunt/1474407372.553232+5932f7df2b1dccdd77f92f45a8271e33e8f945d8.pck
file after this process listed the directory contents but before it
tried to remove the file.

The most likely way for this to occur is by cron running cull_bad_shunt
twice. I suspect that what's going on is there is both a mailman user
crontab in /var/spool/cron/mailman or wherever user crontabs are stored
and a system crontab in /etc/cron.d/mailman and both are running the
same jobs at the same times. This would also cause other anomalies such
as duplicate "nn moderator requests" messages to list owners/moderators.

There should be only one crontab running Mailman's crons. Which one
doesn't matter.

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