Cisco Cisco Prime Network Registrar 8.3 Fehlerbehebungsanleitung
Cisco Prime Network Registrar IPAM 8.3 MySQL Database Replication Guide
21
Replication Monitor Event
Callout Manager Script
The monitor could not connect to the Passive
Master (slave)
replmon_slave_connect_error_callout.sh
The monitor reconnected to the Passive Master
(or slave) server after a prior disconnect
replmon_slave_reconnect_callout.sh
The monitor detected that the slave has begun
to lag behind the master beyond the lag
NotificationThreshold as defined in the
replication monitor’s configuration file
(mysql_replication_monitor.properties),
located under
located under
$INCHOME
.
replmon_slave_lag_start_callout.sh
The monitor detected that the slave has
completely resynchronized with the master
after a prior notified lag
replmon_slave_resynched_callout.sh
To configure the Callout Manager to fire on any of the events listed above, you need to create
the shell script to be executed for each event, and then define these scripts in the Callout
the shell script to be executed for each event, and then define these scripts in the Callout
Manager properties file for the appropriate events.
The section of the
The section of the
callout_manager.properties
file that pertains to the Replication
Monitor is shown below.
#
# Callouts defined for the MySQL Replication Monitor
# Each of the callouts defined below will be passed the
# latest replication status values.
# These include:
# MasterSeq - The sequence number found on the Active Master
# SlaveSeq - The sequence number found on the Passive Master (or slave)
# PurgeTo - The last binary log file number that was purged.
# Errors - The number of errors encountered since the monitor was started.
# This includes connecting to the master or slave and any purge errors.
# Lag - The current lag between Active and Passive Masters. (Lag = MasterSeq -
SlaveSeq).
#
# The monitor was started
#replmon.started = replmon_started_callout.sh
# The monitor was stopped
#replmon.stopped = replmon_stopped_callout.sh
# The monitor could not connect to the Active Master server
#replmon.master.connect.error = replmon_master_connect_error_callout.sh
# The monitor reconnected to the Active Master server after a prior disconnect
#replmon.master.reconnected = replmon_master_reconnect_callout.sh
# The monitor could not connect to the Passive Master (or slave) server
# Callouts defined for the MySQL Replication Monitor
# Each of the callouts defined below will be passed the
# latest replication status values.
# These include:
# MasterSeq - The sequence number found on the Active Master
# SlaveSeq - The sequence number found on the Passive Master (or slave)
# PurgeTo - The last binary log file number that was purged.
# Errors - The number of errors encountered since the monitor was started.
# This includes connecting to the master or slave and any purge errors.
# Lag - The current lag between Active and Passive Masters. (Lag = MasterSeq -
SlaveSeq).
#
# The monitor was started
#replmon.started = replmon_started_callout.sh
# The monitor was stopped
#replmon.stopped = replmon_stopped_callout.sh
# The monitor could not connect to the Active Master server
#replmon.master.connect.error = replmon_master_connect_error_callout.sh
# The monitor reconnected to the Active Master server after a prior disconnect
#replmon.master.reconnected = replmon_master_reconnect_callout.sh
# The monitor could not connect to the Passive Master (or slave) server