Ad Widget

Collapse

Zabbix Proxy setup errors

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • duncan9562
    Member
    • Jan 2017
    • 46
    #1

    Zabbix Proxy setup errors

    Hey guys,

    Very new to Zabbix and would really appreciate some help. To give you a run down of what I have currently setup:-

    2 x Zabbix Server nodes in a HA failover set up (working perfectly)
    1 x DB backend - MariaDB for both Zabbix Server nodes
    Failover IP of 10.5.56.50 which is bought up on the Zabbix Server node with Zabbix Server running (working perfectly).

    What I am trying to do is set up a Zabbix Proxy.

    I have installed zabbix-proxy-mysql 3.2.3. I have used the default config file but set / changed the following values in /etc/zabbix/zabbix_proxy.conf:-

    Code:
    ProxyMode=0
Server=10.5.56.50
HostnameItem=system.hostname
DBName=zabbix_proxy
DBUser=zabbix_proxy
DBPassword=******
    Starting the Zabbix proxy produces the following in the log file:-

    Code:
    31885:20170126:083051.996 Starting Zabbix Proxy (active) [mountae50]. Zabbix 3.2.3 (revision 64610).
 31885:20170126:083051.997 **** Enabled features ****
 31885:20170126:083051.997 SNMP monitoring:       YES
 31885:20170126:083051.997 IPMI monitoring:       YES
 31885:20170126:083051.997 Web monitoring:        YES
 31885:20170126:083051.997 VMware monitoring:     YES
 31885:20170126:083051.997 ODBC:                  YES
 31885:20170126:083051.997 SSH2 support:          YES
 31885:20170126:083051.997 IPv6 support:          YES
 31885:20170126:083051.997 TLS support:           YES
 31885:20170126:083051.997 **************************
 31885:20170126:083051.997 using configuration file: /etc/zabbix/zabbix_proxy.conf
 31885:20170126:083051.999 current database version (mandatory/optional): 03020000/03020000
 31885:20170126:083051.999 required mandatory version: 03020000
 31885:20170126:083052.000 proxy #0 started [main process]
 31893:20170126:083052.002 proxy #5 started [poller #2]
 31894:20170126:083052.004 proxy #6 started [poller #3]
 31892:20170126:083052.006 proxy #4 started [poller #1]
 31895:20170126:083052.008 proxy #7 started [poller #4]
 31891:20170126:083052.010 proxy #3 started [data sender #1]
 31890:20170126:083052.012 proxy #2 started [heartbeat sender #1]
 31896:20170126:083052.014 proxy #8 started [poller #5]
 31889:20170126:083052.017 proxy #1 started [configuration syncer #1]
 31899:20170126:083052.024 proxy #10 started [trapper #1]
 31900:20170126:083052.027 proxy #11 started [trapper #2]
 31903:20170126:083052.029 proxy #14 started [trapper #5]
 31901:20170126:083052.030 proxy #12 started [trapper #3]
 31902:20170126:083052.034 proxy #13 started [trapper #4]
 31890:20170126:083052.036 cannot send heartbeat message to server at "10.5.56.50": proxy "mountae50" not found
 31904:20170126:083052.036 proxy #15 started [icmp pinger #1]
 31898:20170126:083052.036 proxy #9 started [unreachable poller #1]
 31905:20170126:083052.038 proxy #16 started [housekeeper #1]
 31906:20170126:083052.038 proxy #17 started [http poller #1]
 31907:20170126:083052.039 proxy #18 started [discoverer #1]
 31889:20170126:083052.042 cannot obtain configuration data from server at "10.5.56.50": proxy "mountae50" not found
 31908:20170126:083052.042 proxy #19 started [history syncer #1]
 31909:20170126:083052.042 proxy #20 started [history syncer #2]
 31910:20170126:083052.043 proxy #21 started [history syncer #3]
 31911:20170126:083052.044 proxy #22 started [history syncer #4]
 31927:20170126:083052.047 proxy #23 started [self-monitoring #1]
 31890:20170126:083152.044 cannot send heartbeat message to server at "10.5.56.50": proxy "mountae50" not found
 31890:20170126:083252.051 cannot send heartbeat message to server at "10.5.56.50": proxy "mountae50" not found
 31890:20170126:083352.059 cannot send heartbeat message to server at "10.5.56.50": proxy "mountae50" not found
 31890:20170126:083452.067 cannot send heartbeat message to server at "10.5.56.50": proxy "mountae50" not found
    I can see from the documentation that this error is expected as there is no configuration on the Zabbix Servers for the proxy node:-

    Code:
    cannot send heartbeat message to server at "10.5.56.50": proxy "mountae50" not found
    I have configured a new host (Configuration --> Hosts --> Create host), and set the IP to that of the Zabbix Proxy (10.5.56.60).

    I have also created a new proxy (Administration --> Proxies --> Create proxy) and used the hostname of my Proxy Server, "mountae50".

    I have already provided the logs for the Zabbix Proxy, but just for reference the log entries in the zabbix_server log are as follows:-
    Code:
    ....
