On Wed, Mar 11, 2009 at 11:58 AM, John Campbell <jcampbe...@gmail.com> wrote: > On Wed, Mar 11, 2009 at 11:13 AM, Rob Marscher > <rmarsc...@beaffinitive.com> wrote: > >> Is it running but not processing requests? Or is it no longer running? >> Maybe it's rotating log files but doesn't start back up properly? >> Otherwise, maybe some type of odd segmentation fault? > > I am pretty sure it is running, but as soon as I found the issue, I > restarted it immediately, so I can't say for sure. There is nothing > in either the syslog or apache logs that is illuminating. The only > thing that is obvious is the lack anything in the logs during the time > apache was not working. > > I rotate the logs manually (probably not the best idea), but it can't > be a log rotate issue.
What is the platform? Is it Linux? Are workers dying? Run: # ps fax | grep httpd before and during and after the problem to see if workers are actually running. If they are running (as opposed to crashing) then use tcpdump and WireShark to find out what port the browser is using. Can the browser even establish a socket? If yes, note the port number. Then (quickly) use lsof to determine which process the socket is connected to like: # lsof | grep <portnumber> Then run gdb on that pid like: # gdb /usr/sbin/httpd <pid> This will load symbols and give you a prompt. Then type 'bt' for a backtrace. If you don't know how to interpret the backtrace, post it here. Mike -- Michael B Allen Java Active Directory Integration http://www.ioplex.com/ _______________________________________________ New York PHP User Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/show_participation.php
