On Wed, Apr 24, 2002 at 02:32:52PM -0400, vlady wrote: > Hi, > Setting an replication for the first time, I get the following error > message in my slave: > > 020424 13:59:28 Slave: connected to master > '[EMAIL PROTECTED]:3306', replication started in log 'FIRST' at > position 4 > 020424 13:59:29 Slave: did not get the expected error running query > from master - expected: 'Invalid error code' (256), got 'no error' (0) > 020424 13:59:29 Slave: error running query '' > 020424 13:59:29 Error running query, slave aborted. Fix the problem, > and re-start the slave thread with "mysqladmin start-slave". We stopped > at log 'FIRST' position 31632 > 020424 13:59:29 Slave thread exiting, replication stopped in log > 'FIRST' at position 31632 > > If some one knows what can be the reason?
When a MySQL server executes a query and stores a record of it in the replication log (binlog), it also records the result code (or error code) associated with running that query. This allows slaves to make sure that they have the same result (success or failure) when they run the same query. If they notice something wrong, they'll stop dead in their tracks until you have a chance to fix it. I can't say why it happened in your case, but it did. The master had a problem running the original query, but the slave did not. So the slave assumed something is wrong, since it is supposed to be identical to the master. Does that help? Jeremy -- Jeremy D. Zawodny, <[EMAIL PROTECTED]> Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.47-max: up 76 days, processed 2,001,903,357 queries (303/sec. avg) --------------------------------------------------------------------- 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
