New disk status showing "UNKNOWN"

[IT.Toonz]

Will update thanks! 

 

We did try with NSCP-0.4.0.172-x64 but got "Connection refused" error.

 

Should we enable "Interact with desktop"?

 

Thanks

Ananth.

 

From: Travis Runyard [mailto:travisrunyard at gmail.com] 
Sent: Tuesday, July 17, 2012 11:13 PM
To: Nagios Users List
Subject: Re: [Nagios-users] New disk status showing "UNKNOWN"

 

Try installing version .0.3.9 of the NSClient and make sure the service is
running as the System user.

 

http://files.nsclient.org/x-0.3.x_STABLE/NSClient%2B%2B-0.3.9-x64.msi

 

-Travis

On Mon, Jul 16, 2012 at 8:55 PM, IT.Toonz <it.toonz at gmail.com> wrote:

Hi,

We have been using Nagios 3.2.3 (Fully automated Nagios) for over 2 years
now, it is working wonderfully well.....

Recently we added a new "G" drive to one of our monitored storage's and
added that drive's entry in the cfg file but we are getting UNKNOWN status.
We restarted the server, restarted Nagios, pre-flight checks are not showing
any errors. Command is correct, if we replace the parameters with another
drive, like "F", the "F" drive gets correctly monitored.

Server is Windows 2008 64bit R2, NSClient++ - 0.3.8.76 rest of the drives
was already monitored. We checked the drive permissions and noticed that
creator owner didn't have any permission, so we added that, but still no
change.

 

>From the nsclient logs.

2012-07-17 08:57:43: error:modules\CheckSystem\CheckSystem.cpp:810:
Unhandled exception describing PID: 4: Failed to open process: 4: 

2012-07-17 09:07:43: message:modules\CheckSystem\CheckSystem.cpp:813: Failed
to open process: 4:

 



 

Please advice!

anth


----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120718/8a639eef/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 48594 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120718/8a639eef/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 49830 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120718/8a639eef/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 64670 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120718/8a639eef/attachment-0002.jpg>
-------------- next part --------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null