Hello everybody,
I am pretty novice at Nagios, so I hope that my question were easy to answer,
or at least, I could get a hint...
The thing is that I want to monitor a mapped unit on a Windows host, just to
check the available disk space (i.e., drive U:, that might be "myuser at
server\users").
What I have done is the following:
At windows.cfg:
(...)
define host {
use windows-server
host_name myhost
alias My Windows host
address xxx.xxx.xxx.xxx
}
(...)
define service {
use generic-service
host_name myhost
service_description Check C: disk space
check_command check_nt!USEDDISKSPACE!-l c -w 80 -c 90
}
define service {
use generic-service
host_name myhost
service_description Check mapped unit U: disk space
check_command check_nt!USEDDISKSPACE!-l u -w 80 -c 90
}
(I had previously installed NSClient++ at the host...).
The thing is that I get a correct answer from C:, but U: gives me the error
"Return code of 139 is out of bounds".
So obviously I guess that it's not that what I should have done.
I checked the log file at the Windows host and it only says -repeatedly: NSCA
Configuration missmatch. I don't think it has anything to see with my problem
though...
Any hint?
Thanks in advance.
Alejandro
==
Alejandro Sanchez - alejandro.sanc...@ite.es
IT Department
Institute of Electrical Technology - www.ite.es
Valencia - Spain
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Nagios-users mailing list
Nagios-users@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
