Date: Thu, 8 Feb 2007 20:04:26 +1100 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Neil Doody <neil@mpfspromotions.com> Cc: amd64@freebsd.org Subject: Re: Inspecting processes Message-ID: <20070208090426.GB844@turion.vk2pj.dyndns.org> In-Reply-To: <04d601c74972$37e5b990$a7b12cb0$@com> References: <04d601c74972$37e5b990$a7b12cb0$@com>
next in thread | previous in thread | raw e-mail | index | archive | help
--3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Feb-05 22:08:33 -0000, Neil Doody <neil@mpfspromotions.com> wrote: >I am having a problem in which apache processes are slowly going off on so= me >sort of rampage and I cant trace what is causing it.=A0 Basically over time >httpd processes start hogging 100% cpu and new processes are spawned, until >the apache server is shutdown these remain at 100% and they increase until >they bring the server down. > >I was wondering what tools I can use to see exactly what these processes a= re >doing, why they are stuck and what are they waiting for? Specifically for apache, you could try mod-status (/server-status) with "ExtendedStatus On". This should let you track down the the offending URL. General tools would be ktrace and friends to see what syscalls it is performing. You could also try attaching a debugger and getting a backtrace. This might give you some idea where to start looking. If this isn't a totally static website, my initial guess is that one of the CGI scripts is running amok. --=20 Peter Jeremy --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFyuea/opHv/APuIcRAqaEAJ0eGFw9DU9D/KLFAsbxMVh7+yC1ZwCgrKFb V0enMw+am2BT3gjOVGOVVeo= =r47V -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070208090426.GB844>