Summary: | net-www/apache-2.0.59-r1 init script finds no running apache2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ilya Eremin <eremini> |
Component: | New packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | minor | CC: | hkmaly |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ilya Eremin
2006-10-17 09:30:44 UTC
This is a one time only bug, because start-stop-deamon doesn't have information about the running apache. Do a manual stop (killall apache), zap the service (/etc/init.d/apache2 zap), then start it (/etc/init.d/apache2 start). After that you shouldn't have any issues. Please let me know if this doesn't work for you. I am stupid.... That worked fine, thanks a lot and sorry for bugging you. Keep up the great work. It's not one-time bug. The way /etc/init.d/apache2 is now written, start-stop-daemon (at least the one from baselayout-1.12.9-r2) will be unable to stop apache2 after every update of apache2 binary, which is not so often, but still not only one-time. (Reason is start-stop-daemon will compare inode of current /usr/sbin/apache2 with all processes and find no match, because running apaches are refering to now deleted previous version) It is true that sequence apache2ctl stop, /etc/init.d/apache2 zap, /etc/init.d/apache2 start will do correct restart, but it will still be better if /etc/init.d/apache2 restart really worked. |