replication stopped

2006-07-06 Thread Pooly
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:

Re: replication stopped

2006-07-06 Thread Dominik Klein
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

Re: replication stopped

2006-07-06 Thread Dominik Klein
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]

Re: replication stopped

2005-06-05 Thread Gleb Paharenko
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,

Re: replication stopped

2005-06-05 Thread Atle Veka
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

replication stopped

2005-06-03 Thread jabbott
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

Re: R: Replication stopped without reason

2003-07-25 Thread Egor Egorov
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

R: R: Replication stopped without reason

2003-07-25 Thread trashMan
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

Replication stopped without reason

2003-07-24 Thread trashMan
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

Re: Replication stopped without reason

2003-07-24 Thread Dominicus Donny
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

R: Replication stopped without reason

2003-07-24 Thread trashMan
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