.... 
20939:20170126:083052.030 cannot parse heartbeat from active proxy at "10.5.56.60": proxy "mountae50" not found
 20937:20170126:083052.039 cannot parse proxy configuration data request from active proxy at "10.5.56.60": proxy "mountae50" not found
 20937:20170126:083152.044 cannot parse heartbeat from active proxy at "10.5.56.60": proxy "mountae50" not found
....
....
    I have made sure that the hostname set for the zabbix proxy matches that in the Server and Proxy config, however I am now completely lost as to where to go from here.

    Could anyone point me in the right direction?

    For reference, all nodes are running on Debian 8 (Jessie) and Zabbix version 3.2.

    Thanks in advance...

    Duncan.
    Tags: None
    • kloczek
      Senior Member
      • Jun 2006
      • 1771
      #2
      You don't have mountae50 proxy registered on the server.
      http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
      https://kloczek.wordpress.com/
      zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
      My zabbix templates https://github.com/kloczek/zabbix-templates

        Comment

        • duncan9562
          Member
          • Jan 2017
          • 46
          #3
          Originally posted by kloczek
          You don't have mountae50 proxy registered on the server.
          Thanks kloczek, however the proxy was registered on the server as stated in the first post.

          I destroyed the Proxy, recreated it and all seems to work OK, presuming an error in the config file but can''t be sure.

          Thanks for the help!

            Comment

            • kloczek
              Senior Member
              • Jun 2006
              • 1771
              #4
              Originally posted by duncan9562
              Thanks kloczek, however the proxy was registered on the server as stated in the first post.

              I destroyed the Proxy, recreated it and all seems to work OK, presuming an error in the config file but can''t be sure.

              Thanks for the help!
              I guess that your second version of the proxy has different name under which this proxy is and was registered on your server. There is no other explanation
              http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
              https://kloczek.wordpress.com/
              zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
              My zabbix templates https://github.com/kloczek/zabbix-templates

                Comment

                • Clontarf[X]
                  Member
                  • Jan 2017
                  • 80
                  #5
                  Wanted to update this.

                  I found we have the same problem here. If we have a host and a proxy configured with the same name, the Proxy cannot obtain information from the server.

                  We worked around this by giving the host a different name.

                  There seems to be a limitation that the host cannot be the same name as the proxy. Not sure if this is documented anywhere.

                  Agent 2.4.7
                  Proxy 3.2.9
                  Server 3.2.7

                    Comment

                    • lptarik
                      #5.1
                      lptarik commented
                      13-04-2022, 11:21
                      Editing a comment
                      Hi, Is this still exists? I am having below issue

                      cannot obtain configuration data from server at "x.x.x.x": ZBX_TCP_READ() timed out
                    Previous template Next
                    Working...