httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Salisbury" <>
Subject [users@httpd] ServerRoot/logs directory needed, no exceptions?
Date Fri, 15 Sep 2006 17:16:44 GMT

Hi Guys,

Wondering if anyone knows of a fix here, though it's not critical but it is kind of annoying.
 Though I make no reference to a 
"ServerRoot"/logs directory in the configuration file, apparently Apache needs one to exist
in order to run.  ErrorLog, TransferLog, 
PidFile, etc.. all those I give complete path names to a directory outside of ServerRoot,
yet for some reason, Apache will not start 
unless there's a /logs directory underneath the ServerRoot, even though nothing seems to be
written there.  If I remove the 
ServerRoot/logs directory, upon startup the ErrorLog ( written where I've told it to be )

"[emerg] (2)No such file or directory: Couldn't create accept lock (/usr/local/webapp/logs/accept.lock.28901)"

If I take my ErrorLog directives and put them just into the VirtualHost blocks, then I get
a different error sent to stdout, saying 
the serverroot/logs directory can not be found.

This is reminiscent of a below bug report.. but that was for 1.3 and I'm running 2.2.2.

I can leave the empty /log directory laying around I suppose.. put it's just not right. ;)

Thanks for any information,


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message