Date: Sat, 08 Nov 2008 19:20:51 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: php-cgi frozen with sbwait when SMP enable Message-ID: <gf4lab$c1m$1@ger.gmane.org> In-Reply-To: <d018a9bd0811070708r1479656bk46e9c21295cce6ba@mail.gmail.com> References: <d018a9bd0811070329s30b463b0m6885e1f568217b89@mail.gmail.com> <gf1bc5$lbu$1@ger.gmane.org> <d018a9bd0811070610t6eaa5b08l4b59cc1857e2fbd1@mail.gmail.com> <gf1kka$oj6$1@ger.gmane.org> <d018a9bd0811070708r1479656bk46e9c21295cce6ba@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Ken Chen wrote: > I capture something. > > Please check the PID 57776. It's CPU time never change since my previous > mail here. > > web4# ps alx | grep php-cgi | grep -v grep | grep sbwait > 65534 57776 47240 0 4 0 182328 84984 sbwait I ?? 2:02.12 > /usr/local/bin/php-cgi You're right and it is strange. I don't know why this would happen but some things that come to mind are: * Does lighttpd have some kind of status page or a diagnostic utility to show you the states of FastCGI processes? * Does lighttpd have a facility to "reap" old PHP processes? For example, mod_fcgid has a maximum lifetime setting for FastCGI processes. * You could try sending a SIGABRT to the php-cgi process to get a core dump and inspect it. Without debugging symbols it will probably give you the name of the function it's been waiting in. [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkV2IMACgkQldnAQVacBch53wCfcV2w0bP+fT3azObPoSqAqilm CSsAoIk2qZzev8zZflM5O/3/+6VSKBNo =fCn7 -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gf4lab$c1m$1>