Question #59177 on OurDelta changed:
https://answers.launchpad.net/ourdelta/+question/59177
Status: Answered => Open
AdmobDB is still having a problem:
Thanks Mark for responding my question.
I stop the replication by using "stop slave" command. And restart the
replication using "start slave" command. Here are the log entries from
"error-log" on slave db server,
===================
090128 0:46:11 [Note] Slave SQL thread initialized, starting replication in
log 'mysql-bin.000005' at position 98, relay log '
./mysqld-relay-bin.000001' position: 98
090128 0:46:11 [Note] Slave I/O thread: connected to master
'[email protected]:3306', replication started in log 'mysq
l-bin.000005' at position 98
090128 0:46:11 [Note] ReplicationMule: MULE_BEHIND - new(4), old(98)
090128 0:46:11 [Note] ReplMule::dumpEvent - new status(1) master_log_pos(4),
dump_pos(98), file_size(4)
090128 0:46:11 [Note] ReplMule::dumpEvent - new status(2) master_log_pos(98),
dump_pos(98), file_size(4)
090128 0:53:36 [Note] Slave: received end packet from server, apparent master
shutdown:
090128 0:53:36 [Note] Slave I/O thread: Failed reading log event, reconnecting
to retry, log 'mysql-bin.000005' position 98
090128 0:53:36 [ERROR] Slave I/O thread: error reconnecting to master
'[email protected]:3306': Error: 'Lost connection
to MySQL server at 'reading initial communication packet', system error: 111'
errno: 2013 retry-time: 60 retries: 86400
090128 0:54:05 [Note] Slave I/O thread killed during or after a reconnect done
to recover from failed read
090128 0:54:05 [Note] Slave I/O thread exiting, read up to log
'mysql-bin.000005', position 98
090128 0:54:05 [Note] Error reading relay log event: slave SQL thread was
killed
090128 0:54:08 [Note] Slave SQL thread initialized, starting replication in
log 'mysql-bin.000005' at position 98, relay log '
./mysqld-relay-bin.000001' position: 98
090128 0:54:08 [Note] Slave I/O thread: connected to master
'[email protected]:3306', replication started in log 'mysq
l-bin.000005' at position 98
090128 0:54:08 [Note] ReplicationMule: MULE_BEHIND - new(4), old(98)
090128 0:54:08 [Note] ReplMule::dumpEvent - new status(1) master_log_pos(4),
dump_pos(98), file_size(4)
090128 0:54:08 [Note] ReplMule::dumpEvent - new status(2) master_log_pos(98),
dump_pos(98), file_size(4)
090128 1:25:11 [Note] Slave I/O thread killed while reading event
090128 1:25:11 [Note] Slave I/O thread exiting, read up to log
'mysql-bin.000006', position 654415
090128 1:25:11 [Note] Error reading relay log event: slave SQL thread was
killed
090128 1:25:14 [Note] Slave SQL thread initialized, starting replication in
log 'mysql-bin.000006' at position 654415, relay l
og './mysqld-relay-bin.000002' position: 654552
090128 1:25:14 [Note] Slave I/O thread: connected to master
'[email protected]:3306', replication started in log 'mysq
l-bin.000006' at position 654415
090128 1:25:14 [Note] ReplicationMule: MULE_BEHIND - new(4), old(654415)
090128 1:25:14 [Note] ReplMule::dumpEvent - new status(1) master_log_pos(4),
dump_pos(654415), file_size(4)
090128 1:25:15 [Note] ReplMule::dumpEvent - new status(2)
master_log_pos(654415), dump_
=======
Also on the slave following commands are disabled,
reset master;
While following command returns error when relication is stopped, i.e stop
slave,
show binary logs;
Let me know if you have question/needs additional details from our side.
Thank you,
--
You received this question notification because you are a member of
OurDelta-developers, which is an answer contact for OurDelta.
_______________________________________________
Mailing list: https://launchpad.net/~ourdelta-developers
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ourdelta-developers
More help : https://help.launchpad.net/ListHelp
