01-10-2005 04:57 PM
Today I entered my keys for SSH and am experiencing some issues. If I do not keep my session active (constantly issuing commands) for more than approx. 45sec my session will lock up. I can then start another session but the previous session(s) remain active. I can't seem to determine how to kill these.
Having said that here are my questions:
How do I prevent these sessions from hanging?
How do I kill the hung sessions?
bc
01-11-2005 04:53 AM
this kind of issue should not happen.
What version do you use ?
The only valid way to kill sessions is to reboot the CSS.
There is a bug currently open where SSH session are not timing out properly making the box eventually unreachable.
Regards,
Gilles.
01-12-2005 10:15 AM
Gilles
I'm glad to know that this is not something that I would see under normal circumstances. Here is the output of the sho ver
qw-css-1# sho ver
Version: sg0740004 (07.40.0.04)
Flash (Locked): 07.30.1.06
Flash (Operational): 07.40.0.04
Type: PRIMARY
Licensed Cmd Set(s): Standard Feature Set
Secure Management
Do you have any more information on this bug you speak of...I'll research it on my end but if you have it handy I'd appreciate a link.
Also, here is the output from the sho sshd config
qw-css-1# sho sshd config
Sshd Configuration Information:
-------------------------------
Maximum Sessions Allowed: 5
Active Sessions: 1
Log Level: 4
Listen Socket Count: 1
Listen Port: 22
Listen Address: 0.0.0.0
Server Key Bits: 1024
RSA Protocol(SSH1): Enabled
Empty Passwords: Rejected
Keep Alive: Enabled
SSH2 Cipher List: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-cbc@lysator.liu.se
If you see any problems I'd appreciate being pointed in the right direction.
bc
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide