Balazs Rauznitz <[EMAIL PROTECTED]> wrote: > > It's happened to me four times the past few weeks that in a very > lightly used QA environment replication is dying. The symptoms are that > Exec_master_log_pos gets stuck somewhere, while Read_Master_Log_Pos > gets incremented as the master has new updates. There is always a > max-mysqld process that would not die on a restart, only kill -9 makes > it go away, after which replication is hosed. > > The funny thing is that the production environment with 100 times the > load is working OK. > > MySQL 4.0.16 on linux 2.4.x >
What is the value of Slave_SQL_Running in the SHOW SLAVE STATUS output? Is there anything in the error log? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
