You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Lincoln Yeoh <ly...@mecomb.com> on 2000/02/14 03:17:55 UTC
general/5752: If httpd is started with mod_php, it dies when sent SIGHUP
>Number: 5752
>Category: general
>Synopsis: If httpd is started with mod_php, it dies when sent SIGHUP
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Sun Feb 13 18:20:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: lylyeoh@mecomb.com
>Release: 1.3.9
>Organization:
apache
>Environment:
Red Hat Linux release 6.1 (Cartman) Kernel 2.2.12-20 on an i686
egcs-2.91.66
Apache/1.3.9 (Unix) PHP/3.0.14 mod_fastcgi/2.2.2 mod_ssl/2.4.10 OpenSSL/0.9.4
>Description:
If httpd is started with mod_php, it dies when sent SIGHUP
With mod_php uncommented in httpd.conf.
/etc/rc.d/init.d/httpd start
killall -HUP httpd will kill httpd. POOF!
With mod_php commented in httpd.conf
/etc/rc.d/init.d/httpd start
Then killall -HUP httpd will not kill httpd.
There is an interesting workaround:
comment out mod_php, start httpd, then uncomment mod_php, killall -HUP.
PHP will be activated, and SIGHUP doesn't kill httpd now. Weird huh?
Related issues:
logrotate on Redhat installations will SIGHUP httpd everytime it rotates the logs-
which is either weekly, or when the log gets bigger than a certain size. So this may
explain some of the problems where the httpd dies "randomly".
>How-To-Repeat:
>Fix:
No but workaround:
comment out mod_php, start httpd, then uncomment mod_php, killall -HUP.
PHP will be activated, and SIGHUP doesn't kill httpd now.
>Release-Note:
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database automatically because of the potential for mail ]
[loops. If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request from a ]
[developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]