Bug 44476 - Apache service fails to start due to missing dependency
Summary: Apache service fails to start due to missing dependency
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Win32 MSI Installer (show other bugs)
Version: 2.2.8
Hardware: PC Windows 2000
: P2 major (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Keywords: MassUpdate
Depends on:
Reported: 2008-02-23 21:00 UTC by Michael Fischer
Modified: 2018-11-07 21:09 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Michael Fischer 2008-02-23 21:00:10 UTC
The Apache service fails to start. Corresponding entry in the application log:

"The Apache service named  reported the following error:
>>> DocumentRoot must be a directory     . "

However, one is able to start the service manually after login into Windows,
using the same httpd.conf

The directive Apache is complaining about looks like this:

DocumentRoot //Tiny/vboxsrv/www/htdocs/

or like that:

DocumentRoot "//Tiny/vboxsrv/www/htdocs/"

Windows, however, cannot resolve this URI for Apache before its Browser service
has started. Therefore the Apache service depends on Browser service, really.

And Apache's error message in the application log is misleading, to say the least.

Workaround: On Windows use "regedt32" ("regedit" won't work!) and add "Browser"
to the value "DependOnService" in
Comment 1 Takashi Sato 2008-02-24 01:02:38 UTC
I don't think Apache service depends on Browser service since not all Apache 
httpd users use Windows Network.
Comment 2 Michael Fischer 2008-02-24 04:23:30 UTC
(In reply to comment #1)
> I don't think Apache service depends on Browser service since not all Apache 
> httpd users use Windows Network.

Strange logic: Then we wouldn't even need an Apache service under Windows, since
not all httpd users will start Apache automatically during boot time. And there
is no mentioning in the docs or the httpd.conf itself that Windows network
should not be used when starting Apache as a service during boot time.

I am just suggesting to add the "Browser" dependency per default at installation
time and all cases (network - no network) would be handled "out of the box"
without fiddling around with the registry.
Or we put something up in the docs like: "Windows network not supported when
using Apache as a service."
Right now it's a real and really time wasting bug.
Comment 3 William A. Rowe Jr. 2008-05-06 14:09:45 UTC
The right answer doesn't seem to be adding the Browser service, in fact there
are no Windows services which depend upon that service starting.  It would be
interesting to know which mechanism most windows services do use when they
have external file system references.

Commenting so this bug falls into my filtered list of bugs I'm pondering.
Comment 4 William A. Rowe Jr. 2018-11-07 21:09:56 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.