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

listener failed: zbx_tcp_listen() fatal error: unable to serve on any address [[0.0.0.0]:10051]

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Trivial Trivial
    • None
    • 2.4.4
    • Server (S)
    • None
    • Center OS 7

      [root@localhost zabbix]# service zabbix-server start
      Redirecting to /bin/systemctl start zabbix-server.service
      Job for zabbix-server.service failed. See 'systemctl status zabbix-server.service' and 'journalctl -xn' for details.
      [root@localhost zabbix]#
      [root@localhost zabbix]# netstat -an |grep 10051
      tcp 23 0 0.0.0.0:10051 0.0.0.0:* LISTEN
      tcp 64 0 192.168.232.130:10051 192.168.232.129:55510 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53080 CLOSE_WAIT
      tcp 0 0 127.0.0.1:53079 127.0.0.1:10051 FIN_WAIT2
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53073 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53067 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53068 CLOSE_WAIT
      tcp 0 0 127.0.0.1:53078 127.0.0.1:10051 FIN_WAIT2
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53061 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53081 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53079 CLOSE_WAIT
      tcp 64 0 192.168.232.130:10051 192.168.232.129:55509 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53074 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53071 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53066 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53075 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53060 CLOSE_WAIT
      tcp 0 0 127.0.0.1:53081 127.0.0.1:10051 FIN_WAIT2
      tcp 0 0 127.0.0.1:53080 127.0.0.1:10051 FIN_WAIT2
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53070 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53065 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53069 CLOSE_WAIT
      tcp 64 0 192.168.232.130:10051 192.168.232.129:55511 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53076 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53078 CLOSE_WAIT
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53062 CLOSE_WAIT
      tcp 0 0 127.0.0.1:53076 127.0.0.1:10051 FIN_WAIT2
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53063 CLOSE_WAIT
      tcp 0 0 127.0.0.1:53077 127.0.0.1:10051 FIN_WAIT2
      tcp 1 0 127.0.0.1:10051 127.0.0.1:53077 CLOSE_WAIT
      [root@localhost zabbix]#
      [root@localhost zabbix]# service zabbix-server status
      Redirecting to /bin/systemctl status zabbix-server.service
      zabbix-server.service - Zabbix Server
      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; disabled)
      Active: failed (Result: start-limit) since ? 2015-08-09 20:54:30 CST; 3min 48s ago
      Process: 21935 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=killed, signal=SEGV)
      CGroup: /system.slice/zabbix-server.service
      ??21907 /usr/sbin/zabbix_server -c /etc/zabbix/zabbix_server.conf

      Aug 09 20:54:30 localhost.localdomain systemd[1]: zabbix-server.service: control process exited, code=killed status=11
      Aug 09 20:54:30 localhost.localdomain systemd[1]: Failed to start Zabbix Server.
      Aug 09 20:54:30 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
      Aug 09 20:54:30 localhost.localdomain systemd[1]: zabbix-server.service holdoff time over, scheduling restart.
      Aug 09 20:54:30 localhost.localdomain systemd[1]: Stopping Zabbix Server...
      Aug 09 20:54:30 localhost.localdomain systemd[1]: Starting Zabbix Server...
      Aug 09 20:54:30 localhost.localdomain systemd[1]: zabbix-server.service start request repeated too quickly, refusing to start.
      Aug 09 20:54:30 localhost.localdomain systemd[1]: Failed to start Zabbix Server.
      Aug 09 20:54:30 localhost.localdomain systemd[1]: Unit zabbix-server.service entered failed state.
      [root@localhost zabbix]#

            Unassigned Unassigned
            wlzjdm leo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: