nic-6443 commented on issue #13267: URL: https://github.com/apache/apisix/issues/13267#issuecomment-4676896897
This isn't a limit-count bug or an APISIX product bug — the `[error]` line that trips the test comes from lua-resty-events (bundled in apisix-runtime), not from APISIX code. When test-nginx restarts the server between blocks, the event broker's unix socket can close before the other workers see `ngx.worker.exiting()`, so `worker.lua` logs `event worker failed: failed to receive the header bytes: closed` at ERR level and then simply reconnects — the `communicate()` loop only suppresses the log when the exiting flag is already set, which is why this races. That stray line then lands inside the error.log window Test::Nginx checks for the next block, which is exactly why your first run passed and the second failed with identical code. Functionally nothing is broken — the worker restarts its timer and reconnects — so this is shutdown noise, same as what was discussed in #12320. The real fix would be on the lua-resty-events side (don't log ERR for a connection closed during shutdown) or bumping the bundled version in apisix-runtime once that lands. I'd suggest closing this as a test-environment flake rather than a product bug. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
