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

Incorrect error message appears if connection is refused by Zabbix server

    XMLWordPrintable

Details

    • Team A
    • Sprint 93 (Oct 2022)
    • 0.5

    Description

      During https://support.zabbix.com/browse/ZBX-21510 NodeAdress tests, we found that the error message 'Connection to Zabbix server "localhost" refused' contains an outdated list of possible reasons that we should actualize and update.

      Steps to reproduce:

      • Enable 'High availability cluster parameters' in etc/zabbix_server.conf:
        ####### High availability cluster parameters #######
        
        ## Option: HANodeName
        #	The high availability cluster node name.
        #	When empty, server is working in standalone mode; a node with empty name is registered with address for the frontend to connect to.
        #
        # Mandatory: no
        # Default: 
        HANodeName=zabbix-node-01
        
        ## Option: NodeAddress
        #	IP or hostname with optional port to specify how frontend should connect to the server.
        #	Format: <address>[:port]
        #
        #	This option can be overridden by address specified in frontend configuration.
        #
        # Mandatory: no
        # Default: 
        NodeAddress=localhost:10055
        
      • Run zabbix server
      • Check Reports->System information page

      Result: Error message appears:

      Connection to Zabbix server "localhost" refused. Possible reasons:
      1. Incorrect server IP/DNS in the "zabbix.conf.php";
      2. Security environment (for example, SELinux) is blocking the connection;
      3. Zabbix server daemon not running;
      4. Firewall is blocking TCP connection.
      Connection refused
      


      Expected:

      Attachments

        Issue Links

          Activity

            People

              zabbix.dev Zabbix Development Team
              kseve Kirils Seve
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: