If you are having trouble with your Apache server software, you should take the following steps:
Check the errorlog!
Apache tries to be helpful when it encounters a problem. In many cases, it will provide some details by writing one or messages to the server error log. Sometimes this is enough for you to diagnose & fix the problem yourself (such as file permissions or the like). The default location of the error log is /usr/local/apache/logs/error_log, but see the ErrorLog directive in your config files for the location on your
Check the FAQ!
The latest version of the Apache Frequently-Asked Questions list can always be found at the main Apache web site.
Check the Apache bug database
Most problems that get reported to The Apache Group are recorded in the bug database. Please check the existing reports, open and closed, before adding one. If you find that your issue has already been reported, please don't add a "me, too" report. If the original report isn't closed yet, we suggest that you check it periodically. You might also consider contacting the original submitter, because there
may be an email exchange going on about the issue that isn't getting recorded in the database.
Ask in the comp.infosystems.www.servers.unix or comp.infosystems.www.servers.ms-windows USENET newsgroup (as appropriate for the platform you use).
A lot of common problems never make it to the bug database because there's already high Q&A traffic about them in comp.infosystems.www.servers.unix and related newsgroups. These newsgroups are also available via Google. Many Apache users, and some of the developers, can be found roaming its virtual halls, so it is suggested that you seek
wisdom there. The chances are good that you'll get a faster answer there than from the bug database, even if you don't see your question already posted.
If all else fails, report the problem in the bug database
If you've gone through those steps above that are appropriate and have obtained no relief, then please do let The Apache Group know about the problem by logging a bug report.
If your problem involves the server crashing and generating a core dump, please include a backtrace (if possible). As an example,
# cd ServerRoot
# dbx httpd core
(Substitute the appropriate locations for your ServerRoot and your httpd and core files. You may have to use
gdb instead of