openresty / openresty/lua-nginx-module
nginx lua log info includes logs of logs " recv() failed (104: Connection reset by peer) "
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
Hello team,
I have one confusion about the nginx lua redis module logs as below, it occurs very frequently, I am not sure if this has some potential issue or not, would you please help suggest? thanks
2016/08/24 00:33:16 [info] 11153#0: *50641064 recv() failed (104: Connection reset by peer) while waiting for request, client: 100.109.217.0, server: 0.0.0.0:80
2016/08/24 00:33:16 [info] 11153#0: *50641068 recv() failed (104: Connection reset by peer) while waiting for request, client: 100.109.218.0, server: 0.0.0.0:80
2016/08/24 00:33:15 [info] 11153#0: *50641038 recv() failed (104: Connection reset by peer) while SSL handshaking, client: 100.109.219.0, server: 0.0.0.0:443
2016/08/24 00:33:15 [info] 11153#0: *50641039 recv() failed (104: Connection reset by peer) while SSL handshaking, client: 100.109.218.0, server: 0.0.0.0:443
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by tracing the nginx request and SSL-handshake logging paths and checking whether the lua-nginx-module changes this logging; done requires a clear diagnosis of the repeated messages and an agreed fix or explanation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100