[Mailman-Users] Mailman Traceback
msapiro at value.net
Wed Apr 4 02:14:17 CEST 2007
No One wrote:
>Thanks. Here it is:
>Starting mailman: Traceback (most recent call last):
> File "/usr/sbin/mailmanctl", line 548, in ?
> File "/usr/sbin/mailmanctl", line 367, in main
> File "/usr/sbin/mailmanctl", line 277, in check_for_site_list
> sitelist = MailList(sitelistname, lock=0)
> File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
> File "/usr/lib/mailman/Mailman/MailList.py", line 665, in Load
> File "/usr/lib/mailman/Mailman/MailList.py", line 715, in CheckVersion
> File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock
> File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock
> File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write
> fp = open(self.__tmpfname, 'w')
>IOError: [Errno 13] Permission denied: '/var/lib/mailman/locks/mailman.lock.dap002.8626.0'
There are two things going on here. First, and not really relevant to
the big picture, it appears you must be upgrading lists because the
section of code you're in is only reached if the data version of the
/var/lib/mailman/lists/mailman/config.pck file is less that the
current software version.
That aside, you will have problems anyway if the software can't create
and write lock files.
Have you run bin/check_perms to check permissions. You should run it as
root with the -f option until it runs cleanly.
If you're sure that all directories in the /var/lib/mailman/locks/ path
have search (x or maybe group s) permission for Mailman's group (or
world in the case of /var/ and /var/lib/) and the
/var/lib/mailman/locks/ directory itself also has read and write for
Mailman's group and you still get the above error, it may be due to
SeLinux or some other security policy
Mark Sapiro <msapiro at value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users