[Mailman-Users] mailman cron throwing persistentlockerror(IOError: [Errno 2] No such file or directory...)

[Mark Sapiro]

Bob R wrote:
>
>On Wed, Mar 27, 2013 at 11:29 AM, Mark Sapiro <mark at msapiro.net> wrote:
>>
>> That's a bit unusual.
>>
>> drwxrwxrwt 5 root root 100 Mar 26 07:33 ../
>>
>> refers to the /var/lib/mailman/ directory. I would expect it to be
>>
>> drwxrwsr-x 5 root list 100 Mar 26 07:33 ../
>>
>> however, I don't think that would cause this issue.
>>
>> Is it only cron jobs that have this issue? Are they running as user
>> 'list' (they should be). does 'somelist' work normally otherwise? Can
>> you access its web admin interface?
>>
>
>Cron jobs are run as the user listed after the date code, correct?  Thus
>"lists" is the user the scripts run under - here is the mailman cron...


Yes, that's correct.


>/etc/cron.d$ sudo cat mailman
># At 8AM every day, mail reminders to admins as to pending requests.
># They are less likely to ignore these reminders if they're mailed
># early in the morning, but of course, this is local time... ;)
>0 8 * * * list [ -x /usr/lib/mailman/cron/checkdbs ] &&
>/usr/lib/mailman/cron/checkdbs


Entries like this look OK.


>The interface for the list works perfectly.
>
>I have "rmlist -a" the list and rebuilt it, and mailman functions perfectly
>for list mail.
>
>I removed the sticky bit on /var/lib/mailman (and /locks) but the command
>still failed:


There was no sticky bit on locks/ - it was a SETGID bit and should be
set.

chgrp list /var/lib/mailman
chmod 2775 /var/lib/mailman
chmod 2775 /var/lib/mailman/locks


>$ sudo -u list  [ -x /usr/lib/mailman/cron/checkdbs ] &&
>/usr/lib/mailman/cron/checkdbs
>Traceback (most recent call last):
[...]
>    fp = open(self.__tmpfname, 'w')
>IOError: [Errno 13] Permission denied:
>'/var/lib/mailman/locks/somelist.lock.mydomain.com.27297.0'


This is a new error. Previously it wasn't permission denied.

Do the above chgrp and chmod commands
>
>"Permission denied..."  The error seems pretty straightforward, what is it
>looking for, and why wouldn't check_perms catch it?


check_perms isn't perfect, but did youi run it after changing mode bits?

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan