NT Disk Monitoring, OpenBSD Disk Monitoring, 3D Status

[Neil]

Karl R. Balsmeier writes: 

> Howdy, 
> 
> These are but two of the OS's i've been tasked to monitor the disks for. 
> 
> On NT, I get a result that says "connection refused by host".  Should I
> create a nagios user that matches my existing NT/2000 account?  Or is this
> some kind of internal route/proxy error?  It's a large network.

How are you monitoring the disk, is it via NRPE_NT? If so, try this. From 
the nagios machine's console/prompt, do the command below: 

telnet "IP_OF_NT_THAT_RUNS_NRPE" 5666 

You should get similar output below: 

[root at nagios etc]# telnet 10.156.188.159 5666
Trying 10.156.188.159...
Connected to 10.156.188.159.
Escape character is '^]'. 

If you didnt get a connection, go to the NT machine and do this: 

netstat -na|find "5666" 

The output should contain LISTENING and so on. 

If there was an output, I could say that are some devices that's filtering 
that traffic such as firewall. 

Just my 2 cents.
> 
> On OpenBSD, it's saying "disk not mounted or nonexistant", yet when I do a
> df, there's /dev/wd0a.  Should I trim it to wd0? 
> 
> --------
> I built this nagios setup on an openbsd 3.0 machine, and 3D status map
> doesn't work, any suggestions?  Right now it tries to save the status.wrl as
> a file instead of parsing it.  That tells me I need to activate something
> other than the php I already have running, right?  What would that be? VRML?

I used cortvrml plugin for IE or Netscape. :) It saves it because you don't 
have the plugin.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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