Ad Widget

Collapse

Zabbix Proxy - config.refresh_unsupported message

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nilldot
    Junior Member
    • Aug 2011
    • 21

    #1

    Zabbix Proxy - config.refresh_unsupported message

    Gents,
    Odd issue after update. Proxy server getting config.refresh_unsupported and refuse to function properly. Can't downgrade, as DB was 5.2 updated

    #ENV

    #Server

    OS CentOS 7

    zabbix-sender-5.2.2-1.el7.x86_64
    zabbix-web-mysql-scl-5.0.6-1.el7.noarch
    zabbix-server-mysql-5.0.6-1.el7.x86_64

    zabbix-release-5.2-1.el7.noarch
    zabbix-get-5.2.2-1.el7.x86_64
    zabbix-web-deps-scl-5.0.6-1.el7.noarch
    zabbix-agent2-5.2.2-1.el7.x86_64
    percona-zabbix-templates-1.1.6-1.noarch
    zabbix-web-5.0.6-1.el7.noarch
    zabbix-apache-conf-scl-5.0.6-1.el7.noarch
    zabbix-agent-5.2.2-1.el7.x86_64


    #proxy
    zabbix-sender-5.2.2-1.el7.x86_64
    zabbix-proxy-mysql-5.2.2-1.el7.x86_64
    zabbix-agent-5.2.2-1.el7.x86_64
    zabbix-release-5.2-1.el7.noarch


    #Proxy log
    4221:20201208:074652.724 using configuration file: /etc/zabbix/zabbix_proxy.conf
    4221:20201208:074652.737 current database version (mandatory/optional): 05020000/05020000
    4221:20201208:074652.738 required mandatory version: 05020000
    4221:20201208:074652.755 proxy #0 started [main process]
    4226:20201208:074652.756 proxy #1 started [configuration syncer #1]
    4234:20201208:074652.867 proxy #8 started [data sender #1]
    4230:20201208:074652.871 proxy #4 started [trapper #3]
    4231:20201208:074652.882 proxy #5 started [trapper #4]
    4232:20201208:074652.893 proxy #6 started [trapper #5]
    4228:20201208:074652.904 proxy #2 started [trapper #1]
    4233:20201208:074652.915 proxy #7 started [heartbeat sender #1]
    4229:20201208:074652.920 proxy #3 started [trapper #2]
    4235:20201208:074652.930 proxy #9 started [housekeeper #1]
    4241:20201208:074652.930 proxy #15 started [history syncer #4]
    4243:20201208:074652.931 proxy #17 started [task manager #1]
    4244:20201208:074652.941 proxy #18 started [poller #1]
    4246:20201208:074652.952 proxy #20 started [poller #3]
    4249:20201208:074652.963 proxy #23 started [unreachable poller #1]
    4242:20201208:074652.974 proxy #16 started [self-monitoring #1]
    4238:20201208:074652.975 proxy #12 started [history syncer #1]
    4251:20201208:074652.976 proxy #25 started [preprocessing manager #1]
    4236:20201208:074652.977 proxy #10 started [http poller #1]
    4237:20201208:074652.977 proxy #11 started [discoverer #1]
    4240:20201208:074652.988 proxy #14 started [history syncer #3]
    4245:20201208:074652.989 proxy #19 started [poller #2]
    4247:20201208:074652.999 proxy #21 started [poller #4]
    4250:20201208:074653.011 proxy #24 started [icmp pinger #1]
    4239:20201208:074653.012 proxy #13 started [history syncer #2]
    4248:20201208:074653.012 proxy #22 started [poller #5]
    4253:20201208:074653.022 proxy #27 started [preprocessing worker #2]
    4254:20201208:074653.023 proxy #28 started [preprocessing worker #3]
    4252:20201208:074653.082 proxy #26 started [preprocessing worker #1]
    4226:20201208:074653.328 received configuration data from server at "REPLACED", datalen 225695
    4226:20201208:074653.759 failed to update local proxy configuration copy: invalid field name "config.refresh_unsupported"

    Likely proxy 5.2 and server 5.0.2 mismatch. Any ideas how to address that ? Also, no RPMs for server 5.2 on CentOS 7 server, which is a pain to deal with

    Thanks!
  • Hamardaban
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2019
    • 2713

    #2
    In the latest updates, the proxy and server versions must match. Otherwise, you will get errors and a broken system.
    Now what to do: roll back the proxy installation to 5.0.6 !
    The database on the proxy can be safely deleted and re-created in the required version from the distribution.
    All necessary data will be taken from the server.

    Comment

    • nilldot
      Junior Member
      • Aug 2011
      • 21

      #3
      That’s what we did actually. Downgraded to match server version and we are back in business.

      Thanks!

      Comment

      Working...