Ad Widget

Collapse

Distibuted monitoring : child node host availability

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • levo01
    Junior Member
    • Jun 2012
    • 17

    #1

    Distibuted monitoring : child node host availability

    Hello,

    I have upgraded from 1.8.5 to 2.0 and configure zabbix to run with a distibuted monitoring.

    I have a master node (central) and a child node (child). When I create a host from the central interface it is working well (with the good agent configuration -@IP of server) whereas from the child interface the host availability is grey (@IP of the child server).

    However I can run the zabbix_get command : ./zabbix_get -s 163.187.242.55 -p 10050 -k "system.hostname" where 163.187.242.55 is the new host's IP.

    Just to help some people, firstly it was not working for the central node too, when I add the hostname with the ip adress to the /etc/hosts file, it had worked.

    If you have any suggestion or idea to solve this problem.

    Thank you.
    Last edited by levo01; 06-06-2012, 11:11.
  • levo01
    Junior Member
    • Jun 2012
    • 17

    #2
    Up please !!

    Hello ,

    I have reinstalled all the configuration and have still the same problem.

    Is there any special instruction to add/modify in order to configure a new host from a child node within a distributed monitoring ?

    Again I achieved to monitor a new host with the master but not with the child node.

    here are logs :

    The host (hostname : zabbix_server_child) monitored by the child node :

    32582:20120605:161454.156 zabbix_agentd started. Zabbix 1.8.1 (revision 9702).
    32584:20120605:161454.160 zabbix_agentd collector started
    32587:20120605:161454.167 zabbix_agentd listener started
    32586:20120605:161454.167 zabbix_agentd listener started
    32589:20120605:161454.168 zabbix_agentd listener started
    32588:20120605:161454.169 zabbix_agentd listener started
    32590:20120605:161454.169 zabbix_agentd active check started [localhost:10051]
    32585:20120605:161454.171 zabbix_agentd listener started

    The child node :

    7783:20120605:150029.303 syncing history data...
    7783:20120605:150029.304 syncing history data done
    7783:20120605:150029.304 syncing trends data...
    7783:20120605:150029.304 syncing trends data done
    7783:20120605:150029.305 Zabbix Server stopped. Zabbix 2.0.0 (revision 27675).
    8267:20120605:150039.146 Starting Zabbix Server. Zabbix 2.0.0 (revision 27675).
    8267:20120605:150039.147 ****** Enabled features ******
    8267:20120605:150039.147 SNMP monitoring: NO
    8267:20120605:150039.147 IPMI monitoring: NO
    8267:20120605:150039.147 WEB monitoring: NO
    8267:20120605:150039.147 Jabber notifications: NO
    8267:20120605:150039.147 Ez Texting notifications: NO
    8267:20120605:150039.147 ODBC: NO
    8267:20120605:150039.147 SSH2 support: NO
    8267:20120605:150039.148 IPv6 support: NO
    8267:20120605:150039.148 ******************************
    8267:20120605:150039.148 NodeID: 2
    8267:20120605:150039.148 ******************************
    8268:20120605:150039.160 server #1 started [configuration syncer #1]
    8271:20120605:150039.161 server #4 started [poller #2]
    8274:20120605:150039.165 server #7 started [poller #5]
    8273:20120605:150039.165 server #6 started [poller #4]
    8275:20120605:150039.167 server #8 started [unreachable poller #1]
    8272:20120605:150039.168 server #5 started [poller #3]
    8276:20120605:150039.169 server #9 started [trapper #1]
    8277:20120605:150039.171 server #10 started [trapper #2]
    8270:20120605:150039.173 server #3 started [poller #1]
    8278:20120605:150039.174 server #11 started [trapper #3]
    8281:20120605:150039.174 server #14 started [icmp pinger #1]
    8284:20120605:150039.178 server #15 started [alerter #1]
    8280:20120605:150039.178 server #13 started [trapper #5]
    8285:20120605:150039.179 server #16 started [housekeeper #1]
    8285:20120605:150039.179 executing housekeeper
    8279:20120605:150039.179 server #12 started [trapper #4]
    8269:20120605:150039.187 server #2 started [db watchdog #1]
    8292:20120605:150039.190 server #18 started [node watcher #1]
    8291:20120605:150039.192 server #17 started [timer #1]
    8293:20120605:150039.195 server #19 started [http poller #1]
    8295:20120605:150039.198 server #20 started [discoverer #1]
    8267:20120605:150039.200 server #0 started [main process]
    8301:20120605:150039.202 server #24 started [history syncer #4]
    8300:20120605:150039.205 server #23 started [history syncer #3]
    8299:20120605:150039.206 server #22 started [history syncer #2]
    8298:20120605:150039.207 server #21 started [history syncer #1]
    8304:20120605:150039.210 server #26 started [proxy poller #1]
    8305:20120605:150039.212 server #27 started [self-monitoring #1]
    8303:20120605:150039.213 server #25 started [escalator #1]
    8285:20120605:150039.259 housekeeper deleted: 0 records from history and trends
    , 0 records of deleted items, 0 events, 0 alerts, 0 sessions


    PS :I configure the new host thanks to the front-end of the master node, I can choose which node to use (master or child).

    Comment

    • michelis
      Junior Member
      • Jan 2012
      • 14

      #3
      Hi,

      maybe you have a similiar problem as I had. Try to remove the zabbix.conf.php, restart apache and login again. It solved the problem for me.

      Comment

      • levo01
        Junior Member
        • Jun 2012
        • 17

        #4
        It is OK

        Thanks for your reply michelis,

        I have found a solution.

        I install a front end on the child node too and everything is working now.

        Comment

        Working...