Hello Team,
We are facing some error with the drive monitoring.
We have configured few mount point checks on our messaging server with the help of your team's help.
Below is the command that we are using to monitor the same:
$USER1$/check_nrpe -H $HOSTADDRESS$ -c checkdrivesize -a MinWarn=15% MinCrit=10% Drive=C:#_Exc_Data_#DB10_LOG}
The issue is, all such types of checks were working fine and all of a sudden we started receiving the below error and the check went into unknown state:
Filter processing failed: Error: Failed to get size for: 3: Das System kann den angegebenen Pfad nicht finden.
We checked the whole configurations from GUI perspective but no issue was found.
We checked with the technical team and got to know that there was a patching activity performed on the server and since then all such checks went into unknown state with the above mentioned error.
We have a similar case with other server too.
Here, we are putting cluster name(having two active active nodes) at "$HOSTADDRESS$" place. The problem we are facing is: the drives which are hosted on the primary node is showing OK state with correct values, but the drives which are hosted on the secondary node are throwing "unknown" error.
Here also there is a similar kind of error:
Filter processing failed: Error: Failed to get size for: 3: The system cannot find the path specified.
NOTE: The Drives which are having normal letter name is throwing different unknown error :
NSClient - ERROR: Invalid return from command: check_drivesize
but the drives which are NTFS mount points are throwing such errors like:
Filter processing failed: Error: Failed to get size for: 3: Das System kann den angegebenen Pfad nicht finden. &
Filter processing failed: Error: Failed to get size for: 3: The system cannot
Kindly help us at the earliest.
check_drivesize error for drive monitoring
-
aditya.c.anand
- Posts: 56
- Joined: Mon Mar 20, 2017 7:16 am
Re: check_drivesize error for drive monitoring
What version of NSClient++ is installed on the servers?
Can you login to the Nagios server as root and run this test command. (Replace xxx.xxx.xxx.xxx with the IP address of the remote system)
If the Nagios server can connect to the NSClient++ agent, the output of the above should show you the version of the agent.
What type of patching was done on the server and was the firewall enabled?
Can you post the nsclient.log file from this folder C:\Program Files\NSClient++ to this post so we can check it for any errors?
Can you login to the Nagios server as root and run this test command. (Replace xxx.xxx.xxx.xxx with the IP address of the remote system)
Code: Select all
/usr/local/nagios/libexec/check_nrpe -H xxx.xxx.xxx.xxxWhat type of patching was done on the server and was the firewall enabled?
Can you post the nsclient.log file from this folder C:\Program Files\NSClient++ to this post so we can check it for any errors?
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
aditya.c.anand
- Posts: 56
- Joined: Mon Mar 20, 2017 7:16 am
Re: check_drivesize error for drive monitoring
Hello Team,
Below is the output:
-bash-4.2$ /usr/local/nagios/libexec/check_nrpe -H 172.25.44.205
I (0.4.4.19 2015-12-08) seem to be doing fine...
-bash-4.2$
Windows patching was done and firewall was not enabled.
Please find the attached log file.
Please help us.
Below is the output:
-bash-4.2$ /usr/local/nagios/libexec/check_nrpe -H 172.25.44.205
I (0.4.4.19 2015-12-08) seem to be doing fine...
-bash-4.2$
Windows patching was done and firewall was not enabled.
Please find the attached log file.
Please help us.
You do not have the required permissions to view the files attached to this post.
Re: check_drivesize error for drive monitoring
Not much in the log file except this message.
Rejected connection from: 172.25.45.20
What server is that IP address?
One thing to try is to install the latest stable version of the 4.4.xx NSCLient++ service which you can get from here.
http://nsclient.org/download/0.4.4/
If you do that, make sure you backup the nsclient.ini file in case it gets reset back to default.
If it still fails, please post the nsclient.ini file so we can view it.
Rejected connection from: 172.25.45.20
What server is that IP address?
One thing to try is to install the latest stable version of the 4.4.xx NSCLient++ service which you can get from here.
http://nsclient.org/download/0.4.4/
If you do that, make sure you backup the nsclient.ini file in case it gets reset back to default.
If it still fails, please post the nsclient.ini file so we can view it.
Be sure to check out our Knowledgebase for helpful articles and solutions!