You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Doug du Boulay <dd...@crystal.uwa.edu.au> on 1998/12/18 09:44:47 UTC

general/3554: After kill -TERM http.pid and restart, directory indexing no longer works

>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:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Dec 18 00:50:00 PST 1998
>Last-Modified:
>Originator:     ddb@crystal.uwa.edu.au
>Organization:
apache
>Release:        apache_1.3.3
>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.
>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 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!         ]