On 06/16/2010 05:33 AM, David Fallon wrote:
Thanks for the suggestion, but unfortunately I've tried that - truss
in this case is attaching post whatever it's blocking on (so I just
see it sleeping), and I haven't yet waited out the problem to see what
happens when/if whatever's blocking times out
On Wed, Jun 16, 2010 at 9:33 AM, David Fallon wrote:
> Thanks for the suggestion, but unfortunately I've tried that - truss
> in this case is attaching post whatever it's blocking on (so I just
> see it sleeping), and I haven't yet waited out the problem to see what
> happens when/if whatever's b
On Wed, Jun 16, 2010 at 9:33 AM, David Fallon wrote:
> Thanks for the suggestion, but unfortunately I've tried that - truss
> in this case is attaching post whatever it's blocking on (so I just
> see it sleeping), and I haven't yet waited out the problem to see what
> happens when/if whatever's bl
Thanks for the suggestion, but unfortunately I've tried that - truss
in this case is attaching post whatever it's blocking on (so I just
see it sleeping), and I haven't yet waited out the problem to see what
happens when/if whatever's blocking times out. Any other ideas?
On Tue, Jun 15, 2010 at 9:
On Tue, Jun 15, 2010 at 1:02 PM, David Fallon wrote:
[ ... ]
> Any suggestions on a solution, or how I might get more info out of
> apache as to what it's doing while everyone's in the read state?
I would try using strace (or ktrace or truss depending on your OS) on the
processes to see what th
Hi, I've been having problems with apache becoming unresponsive, and
was wondering if anyone had any suggestions on what the problem might
be. Basically, periodically, apache will get into a state where all
the workers are stuck reading:
Server Version: Apache
Server Built: Oct 21 2009 10:54:43
Cu
