Troubleshooting

Contains troubleshooting information 
cacm82
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 
/opt/asm/opms/version.txt
 file.
Versions of individual OPMS components can be obtained by running the following command:
Debian
dpkg -l | grep asm-
RHEL / CentOS
yum list installed | grep asm-
Installation Failure
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/logs
 directory 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.log
 file. To verify that the OPMS stack components are operating correctly, execute the following command:
monit summary
All operating components are listed as 
Running
 or 
Accessible
. If the component status is different, view the logs in the 
/var/log/smartpop
 directory 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
 
monitoring alerts feature in the installer. You receive email alerts during the installation and after restarting the checkpoint host.
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 
monit
 service that the tunnel client service was restarted.
Solution:
 Browse the 
/var/log/optunnel/optunnel-client.log
 file for the root cause. Temporary connection problems to 
opp.cloudmonitor.ca.com
 cause the restarts. When the connection is closed or broken, the tunnel client is terminated. The 
Monit
 service 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:
export XAUTHORITY=/home/<user>/.Xauthority
Where:
 
<user>
 is the standard non-root user that you originally used to log into the computer.