Nagios Support Forum

That worked. I had to remove both the dollar ($) and the double quote (") for it to work.

I didn't see a $ in the nagios.cfg illegal character list. I need to be able to use it.

I edited the javascript and will let you know how it works.

Yes the free variable: Here's the config for one of the servers: ############################################################################### # # Host configuration file # # Created by: Nagios QL Version 3.0.3 # Date: 2013-05-31 15:50:02 # Version: Nagios 3.x config file # # --- DO NOT EDIT THIS ...

Did some testing and it's the Dollar Sign ($). The $ isn't listed as an illegal character and is quite necessary to monitor MSMQ.

Here's the variable I've been using for a while: "MessageCount DIRECT=OS:server.domain.local\\private$\\tn39 1000 5000" As soon as I open the host object I'm getting an error in the new CCM that there is an illegal character in the variable definition and it's removing it, causing all the ...

Can you run this on the host you are trying to check the memory on? Start > Run > "cmd" netstat -an | Find "5666" The response should be C:\Users\cgraham>netstat -an | Find "5666" TCP 0.0.0.0:5666 0.0.0.0:0 LISTENING TCP [::]:5666 [::]:0 LISTENING

Is everyone in your org needing access to Nagios? Just create the users that need access.

I've verified this on one of my servers. They bind in order, NSClient (check_nt agent) then the NRPE (check_nrpe agent). So your NRPE won't bind if you set them both to the same port.

I did a diff of your ini file to mine. Here's the differences. NSClientListener.dll <-- this needs to be uncommented [NSClient] ;# ALLOWED HOST ADDRESSES ; This is a comma-delimited list of IP address of hosts that are allowed to talk to NSClient deamon. ; If you leave this blank the global version ...

He means for you to post your NSC.ini but to obfuscate any information you might deem sensitive.