Re: [Mailman-Developers] Outgoing qrunner dies on 'None' object has no attribute...

On Mon, 2003-04-14 at 08:26, Martin Maechler wrote:

This has happened with increasing intensity here, only since running mailman 2.1.1 (since March 4 or so). Note that the following is an informal bug report of what I think at least two different problems.

---

AttributeError: 'None' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/app/mailman-sfs/2.1.1/bin/qrunner", line 270, in ? main() File "/usr/local/app/mailman-sfs/2.1.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'):

This is fixed in cvs.

--- Bug # 2 ---

BTW: When I do have more than one runner, things get faster, *BUT* I sometimes get the same message delivered by more than one of the outgoing runners. This seems to happen (almost?) ony in the case where the queue is almost empty. But it is quite embarrassing to this twice delivered to everyone on the list.

I think I just fixed this in cvs. There was an off-by-one error in the slice hash space calculation.

-Barry