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

[4031] client was disconnected by server - timeout after 120 seconds

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Fixed
    • Icon: Trivial Trivial
    • None
    • 5.0.19
    • None
    • None
    • Ubuntu 20 LTS

      We are running zabbix 5 LTS with MariaDB and exactly 2 minutes after zabbix-server start, we have many entries

      Code:
      [Z3005] query failed: [4031] The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior. [select h.hostid,h.status,h.tls_accept,h.tls_issuer,h.tls_ subject,h.tls_psk_identity,a.host_metadata,a.liste n_ip,a.listen_dns,a.listen_port,a.flags from hosts h left join autoreg_host a on a.proxy_hostid is null and a.host=h.host where h.host='notebook' and h.status in (0,1) and h.flags<>2 and h.proxy_hostid is null]
      [Z3005] query failed: [4031] The client was disconnected by the server because of inactivity. See wait_timeout and interactive_timeout for configuring this behavior. [begin;]
      in our log.

      it looks like the obvious but it is not

      Code:
      mysql> show variables like 'wait_timeout';
      --------------------+

      Variable_name Value

      --------------------+

      wait_timeout 28800

      --------------------+
      1 row in set (0,00 sec)

      mysql> show variables like 'interactive_timeout';
      --------------------------+

      Variable_name Value

      --------------------------+

      interactive_timeout 28800

      --------------------------+
      1 row in set (0,00 sec)
      We tried to tune almost everything that can be tweaked without any change.

      It seems there is some internal zabbix timeout, that is hitting us right after 2 minutes.

            zabbix.support Zabbix Support Team
            siegmarb Stefan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: