Troubleshooting Infrastructure Management Server issues
The following issues are related to Infrastructure Management Server processes:
Agent controller error
When an Infrastructure Management Server is started, the following error message maybe displayed in the TrueSight.log file.
ERROR status_change_msg_rt [ProcessStatusChangeMessageHandler_Rate] Proactive check for FedCacheRuntime status failed. [AgentController] Missing Resource String
java.rmi.NotBoundException: AgentController
By default, this message is suppressed for 15 minutes.
You can suppress this error message for a specific time period by adding the following property in the <TSIM Install Directory>\pw\custom\conf\pronet.conf file:
If the error message occurs after the specified error suppression time period, restart the Infrastructure Management server again. For further assistance, contact BMC Customer Support.
MCDB and xcat file permission error
The Infrastructure Management server fails to start if you have installed an Infrastructure Management server using a non-root user, and the following sequence of actions are performed:
- Restart the cell as a root user.
- Restart the cell as a non-root user.
Probable cause:
After you install the Infrastructure Management server using a non-root user and restart the cell as a root user, the xcat and mcdb files get the root user permissions. If you restart the cell again using a non-root user, the xcat and mcdb file permissions do not allow the Infrastructure Management server to restart.
Resolution:
Do the following to change the xcat and mcdb file permissions:
chmod 774 %MCELL_HOME%/var/<CellName>/xcat
chmod 774 %MCELL_HOME%/var/<CellName>/mcdb
MCDB mismatch log messages
The following log messages maybe displayed in the <TrueSight Infrastructure Management Install Directory>\pw\pronto\logs\MCDBMismatch.log file for an Infrastructure Management Server running in the standalone or cluster mode:
INFO 08/27 11:40:18 MCDBMismatchDetect [main] 600002 pronet.agent_controller.cell.mcdb.mismatch.check.enabled=true
INFO 08/27 11:40:18 MCDBMismatchDetect [main] 600002 pronet.agent_controller.cell.mcdb.mismatch.check.interval.seconds=4200
INFO 08/27 11:40:18 MCDBMismatchDetect [main] 600002 pronet.agent_controller.cell.mcdb.mismatch.deviation.max.percent=1.0
INFO 08/27 11:40:18 MCDBMismatchDetect [main] 600002 pronet.agent_controller.cell.mcdb.mismatch.delta.seconds=3600
INFO 08/27 11:40:18 MCDBMismatchDetect [main] 600002 pronet.agent_controller.cell.mcdb.mismatch.detect.alarmafter.n.times=3
INFO 08/27 11:40:18 MCDBMismatchDetect [main] 600002 pronet.agent_controller.cell.mcdb.mismatch.delay.startup.seconds=4200
INFO 08/27 11:57:40 MCDBMismatchDetect [RMI TCP Connection(16)-10.133.138.107] 600002 Turn debug message on for MCDBMismatchDetect subsystem.
INFO 08/27 12:50:18 MCDBMismatchDetect [Thread-64] 600002 run Started the thread after delay of 4200 seconds. HA Enable=false HAUserProperties.isCurrentNodeWithMasterRole=false
INFO 08/27 12:50:18 MCDBMismatchDetect [Thread-64] 600002 pronet.agent_controller.cell.mcdb.mismatch.check.enabled=true
INFO 08/27 12:50:18 MCDBMismatchDetect [Thread-64] 600002 pronet.agent_controller.cell.mcdb.mismatch.check.interval.seconds=4200
INFO 08/27 12:50:18 MCDBMismatchDetect [Thread-64] 600002 pronet.agent_controller.cell.mcdb.mismatch.deviation.max.percent=1.0
INFO 08/27 12:50:18 MCDBMismatchDetect [Thread-64] 600002 pronet.agent_controller.cell.mcdb.mismatch.delta.seconds=3600
INFO 08/27 12:50:18 MCDBMismatchDetect [Thread-64] 600002 pronet.agent_controller.cell.mcdb.mismatch.detect.alarmafter.n.times=3
Probable cause
The agent controller tries to initialize the MCDB mismatch detection task when the Infrastructure Management server is running in the standalone or cluster mode.
Resolution
You can ignore the log messages. Alternatively, do the following to disable logging of the messages in the MCDBMismatch.log file.
- Go to the <Infrastructure Management server Install Directory>\pw\custom\conf\ directory and open the pronet.conf file using a text editor.
Set the following configuration property to false.
pronet.agent_controller.cell.mcdb.mismatch.check.enabled=false- Save and close the pronet.conf file.
- Restart the Infrastructure Management Server.