Hello, I've been struggling with a very bizarre Apache problem. I thought I would post on this in case this is a bug with Apache itself. I'm running Apache 2.2.4 under WINDOZE. It came as part of the MS4W mapping package (http://www.maptools.org/ms4w/), all included software and versions can be found on that page, but are replicated here for convenience: Apache HTTP Server version 2.2.4 PHP version 5.2.1 MapServer CGI 4.10.1 MapScript 4.10.1 (CSharp, Java, PHP, Python) Includes support for Oracle 10g, and SDE 9.1 data (if you have associated client/dlls) MrSID support built-in GDAL/OGR 1.4.0 and Utilities MapServer Utilities PROJ Utilities Shapelib Utilities Shp2tile Utility OGR/PHP Extension 1.0.0 OWTChart 1.2.0 These are all installed in the c:\ directory...c:\ms4w\Apache\bin etc. Apologies in advance for working under windows. I am forced to it. Apache is installed as a service. My problem is this: I am trying to convince Apache to access a windows network share that has been mapped to a local drive (Z:). Originally, the permissions on the share were set so that only specific users could access it, including myself. This means that I could access it using Windows Exploder, but Apache could not because it runs as a local system user by default. I could see in the Apache error logs that its read attempts to z: were being denied. Under Services, I changed the user that Apache "logs on" as to myself. Then when I tried to access the share (via MapServer), I received no errors in the error log...but neither was I receiving the image. I then proceeded to work with the folks on freenode/#apache for a couple of hours. I tried adding an Alias to my httpd.conf file. The alias and its associated Directory directive are as follows: Alias /test/ "z:/small/" #try to get access to mapped network drives! <Directory "z:/small/"> Order allow,deny Allow from all </Directory> After adding this to httpd.conf, I am unable to get the service to start. Starting it from the command line: c:\ms4w\Apache\bin\httpd -k start Does not work because its a service, so I have to type: httpd -k start -n "Apache MS4W Web Server" (Stopping and starting the service in this way with the default httpd.conf works fine) With the above Alias and Directory lines added to my conf file, starting it from the command line fails SILENTLY. The error and access logs are created but are completely empty. The only message in the Windoze Event Viewer is that Apache quit with an exit code of 1. The (very helpful)folks in #apache tried their best to find out why those innocuous-looking directives would slay Apache from starting. We couldn't determine why. My hunch was that it was related to the windows drive in some way. After much hassling it was deduced that Apache, when installed following the directions in MS4W to run this bat: @ECHO OFF REM This installs and starts the apache service cd Apache\bin httpd -k install -n "Apache MS4W Web Server" net start "Apache MS4W Web Server" cd ..\.. :ALL_DONE Will run as a local system user (obvious). Whats not obvious is after setting the credentials of the service to run as myself using the Services plugin under Admin Tools, Apache still seems to be running as a local user. I don't know if this is because one of the helper/worker threads is being spawned with the wrong credentials, but the "Log On" tab of the Properties of the Apache service did not seem to make a difference. By uninstalling the service and starting Apache standalone from the console, I was able to access the restricted network drive. Running Apache in this way seemed to guarantee it would be ran as ME and not a local acct. This could be a problem with windows Service management, the way MS4W installs the service, or with Apache itself. I thought I would post here before generating a bug report. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|