OVIS ovprobes module fails to start

Overview

In some seldom situations the OVIS ovprobes module might fail to start on UNIX based remote probe systems. We experienced this behaviour especially after unexpected system restarts of the remote probe system after e.g. power drops. This document describes the issue, the impact and an operational method to fix the problem.

Issue

In seldom situations the OVIS ovprobes module might fail to start on UNIX based remote probe systems.

Impact

Impact of this situation is that the HP OpenView Internet Services Management System does not receive measurement results (metrics) from the particular remote probe system. This information can be retrieved from the OVIS Configuration Manager on the OVIS Management System via the status information page.

By clicking on the "Probe Data Received" tab the particular system will show for all probes configured the status "No Probe Info". Also the dashboard will show "No probe information" tags for affected measurememnts.

More detailed information can be obtained by logging into the remote probe system and checking the OV system status with "ovc". For this purpose log into the system and become root or change to the user id OVIS is using. Afterwards follow the instructions found below:

# cd /opt/OV/bin
# ./ovc -status
ovcd OV Control CORE (3369) Running
ovbbccb OV Communication Broker CORE (3377) Running
ovprobes OV Internet Services Probes PROBE Aborted
ovtiprn HP OpenView TIPs Runner TIPsRunner (3405) Running
#

Trying to restart ovprobes will usually not resolve the problem:

# ./ovc -restart ovprobes
(ctrl-7) Error in the target component.
#

Solution

Explicitly kill OV environment and start afterwards:

# ./ovc -kill
# ./ovc -start
# ./ovc -status
ovcd OV Control CORE (3588) Running
ovbbccb OV Communication Broker CORE (3596) Running
ovprobes OV Internet Services Probes PROBE (3620) Running
ovtiprn HP OpenView TIPs Runner TIPsRunner (3624) Running
#

/HOME/Topics