![\"ssh\"](\"https:\/\/www.uk-cheapest.co.uk\/support\/wp-content\/uploads\/2015\/04\/ssh-150x150.png\")
Apache Error: (98) Address already in use<\/h2>\nApache Error: (98) Address already in use<\/h2>\nOccasionally your VPS or dedicated server will just not play ball.<\/p>\n
Whenever Apache gives up the ghost it usually a case of restarting the service and within seconds your sites are back online, as if nothing happened. Great!<\/p>\n
# service httpd restart<\/pre>\nMost of the time, this resolves the issue. But, on occasion, apache simply doesn’t want to play. The most common issue we hear about is the Address already in use issue, which looks something like this<\/p>\n
# service httpd restart\r\nStopping httpd: [FAILED]\r\nStarting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80\r\n(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80\r\nno listening sockets available, shutting down\r\nUnable to open logs\r\n [FAILED]<\/pre>\nHow to resolve this apache issue<\/h3>\n
Unless apache is restarting at the time you are trying to restart manually then what we have here is a locked process. Thankfully the resolution is quite simple. We just need to find the locked process, kill it then restart apache as usual.<\/p>\n
Let’s find the locked process id<\/p>\n
# netstat -ltnp | grep ':80'<\/pre>\nThis will return something like this<\/p>\n
tcp \u00a00 \u00a00 :::80 \u00a0:::* LISTEN \u00a0 \u00a0 \u00a03826\/sudo<\/pre>\nNow we have identified the PID as 3826, we just need to kill it<\/p>\n
# kill -9 3826<\/pre>\nWith a little luck, a simple apache start will now get everything working<\/p>\n
# service httpd start\r\n\r\nStarting httpd: [ \u00a0OK \u00a0]<\/pre>\nIf the problem persists then\u00a0review the apache error log to locate the issue:<\/p>\n
# tail -500 \/var\/log\/httpd\/error_log<\/pre>\n","protected":false},"excerpt":{"rendered":"