Ad Widget

Collapse

Agent through proxy problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bubi92
    Junior Member
    • Mar 2019
    • 18

    #1

    Agent through proxy problem

    Hey community!
    I have a huge problem. I installed a new Zabbix proxy server. Zabbix proxy is communicating with the server. I would like to install and setup an agent to monitor itself the proxy. The agent installed, running, but im getting the following error: no active cheks on server [zabbixserver.ip] : host [definied hostname of proxyserver] not found
    In the frontend, i added a host, with the exactly same name what i wrote in zabbix_agentd.conf file. So this cant cause the problem. Any advice what can be?
  • Atsushi
    Senior Member
    • Aug 2013
    • 2028

    #2
    Did you restart the Zabbix agent after changing the zabbix_agentd.conf file?

    Comment


    • bubi92
      bubi92 commented
      Editing a comment
      yes, of course. i did restart on everything. agent, proxy, server, my pacemaker.. but its still not working
  • solomonaom
    Member
    • Feb 2019
    • 58

    #3
    when you set zabbix proxy you need to check on zabbix server which mode you set to zb proxy . The zabbix agent need to config IP server active to your new proxy server

    Comment


    • bubi92
      bubi92 commented
      Editing a comment
      you mean on web frontend? on webfrontend proxy added as active, and in the zabbix_proxy.conf its in active mode too.

      only the proxy server? the config files said "server AND proxy"

    • solomonaom
      solomonaom commented
      Editing a comment
      if your active mode match between zb server & zb proxy you can try check zb agent in a host <zabbix_agent.conf> is point to your zb _proxy

    • bubi92
      bubi92 commented
      Editing a comment
      If i modify the agentd.conf serveractive to only proxy address the "host not found" message is gone. BUT in the frontend, de host is still red.
  • bubi92
    Junior Member
    • Mar 2019
    • 18

    #4
    i checked another working host's agentd.log file. its contain "no active checks on server xx : host xxx not found" but, in spite of on the web frontend this host are working. so maybe this error message is a dead end.

    other starting point to investigate the problem, could be the frontend message: get value from agent failed: connection closed during read

    Comment


    • solomonaom
      solomonaom commented
      Editing a comment
      no It will be not correct the message is correct no active check because in server active IP is not working properly
  • bubi92
    Junior Member
    • Mar 2019
    • 18

    #5
    I attachted two server agentlogs. On the first as you can see there are a lot of no active checks message, but below on the frontend ZBX sign is green, the check is working.

    On the second picture there are the same messages, but on frontend ZBX sign is red.

    Click image for larger version

Name:	Screenshot 2019-03-13 at 12.16.04.jpg
Views:	3800
Size:	238.2 KB
ID:	375609




    Click image for larger version

Name:	Screenshot 2019-03-13 at 12.15.23.jpg
Views:	3791
Size:	239.2 KB
ID:	375610

    Comment


    • solomonaom
      solomonaom commented
      Editing a comment
      if you see no active check in a message mean your zb client cannot connect to zb server with default port for active check need 10051 TCP to connect from client to zb server or you change default port you can specify it in zb.config and restart zb agent

      ::The green ZBX mean passive not active check
      Last edited by solomonaom; 14-03-2019, 05:00.
  • bubi92
    Junior Member
    • Mar 2019
    • 18

    #6
    its okay. i checked it and you were right. on 2 host the host name was different from the config file. but on the other host which is monitored by proxy the hostname is exactly the same in config and on the frontend, even so in the log still host not found error message.

    if green zbx mean passive, what should i see if active check?

    client can connect to server on 10051 port, but if i add host on the frontend with 10051 its not working, but with 10050 its ok. why?

    Comment

    Working...