Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: Apache Service|
The Apache service named <application path> reported the following error: <error message> before the error.log file could be opened.
More information may be available in the error.log file.
|English: This information is only available to subscribers. An example of English, please!|
|Concepts to understand:|
What is the Apache service?
Apache can also fail to start with event ID 3299 if you have Skype running because Skype will use port 80 and 443 for some incoming connections and prevent Apache from binding to these ports. To fix this, go to your Skype settings under "Tools-->Options-->Advanced-->Connection" and uncheck the box that says "use port 80 and 443 for incoming connections". Then quit/restart Skype for the settings to take effect and then try starting Apache.
Error: httpd.exe: Could not reliably determine the server's fully qualified domain name, using <ip address> for ServerName - To avoid this type of error, if adding a reverse DNS host name (a pointer) for the specified IP address is not possible, edit the Apache httpd.conf configuration file to include the following line:
Make sure to comment out or remove any other ServerName directives.
Restart the Apache server service and the problem should be gone.
DATE TIME [notice] Disabled use of AcceptEx() WinSock32API.
This is not an error, is a warning of Apache, you can disable the AcceptEx() writing in the httpd.con the following:
More info at EV100166.
See the links to "SWSoft Support Article ID: 1326", "Symantec Knowledge Base Document ID: 2004122212462154" and "Trend Micro Support Solution ID: 12430" for information about this event.
Error message: ">>> <date and time> [warn] pid file <application path>/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run? <<<" - From a newsgroup post: "Apache creates the .pid files so that other processes on the machine can find out what the server's pid is prior to communicating with it. Obviously, when Apache isn't running, it doesn't have a pid and thus the file is deleted during a normal shutdown.
That message means that Apache didn't terminate normally and the old .pid file was found when starting. It doesn't really hurt anything unless the reason Apache shutdown previously was catastrophic."
|Private comment: Subscribers only. See example of private comment|
|Links: Symantec Knowledge Base Document ID: 2004122212462154, Trend Micro Support Solution ID: 12430, SWSoft Support Article ID: 1326|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated