Bug #1459
closedfastcgi crash
Description
Hello There !
In high traffic fastcgi crash
mod_proxy_backend_fastcgi.c.484: (trace) 19128 / 0 -> 19128
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/gry.php?co=1&kat=2&sort=2) terminated before it sent a FIN packet
mod_proxy_backend_fastcgi.c.484: (trace) 32248 / 0 -> 32248
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/video.php) terminated before it sent a FIN packet
mod_proxy_backend_fastcgi.c.484: (trace) 11224 / 0 -> 11224
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/video.php?co=2&idm=4085) terminated before it sent a FIN packet
mod_proxy_backend_fastcgi.c.484: (trace) 4376 / 0 -> 4376
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/ludzie.php) terminated before it sent a FIN packet
mod_proxy_backend_fastcgi.c.484: (trace) 27024 / 0 -> 27024
mod_proxy_backend_fastcgi.c.487: (error) looks like the fastcgi-backend (/) terminated before it sent a FIN packet
I am using 64 worker and 2 backend fastcgi
1500-2000 request per seconds..
server.max-keep-alive-requests = 5000
server.max-keep-alive-idle = 5
server.max-read-idle = 160
server.max-write-idle = 500
server.max-fds = 80024
server.stat-cache-engine = "simple"
server.max-connections = 90000
server.max-worker = 64
#server.network-backend = "linux-aio-sendfile"
server.network-backend = "writev"
#server.network-backend = "linux-sendfile"
server.event-handler = "linux-sysepoll"
#server.use-noatime = "enable"
server.max-stat-threads = 12
server.max-read-threads = 64
$HTTPurl =~ "\.php$" {
proxy-core.balancer = "sqf"
proxy-core.allow-x-sendfile = "enable"
proxy-core.protocol = "fastcgi"
proxy-core.max-keep-alive-requests = 3200
proxy-core.backends = ( "unix:/tmp/php.sock")
proxy-core.max-pool-size = 1000
}
$HTTPurl =~ "(gry.php)$" {
proxy-core.backends = ( "x.x.x.x:1026",
"unix:/tmp/php.sock")
}
Regards,
Piotr Kloc
-- pioklo
Updated by stbuehler over 16 years ago
- Status changed from New to Fixed
- Resolution set to invalid
- It is not lighttpds fault if your backend crashes
- Don't use server.max-worker unless you really need it and understand what it does.
Also available in: Atom