Ad Widget

Collapse

inherited macro does not seem to work (2.4.4)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sphen
    Junior Member
    • Dec 2013
    • 25

    #1

    inherited macro does not seem to work (2.4.4)

    hi there-

    ran into an issue that i have been trying to troubleshoot for quite some time now and not sure if i have uncovered an issue or not.

    long story short i have defined a macro in a template to reference a log file. i use that macro in a log monitor item. right now a host that i have added and linked to that template seems to reference the item just fine. another host that i have linked to another template which is then linked to the template which has the macro ends up giving me "Not supported" and it does not seem to translate the macro value to the agent.

    I have included the debug log section from the agent that is saying "unsupported".

    the item key is:
    log[{$KERNEL_LOG},"I/O error"]

    the value of the macro in the template is:
    {$KERNEL_LOG} = /private/var/log/system.log

    those hosts that i have overridden this value at the host level do seem to work.

    i even tried defining a global macro instead of a template one. honestly from the log entries i think it is working but am not sure why the dashboard is saying "Not supported" and:
    Code:
    Cannot obtain information for file "{$KERNEL_LOG}": [2] No such file or directory
    any ideas? thanks!!

    agent debug log:
    Code:
     20303:20150417:155408.357 active checks #1 [processing active checks]
     20303:20150417:155408.357 In process_active_checks() server:'zabbix.trmacs.com' port:10051)
     20303:20150417:155408.357 In process_logrt() is_logrt:0 filename:'/private/var/log/system.log' lastlogsize:1222923 mtime:0 error_count:0
     20303:20150417:155408.357 In add_logfile() filename:'/private/var/log/system.log' mtime:1429300434 size:1223431
     20303:20150417:155408.357 add_logfile() logfiles:0x104000000 logfiles_alloc:64
     20303:20150417:155408.357 End of add_logfile()
     20303:20150417:155408.357 setup_old2new: is_same_file(/private/var/log/system.log, /private/var/log/system.log) = 1
     20303:20150417:155408.357 process_logrt() old file list:
     20303:20150417:155408.358    nr:0 filename:'/private/var/log/system.log' mtime:1429300414 size:1222923 processed_size:1222923 seq:1 incomplete:0 dev:16777218 ino_hi:0 ino_lo:20994147 md5size:512 md5buf:35e6c9df64be630536e7e593d54aa72e
     20303:20150417:155408.358 process_logrt() new file list: (mtime:0 lastlogsize:1222923 start_idx:0)
     20303:20150417:155408.358    nr:0 filename:'/private/var/log/system.log' mtime:1429300434 size:1223431 processed_size:1222923 seq:0 incomplete:0 dev:16777218 ino_hi:0 ino_lo:20994147 md5size:512 md5buf:35e6c9df64be630536e7e593d54aa72e
     20303:20150417:155408.358 In process_log() filename:'/private/var/log/system.log' lastlogsize:1222923 mtime: 0
     20303:20150417:155408.358 End of process_log() filename:'/private/var/log/system.log' lastlogsize:1223431 mtime: 0 ret:SUCCEED
     20303:20150417:155408.358 End of process_logrt():SUCCEED error_count:0
     20303:20150417:155408.358 End of process_active_checks()
     20303:20150417:155408.358 In get_min_nextcheck()
  • sphen
    Junior Member
    • Dec 2013
    • 25

    #2
    just an update regarding this. i do think that this is a legit bug although doe not really have to do with macros.

    it did appear that the macro was being resolved but the agent was just throwing the log monitoring error. the only way i was able to clear it was to completely delete the log item from the template - wait for housekeeping to run and then re-create it. at this point it is working on all hosts - even though technically there was no change to the item.

    disabling the item, clearing history etc and then re-enabling did not work - only deleting and re-creating.

    Comment

    Working...