Ad Widget

Collapse

"Host not found" and gray availability flag

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ChristopheF
    Junior Member
    • May 2012
    • 1

    #1

    "Host not found" and gray availability flag

    Hello all !

    It's been 3 days I am trying to fix this problem, I read forums and triple checked everything, but I cannot make it work.

    Using zabbix release : 1.8.12
    Agent and server are exact same release.

    Configured an agent with zabbix_agentd.conf :
    Server=serverip
    Hostname=tg_front2

    Everything is default. Configured iptables so that iptables --list contains :
    ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:zabbix-trapper
    ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:zabbix-agent


    On the server :
    Configured DBName, DBUser, DBPassword and DBPort properly.
    ListenPort=10051

    Server is started through /etc/init.d/zabbix_server_ctl start.
    Running OK (seems to).
    Server also has zabbix_agentd running with following (default) configuration :
    Server=127.0.0.1
    Hostname=Zabbix server

    Web frontend works perfectly.

    First :
    I switched the default existing host "Zabbix server" to monitored in the web UI.
    => The availability flag stays gray
    I created a host called "tg_front2" with its IP and Template_Linux : It shows OK in the list : 10 apps, 102 items, 44 Triggers.
    The availability flag remains gray.

    Here is the server log at startup :
    1426:20120511:134850.455 Starting Zabbix Server. Zabbix 1.8.12 (revision 27054).
    1426:20120511:134850.455 ****** Enabled features ******
    1426:20120511:134850.455 SNMP monitoring: YES
    1426:20120511:134850.455 IPMI monitoring: YES
    1426:20120511:134850.455 WEB monitoring: YES
    1426:20120511:134850.455 Jabber notifications: YES
    1426:20120511:134850.455 Ez Texting notifications: YES
    1426:20120511:134850.455 ODBC: NO
    1426:20120511:134850.455 SSH2 support: NO
    1426:20120511:134850.455 IPv6 support: NO
    1426:20120511:134850.456 ******************************
    1429:20120511:134850.470 server #2 started [db watchdog #1]
    1428:20120511:134850.471 server #1 started [configuration syncer #1]
    1436:20120511:134850.491 server #9 started [trapper #1]
    1437:20120511:134850.491 server #10 started [trapper #2]
    1438:20120511:134850.492 server #11 started [trapper #3]
    1445:20120511:134850.503 server #13 started [trapper #5]
    1447:20120511:134850.505 server #14 started [icmp pinger #1]
    1448:20120511:134850.514 server #15 started [alerter #1]
    1449:20120511:134850.518 server #16 started [housekeeper #1]
    1449:20120511:134850.518 executing housekeeper
    1450:20120511:134850.522 server #17 started [timer #1]
    1451:20120511:134850.523 server #18 started [http poller #1]
    1426:20120511:134850.537 server #0 started [main process]
    1444:20120511:134850.538 server #12 started [trapper #4]
    1462:20120511:134850.542 server #20 started [history syncer #1]
    1463:20120511:134850.543 server #21 started [history syncer #2]
    1464:20120511:134850.546 server #22 started [history syncer #3]
    1465:20120511:134850.558 server #23 started [history syncer #4]
    1466:20120511:134850.563 server #24 started [escalator #1]
    1467:20120511:134850.563 server #25 started [proxy poller #1]
    1468:20120511:134850.566 server #26 started [self-monitoring #1]
    1432:20120511:134850.757 server #5 started [poller #3]
    1431:20120511:134850.764 server #4 started [poller #2]
    1430:20120511:134850.766 server #3 started [poller #1]
    1433:20120511:134850.770 server #6 started [poller #4]
    1434:20120511:134850.772 server #7 started [poller #5]
    1435:20120511:134850.775 server #8 started [unreachable poller #1]
    1461:20120511:134850.791 server #19 started [discoverer #1]
    1449:20120511:134850.847 housekeeper deleted: 0 records from history and trends, 0 records of deleted items, 0 events, 0 alerts, 0 sessions


    And then the problematic logs :
    1444:20120511:135002.558 Sending list of active checks to [127.0.0.1] failed: host [Zabbix server] not found
    1444:20120511:135006.435 Sending list of active checks to [176.31.249.208] failed: host [tg_front2] not found


    It seems that client can talk to the server but the server cannot retrieve the info from the hostname. Hostname from zabbix_agentd.conf and Name of the host in the webUI matches perfectly.

    telnet of the agent from server on port 10050 works OK.

    I am totally lost. All posts that I have seen on the forums indicate a difference between agent configured host name and server host name. But in my situation it matches.

    I checked that the zabbix user for mysql can select properly the "hosts" table and it can, showing the correct entries.

    I can provide any information needed. I do want to use zabbix because I'm used to it, but i am about to give up.
    Please help !
    Thank you so much for any help.
    Christophe.
  • luis_josue
    Junior Member
    • Oct 2012
    • 13

    #2
    hi, friend...if you found hot-to fix this problem.....i'd like you post your solution...because I have this error too...

    excuse me, for my bad english....jeje

    Comment

    • herta
      Senior Member
      • Sep 2011
      • 101

      #3
      questions

      Not sure what OS you're on. Looks like linux. What flavour + version are you using?

      nslookup translates 176.31.249.208 to ns387903.ovh.net. If you'd really wanted to monitor that system, I'd expect it to have an internal address which you'd use for monitoring and in-house management.
      If you traceroute to your system, are you seeing the path you'd expect?

      Just curious: why do you want to start a new environment with 1.8.12 when 2.0.3 has been released?

      Kind regards,

      Herta

      Comment

      Working...