Cron error: /usr/bin/python -S /var/lib/mailman/cron/checkdbs
I have yet another cron error that I get every day in my mail. I'm not sure what it is.
Cron <mailman@mail> /usr/bin/python -S /var/lib/mailman/cron/checkdbs
Traceback (most recent call last): File "/var/lib/mailman/cron/checkdbs", line 178, in ? main() File "/var/lib/mailman/cron/checkdbs", line 84, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 126, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 159, in Lock self.__lock.lock(timeout) File "/var/lib/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/var/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.mail.6528.0'
On Mon, 2005-05-09 at 08:09 -0700, James wrote:
I have yet another cron error that I get every day in my mail. I'm not sure what it is.
Cron <mailman@mail> /usr/bin/python -S /var/lib/mailman/cron/checkdbs
Traceback (most recent call last): File "/var/lib/mailman/cron/checkdbs", line 178, in ? main() File "/var/lib/mailman/cron/checkdbs", line 84, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 126, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 159, in Lock self.__lock.lock(timeout) File "/var/lib/mailman/Mailman/LockFile.py", line 243, in lock self.__write() File "/var/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.mail.6528.0'
I'm assuming you installed your cron entries using crontab and not via /etc/cron.d, if so then did you remember to add "-u mailman" to the crontab command so the scripts execute as the mailman user? (If you used /etc/cron.d scripts then the user name goes into the cron file as the 6th field).
If cron is executing your mailman scripts as the user mailman then look at the file permissions on the lock file, its possible it got created with the wrong permissions during an earlier snafu with incorrect installation.
John Dennis <jdennis@redhat.com>
participants (2)
-
James
-
John Dennis