Why Does hvrmaint Alert Notify About a Channel That Does Not Have Latency

Issue

I've received an hvrmaint alert that references a channel that doesn't have latency.

Environment

HVR 5

Resolution

To resolve this remove the transaction files in the router directory by running hvrinit with 'Drop Objects' and 'Transaction files and Capture Time' only for the channel whose integrate Job is not present in the GUI.

In this image, hvrinit is run for channel o2oasm

If the channel has been deleted from the HUB it is required that these transaction files are manually removed from the router directory.

If hvrmaint is reporting latency for the capture job which existed before but does not anymore the possible reason for this is that this job was deleted from the scheduler but the cap_state and enroll files for this job are still present under the router directory.

To resolve this remove the cap_state and enroll the file from the unnecessary location.

These files will be present under the directory structure: $HVR_CONFIG/router/<hubname>/<channelname>/loc_<sourceLocation>

Cause

It can happen that the integrate job that previously existed in the channel was deleted for some reason from the GUI without clearing the unprocessed transaction files present in the router directory. The transaction files are present under the directory: $HVR_CONFIG/router/<hubname>/<channelname>/loc_<source>/loc_<target>/<filename>.tx_<target>.

So, when hvrmaint is calculating latency these files are picked up by hvrmaint.