Any suggestions? I used an application for stress backend server, I created connections between client-backend (without pound), and I detected that all connections was ok, after, I worked the same test with client-poundserver-backend and detected that a lot of lost connections with this error:
JJan 25 09:24:48 poundserver pound: backend 192.168.1.181:80<http://192.168.1.181/>connect: Connection timed out Jan 25 09:24:58 poundserver pound: BackEnd 192.168.1.181:80<http://192.168.1.181/>resurrect Jan 25 09:28:11 poundserver pound: backend 192.168.1.181:80<http://192.168.1.179/>connect: Connection timed out Jan 25 09:28:21 poundserver pound: BackEnd 192.168.1.181:80<http://192.168.1.179/>resurrect Jan 25 09:28:49 poundserver pound: backend 191.168.1.181:80<http://10.232.37.5/>connect: Connection timed out Jan 25 09:28:52 poundserver pound: backend 191.168.1.181:80<http://10.232.37.5/>connect: Connection timed out Jan 25 09:30:06 poundserver pound: backend 192.168.1.181:80<http://192.168.1.179/>connect: Connection timed out Jan 25 09:30:34 poundserver pound: BackEnd 192.168.1.181:80<http://192.168.1.179/>resurrect Jan 25 09:30:45 poundserver pound: backend 192.168.1.181:80<http://192.168.1.182/>connect: Connection timed out Jan 25 09:31:20 poundserver pound: backend 192.168.1.181:80<http://192.168.1.177/>connect: Connection refused Jan 25 09:31:22 poundserver pound: BackEnd 192.168.1.181:80<http://192.168.1.182/>resurrect Jan 25 09:34:39 poundserver pound: backend 192.168.1.181:80<http://192.168.1.181/>connect: Connection timed out I configured backend with Timeout 240 directive Any suggestions? I think would be a operative system configuration problem or pound configuration error, I just discard backend problems with this test. Are there other members with the same problem in the past? This is my pound configuration file ##################################################################### ## global options: User "pound" Group "pound" ## allow PUT and DELETE also (by default only GET, POST and HEAD)?: #ExtendedHTTP 0 ## Logging: (goes to syslog by default) ## 3 Apache-style (common log format) LogLevel 2 ## check backend: Timeout 45 Alive 10 #Client 30 Control "/opt/pound-2.3.2/etc/pound.socket" ListenHTTP Address 10.234.23.231 Port 80 RewriteLocation 1 RewriteDestination 1 Service "static requests HTML" HeadRequire "Host: www.server.com.*" Url "^/proffesional/personal/list2_stres.asp" BackEnd Address 192.168.1.181 Port 80 TimeOut 240 End End End Regards!!!!! 2011/1/25 Emilio Campos <[email protected]> > Hi, I detected two days ago problems in my filelog, and I would like > determine that this is not a pound problem, > > I detected this messages in my filelog > > Jan 25 09:24:48 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 09:24:58 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 09:28:11 poundserver pound: backend > 192.168.1.181:80<http://192.168.1.179:80>connect: > Connection timed out > Jan 25 09:28:21 poundserver pound: BackEnd > 192.168.1.181:80<http://192.168.1.179:80>resurrect > Jan 25 09:28:49 poundserver pound: backend > 191.168.1.181:80<http://10.232.37.5:80>connect: > Connection timed out > Jan 25 09:28:52 poundserver pound: backend > 191.168.1.181:80<http://10.232.37.5:80>connect: > Connection timed out > Jan 25 09:30:06 poundserver pound: backend > 192.168.1.181:80<http://192.168.1.179:80>connect: > Connection timed out > Jan 25 09:30:34 poundserver pound: BackEnd > 192.168.1.181:80<http://192.168.1.179:80>resurrect > Jan 25 09:30:45 poundserver pound: backend > 192.168.1.181:80<http://192.168.1.182:80>connect: > Connection timed out > Jan 25 09:31:20 poundserver pound: backend > 192.168.1.181:80<http://192.168.1.177:80>connect: > Connection refused > Jan 25 09:31:22 poundserver pound: BackEnd > 192.168.1.181:80<http://192.168.1.182:80>resurrect > Jan 25 09:34:39 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 09:35:24 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 09:36:36 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 09:37:00 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 09:42:13 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 09:42:38 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 09:45:24 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 09:45:52 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 09:48:02 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 09:48:16 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 09:48:48 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 09:49:04 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 09:49:51 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 09:49:53 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 09:53:42 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 09:53:53 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 09:53:54 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 09:54:41 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 09:58:15 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 09:58:43 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:03:11 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:03:33 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 10:05:52 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 10:05:57 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 10:06:44 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 10:06:46 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 10:09:21 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:09:44 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:09:51 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 10:09:58 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:09:58 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 10:09:58 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 10:11:03 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:11:34 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:11:37 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:12:24 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:17:11 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:17:16 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 10:19:35 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:19:36 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 10:22:13 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:22:16 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:22:49 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 10:22:56 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 10:28:11 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:28:16 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:28:36 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:28:36 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 10:31:28 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:31:36 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:31:49 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:31:56 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:32:27 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:32:36 poundserver pound: BackEnd 192.168.1.181:80 resurrect > Jan 25 10:33:32 poundserver pound: backend 192.168.1.179:80 connect: > Connection timed out > Jan 25 10:33:36 poundserver pound: BackEnd 192.168.1.179:80 resurrect > Jan 25 10:33:43 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 10:33:56 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 10:34:20 poundserver pound: backend 192.168.1.182:80 connect: > Connection timed out > Jan 25 10:34:36 poundserver pound: BackEnd 192.168.1.182:80 resurrect > Jan 25 10:36:25 poundserver pound: backend 192.168.1.181:80 connect: > Connection timed out > Jan 25 10:36:36 poundserver pound: BackEnd 192.168.1.181:80 resurrect > > > I can see in my poundctl a dead status in the server when the message > "connect: Connection timed out" appears, I checked the 80 port on the > backend server and all is working well, I checked logs in the backend > servers and I didn´t detected network problems but sometimes on any time > of > day I can see these problem in the log. > > These backends webservers runs with IIS and I configured 5 minutes of > timeout in IIS and 6 minutes of timeout in backend directive of pound > > I discard network problems because pound manages other virtualhost and > with > these there is no problem > > maybe this is a silly question but, anyone ever had this problem? > > THANKS! > -- > Load balancer distribution - Open Source Project > http://zenloadbalancer.sourceforge.net > Distribution list (subscribe): > [email protected] > > > -- > To unsubscribe send an email with subject unsubscribe to [email protected]. > Please contact [email protected] for questions. > -- Load balancer distribution - Open Source Project http://zenloadbalancer.sourceforge.net Distribution list (subscribe): [email protected] -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
