Ad Widget

Collapse

Listener failed error

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pmitchel
    Junior Member
    • Mar 2015
    • 6

    #1

    Listener failed error

    We've loaded zabbix-server (version 2.4.5, downloaded from baseurl=http://repo.zabbix.com/zabbix/2.4/rhel/7/x86_64/)
    onto a redhat 7 server. When we start the zabbix_server, we get:

    sudo systemctl start zabbix-server
    Job for zabbix-server.service failed. See 'systemctl status zabbix-server.service' and 'journalctl -xn' for details.

    journalctl -xn returns: zabbix-server.service start request repeated too quickly, refusing to start. request repeated too quickly, refusing to start.
    Failed to start Zabbix Server.

    Buried an insane amount of messages (including a memory map) is the following:

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

    3425:20150501:141259.457 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x18]. Crashing ...

    I made sure there were no other zabbix servers running (although all I did was kill the ones left in the process table from the prior failed run, I didn't reboot the server to free up any ports)..

    Any help will be appreciated.

    Paul Mitchell
  • dthacker
    Member
    • Feb 2014
    • 42

    #2
    The first thing to rule out would be things that block network traffic on the zabbix ports. Is SElinux active? Is iptables active?

    Dave

    Comment

    • pmitchel
      Junior Member
      • Mar 2015
      • 6

      #3
      Listener failed error

      Hi Dave,
      SInce it's redhat 7 I noticed there was a new daemon I didn't know about, firewalld, so I did the following:

      I configured SElinux to be disabled and rebooted the server:
      getenforce
      Disabled

      Then I stopped the two firewall related services:
      sudo systemctl stop iptables.service
      sudo systemctl stop firewalld

      Then I tried starting the zabbix-server:
      sudo systemctl start zabbix-server

      There are a number of locking errors in the log ((they've been there all along, I didn't bother mentioning them) and the final listener error and crash.

      zabbix_server [2382]: [file:'dbconfig.c',line:3037] lock failed: [43] Identifier removed
      zabbix_server [2382]: [file:'log.c',line:271] lock failed: [43] Identifier removed

      2437:20150501:150608.026 using configuration file: /etc/zabbix/zabbix_server.conf
      zabbix_server [2401]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2400]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2401]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2400]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2389]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2389]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2394]: [file:'selfmon.c',line:391] lock failed: [43] Identifier removed
      zabbix_server [2394]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2402]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2402]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2395]: [file:'dbconfig.c',line:4805] lock failed: [43] Identifier removed
      zabbix_server [2395]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2397]: [file:'dbconfig.c',line:4805] lock failed: [43] Identifier removed
      zabbix_server [2397]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2398]: [file:'dbconfig.c',line:4805] lock failed: [43] Identifier removed
      zabbix_server [2398]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2399]: [file:'dbconfig.c',line:4805] lock failed: [43] Identifier removed
      zabbix_server [2399]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2417]: [file:'selfmon.c',line:391] lock failed: [43] Identifier removed
      zabbix_server [2417]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2408]: [file:'selfmon.c',line:391] lock failed: [43] Identifier removed
      zabbix_server [2411]: [file:'selfmon.c',line:391] lock failed: [43] Identifier removed
      zabbix_server [2408]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2411]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      zabbix_server [2412]: [file:'selfmon.c',line:391] lock failed: [43] Identifier removed
      zabbix_server [2412]: [file:'log.c',line:271] lock failed: [43] Identifier removed
      2437:20150501:150608.082 current database version (mandatory/optional): 02040000/02040000
      2437:20150501:150608.082 required mandatory version: 02040000
      2437:20150501:150608.091 listener failed: zbx_tcp_listen() fatal error: unable to serve on any address [[-]:10051]
      2437:20150501:150608.091 Got signal [signal:11(SIGSEGV),reason:1,refaddr:0x18]. Crashing ...

      Paul

      Comment

      • syndeysider
        Senior Member
        • Oct 2013
        • 115

        #4
        I have this exact same problem....

        Running RHEL 7 Zabbix 2.4.5

        Any luck with this?

        Comment

        • Atsushi
          Senior Member
          • Aug 2013
          • 2028

          #5
          If are use RHEL 7.1, I think that is RHEL's bug.

          I think you can resolve by update trousers package.
          And, Please report to Red Hat Support.

          listener failed: zbx_tcp_listen() fatal error: unable to serve on any address

          ZBX-7790: zabbix_server_m[13777]: segfault at 18 ip 00007fe6639a8fe0 sp 00007fffbb66e498 error 4 in libpthread-2.18 - crash in "main" process

          Bug 1071171 - crash when linking libtspi and libmysqlclient [NEEDINFO]

          Bug 1069079 - crash when linking libgnutls and libmysqlclient

          Comment

          Working...