-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi list, Peter,

thanks for the tip with gdb.

At the moment I'm not able to reproduce the cpu-hog,
I only have the backtrace of one such event.

Situation was:

After one or two updates of the master (and perhaps some 
"show slave status" or "show master status" on both machines, 
the slave-machine "hangs", i.e. the mysqld starts eating 
CPU and doing nothing else.
A normal kill is of no use, only kill -9 stops the process.
gdb showed after connectiong to mysqld:

(gdb) bt
#0  0x081488de in chunk_free ()
#1  0x08148663 in free ()
#2  0x0814109f in fclose ()
#3  0x08152847 in vsyslog ()
#4  0x081525ea in syslog ()
#5  0x0806ddd3 in handle_connections_sockets ()
#6  0x0806d64b in main ()
#7  0x0812f194 in __libc_start_main ()
(gdb) c
Continuing.

Then gdb is no longer interruptable with Ctrl+C.

In addition to the cycling mysql-daemon, there is a <defunct> son-process 
of it (probably waiting for the father to accept it's return-code)

mysql    11245 11179 41 20:42 ?        00:08:00 /usr/sbin/mysqld 
mysql    11289 11245  0 20:42 ?        00:00:00 [mysqld <defunct>]


So that's the present state of my findings. To be able to debug
into the source, I recompiled the mysqld from the SRPM, but was not
able to reproduce the cpu-hog behaviour. I only get a blocking
situation when I try to do crosswise replication. Hence I give up
on this problem for the moment. Perhaps the above backtrace lets
somebody have an AHA! moment?

Have a happy day!
Michael
- -- 
Michael Zimmermann (Vegaa Safety and Security for Internet Services)
<[EMAIL PROTECTED]>   phone +49 89 6283 7632    hotline +49 163 823 1195
Key fingerprint = 1E47 7B99 A9D3 698D 7E35  9BB5 EF6B EEDB 696D 5811
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8qXIK72vu22ltWBERAqyOAJ9cVcw/cFYTZ2eQwUbZLQ99SKpRUgCcC877
4ItHMe+3nnY9y/rY+fs0y+0=
=0Jjr
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
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

Reply via email to