[Mailman-Users] Permissions error on all Mailman overnights

Steve Matzura sm at noisynotes.com
Sun Aug 9 03:22:44 CEST 2015

On Sat, 08 Aug 2015 09:19:27 -0700, Mark Sapiro <mark at msapiro.net>

>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".

More information about the Mailman-Users mailing list