|
On Mon, May 21, 2007 at 08:59:05AM -0400, Bill Omer wrote:
> I'm being faced with an issue where there is a 15 minute timeout value
> set which is effecting people with idle telnet sessions. I'm doing
> the follow to address this:
>
> /sbin/ipvsadm --set 28800 120 300
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_close
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_closewait
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_established
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_finwait
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_icmp
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_lastack
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_listen
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_synack
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_synrecv
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_synsent
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_timewait
> echo 28800 > /proc/sys/net/ipv4/vs/timeout_udp
>
> But this does not seem to be solving the issue at all. Are there any
> suggestions as to how to overcome this timeout?
Hi Bill,
which kernel are you using? I thought that those proc values
were removed many moons ago.
In relation to the actual problem. After you make this change,
what to the timeouts for (new) connections in the established
state look like. You can see them by examining ipvsadm -Lcn
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
|
