Hello,
I hope you are doing well.
I have an OpenResty implementation feature that is used as a counter via a timerng object. The code related to the functionality that is being used is the following:
local timer_module = require("resty.timerng")
local timer_sys = timer_module.new({restart_thread_after_runs = 1000}) -- restart_thread_after_runs was added after the problem started
[. . .] -- unrelated other nginx code
timer_sys:start()
timer_sys:named_every(key, 1, function_new)
After about an hour of execution, we are seeing the following logs:
2024/07/26 09:03:08 [error] 1771830#1771830: *1339053 lua udp socket read timed out, client: [IP], server: , request: "GET [Request_URI] HTTP/2.0", host: "[host]"
Have you ever encountered an issue similar to that one and what would be a possible solution?
Hello,
I hope you are doing well.
I have an OpenResty implementation feature that is used as a counter via a timerng object. The code related to the functionality that is being used is the following:
local timer_module = require("resty.timerng")local timer_sys = timer_module.new({restart_thread_after_runs = 1000}) -- restart_thread_after_runs was added after the problem started[. . .] -- unrelated other nginx codetimer_sys:start()timer_sys:named_every(key, 1, function_new)After about an hour of execution, we are seeing the following logs:
2024/07/26 09:03:08 [error] 1771830#1771830: *1339053 lua udp socket read timed out, client: [IP], server: , request: "GET [Request_URI] HTTP/2.0", host: "[host]"Have you ever encountered an issue similar to that one and what would be a possible solution?