Contains troubleshooting information
Unknown Software Version
Symptom:I do not know which version of OPMS I have.
Solution:You can find the version number of the OPMS Installer in the
Versions of individual OPMS components can be obtained by running the following command:
dpkg -l | grep asm-
RHEL / CentOS
yum list installed | grep asm-
Symptom:The installation did not complete successfully.
Solution:Re-run the installer. If this operation does not resolve the issue, open the installation log file from the
/opt/asm/opms/logsdirectory and search for errors.
Checkpoint Availability Error
Symptom:The log shows the following error message:
'Checkpoint not available'
Solution:Ensure that the tunnel client is operating correctly. Search for tunnel client errors in the
/var/log/optunnel/optunnel-client.logfile. To verify that the OPMS stack components are operating correctly, execute the following command:
All operating components are listed as
Accessible. If the component status is different, view the logs in the
/var/log/smartpopdirectory for each component separately.
Finally, ensure that the system hardware resources such as memory and disk space are sufficient.
Alert Email Sent on Activation
Symptom:You activated the
Solution:You can ignore these email alerts until the checkpoint is fully up and running.
Alert Email Sent on Tunnel Client Restart
Symptom:You received an email alert from the
monitservice that the tunnel client service was restarted.
/var/log/optunnel/optunnel-client.logfile for the root cause. Temporary connection problems to
opp.cloudmonitor.ca.comcause the restarts. When the connection is closed or broken, the tunnel client is terminated. The
Monitservice then starts a new instance that reconnects to the tunnel server.
Graphical Installer Launch Issue
Symptom:The installer starts in console mode instead of graphical mode.
Solution:Run the following command before launching the installer:
<user>is the standard non-root user that you originally used to log into the computer.