Welcome to the VanDyke Software Forums

Join the discussion today!


Go Back   VanDyke Software Forums > General

Reply
 
Thread Tools Display Modes
  #1  
Old 01-13-2005, 07:01 AM
rwatson rwatson is offline
Registered User
 
Join Date: Jan 2005
Posts: 3
SecureCRT 4.0 hangs

I could not get access to the SSH forum so i had to post here.

I recently upgraded SecureCRT from a previous version to 4.0. Now it seems that if the session is inactive for only a few minutes or I switch to another application and come back to CRT window, the session has hung. Once I starttyping I get a message the session was terminated.

However, when I open new session and login to server, the session which was supposed to have terminated is still active as far as the server is concerned. In other words the server didn't timeout the session.

I still have 3.4 on my laptop which runs fine - no hangs.

Running Win XP SP2 on both. Any ideas on what's causing this...very annoying.
Reply With Quote
  #2  
Old 01-13-2005, 08:39 AM
miked's Avatar
miked miked is offline
Registered User
 
Join Date: Feb 2004
Posts: 2,040
Calling the problem you're experiencing "annoying" seems like an understatement!

A few questions:

- How do you know the server still thinks the hung Session
process is running (ie: ps, tasklist, other)?

- What other programs are running on the computer with
SecureCRT 4.0?

- Do you connect to multiple computers, and if so, does
this problem occur with all Sessions, or does it only
occur when connecting to a particular server?

- Could you post Trace Options output from a Session
that gets disconnected?

To enable Trace Options click the File pull down menu and select Trace Options. After doing that if you click the File pull down menu again you should see a check mark next to Trace Options. The reason I'd like to see Trace Options is because it shows the low level interaction between SecureCRT and the server. You said that when you logon again with a new connection you see that the Session that was supposed to have been terminated is still active on the server and therefore it's not a timeout issue, so Trace Options may show nothing, but it's a simple test and may show something.

~miked

ps: We should also find out why you couldn't access the SSH forum, but fixing the disconnect problem seems a far higher priority.
Reply With Quote
  #3  
Old 01-18-2005, 02:31 PM
rwatson rwatson is offline
Registered User
 
Join Date: Jan 2005
Posts: 3
answers...

- How do you know the server still thinks the hung Session
process is running (ie: ps, tasklist, other)?

ps -aux | grep <TTY> and/or w. I've noticed the hand occurs even while running top or tail -f which should continue until terminated. In previous version, I would run these for an hour or two, but now only a few minutes before session hangs.

- What other programs are running on the computer with
SecureCRT 4.0?

normally outlook 2003, Perl Builder, WSFTP, sometimes HotDog also. it varies but these are the main ones.

- Do you connect to multiple computers, and if so, does
this problem occur with all Sessions, or does it only
occur when connecting to a particular server?

I may have a few sessions open doint things like tail and top, etc. as I debug my applications. Normally no more than 3, but the session hangs happen no matter how many sessions I have open.

- Could you post Trace Options output from a Session
that gets disconnected?

Trace is on now but as luck would have it, I can't duplicate problem...funny how this was happening all the time until now.

ps: We should also find out why you couldn't access the SSH forum, but fixing the disconnect problem seems a far higher priority.
As a guest, I can see and read messages from the ssh forum, but once I login, no forum.
Reply With Quote
  #4  
Old 01-18-2005, 03:49 PM
rwatson rwatson is offline
Registered User
 
Join Date: Jan 2005
Posts: 3
trace...

The only data from the trace was at the beginning of the session:

SSH: connected
SSH: RCVD: server public key
SSH: SEND: session key
SSH: setting cipher to 3DES
SSH: RCVD: success
SSH: SEND: username
SSH: RCVD: failure
SSH: SEND: Auth Password
SSH: RCVD: success
SSH: SEND: max packet size: 4096
SSH: RCVD: success
SSH: SEND: request pty
SSH: RCVD: success
SSH: SEND: exec shell

After being idle for about 12 minutes SecureCRT reported the session was terminted. This ony happens a few seconds after I attempt to enter a command. As you can see from the data below the session was still active on the server 6 minutes later. I have a ssh timeout on the server set to 30 minutes so the server should not be timing out the session.

USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 xxxxxxxxxx 3:58pm 12:48 0.05s 0.05s -bash
root pts/1 xxxxxxxxxx 5:27pm 0.00s 0.03s 0.01s w

USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 xxxxxxxxxx 3:58pm 18:52 0.05s 0.05s -bash
root pts/1 xxxxxxxxxx 5:27pm 0.00s 0.04s 0.02s w
Reply With Quote
  #5  
Old 06-16-2005, 09:32 AM
mlindenb mlindenb is offline
Registered User
 
Join Date: Jun 2005
Posts: 1
Same problem here

Hi,

I have the same problem (version 4.1.11, build 297). Sometimes, the connection to an SSH2 server freezes. On the destination server the connection is still there (ps output).

I was wondering if the cause for this problem has already been found?

I also activated Trace Options and will report back to here if new information is found.
Reply With Quote
  #6  
Old 07-05-2005, 07:09 AM
bocks's Avatar
bocks bocks is offline
VanDyke Customer Support
 
Join Date: Jan 2004
Location: Albuquerque, NM
Posts: 184
Quote:
Originally Posted by rwatson
The only data from the trace was at the beginning of the session:

SSH: connected
SSH: RCVD: server public key
SSH: SEND: session key
SSH: setting cipher to 3DES
SSH: RCVD: success
SSH: SEND: username
SSH: RCVD: failure
SSH: SEND: Auth Password
SSH: RCVD: success
SSH: SEND: max packet size: 4096
SSH: RCVD: success
SSH: SEND: request pty
SSH: RCVD: success
SSH: SEND: exec shell
This Trace looks like if came from aconnection using SSH1. Do you see the same behavior when using SSH2 to connect?

Also, in your session options under the Terminal Category, do you have the anti-idle disconnect option "Send protocol NO-OP" option checked?
Thanks,

-bocks
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -6. The time now is 08:18 PM.