Re: Replication stopping
Il lun, 2004-07-12 alle 13:45, Cemal Dalar ha scritto: To debug the problem. Make SHOW SLAVE STATUS in the slave and check for the error number.. Best Regards, Cemal Dalar a.k.a Jimmy System Administrator Web Developer http://www.gittigidiyor.com http://www.dalar.net - Original Message - From: Nico Sabbi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:08 PM Subject: Replication stopping Hi, it happened again just now, this is the status: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 55463 to server version: 4.0.18-Max-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql show slave status \G *** 1. row *** Master_Host: master Master_User: replica Master_Port: 3306 Connect_retry: 60 Master_Log_File: db-bin.3323 Read_Master_Log_Pos: 437183883 Relay_Log_File: server-relay-bin.005 Relay_Log_Pos: 228252575 Relay_Master_Log_File: db-bin.3323 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_do_db: Replicate_ignore_db: mysql Last_errno: 0 Last_error: Skip_counter: 0 Exec_master_log_pos: 437183883 Relay_log_space: 228252575 1 row in set (0.00 sec) Nico -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Replication stopping
Ok. better check .err files in /usr/local/mysql/data/hostname.err for any errors.. It seems that there isn't any problems on slave but from my experience there can be problem on the slave like auth. For example when replica user can not login to master then 'show slave status' doesn't give any error messages but writes some lines to .err file.. Check those files both in master and in slave.. Best Regards, Cemal Dalar a.k.a Jimmy System Administrator Web Developer http://www.dalar.net - Original Message - From: Nico Sabbi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 2:15 PM Subject: Re: Replication stopping Il lun, 2004-07-12 alle 13:45, Cemal Dalar ha scritto: To debug the problem. Make SHOW SLAVE STATUS in the slave and check for the error number.. Best Regards, Cemal Dalar a.k.a Jimmy System Administrator Web Developer http://www.gittigidiyor.com http://www.dalar.net - Original Message - From: Nico Sabbi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:08 PM Subject: Replication stopping Hi, it happened again just now, this is the status: Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 55463 to server version: 4.0.18-Max-log Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql show slave status \G *** 1. row *** Master_Host: master Master_User: replica Master_Port: 3306 Connect_retry: 60 Master_Log_File: db-bin.3323 Read_Master_Log_Pos: 437183883 Relay_Log_File: server-relay-bin.005 Relay_Log_Pos: 228252575 Relay_Master_Log_File: db-bin.3323 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_do_db: Replicate_ignore_db: mysql Last_errno: 0 Last_error: Skip_counter: 0 Exec_master_log_pos: 437183883 Relay_log_space: 228252575 1 row in set (0.00 sec) Nico -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Replication stopping
Hi, often my slave suddenly stops, reporting these the logs: 040712 12:19:00 Slave I/O thread exiting, read up to log 'db-bin.3323', position 197564621 040712 12:19:10 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'db-bin.3323' at position 197564621 040712 13:48:22 Slave I/O thread exiting, read up to log 'db-bin.3323', position 208931388 040712 13:48:25 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'db-bin.3323' at position 208931388 this is the configuration of the slave: [mysqld] log-bin server-id=20 master-host=master master-port=3306 master-user=replica master-password=*** replicate-ignore-db=mysql replicate-wild-do-table=db1.prc replicate-wild-do-table=db2.provincia_rc replicate-wild-do-table=db3.tc replicate-wild-do-table=prc.% master-connect-retry=60 slave-skip-errors=all How can I understand exactly what is stopping the replication? Thanks, Nico -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Replication stopping
To debug the problem. Make SHOW SLAVE STATUS in the slave and check for the error number.. Best Regards, Cemal Dalar a.k.a Jimmy System Administrator Web Developer http://www.gittigidiyor.com http://www.dalar.net - Original Message - From: Nico Sabbi [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 12, 2004 6:08 PM Subject: Replication stopping Hi, often my slave suddenly stops, reporting these the logs: 040712 12:19:00 Slave I/O thread exiting, read up to log 'db-bin.3323', position 197564621 040712 12:19:10 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'db-bin.3323' at position 197564621 040712 13:48:22 Slave I/O thread exiting, read up to log 'db-bin.3323', position 208931388 040712 13:48:25 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'db-bin.3323' at position 208931388 this is the configuration of the slave: [mysqld] log-bin server-id=20 master-host=master master-port=3306 master-user=replica master-password=*** replicate-ignore-db=mysql replicate-wild-do-table=db1.prc replicate-wild-do-table=db2.provincia_rc replicate-wild-do-table=db3.tc replicate-wild-do-table=prc.% master-connect-retry=60 slave-skip-errors=all How can I understand exactly what is stopping the replication? Thanks, Nico -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
