The problem has vanished since then.
Pity that there seems to be no simple way to diagnose the problem in innodb.
check table has showed no problems. Seems like I have to stay away from innodb for the time
being :(.
thomas
Victor Pendleton wrote:
Do you have anything in the show processlist? Are you using innodb table types and a rollback is occurring?
-----Original Message----- From: Thomas - Lists To: [EMAIL PROTECTED] Sent: 8/24/04 6:49 AM Subject: runaway process eating all cpu-time?
Hi there,
after a system-crash I got the following problem.
Some seconds after starting mysql (v4.0.20) a process will stay
there taking all cpu-time it can get (99.9% ;)) ... and it can't be terminated,
just killed completely.
mysqlcheck ran through without any problems, the logs tell nothing.
I just did a strace on the last process doing that:
---
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348119
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
time(NULL) = 1093348120
sched_yield() = 0
time(NULL) = 1093348120
rt_sigprocmask(SIG_SETMASK, NULL, [HUP INT QUIT PIPE TERM TSTP 32], 8) =
0
rt_sigsuspend([HUP INT QUIT PIPE TERM TSTP] <unfinished ...>
--- SIGRT_0 (Real-time signal 0) ---
---
Any idea where to look at that problem further?
The system is a linux - redhat-7.2 with dual athlon-mp, 2 GB ram, running kernel-2.4.26.
Using the official mysql.com-binaries (rpm-install).
TIA,
Thomas
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]