Ian Kaufman wrote: > >I am having trouble getting my mailman instance to run. It was working for >sometime, >but I had to move some files around and add a new disk to the system, and >now >it refuses to start. The error I see is: > >Starting mailman: Traceback (most recent call last): > File "/usr/lib/mailman/bin/mailmanctl", line 607, in ? > main() > File "/usr/lib/mailman/bin/mailmanctl", line 449, in main > lock = acquire_lock(force) > File "/usr/lib/mailman/bin/mailmanctl", line 263, in acquire_lock > lock = acquire_lock_1(force) > File "/usr/lib/mailman/bin/mailmanctl", line 248, in acquire_lock_1 > lock.lock(0.1) > File "/usr/lib/mailman/Mailman/LockFile.py", line 243, in lock > self.__write() > File "/usr/lib/mailman/Mailman/LockFile.py", line 422, in __write > fp = open(self.__tmpfname, 'w') >IOError: [Errno 13] Permission denied: >'/var/lock/mailman/master-qrunner.calit2-web05.ucsd.edu.5359.1' >Exception exceptions.OSError: <exceptions.OSError instance at 0xb7b01eec> in >Exception exceptions.OSError: <exceptions.OSError instance at 0xb7b01ecc> >in [FAILED] > >It appears that mailmanctl tries to create the lockfile, but does not, as >there is nothing >in /var/lock/mailman. I have run check_perms and there were no errors.
Mailman (or the user running mailmanctl) doesn't have permission to create files in it's locks directory. This could be /var/lock/mailman if this is a RedHat package. See the definition of LOCK_DIR in Defaults.py/mm_cfg.py. Are you running mailmanctl as root? -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org 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