Ad Widget

Collapse

zabbix helm chart: proxy returns "RangeError: execution timeout"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • harri
    Member
    • Nov 2010
    • 89

    #1

    zabbix helm chart: proxy returns "RangeError: execution timeout"

    Trying to watch the nodes from within the Kubernetes cluster (template Kubernetes nodes by HTTP) the proxy fails to connect. Error messages (using ZBX_DEBUGLEVEL 4):
    Code:
    :
    198:20250701:072011.338 End of zbx_ipc_service_recv():2
    198:20250701:072011.338 In zbx_pp_manager_process_finished()
    198:20250701:072011.338 End of zbx_pp_manager_process_finished() values_num:1
    198:20250701:072011.338 In preproc_flush_value_proxy()
    198:20250701:072011.338 End of preproc_flush_value_proxy()
    198:20250701:072011.338 [16] In pp_execute(): value:Cannot execute script: RangeError: execution timeout
    at [anon] (duktape.c:79217) internal
    at [anon] (function:272) preventsyield type:error
    198:20250701:072011.338 In zbx_ipc_service_recv() timeout:0.500
    198:20250701:072011.338 [15] In pp_execute(): value:Cannot execute script: RangeError: execution timeout
    at [anon] (duktape.c:79217) internal
    at [anon] (function:272) preventsyield type:error
    198:20250701:072011.339 [16] End of pp_execute(): value:'Cannot execute script: RangeError: execution timeout
    at [anon] (duktape.c:79217) internal
    at [anon] (function:272) preventsyield' type:error
    198:20250701:072011.339 [15] End of pp_execute(): value:'Cannot execute script: RangeError: execution timeout
    at [anon] (duktape.c:79217) internal
    at [anon] (function:272) preventsyield' type:error
    198:20250701:072011.339 End of zbx_ipc_service_recv():2
    198:20250701:072011.339 In zbx_pp_manager_process_finished()
    198:20250701:072011.339 End of zbx_pp_manager_process_finished() values_num:2
    198:20250701:072011.339 In preproc_flush_value_proxy()
    198:20250701:072011.339 End of preproc_flush_value_proxy()
    :
    I have increased the proxy timeout in values.yaml to 30 seconds, so I wonder WTH is going on? Either the script *can* be executed, but didn't complete in time, or it *cannot* be executed and is rejected immediately. And why doesn't it tell *which* script it cannot execute?

    Every helpful comment is highly appreciated.
Working...