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
Hi Victor,
thanks for your reply.
Victor Pendleton wrote:
Do you have anything in the show processlist? Are you using innodb table
types and a rollback is occurring?
mysql show processlist;
Hey folks,
before posting to the bugs-list I would like to try it here to get some help :).
Every now and then MySQL-4.0.13 crashes on my Dual-Athlon-MP-machine.
Its not reproducible nor I know a query which does it.
(The log shows that at the end, so no query :-( :
Trying to get some variables.
