On Thu, Oct 18, 2007 at 06:33:22PM -0400, Joshua Slive wrote: > On 10/18/07, Tom Hart <tomhart@xxxxxxxxxxx> wrote: > > Hey everybody. I'm getting a 500 error code (Internal Server Error), > > that doesn't tell me anything about why the error happened. Naturally I > > looked to the error.log but that contained nothing. At this point I > > decided to try "LogLevel notice" to up the verbosity and number of > > messages written to the error log, and still nothing. The real pain > > about this problem is it seems to happen no matter what file or > > directory I'm requesting, and if I refresh it comes through fine, every > > time. Obviously I can't fix the problem if I can't find it. Does anybody > > have any ideas on common things that may cause this, or how I might be > > able to get the log to actually log the error? > > Are you sure it is an Apache error and not something generated by a proxy? > > If so, I'd start by stripping out modules. Take out the non-standard > and third-party modules first and see if that gets rid of the problem. That's certainly a good idea. You can also run apache in single process mode with httpd -X and watch it with strace/truss. Nick Kew's mod_diagnostics is helpful too sometimes. Use a tool to dump all your IO and watch it closely. Mod_Security can write complete dumps of your IO and you can configure it to run in four different request phases in apache. This can be of additional help. Good luck, Christian --------------------------------------------------------------------- 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
|