Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
Topic: Service Error after trying to jail Apache in Windows |
|
Author |
|
rhossis
Joined: 30 Mar 2011 Posts: 9
|
Posted: Mon 18 Apr '11 14:59 Post subject: Service Error after trying to jail Apache in Windows |
|
|
Hi, I have an Apache server 2.2.17 on Windows XP SP2 and have been trying to "harden" the server. With regards, to Apache, I set up an "apache" user which would limit potential damage to the system in case of a compromise as per the following modsecurity post http://www.modsecurity.org/blog/archives/2006/06/jailing_apache.html. After putting in all the user settings, my service has completely failed, but I can launch the httpd from command line or by double clicking on it. What could be the problem here? Kindly help. I tried to jail Apache but have jailed myself
The error from event viewer is "The description for Event ID ( 7024 ) in Source ( Service Control Manager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Apache2.2, 1 (0x1)." |
|
Back to top |
|
glsmith Moderator
Joined: 16 Oct 2007 Posts: 2268 Location: Sun Diego, USA
|
Posted: Tue 19 Apr '11 3:02 Post subject: |
|
|
Try logging in yourself once with the apache account. That builds the registry settings for the user as well as the Docs & Settings folders as well. |
|
Back to top |
|
Kanashii
Joined: 17 Jul 2006 Posts: 155 Location: Porando
|
Posted: Tue 19 Apr '11 7:59 Post subject: |
|
|
try check
runas.exe /user:apache httpd.exe
Then:
check privilege to directory and check log |
|
Back to top |
|
|
|
|
|
|