[Mailman-Users] mailman cron throwingpersistentlockerror(IOError:[Errno 2] No such file or directory...)

Bob R bob.reap at gmail.com
Thu Mar 28 03:01:10 CET 2013


On Wed, Mar 27, 2013 at 6:18 PM, Mark Sapiro <mark at msapiro.net> wrote:

> Another thought.
>
> If you temporarily move the /var/lib/mailman/lists/somelist/ directory
> out of the /var/lib/mailman/lists/ directory and then run the
>
> sudo -u list  [ -x /usr/lib/mailman/cron/checkdbs ] &&
> /usr/lib/mailman/cron/checkdbs
>
> command, does it succeed or does it fail on the next list?
>
>

I short-circuited the cron to run now, and it does indeed move on to the
next list:

Traceback (most recent call last):
  File "/usr/lib/mailman/cron/checkdbs", line 203, in <module>
    main()
  File "/usr/lib/mailman/cron/checkdbs", line 86, in main
    mlist = MailList.MailList(name)
  File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__
    self.Lock()
  File "/var/lib/mailman/Mailman/MailList.py", line 161, in Lock
    self.__lock.lock(timeout)
  File "/var/lib/mailman/Mailman/LockFile.py", line 243, in lock
    self.__write()
  File "/var/lib/mailman/Mailman/LockFile.py", line 422, in __write
    fp = open(self.__tmpfname, 'w')
IOError: [Errno 2] No such file or directory:
'/var/lib/mailman/locks/differentlist.lock.mydomain.com.1200.0'


(Note that the cron email reports a different error than the command line,
as you noted, so the environment obviously is not quite the same.  But I
did run the checkdbs from the command line, and like the cron script it
also moves on to the next list before it reports an error.)

> What about
>
> ls -ld /var/lock/mailman

:/www/lists/conf$ ls -ld /var/lock/mailman
drwxrwsr-x 2 root list 80 Mar 27 18:31 /var/lock/mailman


Bob R


More information about the Mailman-Users mailing list