• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Httpd won't stop/start/restart

J

Janson0

Guest
Hi All,

I have been working on this problem for like 6 hours.

I was changing my hostname on my box and after i changed the hostname in /etc/hosts and /etc/sysconfig/network, I also changed it in Plesk.

Ever since that time, I have been unable to get httpd to restart, even after setting everything back the way it was. Also, none of my domains are resolving.

If you ping the domains, they are going to the correct IP address, but they are not pulling up any sites. This leads me to believe that Plesk is messed up on my box.

Whenever I try to restart httpd, I get the following error messages:
Stopping httpd: [FAILED]
Starting httpd: [Wed Nov 02 23:32:41 2011] [warn] module ssl_module is already loaded, skipping
(98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
[FAILED]

I have tried:
netstat -anp | grep ':80.*LISTEN'
tcp 0 0 :::80 :::* LISTEN 2503/httpd

That seems right... but its just weird that I cannot stop the httpd service.

Please let me know if you have any answers? Plesk seems to not want to start because it cannot restart the httpd service.

Thanks,
Michael
 
Hey Igor,

Thanks for your help. I have actually checked that strategy a few times, and done some more digging. Apparently, the httpd.pid file is not being created by the httpd start program, and so while the process is being created by the httpd start code, it is never registering a pid file with the process id.

In both the httpd.conf and the /etc/init.d/httpd files i have the PidFile entry set to "/var/run/httpd.pid", but it is not being created.

Since the /etc/init.d/httpd stop operation checks for the httpd.pid file to determine if there is a process running, even though the httpd process is running... it cannot stop it because it does not know its process id. This is why the stop operation is failing and then there is already the process running on port 80.

If I manually create an httpd.pid file with the right process id, the stop function works correctly.

Any thoughts?
 
Since apache fails to stop gracefully, try to kill it with

# killall -9 httpd

Then try to start it. In case of failure please post latter lines from /var/log/httpd/error_log
 
Back
Top