Thanks for the reply. I am running 1.5-dev21-6b07bf7. I wrote a script to perform netstat dump every second and track how long my connections are. If tunnel timeout is set to 3600s, the connects are like these: 192.168.78.155:43089 disappeared at 1390317336, lasted 3600 192.168.78.155:43090 disappeared at 1390317336, lasted 3600 192.168.78.155:43091 disappeared at 1390317346, lasted 3600 192.168.78.155:43084 disappeared at 1390317682, lasted 3967 192.168.78.155:43085 disappeared at 1390317682, lasted 3967 192.168.78.155:43086 disappeared at 1390317683, lasted 3968 192.168.78.155:43176 disappeared at 1390317983, lasted 3668 192.168.78.155:43174 disappeared at 1390317983, lasted 3668 192.168.78.155:43175 disappeared at 1390317983, lasted 3668
Then, I changed tunnel timeout to 300s. 192.168.78.155:43901 disappeared at 1390318815, lasted 300 192.168.78.155:43900 disappeared at 1390318815, lasted 300 192.168.78.155:43902 disappeared at 1390318815, lasted 300 Looks like the tunnel timeout is definitely making a difference.. -Simon On Mon, Jan 20, 2014 at 1:08 AM, Baptiste <bed...@gmail.com> wrote: > Hi Xu, > > Which version of HAProxy? > Can you test with a timeout tunnel set to 10s, open a client > connection and run some test over it and confirm the connection is > shut after 10s, whatever happens? > > Baptiste > > > On Sun, Jan 19, 2014 at 3:03 PM, Xu (Simon) Chen <xche...@gmail.com> > wrote: > > Hey folks, > > > > I am using haproxy to front a variety of services, including > mariadb-galera > > and spice console. I am setting "timeout tunnel" to be 3600s, but > strangely > > my connections seem to be broken about an hour, even if I pass traffic > > throughout the hour. Shouldn't the timeout deadline be extended if there > is > > traffic? Or maybe I set something wrong? > > > > Thanks. > > -Simon >
