[emerg] (28)No space left on device: Couldn't create accept lock (/etc/httpd/logs/accept.lock.15449) (5) solution


[Wed Jan 08 18:50:07 2014] [emerg] (28)No space left on device: Couldn't create accept lock (/etc/httpd/logs/accept.lock.15449) (5)

This may happen when trying to restart Apache and you find it dies right after starting and check /var/log/httpd/error_logs.

What is the cause of this?

  1. You could be out of disk space (if you're not then see #2 and below)
  2. You're out of Semaphores, you need to kill all the old ones.


Check to see current Semaphores, if Apache has stopped it should have none.  If you run the command below and see them you need to manually kill them.


ipcs -s
------ Semaphore Arrays --------
key        semid      owner      perms      nsems    
0x00000000 0          apache    600        1        
0x00000000 229377     apache    600        1        
0x00000000 262146     apache    600        1        
0x00000000 294915     apache    600        1        
0x00000000 327684     apache    600        1        
0x00000000 360453     apache    600        1        
0x00000000 1671174    apache    600        1        
0x00000000 1900551    apache    600        1        
0x00000000 8781832    apache    600        1        
0x00000000 8814601    apache    600        1        
0x00000000 8847370    apache    600        1        
0x00000000 8880139    apache    600        1        
0x00000000 8912908    apache    600        1        
0x00000000 8945677    apache    600        1        
0x00000000 8978446    apache    600        1        
0x00000000 13205519   apache    600        1        
0x00000000 13238288   apache    600        1        
0x00000000 13271057   apache    600        1        
0x00000000 13303826   apache    600        1        
0x00000000 13336595   apache    600        1       
 
 

The bash script below will kill all the old semaphores and you should be able to start Apache succesfully after that.


for ipcs in `ipcs -s|awk '{print $2}'`;
do
echo "ipcs=$ipcs"
ipcrm -s $ipcs
done

 


Tags:

emerg, couldn, etc, httpd, logs, wed, restart, apache, var, error_logs, disk, semaphores, manually, ipcs, semaphore, arrays, semid, perms, nsems, bash, succesfully, awk, echo, quot, ipcrm,

Latest Articles

  • How to resize a pdf without losing much quality in Linux Mint Ubuntu Debian Redhat Solution
  • qemu: could not load PC BIOS 'bios-256k.bin' solution
  • Proxmox How To Custom Partition During Install
  • Hyper-V Linux VM Boots to Black Screen, Storage, NIC Not Found Issues
  • Ubuntu Mint How to Fix Missing/Broken /dev and /dev/pts which causes terminal to immediately close exit and not work
  • How high can a Xeon CPU get?
  • bash fix PATH environment variable "command not found" solution
  • Ubuntu Linux Mint Debian Redhat Youtube Cannot Play HD or 4K videos, dropped frames or high CPU usage with Nvidia or AMD Driver
  • hostapd example configuration for high speed AC on 5GHz using WPA2
  • hostapd how to enable and use WPS to connect wireless devices like printers
  • Dell Server Workstation iDRAC Dead after Firmware Update Solution R720, R320, R730
  • Cloned VM/Server/Computer in Linux won't boot and goes to initramfs busybox Solution
  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm