Received: (qmail 11115 invoked by uid 2012); 18 Dec 1998 08:44:47 -0000 Message-Id: <19981218084447.11114.qmail@hyperreal.org> Date: 18 Dec 1998 08:44:47 -0000 From: Doug du Boulay Reply-To: ddb@crystal.uwa.edu.au To: apbugs@hyperreal.org Subject: After kill -TERM http.pid and restart, directory indexing no longer works X-Send-Pr-Version: 3.2 >Number: 3554 >Category: general >Synopsis: After kill -TERM http.pid and restart, directory indexing no longer works >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Fri Dec 18 00:50:00 PST 1998 >Closed-Date: Mon Oct 30 18:47:46 PST 2000 >Last-Modified: Mon Oct 30 18:47:46 PST 2000 >Originator: ddb@crystal.uwa.edu.au >Release: apache_1.3.3 >Organization: >Environment: OSF1 V4.0D 878 alpha running on a 600au personal workstation >Description: I compiled the server with maximum dynamicaly loaded modules and added in mod_perl-1.16_01 and php-3.0.5 as dynamic modules also. all seemed to be working well (for several weeks) until I set Options Indexes FollowSymLinks Includes ExecCGI AllowOverride AuthConfig options to document root directory inaccess.conf (to enable .htaccess files). After restarting the server directory indexing seems to have been disabled. Subsequently, no amount of stopping the server, resetting the original options etc, restarting switches the directory indexing back on. I can however fix the problem by completely rebooting the computer the Apache server is running on, But having done so, shutting down the server and restarting, i get the same no indexes problem (no reading of directory contents and no reading of the index.html file). There seem to be a few errors in the error log also, as indicated below error log [Fri Dec 18 12:10:27 1998] [notice] Apache/1.3.3 (Unix) PHP/3.0.5 mod_perl/1.16_ 01 configured -- resuming normal operations [Fri Dec 18 12:26:24 1998] [warn] child process 598 still did not exit, sending a SIGTERM [Fri Dec 18 12:26:24 1998] [warn] child process 599 still did not exit, sending a SIGTERM [Fri Dec 18 12:26:24 1998] [warn] child process 600 still did not exit, sending a SIGTERM [Fri Dec 18 12:26:28 1998] [notice] httpd: caught SIGTERM, shutting down [Fri Dec 18 12:26:38 1998] [notice] Apache/1.3.3 (Unix) PHP/3.0.5 mod_perl/1.16_ 01 configured -- resuming normal operations [Fri Dec 18 12:26:44 1998] [notice] httpd: child pid 671 exit signal Segmentatio n fault (11) [Fri Dec 18 12:26:56 1998] [notice] httpd: child pid 672 exit signal Segmentatio n fault (11) >How-To-Repeat: >Fix: As stated, the problem is circumvented by starting the server on a cleanly booted system. I can live with this, but I suspect you might want to look at it further. >Release-Note: >Audit-Trail: State-Changed-From-To: open-feedback State-Changed-By: marc State-Changed-When: Fri Dec 18 10:45:08 PST 1998 State-Changed-Why: This is very unlikely to be any issue with Apache, and is probably related to how you are starting it. How are you starting it at boot? Are you sure it is using the same config files when started at boot as when you are starting it later? Are you sure there are no -d or -f flags pointing to different config files that you are missing? Comment-Added-By: coar Comment-Added-When: Thu May 25 11:00:43 PDT 2000 Comment-Added: [This is a standard response.] This Apache problem report has not been updated recently. Please reply to this message if you have any additional information about this issue, or if you have answers to any questions that have been posed to you. If there are no outstanding questions, please consider this a request to try to reproduce the problem with the latest software release, if one has been made since last contact. If we don't hear from you, this report will be closed. If you have information to add, BE SURE to reply to this message and include the apbugs@Apache.Org address so it will be attached to the problem report! State-Changed-From-To: feedback-closed State-Changed-By: slive State-Changed-When: Mon Oct 30 18:47:46 PST 2000 State-Changed-Why: [This is a standard response.] No response from submitter, assuming issue has been resolved. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [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! ]