Web frontend shows "Zabbix server is not running" after upgrade to 7.0.26 — server is actually running

XMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 7.0.26
    • Component/s: Frontend (F), Packages (C)
    • Environment:
      Kubernetes (AKS), Docker image zabbix-web-nginx-pgsql:alpine-7.0.26, PostgreSQL backend

      Steps to reproduce:

      1. Run Zabbix 7.0.25 on Kubernetes using zabbix-web-nginx-pgsql:alpine-7.0.25 — web frontend shows server as running
      2. Upgrade all images to alpine-7.0.26 without any other configuration changes
      3. Web frontend shows banner: "Zabbix server is not running"

      Actual result:
      Banner "Zabbix server is not running" is displayed. The Zabbix server pods are confirmed running (kubectl shows 2/2 Running, 0 restarts). Server is accepting connections on port 10051.

      Expected result:
      Web frontend correctly reports server as running, identical to behavior in 7.0.25.

      Notes:
      Environments still on 7.0.25 or lower show the server as running without issue. The problem is reproducible across multiple Kubernetes namespaces after upgrading to 7.0.26.

            Assignee:
            Zabbix Support Team
            Reporter:
            Raoul Sellink
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: