Our commserve server and two mediaagents use nagios, specifically the NSClient++ most recent version, to monitor services, CPU and RAM, etc.
I have noticed something odd with the mediaagents and nagios. Whenever I try to do a live browse, I get a string of warning emails from our nagios server about not being able to connect to whichever mediaagent I'm trying to do the Live Browse from. This occurs on both media agents with great reliability - if I browse on MA2, I get emails about MA2 within minutes. If I browse on MA1, I get the same.
After the live browse is finished, within another few minutes I get "recovery successful" emails from nagios saying that it's re-established the connection.
The contents of the email are always this:
Subject is always like: ** PROBLEM: mediaagent01 - CPU Usage is UNKNOWN **
Body is always like:
CHECK_NRPE STATE UNKNOWN: Socket timeout after 25 seconds.
CHECK_NRPE: Invalid packet version received from server.
I am wondering what the heck the mediaagents are doing during a live browse that causes these errors to occur so consistently. Anyone else using NSClient++ or nagios in general to monitor their commvault infrastructure?