>Number: 1619 >Category: general >Synopsis: Apache fails to start up when $ServerRoot/logs is missing. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Sat Jan 3 09:20:00 PST 1998 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.2.4 >Environment: $ uname -a BSD/OS maple.oeko.net 2.1 BSDI BSD/OS 2.1 Kernel #0: Sun Feb 16 20:09:06 MET 1997 [EMAIL PROTECTED]:/usr/src/sys/compile/OEKONET.maple i386
Apache 1.2.4 >Description: First I would like to illustrate the problem: maple 18:06:34 ~/W3/conf $ ls .. ./ ../ auth/ c2/ cgi/ conf/ doc/ log/ pcgi/ There is a dir "log" instead of the usual "logs". maple 18:06:35 ~/W3/conf $ /bin/sh start-apache maple 18:06:39 ~/W3/conf $ open: No such file or directory Cannot open lock file: /home/geek/W3/logs/accept.lock.16291 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This message is produced from within the routine main and immediately followed by an exit(1). maple 18:06:50 ~/W3/conf $ /bin/pwd /home/geek/W3/conf ^^^^^^^^^^^^^^^^^^ This is only for you to see that i am in the right direcory, and the file system relations do make sense. What I would expect: A directive to tell where to open this file (which I can't find anymore once Apache is running), or (b) a place in the documentation mentioning the need for this file. Solution: I placed a soft link: ln -s log logs which solved the problem for me. >How-To-Repeat: Starting Apache 1.2.4 w/o a dir named "logs" under the ServerRoot should reproduce the problem. >Fix: Yes, mention this in the README or so >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. ]
