I am using 1 master (4.0.13 named PISSARRO ) and 3 slaves (4.0.15); of course the my.ini are different in the master and slaves. Today for an error (I thinked to be on my slave) I executed in sequence these commands:
change master to master_host='pissarro',master_user='root',master_password='',master_log_file ='pissarro-bin.313',MASTER_LOG_POS=4 SLAVE START and then thread slave start as you can see below ! but this command were on my MASTER ! 031013 22:33:15 InnoDB: Started MySql: ready for connections. Version: '4.0.13-max-nt-log' socket: '' port: 3306 031014 11:17:32 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'pissarro-bin.352' at position 4 031014 11:17:45 Slave I/O thread exiting, read up to log 'pissarro-bin.352', position 98405708 031014 11:17:45 Slave SQL thread exiting, replication stopped in log 'pissarro-bin.352' at position 3 Immediately I see the error and execute a slave stop But it seem is possible to start a slave command on a master to update itself ! There is way to avoid this error ? tks in advance --------------------------------------------------------- Massimo Petrini c/o Omt spa Via Ferrero 67/a 10090 Cascine Vica (TO) Tel. +39 011 9505334 Fax +39 011 9575474 E-mail [EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
