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
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
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 Ju
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,
LOA
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