Breaking expired locks logs a traceback

Bug #266248 reported by Fehwalker-users
2
Affects Status Importance Assigned to Milestone
GNU Mailman
New
Medium
Unassigned

Bug Description

This looks like a bug to me, though perhaps there's
some reason a traceback is needed each time an expired
lock is broken?

Jun 29 23:51:18 2005 (4405) bryans-list.lock lifetime
has expired, breaking
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/bin/qrunner", line 270, in ?
Jun 29 23:51:18 2005 (4405) main()
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/bin/qrunner", line 230, in main
Jun 29 23:51:18 2005 (4405) qrunner.run()
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/Queue/Runner.py", line 70,
in run
Jun 29 23:51:18 2005 (4405) filecnt = self._oneloop()
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/Queue/Runner.py", line 111,
in _oneloop
Jun 29 23:51:18 2005 (4405) self._onefile(msg, msgdata)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/Queue/Runner.py", line 167,
in _onefile
Jun 29 23:51:18 2005 (4405) keepqueued =
self._dispose(mlist, msg, msgdata)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/Queue/VirginRunner.py",
line 38, in _dispose
Jun 29 23:51:18 2005 (4405) return
IncomingRunner._dispose(self, mlist, msg, msgdata)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/Queue/IncomingRunner.py",
line 115, in _dispose
Jun 29 23:51:18 2005 (4405)
mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/MailList.py", line 160, in Lock
Jun 29 23:51:18 2005 (4405) self.__lock.lock(timeout)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/LockFile.py", line 306, in lock
Jun 29 23:51:18 2005 (4405) important=True)
Jun 29 23:51:18 2005 (4405) File
"/usr/local/mailman/Mailman/LockFile.py", line 416, in
__writelog
Jun 29 23:51:18 2005 (4405)
traceback.print_stack(file=logf)

Thanks,
Bryan

[http://sourceforge.net/tracker/index.php?func=detail&aid=1233670&group_id=103&atid=100103]

Revision history for this message
Fehwalker-users (fehwalker-users) wrote :

Oh, I'm running 2.1.6.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.