Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a CRON script that emails daily using mutt.

This script has begun to fail, and I now get an email from cron stating:

Can't dotlock /root/sent.

Couldn't lock /root/sent

Could not send the message.

The wierd thing is that I get this email from cron fine, but mutt can't send email. The cron job is run by root, so I don't think this is a permissions issue.

Can anyone shed some light on this?

share|improve this question
cron reports are sent using sendmail by default, so unless you've changed that, it's still the same. – Chris S Aug 23 '10 at 20:06
up vote 2 down vote accepted

Is there a /root/sent file/directory/link/other existent ? Is there an other process which take the lock for a while ? Check with lsof -n | grep /root/sent. The rights are good on this file ?

share|improve this answer
There was a /root/sent.lock file, I deleted this file and it worked! – Josiah Aug 25 '10 at 20:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.