You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Blue Lang <bl...@calico.gator.net> on 2000/01/28 21:03:04 UTC
config/5665: getting the perror("fopen") in http_config.c:1196 - will not read conf
>Number: 5665
>Category: config
>Synopsis: getting the perror("fopen") in http_config.c:1196 - will not read conf
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Fri Jan 28 12:10:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: blue@calico.gator.net
>Release: 1.3.11
>Organization:
apache
>Environment:
DYNIX/ptx 4.4.6, DYNIX cc: v4.4.5n1019 (00122)
>Description:
apache 1.3.11 compiles successfully, but will not start. we have used both a working
httpd.conf (from a 1.3.9 build) and the default httpd.conf, as well as
a new one. we get the error: httpd: could not open document config file /opt/app/apache_1.3.11/conf/httpd.conf
as supplied by http_config.c, line 1196. we have checked/changed perms
- including trying to start it as root. the path looks correct, etc, etc.
i have tried to look through the source - but stopped at th e ap_pcfg_openfile
definition.
>How-To-Repeat:
got a NUMA-Q? :) i can mail you the truss output, which shows
everything that happens as httpd tries to run.
>Fix:
no - i'm not sure what is causing the fopen failure.
>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! ]