[Mailman-Users] Archiving is broken
mark at msapiro.net
Thu Aug 21 06:08:23 CEST 2008
Mark Heer wrote:
>I only get the following error for a few lists but in each case the ownership is mailman:mailman
>I noted an error re: ownership problems - but mailman user and group do indeed own the dirs/files so that message is confusing :
>Aug 20 09:31:06 2008 (27219) Traceback (most recent call last):
> File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
> self._onefile(msg, msgdata)
> File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
> keepqueued = self._dispose(mlist, msg, msgdata)
> File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose
> File "/usr/local/mailman/Mailman/MailList.py", line 568, in Save
> File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 236, in CheckHTMLArchiveDir
> File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 56, in breaklink
>OSError: [Errno 1] Not owner: '/usr/local/mailman/archives/public/wan-data-transfers'
>Aug 20 09:31:06 2008 (27219) SHUNTING: 1219249865.3392961+47525c120442e9f4bd836c09cd41c46b6feb351e
It appears that at some point, the archive of this list
(wan-data-transfers) was changed from public to private and now
mailman is trying to remove the symlink from
/usr/local/mailman/archives/prvate/wan-data-transfers. It is being
denied by the OS when it tries to do this.
This may be a permissions issue not checked by check_perms or it may be
a SELinux or other security policy manager issue or it may be that
IncomingRunner was not started properly (i.e. by 'mailmanctl start'
run by root) and is not running as the correct user:group.
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users