Nagios doesn't trigger command

Andreas Ericsson ae at
Wed Feb 2 17:03:37 CET 2011

On 02/02/2011 04:30 PM, Libor Jelinek wrote:
> OMG! I solved it! So solution for next generation:
> * How to see actual ouput of processed command (directive command_line)? *
> In nagios.cfg:
> a) set debug_level=<desired level of debugging>
> b) set debug_verbosity=2
> c) see "Raw notification command" and "Processed notification command"
> in /var/log/nagios.debug
> This output shows me that there is probably bug in Nagios during
> processing comments for macros in resource.cfg. ; and # charaters are
> not correctly parsed like comments. It's not stated anywhere that in
> resource.cfg and/or for macros there's some exception how to express
> comments.
> $USER5$=someValue           ; This will not be parsed like comment
> $USER6$=otherValue           # Also this will not be parsed like comment
> So I will file the bug.

There's no bug. So called "winged" comments are only available in
object configuration files, and they're never mentioned for any
other configuration file.

Andreas Ericsson          at
OP5 AB                   
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY!
Nagios-users mailing list
Nagios-users at
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null

More information about the Users mailing list