[Mailman-Developers] Lock file problems in 2.0b2...

[Lance A. Brown]

Greetings,

We had our mailman spit up a bunch of these traces the other 
night.  All of these appear to be related to a single message 
sent to one of our largest lists at a time when the mailman 
server was under load from doing backups.

Trolling in the archives seems to indicate this is a lock 
timeout issue.  Will upgrading to the soon-to-be-released 
production 2.0 fix this?

Thanks,
  --[Lance]

   ----- The following addresses had permanent fatal errors -----
"|/usr/local/mailman/mail/wrapper mailowner sf-brief"
    (expanded from: <sf-brief-admin@bobo.niehs.nih.gov>)

   ----- Transcript of session follows -----
Traceback (innermost last):
  File "/usr/local/mailman/scripts/mailowner", line 71, in ?
    main()
  File "/usr/local/mailman/scripts/mailowner", line 48, in main
    mlist = MailList.MailList(sys.argv[1])
  File "/usr/local/mailman/Mailman/MailList.py", line 69, in 
__init__
    self.Load()
  File "/usr/local/mailman/Mailman/MailList.py", line 858, in 
Load
    self.Lock()
  File "/usr/local/mailman/Mailman/MailList.py", line 1300, in 
Lock
    self.__lock.lock()
  File "/usr/local/mailman/Mailman/LockFile.py", line 228, in 
lock
    self.__kickstart(force=1)
  File "/usr/local/mailman/Mailman/LockFile.py", line 138, in 
__kickstart
    os.unlink(self.__lockfile)
OSError: [Errno 2] No such file or directory: '/usr/local/mailman
/locks/sf-brief.lock'
554 "|/usr/local/mailman/mail/wrapper mailowner sf-brief"... 
unknown mailer error 1