Bug #3057
closedsockets disabled, connection limit reached
Description
few times lighttpd goes to hung state and the error log shows sockets disabled, connection limit reached. When I restart lighttpd server, it works properly.
- What does this "sockets disabled, connection limit reached" print means ?
- How to avoid lighttpd going to bad state ?
- Is this because of lighttpd server configuration issue ?
Went through relevant bugs but not able to find effective solution. Please suggest me any docs/material to resolve this issue as my application depends on lighttpd a lot.
Lighttpd version: 1.4.51
#Server configuration:
server.event-handler = "linux-sysepoll"
server.max-fds = 64
server.stat-cache-engine = "simple"
server.max-connections = 8
server.max-keep-alive-idle = 5
server.max-keep-alive-requests = 16
server.max-request-size = 0
server.max-read-idle = 60
server.max-write-idle = 360
#Logs:
2021-01-14 03:06:59: (server.c.1521) server started (lighttpd/1.4.54)
2021-01-14 03:12:27: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:27: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:27: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:12:57: (server.c.1000) [note] sockets disabled, connection limit reached
2021-01-14 03:12:57: (server.c.992) [note] sockets enabled again
2021-01-14 03:21:45: (server.c.969) [note] graceful shutdown started
Updated by gstrauss over 3 years ago
- Status changed from New to Invalid
- Priority changed from Normal to Low
- Target version deleted (
1.4.x)
This is the lighttpd issue tracker for issues in lighttpd, not issues with your configuration.
Questions belong in the "Forums". See the tab at the top.
- Is this because of lighttpd server configuration issue ?
If you do not know what items in your configuration means, you should comment them out and read the documentation for lighttpd configuration options to find out what they mean.
server.max-connections = 8
"connection limit reached" means "connection limit reached". If you think that is unclear, then please post in the Forums.
Also available in: Atom