Ad Widget

Collapse

proxy error - cannot process received configuration data : "httptest.status"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ChandanP
    Junior Member
    • May 2024
    • 2

    #1

    proxy error - cannot process received configuration data : "httptest.status"

    I created a new host for monitoring and no data was fetched for a few days. While checking the logs there were lines on the proxy where the items were supposed to be monitored


    HTML Code:
    2541:20240514:195250.369 cannot perform check now for itemid [76450]: item is not in cache
    2541:20240514:195250.375 cannot perform check now for itemid [76451]: item is not in cache
    2541:20240514:195250.380 cannot perform check now for itemid [76452]: item is not in cache
    2541:20240514:195250.384 cannot perform check now for itemid [76453]: item is not in cache
    2541:20240514:195250.388 cannot perform check now for itemid [76454]: item is not in cache
    2541:20240514:195250.391 cannot perform check now for itemid [76455]: item is not in cache
    2541:20240514:195250.394 cannot perform check now for itemid [76456]: item is not in cache
    2541:20240514:195250.397 cannot perform check now for itemid [76457]: item is not in cache
    I tried to dig deeper and it was found that configuration data was not getting updated on the proxy server.

    Proxy log had lines similar to below -
    HTML Code:
    2216:20240514:195728.031 received configuration data from server at "x.x.x.x", datalen 2441703
    2216:20240514:195728.063 cannot process received configuration data from server at "x.x.x.x": unexpected field "httptest.status"
    HTML Code:
    zabbix_proxy (Zabbix) 6.4.14
    Revision 0a50e619ef7 22 April 2024, compilation time: Apr 22 2024 00:00:00
    
    zabbix_server: /lib64/libpq.so.5: no version information available (required by zabbix_server)
    zabbix_server (Zabbix) 6.4.12
    Revision dba2d5bd63b 26 February 2024, compilation time: Feb 26 2024 00:00:00
    Using on-prem installation on RHEL version 9 with Postgres database
  • ChandanP
    Junior Member
    • May 2024
    • 2

    #2
    Updated Zabbix server to match the proxy version and that solved the problem.

    Comment

    Working...