Hi pound users. We got some serious problems today with pound. Sites being down, error 503 to users. We isolated it to being to many connections in state FIN_WAIT_2. This is how we solved it on FreeBSD, setting: net.inet.tcp.fast_finwait2_recycle=1 (was 0) net.inet.tcp.finwait2_timeout=15000 (was 60000)
## Here's what we saw in the logs # in dmsg pid 42111 (pound), uid 65534: exited on signal 8 pid 25660 (pound), uid 65534: exited on signal 8 pid 42097 (pound), uid 65534: exited on signal 8 pid 25781 (pound), uid 65534: exited on signal 8 # in pound logs Dec 21 11:12:17 192.168.76.2 pound: (2837e7b0) connect_nb: connect failed: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (2837e7b0) backend 192.168.72.221:80 connect: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (28385bc0) connect_nb: connect failed: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (2837e7b0) BackEnd 192.168.72.221:80 dead (killed) Dec 21 11:12:17 192.168.76.2 pound: (28389780) connect_nb: connect failed: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (28389780) backend 192.168.72.221:80 connect: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (28385bc0) backend 192.168.72.229:80 connect: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (28357360) connect_nb: connect failed: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (28357360) backend 192.168.72.229:80 connect: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (2837e7b0) connect_nb: connect failed: Can't assign requested address Dec 21 11:12:17 192.168.76.2 pound: (2837e7b0) backend 192.168.72.222:80 connect: Can't assign requested address etc... -- Mattias Berge -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
