[Mailman-Users] Possible Backup Issue

[Mark Sapiro]

On 2/27/20 6:27 AM, Dennis Putnam wrote:
> 
> It has not happened in 2 days however, there are no files in any of
> those directories. Does that not imply the backups are not working? Is
> that handled by a cronjob?


This has nothing to do with backups per se. The error messages are
somewhat different.

> Feb 25 12:02:06 2020 (14100) Uncaught runner exception: [Errno 2] No
> such file or directory

The above actually goes with a set below (pid 14100).


> Feb 25 12:02:06 2020 (5133) Uncaught runner exception: [Errno 2] No such
> file or directory:
> '/var/spool/mailman/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.pck'
> Feb 25 12:02:06 2020 (5133) 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/out/1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d.pck'


The above says OutgoingRunner has listed its queue and is now trying to
retrieve the indicated .pck file from the queue, but it is gone. The
only way this can happen is if another instance of OutgoingRunner has
retrieved the message in the mean time.


> Feb 25 12:02:06 2020 (5133) Skipping and preserving unparseable message:
> 1582657325.390982+504a3666a91ef8722e1af700669bf0190e00417d

This goes with the above, but is spurious. The missing file exception is
assumed to be an unparseable message, but it's not.


> Feb 25 12:02:06 2020 (14100) 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 158, in dequeue
>     os.rename(filename, backfile)
> OSError: [Errno 2] No such file or directory
> 
> Feb 25 12:02:06 2020 (14100) Skipping and preserving unparseable
> message: 1582657325.390982+30007f7a3ce65a426ba60c1ab46d996c33d2bb9a


Here again, we are trying to retrieve a queued message that another
instance has already retrieved.

The rest of the messages are similar.

As best as I can tell, this is all due to the issue discussed at
<https://wiki.list.org/x/4030715>. If the server has been rebooted since
this happened, that would have fixed it.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20200227/2048063b/attachment.sig>