Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-10376

Numbered macros {MACRO<1-9>} not passing to proxies correctly

    XMLWordPrintable

Details

    • Incident report
    • Status: Closed
    • Trivial
    • Resolution: Fixed
    • 3.0.0rc1
    • None
    • Proxy (P), Server (S)
    • 3.0rc2 on both server and proxy

    Description

      The Macros on the frontend and server seem to have gotten fixed from rc1 to rc2 but they are still not being correctly passed to the proxies.

       
      Feb 11 19:04:27 zabprxphx01-test zabbix_proxy[20094]: Zabbix Proxy stopped. Zabbix 3.0.0beta2 (revision 58097).
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: Starting Zabbix Proxy (passive) [zabprxphx01-test]. Zabbix 3.0.0rc2 (revision 58396).
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: **** Enabled features ****
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: SNMP monitoring:       YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: IPMI monitoring:       YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: Web monitoring:        YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: VMware monitoring:     YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: ODBC:                   NO
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: SSH2 support:          YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: IPv6 support:          YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: TLS support:           YES
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: **************************
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: using configuration file: /usr/local/zabbix/conf/zabbix_proxy.conf
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: current database version (mandatory/optional): 02050119/02050119
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: required mandatory version: 03000000
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: starting automatic database upgrade
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: completed 100% of database upgrade
      Feb 11 19:04:47 zabprxphx01-test zabbix_proxy[27513]: database upgrade fully completed
      
       
      Feb 11 19:04:51 zabprxphx01-test zabbix_proxy[27525]: fping failed: {HOST.IP1} address not found
      Feb 11 19:05:17 zabprxphx01-test zabbix_proxy[27525]: fping failed: {HOST.IP1} address not found
      Feb 11 19:05:21 zabprxphx01-test zabbix_proxy[27525]: fping failed: {HOST.IP1} address not found
      

      The check itself is:

       
      icmpping[{HOST.IP1},3,300,68,{$PING_TIMEOUT_MS}]
      

      That's the same format that we are using find on our 2.4.5 production system.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              matthew.tolle Matt Tolle
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: