[Nagiosplug-help] check_nwstat

[Brian Hellman]

I have mine setup as individual host checks. I was  not on the list when 
that message was sent out. Part of the reason for my setup is I have the 
servers setup by city. For example CHI1, Chicago-snapshot are in the 
Chicago Servers group.  Is there a way to set it up using hostgroups? It 
would be nice to know for future reference

Alex Hargrove wrote:

>I think it's a plugin issue, because it used to work for me, then I updated the plugins to the latest version, and it started doing the same thing to me also...
>
>I too would be interested in a fix for this...
>
>PS-Say, I sent a message a while ago to this list about using hostgroups instead of individual hosts for each check_nwstat command... might I ask how yours is setup?
>
>Thanks!
>Alex
>
>  
>
>>>>Brian Hellman <bhellman at dlz.com> 4/8/2005 10:04 AM >>>
>>>>        
>>>>
>For some reason out of the blue, when I am running the check_nwstat 
>command it is reporting the following back to nagios
>sys_stat 
><http://nagios.southbend.dlzcorp.com/nagios/cgi-bin/extinfo.cgi?type=2&host=bh1&service=sys%5Fstat> 
>
>
>	
>
>	OK 	04-08-2005 05:08:44 	135d 19h 56m 13s 	1/3 	19392 MB (2147483648%) 
>free on volume sys 
>
>
>Note the % free on the volume.... I have tried updating the mrtgext.nlm 
>and am still getting this on all of the servers. Has anyone seen this or 
>have any clue as to why its telling me the wrong info?
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click 
>_______________________________________________
>Nagiosplug-help mailing list
>Nagiosplug-help at lists.sourceforge.net 
>https://lists.sourceforge.net/lists/listinfo/nagiosplug-help 
>::: Please include plugins version (-v) and OS when reporting any issue. 
>::: Messages without supporting info will risk being sent to /dev/null
>
>
>  
>