- May 24, 2019 at 2:55 pm #19882
Problem Summary: Why does hvrmaint alert notify about a channel that does not have latency?
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 transactions files present in router directory. The transaction files are present under 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.
To resolve this remove the transaction files in 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 ran 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 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 router directory.
To resolve this remove the cap_state and enroll file from the unnecessary location.
These files will be present under the directory structure $HVR_CONFIG/router/<hubname>/<channelname>/loc_<sourceLocation>
You must be logged in to reply to this topic.