replication stopped
Hi, recently, our slave stopped for a duplicate key error (which is a bug to me : http://bugs.mysql.com/bug.php?id=9929 ) How do you usually check automatically that slaves are up and running ? -- http://www.w-fenec.org/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: replication stopped
How do you usually check automatically that slaves are up and running ? echo show slave status\G|mysql -u user -ppassword|grep -i slave.*running|grep -i no mail -s MySQL Slave stopped [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: replication stopped
echo show slave status\G|mysql -u user -ppassword|grep -i slave.*running|grep -i no mail -s MySQL Slave stopped [EMAIL PROTECTED] well, actually echo show slave status\G|mysql -u user -ppassword|grep -i slave.*running|grep -i no echo .|mail -s MySQL Slave stopped [EMAIL PROTECTED] sorry -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: replication stopped
Hello. Replication process runs tree threads, two on slave and one on master, so if your master was running with no free space it's behavior unpredictable and replication could halt. SHOW SLAVE STATUS usually reports errors. I would stop replication and setup it again using, for example, LOAD DATA FROM MASTER. But if the data size is huge enough I would check the master.info and relay-log.info and continue the replication from where it had stopped. See: http://dev.mysql.com/doc/mysql/en/slave-logs.html [EMAIL PROTECTED] wrote: I took a couple of days vacation last week and naturally the /data partition of my database server filled up because of something I was running and had forgotten about. So my backup guy, thinking to help out, gzipped all my .bin logs. Now I am noticing replication seems to have stopped on my other server. Not sure if the two events are related or not. It could be that things got all hosed up not because of the gzipping but because the partition filled up in the first place? Anyway, what do I do now? Do I need to do a new dump and start replication all over again? --ja -- 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]
Re: replication stopped
It's impossible to say pretty much without more information. Have you checked the error log on the slave? How about 'SHOW SLAVE STATUS'? Did your backup guy gzip all binlogs, if so that would most definitely stop replication. Atle - Flying Crocodile Inc, Unix Systems Administrator On Fri, 3 Jun 2005 [EMAIL PROTECTED] wrote: I took a couple of days vacation last week and naturally the /data partition of my database server filled up because of something I was running and had forgotten about. So my backup guy, thinking to help out, gzipped all my .bin logs. Now I am noticing replication seems to have stopped on my other server. Not sure if the two events are related or not. It could be that things got all hosed up not because of the gzipping but because the partition filled up in the first place? Anyway, what do I do now? Do I need to do a new dump and start replication all over again? --ja -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
replication stopped
I took a couple of days vacation last week and naturally the /data partition of my database server filled up because of something I was running and had forgotten about. So my backup guy, thinking to help out, gzipped all my .bin logs. Now I am noticing replication seems to have stopped on my other server. Not sure if the two events are related or not. It could be that things got all hosed up not because of the gzipping but because the partition filled up in the first place? Anyway, what do I do now? Do I need to do a new dump and start replication all over again? --ja -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: R: Replication stopped without reason
trashMan [EMAIL PROTECTED] wrote: YesThe replication stopped in the next 60 secs. I've tried to change connect-retry to 30 secs without result. What do you mean without result? -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [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]
R: R: Replication stopped without reason
After 60~120 secs the replication stopped. Setting the parameter Connect-rety to 30 secs doesn't change the situation: the slave lose the connection and the replication is stopped. Massi -Messaggio originale- Da: Egor Egorov [mailto:[EMAIL PROTECTED] Inviato: venerdì 25 luglio 2003 10.34 A: [EMAIL PROTECTED] Oggetto: Re: R: Replication stopped without reason trashMan [EMAIL PROTECTED] wrote: YesThe replication stopped in the next 60 secs. I've tried to change connect-retry to 30 secs without result. What do you mean without result? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Replication stopped without reason
Hi, I've a big problem!!! The replication start and work correctly but after 10 minutes slave don't update anymore. I must do slave stop - slave start for restarting replication. In the log there are not error. The slave is connected to internet with a isdn-router while the master is connected with a cdn. What can i do for stabilize the replication?? Massimiliano -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Replication stopped without reason
Assume you leave the default connect-retry to 60 secs. Is the replication still stopped in the next 60 secs after that? Me fail English? That's unpossible ###___Archon___### - Original Message - From: trashMan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 24, 2003 3:38 PM Subject: Replication stopped without reason Hi, I've a big problem!!! The replication start and work correctly but after 10 minutes slave don't update anymore. I must do slave stop - slave start for restarting replication. In the log there are not error. The slave is connected to internet with a isdn-router while the master is connected with a cdn. What can i do for stabilize the replication?? Massimiliano -- 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]
R: Replication stopped without reason
YesThe replication stopped in the next 60 secs. I've tried to change connect-retry to 30 secs without result. :-/ Max -Messaggio originale- Da: Dominicus Donny [mailto:[EMAIL PROTECTED] Inviato: giovedì 24 luglio 2003 11.36 A: [EMAIL PROTECTED] Oggetto: Re: Replication stopped without reason Assume you leave the default connect-retry to 60 secs. Is the replication still stopped in the next 60 secs after that? Me fail English? That's unpossible ###___Archon___### - Original Message - From: trashMan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 24, 2003 3:38 PM Subject: Replication stopped without reason Hi, I've a big problem!!! The replication start and work correctly but after 10 minutes slave don't update anymore. I must do slave stop - slave start for restarting replication. In the log there are not error. The slave is connected to internet with a isdn-router while the master is connected with a cdn. What can i do for stabilize the replication?? Massimiliano -- 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] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
