Bug #1996
closedbacklog: all addresses are down
Description
after about 24 hours running under moderate load (40-50 req/s) i keep getting this in my logs and the server becomes unresponsive. not sure if this a bug or a problem on my end? if this is not a bug i apologize as I just recently went from 1.4 to 1.5 and hadn't experience this problem before.
2009-05-31 21:48:04 (trace) (mod_proxy_core.c:1448) connecting to address unix:/tmp/php-fastcgi.sock (0x97b1928) failed, disabling for 60 sec
2009-05-31 21:48:04 (trace) (mod_proxy_core.c:2330) backlog: all addresses are down, putting /index.php (25) into the backlog, retry = 2
2009-05-31 21:49:06 (error) (mod_proxy_core.c:932) connect(unix:/tmp/php-fastcgi.sock) failed: Resource temporarily unavailable (11)
config:
$HTTP["url"] =~ "\.php$" {proxy-core.balancer = "round-robin"
proxy-core.allow-x-sendfile = "enable"
- proxy-core.check-local = "enable"
proxy-core.protocol = "fastcgi"
proxy-core.backends = ( "unix:/tmp/php-fastcgi.sock" )
proxy-core.max-pool-size = 16
}
startup:
/usr/local/bin/spawn-fcgi -s /tmp/php-fastcgi.sock -f /usr/local/bin/php-cgi -u csplanet -g csplanet -C 5 -P /var/run/spawn-fcgi.pid
Updated by scub almost 15 years ago
still having this problem.. i tried increasing php spawns from 5 to 8 and it didn't seem to make a difference..
Updated by darix almost 15 years ago
pool size and the number for -C should be identical.
Updated by nitrox almost 15 years ago
- Status changed from New to Need Feedback
- Priority changed from High to Low
This is lighty´s intentional behaviour if your backend is down.
There is no proof that your backend is working, or other way around, lighty not behaving as it should. You could simply check if lighty is still working by requesting a static file uppon that messages showing up in your logs.
Updated by nitrox almost 15 years ago
- Status changed from Need Feedback to Missing Feedback
Also available in: Atom