(by peter pilsl)

  apache claims 'no space on device'

keywords : apache ipcs semaphore no space on device lock accept

tested with apache 2.0.43 and 2.0.45

When dealing with mem-leaks in my mod_perl-apps I ran into a curious apache-problem. After a while apache could not be started but failed with strange errors like:

[emerg] (28)No space left on device: Couldn't create accept lock

[crit] (28)No space left on device: mod_rewrite: could not create rewrite_log_lock Configuration Failed

There was definitely enough space on the device where the locks are stored (default /usr/local/apache2/logs/). I tried to explicetely different Lockfiles using the LockFile-directive but this did not help. I also tried a non-default AcceptMutex (flock) which then solved the acceptlock-issue and ended in the rewrite_log_lock-issue.

Only reboot of the system helped out of my crisis.

Solution: There were myriads of semaphore-arrays left, owned by my apache-user.

ipcs -s | grep nobody

Removing this semaphores immediately solved the problem.

ipcs -s | grep nobody | perl -e 'while (<STDIN>) { @a=split(/\s+/); print `ipcrm sem $a[1]`}'

peter at 2003-04-11 (updated 2003-04-11)

serial : 224

If you found any nonsense in this entry or want to see important improvements, I would appreatiate to receive your comments at

disclaimer : all these entries are part of my very private knowledgebase that I created while solving problems. Many solutions are taken from other webpages or from usenet. There is no warranty for this entries of course. Some of the articles are even stupid and one day you might even find the name of my prefered pizza-service in here, cause I always forget about it. Remember : This is my knowledgebase. If you need professional support and are willing to pay for it just email me at
For enlightment take a look at