Highlighted
Trusted Contributor.
Trusted Contributor.
2120 views

Agent Health Problem. The agent did not send events during the last 35 minutes.

Hello Team,

We get these continous/repetaed events (Agent Health Problem. The agent did not send events during the last 35 minutes. No additional information is available.) from one of the windows node. We have reinstalled the agent twice . But the issue remains the same.  Approx we get 50-60 alerts on daily basis. Any help on this is much appreciated.

Thanks

Sri

Labels (1)
0 Likes
15 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Go to Administration->Monitored Nodes, double click this node and tell us the method of Heartbeat used.

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Server-Healthcheck.png

 

Please find the details attached,

 

Thanks

Sri

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Any help on this would be much appreciated. Let me know if you need any additional details.This is the summary on number of events getting created.

    • January: 632
    • February: 376
    • March till today: 365

 

Thanks

Sri.

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Hello,

1) Please provide oa_data_collector information.

# cd /opt/OV/contrib/OpC
# ./oa_data_collector.sh -sap

2) Collect it from /var/opt/OV/tmp/oa_data_{date&time}.tar.gz 

Make sure to collect the information that includes issue occurred timestamp.

 

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

The file is very huge around 50MB. Let me know the exact files, will share it accordingly.

 

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Was not able to upload here. Please find the file in the below link

https://drive.google.com/drive/folders/1CXHSwnEUU49dj6ugFgjm1XmwR7gNnigG?usp=sharing

Thanks

Sri

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Any help on this is much appreciated. Let me know if you need any other details

Thanks in Advance

Sri

0 Likes
Highlighted
Super Contributor.
Super Contributor.

Please provide system.txt if possible.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Dear

Please go through OMI admin guide which talks about health check below,

If the server does not receive an event from an agent within the configured interval, the server can
generate an agent problem event or, if Agent & Server checking is configured, can actively check the
status of the agent before generating an agent problem event.


The server attempts to make two checks using HTTP connections to the agent. The first check opens
a socket connection to verify that the control daemon (ovcd) and communication broker (ovbbccb) are
running.

The second check attempts to get the following additional information from the message subagent
(opcmsga):

Message agent status
Certificate status
Control daemon status
Whether the agent is buffering events for this server
Whether the agent is buffering events for other servers

After the server has received the information from the agent, it generates an agent problem event and
adds the agent output to the event. The agent problem event is always generated, even if the server
check reports a running agent. The status of the agent changes to up only when the server receives
events again from the agent.

Please also check OPC_HB_MSG_INTERVAL agent configuration variable by running ovconfchg -edit, this will tell you at what interval agent is sending heartbeat event.

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

Thanks wil check on this.

Current Agent version 12.0.3. will it help if we upgrade.

 

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi

It does not make sense if you upgrade. Point is please check whether heart-beat issues are seen only for one agent or for all agents. If it is for one agent, check heart beat polling interval and variable which was discussed. Also check whether there are any networking issues on both sides.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.