[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
William Charles firstname.lastname@example.org
Thu, 13 May 2004 17:42:34 -0700 (PDT)
Many thanks to all those who responded. All were right in saying that the likely culprit was our Cisco terminal servers timing-out the connections after five minutes... I'm not yet sure whether our Network colleagues have changed anything, but I'm almost certain that Conserver 7.x was somewhat less sensitive to this? I certainly don't recall the logs being full of reconnection messages? Could be wrong... Thanks Again, Will. William Charles ______________________________________________________________ Global UNIX Engineering, Asia/Pacific [/] Deutsche Bank Sydney +61 2 9258 1916 email@example.com om To: firstname.lastname@example.org Sent by: cc: users-bounces@con Subject: Re: Conserver 8.x on Solaris 8... server.com 13/05/2004 22:39 On Thu, May 13, 2004 at 03:11:57PM +1000, William Charles wrote: > Folks, > > Before I spend too much time tracking this down, has anyone seen the following behaviour before? I'm using Conserver 8.1.5 on a Solaris 8 host connecting to several terminal servers via TCP. Every five minutes each Conserver daemon wakes up and reports the following for each console in its group... The same behaviour has been observed with older versions of Conserver 8... > > [Thu May 13 15:01:29 2004] conserver (5783): ERROR: [scholes] read failure > [Thu May 13 15:01:29 2004] conserver (5783): [scholes] automatic reinitialization > looks like the terminal server is timing out the console connections. i know some have default idle-timeouts that disconnect clients after a certain amount of inactivity. and, then again, others can be set that way. that's my guess...a 5 minute idle-timeout. Bryan _______________________________________________ users mailing list email@example.com https://www.conserver.com/mailman/listinfo/users -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.