Daniel B. Thurman wrote:
To my surpise, I somehow ended up not
being able to shutdown httpd!
# killall httpd
# service httpd start
Starting httpd: [ OK ]
# service httpd stop
Stopping httpd: [FAILED]
# service httpd restart
Stopping httpd: [FAILED]
Starting httpd: (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
and yet all of the httpd daemons are still running.
I can stop all of the httpd with the killall command
but the point is, why does the service command fail
to shut it down?
Note, that when rebooting, httpd starts up with no
reported errors as far as I can tell, it is not in the
messages logs.
Any pointers on this?
That's usually caused by the httpd.pid file being in a different spot
than the startup script expects it to be. The "stop" looks for that
file and uses the PID inside it to kill Apache. If the file can't
be found, it aborts the shutdown.
The scripts expcect the pid file to be /var/run/httpd/httpd.pid. Check
your /etc/httpd/conf/httpd.conf file and make sure that the "PidFile
argument agrees with that.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer ricks@xxxxxxxx -
- AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
- -
- Always remember you're unique, just like everyone else. -
----------------------------------------------------------------------
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
