Ad Widget

Collapse

Autoregistration and farther monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • i.kulagin
    Member
    • Aug 2011
    • 35

    #1

    Autoregistration and farther monitoring

    Hi everyone.
    I need some help with an automation of host adding and monitoring.
    The idea is to autoregister hosts via "Configuration->Actions->Autoregistration", link relevant templates to the hosts, add them to groups and start monitoring automatically.

    The first part is successfully done. I registered zabbix proxy with zabbix agent installed as a host. The problem is with the second part: items data is not collected with the next error: no active checks on server [10.0.1.155:10051]: host [VZBXPRX01] not found.
    I wonder how is it possible that host is not found if it was autoregistered?
    I can see the host in proper groups and linked templates with appropriate hostname in the zabbix frontend (everything according to autoregistration action). I have double checked:
    • "Host name" feild of autoregistred host in zabbix front end - it is correct (VZBXPRX01).
    • In the agent config file "HostnameItem=system.hostname" is used.
    • Hostname command in the shell returns VZBXPRX01.

    Another question is if "ServerActive" parameter is set, can I use passive checks at the same time for the host? What if both "Server" and "ServerActive" are set? Will this configuration work? In case of using proxy should both parameters point to proxy server IP address and could it be 127.0.0.1 in case agent is installed on zabbix proxy server?
    Thank you in advance for your help and ideas.
    Last edited by i.kulagin; 03-03-2015, 11:55.
  • ingus.vilnis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2014
    • 908

    #2
    Hi,

    In 99.99% cases "Server" and "ServerActive" should be set to the same IP and normally must be set simultaneously.

    IP should be the one that is monitoring the agent. If particular agent is monitored by server then it will be server IP, if proxy, then proxy IP needs to be set on agent.

    Agent on proxy machine should also be set to proxy IP, preferably to proxy external IP, not 127.0.0.1.

    In Zabbix frontend proxy host must also be set to be monitored by the same proxy. How to determine that the proxy is down, you will ask. For this on Zabbix server you create a new item with key zabbix[proxy,<name>,lastaccess] and see when was the last time the proxy was checking in. And then create a trigger based on it. https://www.zabbix.com/documentation...types/internal

    Hope this helps.

    Best Regards,
    Ingus

    Comment

    • ingus.vilnis
      Senior Member
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Mar 2014
      • 908

      #3
      Forgot to add. Theoretically you can set multiple IP addresses in Server and ServerActive fields, also both Zabbix server and Proxy IP, but that really is not a recommended approach and most likely will break your autoregistration functionality.

      Comment

      • i.kulagin
        Member
        • Aug 2011
        • 35

        #4
        Thank you for your answer, Ingus.

        I will take into account all the information you have provided. I did a workaround and configured Discovery and Action rules which work just fine. Autoregistration is turned off by now, but still it is interesting to undrstand how is it possible to get "Host not found" message then it was autoregistered .

        Comment

        • ingus.vilnis
          Senior Member
          Zabbix Certified Trainer
          Zabbix Certified SpecialistZabbix Certified Professional
          • Mar 2014
          • 908

          #5
          "Host not found" was probably of IP misconfiguration, also taking into account you had 127.0.0.1 somewhere and also I don't know if you had set the host to be monitored by proxy. Server basically looked for host on server itself but it was on proxy.

          Anyways, try now with correct IP addresses and you should be fine, and no such messages will be in the logs anymore.

          Comment

          Working...