-
2024/01/24 03:32:09 [error] 40#0: *412372185 [lua] job.lua:284: execute(): [timer-ng] failed to run timer unix_timestamp=1706067129907.000000;counter=6761692:meta=debug off: /usr/local/openresty/lualib/resty/dns/resolver.lua:384: bad argument #1 to 'lshift' (number expected, got nil), context: ngx.timer |
Beta Was this translation helpful? Give feedback.
Answered by
zhen86889
Apr 17, 2024
Replies: 1 comment 9 replies
-
@chobits, could you take a look? thanks. |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello, Following the testing method outlined in https://github.com/openresty/lua-resty-dns/issues/70 , we set up a simplified DNS server and were unable to reproduce the issue. Therefore, we shifted our troubleshooting focus to our production DNS service. After analysis, we discovered that the issue was caused by our DNS server truncating the response without setting the
tc
flag when transmitting information that exceeded the UDP packet size limit. Thanks again to the community for your assistance.