Macros do not expand when debugging

[Claudio Kuenzler]

Umm....

1299 #          2048 = Macros

Right now you've set
1301 debug_level=256

this is to mainly debug the commands. For real debugging of the whole chain
you can use the value -1 (for everything).
Gives you a whole lot of log but that's always good for debugging.


On Fri, Mar 30, 2012 at 7:03 AM, Samuel Kidman <Samuel.Kidman at panres.com>wrote:

> Hello****
>
> ** **
>
> [1333083426.020333] [2320.2] [pid=19230] Raw Command Input:
> $USER1$/check_ping -H $HOSTADDRESS$ -4 -w 1000,33% -c 1000,100% -p 3 -t 1000
> ****
>
> [1333083426.020347] [2320.2] [pid=19230] Expanded Command Output:
> $USER1$/check_ping -H $HOSTADDRESS$ -4 -w 1000,33% -c 1000,100% -p 3 -t 1000
> ****
>
> ** **
>
> I have enabled debugging in my nagios.cfg file:****
>
> ** **
>
> 1281 # DEBUG LEVEL****
>
> 1282 # This option determines how much (if any) debugging information will
> ****
>
> 1283 # be written to the debug file.  OR values together to log multiple**
> **
>
> 1284 # types of information.****
>
> 1285 # Values:****
>
> 1286 #          -1 = Everything****
>
> 1287 #          0 = Nothing****
>
> 1288 #          1 = Functions****
>
> 1289 #          2 = Configuration****
>
> 1290 #          4 = Process information****
>
> 1291 #          8 = Scheduled events****
>
> 1292 #          16 = Host/service checks****
>
> 1293 #          32 = Notifications****
>
> 1294 #          64 = Event broker****
>
> 1295 #          128 = External commands****
>
> 1296 #          256 = Commands****
>
> 1297 #          512 = Scheduled downtime****
>
> 1298 #          1024 = Comments****
>
> 1299 #          2048 = Macros****
>
> 1300****
>
> 1301 debug_level=256****
>
> 1302****
>
> 1303****
>
> 1304****
>
> 1305 # DEBUG VERBOSITY****
>
> 1306 # This option determines how verbose the debug log out will be.****
>
> 1307 # Values: 0 = Brief output****
>
> 1308 #         1 = More detailed****
>
> 1309 #         2 = Very detailed****
>
> 1310****
>
> 1311 debug_verbosity=2****
>
> 1312****
>
> 1313****
>
> 1314****
>
> 1315 # DEBUG FILE****
>
> 1316 # This option determines where Nagios should write debugging
> information.****
>
> 1317****
>
> 1318 debug_file=/usr/local/nagios/var/nagios.debug****
>
> 1319****
>
> 1320****
>
> ** **
>
> However when the commands are output into the debug file, the macros don’t
> expand. This make debugging difficult. Anyone know what is going on?****
>
> ** **
>
> *Sam Kidman*****
>
> *IT System Administrator*
>
> --------------------------****
>
> *T:*        08 9225 0944****
>
> *M:        *0466137318****
>
> * *
>
> ** **
>
> ** **
>
> [image: Description: panres]****
>
> ** **
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120330/c0017ec3/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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