From owner-freebsd-questions Sat Jan 19 6:21:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by hub.freebsd.org (Postfix) with ESMTP id 75EB837B419 for ; Sat, 19 Jan 2002 06:21:28 -0800 (PST) Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by cactus.fi.uba.ar (8.11.6/8.11.6) with ESMTP id g0JEJND37476; Sat, 19 Jan 2002 11:19:24 -0300 (ART) (envelope-from fgleiser@cactus.fi.uba.ar) Date: Sat, 19 Jan 2002 11:19:23 -0300 (ART) From: Fernando Gleiser To: Sean Chittenden Cc: Subject: Re: kill -9 not strong enough... In-Reply-To: <20020118163526.A56293@ninja1.internal> Message-ID: <20020119110834.T36973-100000@cactus.fi.uba.ar> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 18 Jan 2002, Sean Chittenden wrote: > 1st: everyone should use postgres. I hate supporting MySQL. > > 2nd: when MySQL gets wedged, why can't I kill it? kill -9 333 doesn't > seem to get it. I don't think it's a hardware problem because > everything else is ticking along fine and I haven't seen any error > messages anyplace. Any ideas? I remember having this problem a few > years ago on Linux so it seems to be a MySQL prob, but why isn't kill > -9 solving my probs? <:~( -sc Because the process is sleeping in uninterruptable state. It means the process is executing a short syscall, and the overhead of context switching to the signal handler (or terminating the process) is bigger than waiting for the syscall to complete and then executing the signal handler. This is the tipical behavior for file I/O syscalls. I have seen your problem with NFS mounted file systems without o=intr when the NFS server dies. Without o=intr, there is no way to kill a process which is trying to access a file in an NFS mounted file system when the server crashes. Do a 'ps alx' and look at the WCHAN field. It will tell you what the process is waiting for. Fer > > > # ps auxwww|grep mysqld > mysql 333 0.0 1.5 31120 15980 con- R Wed12PM 50:42.10 /usr/local/libexec/mysqld --basedir=/usr/local --datadir=/var/db/mysql --user=mysql --pid-file=/var/db/mysql/ninja1.pid > # kill -9 333 > # kill -9 333 > # kill -9 333 > # ps auxwww | grep mysqld > mysql 333 0.0 1.5 31120 15980 con- R Wed12PM 50:42.10 /usr/local/libexec/mysqld --basedir=/usr/local --datadir=/var/db/mysql --user=mysql --pid-file=/var/db/mysql/ninja1.pid > > > -- > Sean Chittenden > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message