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 Any ideas ? Thanks, Balazs -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
