Oh snap, my bad - I just replied to Keith earlier. D'oh :P
See below:
Keith, thanks again for the help. I compared the two and aside from some
minor stuff we have similar files. In other good news, it is now working
correctly. I modified the check to look like this:
define service{
use
Hi all, looking for my Nagios gurus out there.
I'm trying to monitor some Windows systems using Nagios through OSSIM. OSSIM
is just an SIEM platform that rolls a bunch of open source security stuff
like snort, nagios, ntop, openvas, etc. into one nice package with a great
web interface. It ships
I've been using Nagios for 5+ years and as such, have a massive config
from the old 1.x version. I use NSClient+ on the Windows side.
All of my commands for disk space require defining Critical and
Warning levels.
i.e.
define command{
command_namecheck_nt_disk_d
By default NSClient+ works on a different port than the old client I
used. For compatibility until I manage to modify all of my Nagios
configs, I changed the listener on NSClient+ to the old port.
Here's my nsc.ini config. Notice I masked my source addresses in blue.
[modules]
Jarred, I don't know that I would consider myself as an expert in Nagios, but
more of somebody who can definitely get myself into trouble with it.
I think you need to remove '$ARG3$' from the end of your command line
directive. Your service's check_command is not passing a 3rd parameter, and
Actually Mark I think you were on to something. I did have to add the third
argument variable onto that because some of the other checks DO have a third
argument, however after modifying my check to the one above, it worked fine.
Thanks for the help though dude.
On Thu, Mar 24, 2011 at 4:16 PM,
Wait, what did you en up with? There was nothing above. Top posting is bad
Mark A. Lappin, CCNA, MCSE:Security | Lee Michaels Fine Jewelry
Director of Information Technology
11314 Cloverland Ave | Baton Rouge, LA 70809
Ph: 225.291.9094 ext 245 | Fax: 225-291-5778 | Mobile: 225-362-2770
