Monitors pointed to OPMS receive -97 "Checkpoint did not respond" error

Document ID : KB000071416
Last Modified Date : 21/02/2018
Show Technical Document Details
Introduction:
All scripts are receiving error -97 "checkpoint did not respond from our OPMS station." What should be done to resolve this?
Instructions:
There can be many causes of a -97 for an OPMS. 

This article discusses some approaches to help determine what is wrong.

Let's start by running the command below.  A healthy OPMS will show as follows:

# monit summary
 
     
Process 'tunnel-client'                 Running
System <your host name>          Running
Process 'api'                               Running
Process 'httpbroker'                     Running
Process 'assetsmanager'             Running
Process 'resultbroker'                  Running
Process 'fpm'                             Running
Process 'redis-server'                  Running
Process 'rbtm1'                           Running
Process 'rbtm1-Xvfb'                   Running
Process 'rbtm2'                           Running
Process 'rbtm2-Xvfb'                    Running
Process 'rbtm3'                            Running
Process 'rbtm3-Xvfb'                    Running
Process 'rbtm4'                            Running
Process 'rbtm4-Xvfb'                     Running
Process 'php-fpm'                          Running
Process 'nginx'                             Running
File 'jmeter-jail-proc'                     Accessible
Filesystem 'devshmfs_warning'    Accessible
Filesystem 'devshmfs_critical'     Accessible
Filesystem 'rootfs_warning'         Accessible
Filesystem 'rootfs_critical'            Accessible
Process 'fcgiwrap'                          Running
Process 'bm_proxy'                       Running



So far so good.  Now that we can see that monit is running properly, let us test connectivity to CA’s ASM site by running the following command:
 
# curl -v asm.ca.com
 
There are 3 possible outputs from curl.
 
1. Fail to reach asm.ca.com due to no network or unknown host.
* Could not resolve host: asm.ca.com; No address associated with hostname
* Closing connection 0
curl: (6) Could not resolve host: asm.ca.com; No address associated with hostname
 
2. Your Linux system is using a proxy server to get out to the internet and causing interference:
* About to connect() to asm.ca.com port 80 (#0)
* Trying 72.32.41.105...
* Connected to asm.ca.com (72.32.41.105) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: asm.ca.com
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: text/html; charset=utf-8
< Content-Length: 718
<
< HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Access Denied (policy_denied)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
Your system policy has denied access to the requested URL.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
 
3. Successfully reached asm.ca.com which means you do have connectivity.
 
* About to connect() to asm.ca.com port 80 (#0)
* Trying 72.32.41.105...
* Connected to asm.ca.com (72.32.41.105) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: asm.ca.com
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Cache-Control: no-cache
< Pragma: no-cache
< Content-Type: text/html; charset=utf-8
< Content-Length: 718
<
< HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Access Denied (policy_denied)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
Your system policy has denied access to the requested URL.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
 
 
As you can see, the first output suggests that there is a network issue on the OPMS server.  The second output shows the proxy server is rejecting the curl command.  You would need your Linux admin to administer the proxy setup on the OPMS server or if you have one already set up, verify that the proxy URL is correct.