mailman cron throwing persistent lock error (IOError: [Errno 2] No such file or directory...)
Hi folks - I keep getting my mailman cron throwing and emailing me consistent errors:
[somelist and myhost redacted...]
Example 1:
Subject: Cron <list@myhost> [ -x /usr/lib/mailman/cron/disabled ] && /usr/lib/mailman/cron/disabled
Traceback (most recent call last): File "/usr/lib/mailman/cron/disabled", line 224, in <module> main() File "/usr/lib/mailman/cron/disabled", line 150, in main mlist = MailList.MailList(listname) File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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 2] No such file or directory: '/var/lib/mailman/locks/somelist.lock.myhost.24422.0'
======
Example 2:
Cron <list@myhost> [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/mailman/cron/checkdbs
Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 203, in <module> main() File "/usr/lib/mailman/cron/checkdbs", line 86, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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 2] No such file or directory: '/var/lib/mailman/locks/somelist.lock.myhost.21892.0'
======
Example 3:
Cron <list@myhost> [ -x /usr/lib/mailman/cron/senddigests ] && /usr/lib/mailman/cron/senddigests
Traceback (most recent call last): File "/usr/lib/mailman/cron/senddigests", line 106, in <module> main() File "/usr/lib/mailman/cron/senddigests", line 86, in main mlist.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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 2] No such file or directory: '/var/lib/mailman/locks/somelist.lock.myhost.31648.0'
--
This seems to be the only list (of nearly 200) that throws this error.
The installation is running on an Ubuntu server per instructions here:
https://help.ubuntu.com/community/Mailman
I checked and fixed permissions:
sudo check_perms -f
I deleted and recreated the list:
sudo config_list -o somelist.cfg somelist; sudo /usr/lib/mailman/bin/rmlist -a somelist; sudo newlist somelist listmgr@mydomain.com mypasswd; sudo config_list -i somelist.cfg somelist;
But the problem persists. Any suggestions?
Bob R wrote:
[...]
There's a FAQ at <http://wiki.list.org/x/OIDD> on that ;)
I checked and fixed permissions:
The error says that some directory in the path '/var/lib/mailman/locks/somelist.lock.myhost.24422.0' doesn't exist. Unless either 'somelist' or 'myhost' contains a '/' which shouldn't be possible, that means one of the directories in the path '/var/lib/mailman/locks/' which again seems unlikely given that other lists work.
What is the contents of the '/var/lib/mailman/locks/' directory? If Mailman is quiet, it should be only master-qrunner and master-qrunner.HOST.PID.
Also see <http://wiki.list.org/x/noA9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Mar 26, 2013 at 12:04 PM, Mark Sapiro <mark@msapiro.net> wrote:
$ ll /var/lib/mailman/locks/ total 8 drwxrwsr-x 2 root list 80 Mar 26 12:22 ./ drwxrwxrwt 5 root root 100 Mar 26 07:33 ../ -rw-rw-r-- 2 list list 61 Mar 27 2013 master-qrunner -rw-rw-r-- 2 list list 61 Mar 27 2013 master-qrunner.mydomain.com.3488
Bob R 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?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 11:29 AM, Mark Sapiro <mark@msapiro.net> wrote:
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...
/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 # # At 9AM, send notifications to disabled members that are due to be # reminded to re-enable their accounts. 0 9 * * * list [ -x /usr/lib/mailman/cron/disabled ] && /usr/lib/mailman/cron/disabled # # Noon, mail digests for lists that do periodic as well as threshold delivery. 0 12 * * * list [ -x /usr/lib/mailman/cron/senddigests ] && /usr/lib/mailman/cron/senddigests # # 5 AM on the first of each month, mail out password reminders. 0 5 1 * * list [ -x /usr/lib/mailman/cron/mailpasswds ] && /usr/lib/mailman/cron/mailpasswds # . . . # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py 27 3 * * * list [ -x /usr/lib/mailman/cron/nightly_gzip ] && /usr/lib/mailman/cron/nightly_gzip # # At 4:30AM daily, cull old entries from the 'bad' and 'shunt' queues. 30 4 * * * list [ -x /usr/lib/mailman/cron/cull_bad_shunt ] && /usr/lib/mailman/cron/cull_bad_shunt
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:
$ sudo -u list [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/mailman/cron/checkdbs Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 203, in <module> main() File "/usr/lib/mailman/cron/checkdbs", line 86, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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/somelist.lock.mydomain.com.27297.0'
"Permission denied..." The error seems pretty straightforward, what is it looking for, and why wouldn't check_perms catch it?
-br
Bob R wrote:
Yes, that's correct.
Entries like this look OK.
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
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 5:12 PM, Mark Sapiro <mark@msapiro.net> wrote:
Possibly because the other errors were reported by cron vie email, and the above was running the cron sequence by the command line?
I ran the chmod and chgroup cmmands as suggested, and ran check_perms before and after - it reports no problems.
Running the cron from the command line still creates the error as described, but I may have wrongly assumed that replicated the conditions from the cron. ???
I appreciate your assistance with this...
br
Bob R wrote:
Possibly because the other errors were reported by cron vie email, and the above was running the cron sequence by the command line?
Not likely as you ran the command from the command line as user 'list' and it runs via cron as user 'list'.
What does
groups list
give? what do
ls -l -d /var ls -l -d /var/lib ls -l -d /var/lib/mailman ls -l -d /var/lib/mailman/locks
give? Do you have SELinux or some other security manager enabled?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Another thought.
If you temporarily move the /var/lib/mailman/lists/somelist/ directory out of the /var/lib/mailman/lists/ directory and then run the
sudo -u list [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/mailman/cron/checkdbs
command, does it succeed or does it fail on the next list?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 6:18 PM, Mark Sapiro <mark@msapiro.net> wrote:
I short-circuited the cron to run now, and it does indeed move on to the next list:
Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 203, in <module> main() File "/usr/lib/mailman/cron/checkdbs", line 86, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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 2] No such file or directory: '/var/lib/mailman/locks/differentlist.lock.mydomain.com.1200.0'
(Note that the cron email reports a different error than the command line, as you noted, so the environment obviously is not quite the same. But I did run the checkdbs from the command line, and like the cron script it also moves on to the next list before it reports an error.)
What about
ls -ld /var/lock/mailman
:/www/lists/conf$ ls -ld /var/lock/mailman drwxrwsr-x 2 root list 80 Mar 27 18:31 /var/lock/mailman
Bob R
Bob R wrote:
OK. so none of the crons are able to create locks for any list. Although it's puzzling why it's error 2 when run by cron and error 13 when run from the command line as the same user.
:/www/lists/conf$ ls -ld /var/lock/mailman drwxrwsr-x 2 root list 80 Mar 27 18:31 /var/lock/mailman
How about
ls -ld /var/lock
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/27/2013 7:24 PM, Bob R wrote:
$ ls -ld /var/lock lrwxrwxrwx 1 root root 9 May 1 2012 /var/lock -> /run/lock
and /run and /run/lock ?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 7:28 PM, Mark Sapiro <mark@msapiro.net> wrote:
$ ls -ld /run/lock; ls -ld /run drwxrwxrwt 5 root root 100 Mar 27 19:49 /run/lock drwxr-xr-x 21 root root 780 Mar 27 19:53 /run
Bob R wrote:
OK, I'm grasping at straws here, but the issue appears to be that the 'list:list' user:group can't create files in /var/lib/mailman/locks, aka /run/lock, but Mailman's qrunners and web cgi's are able to do so.
what does
ps -fAw | grep qrunner
and
ls -l /usr/lib/mailman/cgi-bin
give? The qrunner processes should be user 'list' and the wrappers in cgi-bin should be group 'list' and SETGID. is that the case or are they some other user:group?
Also, I think if you do
sudo -u list touch /var/lib/mailman/locks/test_file
or create an entry in /etc/cron.d/mailman that runs
0,10,20,30,40,50 * * * * list touch /var/lib/mailman/locks/test_file
(i.e. runs the touch command every 10 minutes), you will see the same errors. If this is the case, figure out why. I suspect some security manager must be involved as all the permissions on the directories should allow it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 5:56 PM, Mark Sapiro <mark@msapiro.net> wrote:
$ sudo groups list list : list
$ ls -l -d /var; ls -l -d /var/lib; ls -l -d /var/lib/mailman; ls -l -d /var/lib/mailman/locks drwxr-xr-x 13 root root 4096 Mar 24 09:23 /var drwxr-xr-x 43 root root 4096 Jan 20 08:41 /var/lib drwxrwsr-x 8 root list 4096 Jan 15 06:48 /var/lib/mailman lrwxrwxrwx 1 root list 17 Jul 17 2012 /var/lib/mailman/locks -> /var/lock/mailman
Do you have SELinux or some other security manager enabled?
No, I didn't install that (I don't think that program is even compatible with the Ubuntu LTS)....
Bob R
Bob R wrote:
lrwxrwxrwx 1 root list 17 Jul 17 2012 /var/lib/mailman/locks -> /var/lock/mailman
What about
ls -ld /var/lock/mailman
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Bob R wrote:
[...]
There's a FAQ at <http://wiki.list.org/x/OIDD> on that ;)
I checked and fixed permissions:
The error says that some directory in the path '/var/lib/mailman/locks/somelist.lock.myhost.24422.0' doesn't exist. Unless either 'somelist' or 'myhost' contains a '/' which shouldn't be possible, that means one of the directories in the path '/var/lib/mailman/locks/' which again seems unlikely given that other lists work.
What is the contents of the '/var/lib/mailman/locks/' directory? If Mailman is quiet, it should be only master-qrunner and master-qrunner.HOST.PID.
Also see <http://wiki.list.org/x/noA9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Mar 26, 2013 at 12:04 PM, Mark Sapiro <mark@msapiro.net> wrote:
$ ll /var/lib/mailman/locks/ total 8 drwxrwsr-x 2 root list 80 Mar 26 12:22 ./ drwxrwxrwt 5 root root 100 Mar 26 07:33 ../ -rw-rw-r-- 2 list list 61 Mar 27 2013 master-qrunner -rw-rw-r-- 2 list list 61 Mar 27 2013 master-qrunner.mydomain.com.3488
Bob R 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?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 11:29 AM, Mark Sapiro <mark@msapiro.net> wrote:
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...
/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 # # At 9AM, send notifications to disabled members that are due to be # reminded to re-enable their accounts. 0 9 * * * list [ -x /usr/lib/mailman/cron/disabled ] && /usr/lib/mailman/cron/disabled # # Noon, mail digests for lists that do periodic as well as threshold delivery. 0 12 * * * list [ -x /usr/lib/mailman/cron/senddigests ] && /usr/lib/mailman/cron/senddigests # # 5 AM on the first of each month, mail out password reminders. 0 5 1 * * list [ -x /usr/lib/mailman/cron/mailpasswds ] && /usr/lib/mailman/cron/mailpasswds # . . . # At 3:27am every night, regenerate the gzip'd archive file. Only # turn this on if the internal archiver is used and # GZIP_ARCHIVE_TXT_FILES is false in mm_cfg.py 27 3 * * * list [ -x /usr/lib/mailman/cron/nightly_gzip ] && /usr/lib/mailman/cron/nightly_gzip # # At 4:30AM daily, cull old entries from the 'bad' and 'shunt' queues. 30 4 * * * list [ -x /usr/lib/mailman/cron/cull_bad_shunt ] && /usr/lib/mailman/cron/cull_bad_shunt
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:
$ sudo -u list [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/mailman/cron/checkdbs Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 203, in <module> main() File "/usr/lib/mailman/cron/checkdbs", line 86, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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/somelist.lock.mydomain.com.27297.0'
"Permission denied..." The error seems pretty straightforward, what is it looking for, and why wouldn't check_perms catch it?
-br
Bob R wrote:
Yes, that's correct.
Entries like this look OK.
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
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@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 5:12 PM, Mark Sapiro <mark@msapiro.net> wrote:
Possibly because the other errors were reported by cron vie email, and the above was running the cron sequence by the command line?
I ran the chmod and chgroup cmmands as suggested, and ran check_perms before and after - it reports no problems.
Running the cron from the command line still creates the error as described, but I may have wrongly assumed that replicated the conditions from the cron. ???
I appreciate your assistance with this...
br
Bob R wrote:
Possibly because the other errors were reported by cron vie email, and the above was running the cron sequence by the command line?
Not likely as you ran the command from the command line as user 'list' and it runs via cron as user 'list'.
What does
groups list
give? what do
ls -l -d /var ls -l -d /var/lib ls -l -d /var/lib/mailman ls -l -d /var/lib/mailman/locks
give? Do you have SELinux or some other security manager enabled?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Another thought.
If you temporarily move the /var/lib/mailman/lists/somelist/ directory out of the /var/lib/mailman/lists/ directory and then run the
sudo -u list [ -x /usr/lib/mailman/cron/checkdbs ] && /usr/lib/mailman/cron/checkdbs
command, does it succeed or does it fail on the next list?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 6:18 PM, Mark Sapiro <mark@msapiro.net> wrote:
I short-circuited the cron to run now, and it does indeed move on to the next list:
Traceback (most recent call last): File "/usr/lib/mailman/cron/checkdbs", line 203, in <module> main() File "/usr/lib/mailman/cron/checkdbs", line 86, in main mlist = MailList.MailList(name) File "/var/lib/mailman/Mailman/MailList.py", line 128, in __init__ self.Lock() File "/var/lib/mailman/Mailman/MailList.py", line 161, 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 2] No such file or directory: '/var/lib/mailman/locks/differentlist.lock.mydomain.com.1200.0'
(Note that the cron email reports a different error than the command line, as you noted, so the environment obviously is not quite the same. But I did run the checkdbs from the command line, and like the cron script it also moves on to the next list before it reports an error.)
What about
ls -ld /var/lock/mailman
:/www/lists/conf$ ls -ld /var/lock/mailman drwxrwsr-x 2 root list 80 Mar 27 18:31 /var/lock/mailman
Bob R
Bob R wrote:
OK. so none of the crons are able to create locks for any list. Although it's puzzling why it's error 2 when run by cron and error 13 when run from the command line as the same user.
:/www/lists/conf$ ls -ld /var/lock/mailman drwxrwsr-x 2 root list 80 Mar 27 18:31 /var/lock/mailman
How about
ls -ld /var/lock
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/27/2013 7:24 PM, Bob R wrote:
$ ls -ld /var/lock lrwxrwxrwx 1 root root 9 May 1 2012 /var/lock -> /run/lock
and /run and /run/lock ?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 7:28 PM, Mark Sapiro <mark@msapiro.net> wrote:
$ ls -ld /run/lock; ls -ld /run drwxrwxrwt 5 root root 100 Mar 27 19:49 /run/lock drwxr-xr-x 21 root root 780 Mar 27 19:53 /run
Bob R wrote:
OK, I'm grasping at straws here, but the issue appears to be that the 'list:list' user:group can't create files in /var/lib/mailman/locks, aka /run/lock, but Mailman's qrunners and web cgi's are able to do so.
what does
ps -fAw | grep qrunner
and
ls -l /usr/lib/mailman/cgi-bin
give? The qrunner processes should be user 'list' and the wrappers in cgi-bin should be group 'list' and SETGID. is that the case or are they some other user:group?
Also, I think if you do
sudo -u list touch /var/lib/mailman/locks/test_file
or create an entry in /etc/cron.d/mailman that runs
0,10,20,30,40,50 * * * * list touch /var/lib/mailman/locks/test_file
(i.e. runs the touch command every 10 minutes), you will see the same errors. If this is the case, figure out why. I suspect some security manager must be involved as all the permissions on the directories should allow it.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Wed, Mar 27, 2013 at 5:56 PM, Mark Sapiro <mark@msapiro.net> wrote:
$ sudo groups list list : list
$ ls -l -d /var; ls -l -d /var/lib; ls -l -d /var/lib/mailman; ls -l -d /var/lib/mailman/locks drwxr-xr-x 13 root root 4096 Mar 24 09:23 /var drwxr-xr-x 43 root root 4096 Jan 20 08:41 /var/lib drwxrwsr-x 8 root list 4096 Jan 15 06:48 /var/lib/mailman lrwxrwxrwx 1 root list 17 Jul 17 2012 /var/lib/mailman/locks -> /var/lock/mailman
Do you have SELinux or some other security manager enabled?
No, I didn't install that (I don't think that program is even compatible with the Ubuntu LTS)....
Bob R
Bob R wrote:
lrwxrwxrwx 1 root list 17 Jul 17 2012 /var/lib/mailman/locks -> /var/lock/mailman
What about
ls -ld /var/lock/mailman
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Bob R -
Mark Sapiro