>Number: 2507
>Category: other
>Synopsis: Complete server lockup
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Jun 26 01:10:00 PDT 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3
>Environment:
Linux maxxserv.ml.org 2.0.34 #1 Tue Jun 9 20:58:36 MDT 1998 i586 unknown
Slackware Linux, Kernel 2.0.34
>Description:
Here is the basic problem, if you attempt to kill the server daemon by killing
it's PIDs(killall -p apachectl) and then try to start the server once
again(apachectl start) apache v1.3 reports the following:
bash# ./apachectl start
usage: /usr/local/apache/sbin/httpd
(start|stop|restart|fullstatus|status|graceful|help)
start - start httpd
stop - stop httpd
restart - restart httpd if running by sending a SIGHUP or start if
not running
fullstatus - dump a full status screen; requires lynx and mod_status enabled
status - dump a short status screen; requires lynx and mod_status enabled
graceful - do a graceful restart by sending a SIGUSR1 or start if not running
help - this screen
./apachectl start: httpd could not be started
and I have not been able to start the server in 1hour, it's still down... I
dont want to reboot!
>How-To-Repeat:
Kill apache via it's PID(s) and then try to start the server once again.
>Fix:
No clue... but I could kill v1.2 this way.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
