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

Proxy server crashes at startup

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • 3.2.2
    • Proxy (P)

      Server, proxy and agent compiled from sources as I've always done.
      All versions from 1.8 to 3.0.4 have compiled and run without any problems until now.

      Compiled configuration completes without any problems.
      Compile completes without any problems.
      I create an RPM from compile as we have 12 proxies and two servers and an RPM makes distribution easier.

      Main zabbix servers use an external Oracle DB each.
      All proxies use local MySQL DB on each proxy.
      Proxies are used to interface with VMware environment

      I was able to upgrade our Dev/test zabbix server and proxy from 3.0.4 to 3.2.2 without any problems.
      Our first production zabbix server upgraded from 3.0.4 to 3.2.2 without any problems.
      The first production proxy crashes after upgrade from 3.0.4 to 3.2.2.
      I have stopped any further upgrades to proxies until this problem can be resolved.

      This proxy has 34 servers and 1112 items connecting to it.
      And has run versions 2.2.2 to 3.0.4 without any problems till now.

      The first zabbix server has five proxies connecting to it and
      ~1030 hosts with ~40,000 items.

      I have not upgraded our second zabbix server.

      Some basic troubleshooting I've been able to perform shows that if I set either
      StartVMwareCollectors to zero
      or
      StartVMwareCollectors to zero
      the proxy does not crash. If both parameters are set to a non-zero value the proxy crashes.

      Please see attached log and disassembly.

      Any help, insight, comments would be appreciated.

            Unassigned Unassigned
            oellhnas Nick Chondropoulos
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: