On Wednesday, August 13, 2003, at 01:24 pm, Anders Norrbring wrote:
Richard,
Thanks.. :) A -f fixed quite some errors, but still I get this in e-mail
from the server:
Traceback (most recent call last):
File "/usr/lib/mailman/cron/gate_news", line 274, in ?
main()
File "/usr/lib/mailman/cron/gate_news", line 249, in main
lock.lock(timeout=0.5)
File "/var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py",
line 238, in lock
File "/var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py",
line 415, in __write
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/locks/gate_news.lock.berit.20898.0'
Then I guess you will have to check what uid/gid has write permissions over the /var/lib/mailman/locks/ directory and compare this for compatibilty with the uid that the Mailman crontab has been installed under.
I would expect then both to be the 'mailman' uid (as decided by the installer when Mailman was configured) but plainly they cannot be compatible or you would not have a permissions failure when the cron job is (presumably) trying to create a lock file in the directory.
Still there's no directory in /var/tmp
Anders Norrbring
-> -----Original Message-----
-> From: Richard Barrett [mailto:[EMAIL PROTECTED]
-> Sent: den 13 augusti 2003 12:44
-> To: Anders Norrbring
-> Cc: Mailman users
-> Subject: Re: [Mailman-Users] Access problem..
->
->
-> On Wednesday, August 13, 2003, at 10:13 am, Anders Norrbring wrote:
->
-> > Here's one of the mails I get every 5 minutes from my server:
-> >
-> > Traceback (most recent call last):
-> > File "/usr/lib/mailman/cron/gate_news", line 274, in ?
-> > main()
-> > File "/usr/lib/mailman/cron/gate_news", line 249, in main
-> > lock.lock(timeout=0.5)
-> > File
-> > "/var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py",
-> > line 238, in lock
-> > File
-> > "/var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py",
-> > line 415, in __write
-> > IOError: [Errno 13] Permission denied:
-> > '/var/lib/mailman/locks/gate_news.lock.berit.6176.0'
-> >
->
-> You could try running Mailman's check_perms program. Looks from the
-> paths in the traceback above as though it could be in
-> /usr/lib/mailman/bin/check_perms. Run it with the -h option to get it
-> to print its usage.
->
-> > And when I look in '/var/mailman/locks' that dir is empty!
-> > Also, in '/var/tmp' there's only one entry, a subdir named 'vi.recover'
-> >
-> > There's something wrong, but I don't know where to start looking. It's
-> > installed on a SuSE system based on United Linux 1.0 and the mailman
-> > package
-> > is a SuSE distributed one.
-> >
-> > Anders Norrbring
-> > Norrbring Consulting
----------------------------------------------------------------------- Richard Barrett http://www.openinfo.co.uk
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
