What OS is running on the back end? I have seen something similar in the past when there are not enough file handles on Linux
On Monday, December 28, 2015, Fernando Costa <[email protected]> wrote: > > Hey everybody, > > I'm running Pound 2.7d. > > Usually my load is less than 200 http/https connections but sometimes I > have a peak of 1500 connections. The server always has free memory, cpu, > disk, network, everything seems fine but pound goes crazy with no reason > sometimes. I start getting the following errors (after I restart pound > everything comes back to normal immediately). Any thoughts ? > > pound: (7f4c18f17700) error copy chunk cont: Broken pipe > > pound: (7f4c1e836700) error copy server cont: Broken pipe > > pound: (7f4c25d84700) connect_nb: poll timed out > > pound: (7f4c25d84700) backend 192.168.9:80 connect: Connection timed out > > pound: (7f4c25d84700) BackEnd 192.168.9.220:80 dead (killed) > > pound: (7f4c1ce91700) connect_nb: poll timed out > > pound: (7f4c1ce91700) backend 192.168.9.224:80 connect: Connection timed > out > > pound: (7f4c1e2e1700) connect_nb: poll timed out > > pound: (7f4c21e4b700) connect_nb: poll timed out > > pound: (7f4c24051700) error read from 187.210.150.156: Connection timed > out > > pound: (7f4c1d733700) error read from 99.239.49.73: Connection timed out > > pound: (7f4c1d56c700) BackEnd 192.168.9.220:80 dead (killed) > > pound: (7f4c19633700) BackEnd 192.168.9.224:80 dead (killed) > > pound: (7f4c1b7f8700) BackEnd 192.168.9.224:80 dead (killed) > > pound: (7f4c19b47700) BackEnd 192.168.9.224:80 dead (killed) > > pound: (7f4c2266b700) BackEnd 192.168.9.220:80 dead (killed) > > pound: (7f4c20c85700) BackEnd 192.168.9.224:80 dead (killed) > > pound: (7f4c1a222700) BackEnd 192.168.9.220:80 dead (killed) > > pound: (7f4c1df53700) BackEnd 192.168.9.224:80 dead (killed) > > thank you, > -- > > *FERNANDO COSTA* > > *Infrastructure Specialis* > -- David Martineau CTO ContractPal, Inc. 801.494.1861 x120 [email protected] <[email protected]>
