Thanks Benjamin,
I found that kill -9 seems to be the only way to kill the hung process.
I'll see if I can find another way.
Here is the output of mysqlbug:
>Submitter-Id: Paul Borghese
>Originator: -
>Organization: -
>MySQL support: [none]
>Synopsis: MySQL process hanging
>Severity: < serious>
>Priority: <[ medium ] (one line)>
>Category: mysql
>Class: <[ support ]>
>Release: mysql-3.23.46 (Source distribution)
>Environment:
<machine, os, target, libraries (multiple lines)>
System: Linux groupstudy.com 2.2.20 #1 Wed Dec 12 12:11:07 EST 2001 i586
unknown
Architecture: i586
Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
/usr/bin/cc
GCC: Reading specs from
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
Compilation info: CC='gcc' CFLAGS='' CXX='c++' CXXFLAGS=''
LDFLAGS=''
LIBC:
lrwxrwxrwx 1 root root 13 Aug 10 2000 /lib/libc.so.6
-> libc-2.1.3.so
-rwxr-xr-x 1 root root 4106572 Oct 10 19:55
/lib/libc-2.1.3.so
-rw-r--r-- 1 root root 20336836 Oct 10 19:55 /usr/lib/libc.a
-rw-r--r-- 1 root root 178 Oct 10 19:55 /usr/lib/libc.so
Configure command: ./configure --prefix=/usr/local/mysql-3.23.46
--localstatedir=/home/httpd/mysql --with-mysqld-user=nobody
Perl: This is perl, version 5.005_03 built for i386-linux
Thanks!
Paul Borghese
-----Original Message-----
From: Benjamin Pflugmann [mailto:[EMAIL PROTECTED]]
Sent: Saturday, December 07, 2002 1:20 PM
To: Paul Borghese
Cc: [EMAIL PROTECTED]
Subject: Re: Single process hanging
Hello.
On Sat 2002-12-07 at 12:09:44 -0500, [EMAIL PROTECTED] wrote:
> I am running MySQL 3.23.46 under Linux kernel 2.2.20 as the back-end
of
> an active website. On occasion mysql seems to stop responding. When
I
> log into the server one of the MySQL processes is consuming a
> substantial amount of CPU resources (i.e. it is on the top of the list
> when viewing the “top” command.).
>
> Killing all of the mysql processes (using killall -9) and restarting
> seems to fix the problem.
Arg! Do NOT use killall -9 on your database, except if you are
prepared to screw it majorly or know about all the consequences. This
signal does not give MySQL the tiniest chance to do some cleanup.
Using -9 should only be your *very* last resort.
> After reading the list archives, I came upon the idea of repairing and
> optimizing the database using the command:
> ./mysqlcheck -or -A -u root –p
>
> But when I type that command, I receive the following message
>
> error : The handler for the table doesn't support check/repair
>
> for most of the tables in the database.
MySQL 3.23.46 supports check/repair only for tables of type MYISAM.
The error simply means that you are using different table types. Use
SHOW CREATE TABLE to determine the table type and then read in the
manual how to do maintenance for it.
> Any ideas/suggestions on how I can troubleshoot the hung process
The answers depend a lot on what/how you are using (e.g. did you
compile it yourself). You could start with presenting the full output
of mysqlbug.
HTH,
Benjamin.
--
[EMAIL PROTECTED]
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail
<[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
