Hello. Resolve a stack trace and provide it to the list. See: http://dev.mysql.com/doc/refman/5.0/en/crashing.html http://dev.mysql.com/doc/refman/5.0/en/using-stack-trace.html
Now about the replication problem. As I've understood you have triggers only on the slave. In my opinion, to solve this problem, you should just recreate all triggers after an upgrade. If you use mysqldump during the upgrade, it should recreate triggers automatically. Ian Sales (DBA) wrote: > Gleb Paharenko wrote: > >> Hello. >> >> Please, could you explain what does it mean 'Signal 11 without fail'. >> Usually after receiving such a signal MySQL crashes. Of course, it >> should do this in normal circumstances. What is in the error log? Check >> if the problem still exists on official binaries of 5.0.18. >> >> >> > - sorry, idiomatic English :-) "signal 11 without fail" means it > *always* causes a signal 11. I have tried upgrading to 5.0.18, but > encountered the same problem. I downgraded back to 5.0.16 because the > DEFINER functionality added to triggers in 5.0.17 does not allow > triggers to be fired off my replicated queries. > > - the error log gives a stack dump, and says this "could be because you > hit a bug". I'm looking for a little more information than that... > > - ian > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [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]