On Sat, 08 Aug 2015 09:19:27 -0700, Mark Sapiro <m...@msapiro.net>
wrote:
>On 08/08/2015 08:12 AM, Steve Matzura wrote:
>> Every night, I get the following error at the bottom of a mail message
>> to my mailman list telling me that checkdbs, digest and disabled
>> failed:
>>
>> IOError: [Errno 13] Permission denied:
>> '/usr/local/mailman/locks/mailman.lock.{my-FQDN}.{some-number}.0'
>
>
>So cron/checkdbs cant create a lock.
>
>How are these crons running? Are they run form a user crontab
>(/var/spool/cron/mailman ?) or a system crontab (/etc/cron.d/mailman ?)?
The former.
>Your locks directory is fine. The master qrunner can create its locks
>and the running Mailman and presumably the web CGIs can lock and unlock
>lists which is done repeatedly. Your only issue seems to be with crons.
>This must be either an issue with the user:group running the crons or a
>security policy (SELinux or ?) issue.
No SELinux. getenforce says "Disabled".
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://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:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
