Ad Widget

Collapse

Zabbix Proxy don't receive its hosts informations

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jcduss59
    Member
    • Jun 2011
    • 33

    #1

    Zabbix Proxy don't receive its hosts informations

    Hello,

    I'm facing a critical problem.

    I have a production zabbix server envirronement with zabbix-server and mulitples proxys.
    My envirronement is in zabbix 1.8.

    My server was initally in zabbix-server 1.8.10 behind mysql 5.1 and proxy 1.8.2 behind mysql 5.1
    I renamed an host behind a proxy. (changing its hostname and zabbix-agent hostname too).
    Then I renamed it into my server.. I never get any information from the server. It was not a case problem in zabbix. My hosts tables in zabbix-proxy was never updated by zabbix-server...

    I thought I was facing this bug :


    So I decided to upgrade my proxy into 1.8.18... and get the same problem...
    I've got about 10 hosts monitored behind it... 9 of them was working fine.. the renamed was still not updated...

    Then... I decided to upgrade my server to 1.8.18. Every host directly on the server are still monitored, and every host behind this proxy too, but still not the renamed one...

    Between each upgrade/operation, I tried to monitor/unmonitor it, place it directly or place it behind the proxy... it never appears at proxy DB side....

    I decided to restart my proxy installation from scratch....
    Remove all the proxy database, reinstall 1.8.18, and reconfigure it.
    Then all my ten host are not monitored anymore.. No hosts are present in proxy "hosts" table....

    I tried to rename my proxy... still no success.

    I tried to install a new proxy into another machine.. still no luck.

    What the hell am I missing ???

    I conclude that it is a server side problem.. what can be wrong ????

    In debug (at proxy side ) I've got such errors :
    End of get_host_availability_data():FAIL
    But I'm not sure it means something???

    Thank you for your help in advance.
  • MaxM
    Member
    • Sep 2011
    • 42

    #2
    Have you tried deleting the host and letting it rediscover?

    Comment

    • jcduss59
      Member
      • Jun 2011
      • 33

      #3
      Thank you for your reply.

      I never use auto discover. I give it a try without success.
      I configured the /24 behind my proxy to be discovered with zabbix_agent item Zabbix agent "proc.num[zabbix_agentd]"

      And it give no new host in my server (my previously not monitored removed host didn't came back).

      Here in the proxy debug log :
      30748:20131211:023707.594 discoverer #1 spent 0.000343 seconds while processing rules

      I assume, discovery has been tried ???

      For the moment I removed everything and tried to make it as simple as possible :
      One server running a proxy and an agent.
      The agent is configured with its own IP as "Server". The proxy listen to this ip. Port configuration is correct.

      On the zabbix proxy database here is what I can see :
      - My hosts tables is only composed of "template_XXX" and not my local host proxyfied
      The proxy_autoreg_host has this records :

      select * from proxy_autoreg_host
      -> ;
      +-----+------------+---------------+
      | id | clock | host |
      +-----+------------+---------------+
      | 516 | 1386747116 | nyankmirror01 |
      | 517 | 1386747236 | nyankmirror01 |
      | 518 | 1386747356 | nyankmirror01 |
      | 519 | 1386747476 | nyankmirror01 |
      | 520 | 1386747596 | nyankmirror01 |
      | 521 | 1386747717 | nyankmirror01 |
      | 522 | 1386747837 | nyankmirror01 |
      | 523 | 1386747957 | nyankmirror01 |
      | 524 | 1386748077 | nyankmirror01 |
      +-----+------------+---------------+
      9 rows in set (0.00 sec)

      - proxy_dhistory table is empty
      - proxy_history table is empty.
      - ids table ad this info : select * from ids;
      +--------+--------------------+---------------------+--------+
      | nodeid | table_name | field_name | nextid |
      +--------+--------------------+---------------------+--------+
      | 0 | proxy_autoreg_host | autoreg_host_lastid | 525 |
      +--------+--------------------+---------------------+--------+




      I don't know what can i check at zabbix-server side or DB... but I'm pretty sure those troubles come from the zabbix-server.. :/

      Any comment should help... I really don't know how can I solve it

      Thank you!

      Comment

      • jcduss59
        Member
        • Jun 2011
        • 33

        #4
        I tried autodiscovery on both proxy (my upgraded to 1.8.18, and the reinstalled from scratch with deb 1.8.2) and it doesn't discover anything


        On the 1.8.18 log file I read such errors, not on the on the 1.8.2 :
        17860:20131211:032929.400 Message size 140735816681624 exceeds the maximum size 134217728 bytes. Message ignored.
        17860:20131211:032929.400 Error while receiving answer from server []

        ??? What does it mean!?

        Comment

        • jcduss59
          Member
          • Jun 2011
          • 33

          #5
          This has been solved.

          It was due to a network problem.

          MTU was too high, and network device wasn't configure to refragment such packets..

          The packet, which were dropped, were the server's reply (with items active list etc)....

          Comment

          • denialmx
            Junior Member
            • Jul 2014
            • 2

            #6
            I know this is a very old post but, how did you solve it?
            I am facing the same issue, I thought I had hit a bug so I went and change all TEXT fields in the database from NOT NULL to nothing, I tried sqlite3 and mysql with no success.

            After some more troubleshooting I believe I hit the same problem you faced.
            Proxy is on a Site to Site VPN with a Cisco ASA on one side. I did a capture and I am seeing a lot of TCP DUPs and Retransmissions when the server tries to send the host list to the proxy.

            On the other side, the proxy never gets the the host list.

            Did you do something on the ASAs or you did something locally in the server to get this fixed?

            Thanks in advance.

            Comment

            Working...