Cisco Cisco Prime Network Registrar 8.1 Troubleshooting Guide
Troubleshooting MySQL
• 21
4 Troubleshooting
4.1 Troubleshooting MySQL
4.1.1 Timing Issue
On Solaris systems only, an intermittent problem (Reference: IN-6134) occurs with any script that
needs to shut down the MySQL database, such as
prepslave.sh
. If you see the following
message when any replication script is executed, use the appropriate workarounds described in
“Stopping MySQL Database Server...
MySQL Database Server could not be stopped: pid=<pid#> user=incadmin”
MySQL Database Server could not be stopped: pid=<pid#> user=incadmin”
Table 2 MySQL Timing Issue
Problem
Workaround
MySQL stopped but the script reported it could
not stop the server.
No action is needed and you can ignore message.
MySQL could not stop and the script also
reported it could not stop the server and failed.
Follow these steps:
1. Execute commands to stop and start the
MySQL database.
2. Retry the script that just failed.
4.2 Troubleshooting with the Replication Monitor
The Replication Monitor can report information in two ways. The first is a simple HTML page
and the second is via scripts launched by the Cisco Prime Network Registrar IPAM Callout
Manager.
4.2.1 Monitoring with ReplmonStats.html
Cisco Prime Network Registrar IPAM provides an HTML page called
ReplmonStats.html
,
which is served by the Tomcat server installed on the Production Executive. This page
(
http://localhost:8080/incontrol/ReplmonStats.html
) shows the sequence
number value on both the master and the slave, and calculates the lag between the two values.
The user can see the recent history of the sequence numbers for both servers. A sample page
showing a lag between the sequence numbers of the master and slave servers is shown in Figure 2.