in reply to Re^2: 'A' web server takes another "time out" (sar)
in thread 'A' web server takes another "time out"

Well, that's a bust.. too bad.

How about capturing some regular snapshots with vmstat? Maybe

vmstat 60

and a

vmstat -d 60

piped to a file for a few days (or at least a good bit of time before, during and after the event in question). (These commands may require different syntax if you're on FreeBSD, which I can't test with -- we're basically looking for VM stuff and IO/disk stuff... also see iostat) Maybe also throw in a few vmstat -s's for good measure. This would at least provide a little bit more detail around swap in/out and IO.


Replies are listed 'Best First'.
Re^4: 'A' web server takes another "time out" (sar)
by tye (Sage) on May 04, 2006 at 18:46 UTC

    But I think that'd mostly be less information than I'm currently getting from 'top'. In any case, it doesn't give me the main system data I'm now wanting: which process(es) is creating the flood of new 'httpd's. I tell you, Win32's PerfMon sure looks great in comparison to this hacking....

    - tye