The Network People Support Forums

Mail::Toaster => General Questions => Topic started by: Guest on March 23, 2004, 04:26:18 AM

Title: Get this error multilog: fatal: unable to lock directory....
Post by: Guest on March 23, 2004, 04:26:18 AM
When i run the services start command i get this error message

bsd# services start
multilog: fatal: unable to lock directory /var/log/mail/submit: access denied
Couldn't chown /var/log/mail to 83: Operation not permitted
Couldn't find cronolog!
at ./sendlog line 95
multilog: fatal: unable to lock directory /var/log/mail/submit: access denied
Title: Get this error multilog: fatal: unable to lock directory....
Post by: matt on March 23, 2004, 09:01:49 AM
There's a 98% probability that it means you didn't follow the directions. Seriously, I build every release at least a few times before it get's released.

There's also the possibliity that there's a bug in the code that you uncovered by setting a config value that's unexpected, but that doesn't appear to be the case.

Matt
Title: Get this error multilog: fatal: unable to lock directory....
Post by: eugeniopacheco on November 04, 2004, 10:48:11 AM
I had this same problem and to solve it by removing the lock files from each directory in /var/log/mail/ and making them again:

First I stopped the services (services stop) then I did:

rm /var/log/mail/smtp/lock
touch /var/log/mail/smtp/lock
chown qmaill:qnofiles /var/log/mail/smtp/lock

rm /var/log/mail/submit/lock
touch /var/log/mail/submit/lock
chown qmaill:qnofiles /var/log/mail/submit/lock

rm /var/log/mail/send/lock
touch /var/log/mail/send/lock
chown qmaill:qnofiles /var/log/mail/send/lock

rm /var/log/mail/pop3/lock
touch /var/log/mail/pop3/lock
chown qmaill:qnofiles /var/log/mail/pop3/lock

And when I started the services (services start) it worked all right.

Hope this helps you...

Eugenio