Re: Server Staus information by other means

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I know that ps doesn't show you what the httpd threads are doing, but on my RedHat system the "top" command shows which CGI script is executing, and that is a step forward.  Of course, this only works if the CGI is looping or using a lot of CPU (otherwise it doesn't show in the "top" command).

Look around in the /proc directory - this has a wealth of information on running processes (it is where "top" gets its information). The numeric subdirectories are the process IDs (PIDs)

On 04/12/06, Nikolai Lusan <nikolai.lusan@xxxxxxxxxxx> wrote:
Greetings one and all,

I have a little problem I am trying to track down ...

We run a number of production boxen that are apache 2.0 with php5,
occasionally we hit MaxClients and the site becomes unreachable (until
some things time out and come back to papa). We know that some of the
time this is a database issue, the rest we suspect are php code related
issues.

What I am after is something that will give me the information from
mod_status, but without using a port 80 connection (obviously the thing
is at MaxClients and not taking connections to the server). I basically
need a full list of the requests that are being processed when this
happens and the vhosts they are being processed within (so I can track
down the actual problem).

Having asked this question elsewhere let me spell out a few things,

  a) apache2ctl status [and full-status] use lynx and a connection to
     the server so will not do the job (MaxClients having been hit and
     the server not taking connections).
  b) ps [with any options] give a process listing and does not supply
     the information I require (that being the list of requests being
     processed).
  c) Raising MaxClients is not a solution because:
        1) If I do that and we come close to MaxClients with all
           processes using the average memory resources the machine will
           swap out and die(tm).
        2) The problem will keep occurring just with more connections
           made at the time of the problem and I will still not have the
           list of information I need.
   d) Given that the problem is happening infrequently (at about 3 weeks
      separation) polling once a second is just going to waste resources
      on my server and still not provide me with what I need.

Sorry if that sounds a little abrupt, but I have had too many people
suggest all these things, assuming I hadn't thought of all of them and
their impact (infact most people don't realise the impact of what they
are suggesting).

If anyone knows of some utility (or set of options to the apache2 binary
I could use) I would be most appreciative. The other option I had
thought of was trying to get a single worker (we are using mpm-prefork)
running and listening only to loopback, but I am a little unsure if this
is actually possible or how to go about it.

Thanks in advance.
--

Nikolai Lusan
Systems Administrator

Hitwise Pty. Ltd.
Level 7 / 580 St Kilda Road
Melbourne, Victoria 3004
Australia
Phone: +61 3 8530 2400
Fax:  +61 3 9529 8907
www.hitwise.com.au
nikolai.lusan@xxxxxxxxxxx


Worldwide:  •  United States  •  United Kingdom  •  Australia  •  New
Zealand  •  Singapore  •  Hong Kong

To subscribe to our complimentary monthly newsletter, visit:
http://www.hitwise.com.au/

The information transmitted may be confidential, is intended only for
the person to which it is addressed, and may not be reviewed,
retransmitted, disseminated or relied upon by any other persons. If you
received this message in error, please contact the sender and destroy
any paper or electronic copies of this message. Any views expressed in
this email communication are those of the individual sender, except
where the sender specifically states otherwise. Hitwise does not
represent, warrant or guarantee that the communication is free of
errors, virus or interference.


---------------------------------------------------------------------
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




--
Steve Swift
http://www.swiftys.org.uk
[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux