LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   nagios status (https://www.linuxquestions.org/questions/linux-newbie-8/nagios-status-831003/)

divyashree 09-08-2010 10:49 AM

nagios status
 
I am monitoring one windows client from my linux server ,it is showing an error like this :
Quote:

F:\ Drive Space CRITICAL 09-08-2010 21:12:21 0d 0h 58m 9s 3/3 (Return code of 139 is out of bounds)

What does this mean ?

quanta 09-08-2010 10:57 AM

Did F drive exist on your Windows? Post the nsclient++ configuration file.

TB0ne 09-08-2010 10:58 AM

Quote:

Originally Posted by divyashree (Post 4091523)
I am monitoring one windows client from my linux server ,it is showing an error like this :

What does this mean ?

It means either that you've got a mistake in your Nagios client configuration, or the drive is getting full.

If you tried to Google for this, you'd have found lots in the Nagios forums/archives. Usually related to a misconfiguration, or the attempt by the Windows client to get drive states from a non-local device.

divyashree 09-08-2010 11:21 AM

Quote:

Originally Posted by quanta (Post 4091537)
Did F drive exist on your Windows? Post the nsclient++ configuration file.

Yes bro F drive exist on that machine and its free 100GB out of 120 GB

TB0ne 09-08-2010 11:48 AM

Quote:

Originally Posted by divyashree (Post 4091565)
Yes bro F drive exist on that machine and its free 100GB out of 120 GB

Ok...what did you set the alert status to be? And as I asked, is this a local drive??

Code 139 indicates a segfault. So again, you've either got a misconfiguration, a non-local drive, or the device has hit the alert point, and is alerting you.

EricTRA 09-08-2010 12:17 PM

Hello,

Check your client configuration file on the Windows machine. This kind of errors happens, just like TB0ne pointed out, when you have an error in your configuration file. See if your Nagios server is allowed to query the Windows machine, restart the service on Windows and check again.

Kind regards,

Eric

divyashree 09-08-2010 01:36 PM

Quote:

Originally Posted by TB0ne (Post 4091592)
Ok...what did you set the alert status to be? And as I asked, is this a local drive??

Code 139 indicates a segfault. So again, you've either got a misconfiguration, a non-local drive, or the device has hit the alert point, and is alerting you.

I got your point ,this is a local drive but a misconfiguration was leading to that point. I put the wrong drive letter in the configuration.
Thank you.


All times are GMT -5. The time now is 07:27 AM.