Hi,
today we successfully upgraded our installation from 2.1.14 to 2.1.15.
Thanks for that! I have to admit that Mailman generally works so flawlessly
that I usually don't look at its logs. Because of the update, today I did.
And I noticed a pattern that I don't understand. It's not new, but I only
noticed it today. I've searched the list archives, but didn't find anything
appropriate.
Every day, we get several of these entries in the error log:
2.1.14:
Jun 25 08:00:17 2012 (12651) Skipping and preserving unparseable message:
1340604017.5663309+f03cd934fd9f24fb5ee97e641a2bf0611a43df85
Jun 25 08:00:17 2012 (12651) Uncaught runner exception: [Errno 2] No such
file or directory:
'/var/spool/mailman/bounces/1340604017.5663309+f03cd934fd9f24fb5ee97e641a2bf0611a43df85.pck'
Jun 25 08:00:17 2012 (12651) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop
msg, msgdata = self._switchboard.dequeue(filebase)
File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 154, in dequeue
fp = open(filename)
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/bounces/1340604017.5663309+f03cd934fd9f24fb5ee97e641a2bf0611a43df85.pck'
Jun 25 08:00:17 2012 (12651) Skipping and preserving unparseable message:
1340604017.5663309+f03cd934fd9f24fb5ee97e641a2bf0611a43df85
2.1.15:
Jun 25 14:57:40 2012 (17936) Uncaught runner exception: [Errno 2] No such
file or directory:
'/var/spool/mailman/bounces/1340629059.7912431+ac4d5683bef1c9339cfd32283c3ae1a9b814cecb.pck'
Jun 25 14:57:40 2012 (17936) Traceback (most recent call last):
File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 99, in _oneloop
msg, msgdata = self._switchboard.dequeue(filebase)
File "/usr/lib/mailman/Mailman/Queue/Switchboard.py", line 154, in dequeue
fp = open(filename)
IOError: [Errno 2] No such file or directory:
'/var/spool/mailman/bounces/1340629059.7912431+ac4d5683bef1c9339cfd32283c3ae1a9b814cecb.pck'
Jun 25 14:57:40 2012 (17936) Skipping and preserving unparseable message:
1340629059.7912431+ac4d5683bef1c9339cfd32283c3ae1a9b814cecb
The messages are preserved in the "bad" directory, which is culled
regularly using cull_bad_shunt. When I look at them with "dumpdb -p", I see
bounces. I understand that the "usual" reason for that is an unparseable
message, as the logging indicates, but in this case it's apparently a
failed open command.
Is that a race condition, a purely cosmetic issue, or something that should
be fixed?
Thanks, Sebastian
--
Sebastian Hagedorn - Listmaster - RZKR-R1 (Gebäude 52), Zimmer 18
Regionales Rechenzentrum (RRZK)
Universität zu Köln / Cologne University - Tel. +49-221-478-5587
------------------------------------------------------
Mailman-Users mailing list [email protected]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
