Connections fail

[toloughlin]

How to explain this ... after a while, SecureCRT won't connect any new sessions. I'm currently running b247 - but I'm positive it happened in earlier releases.

I am running my configuration out of Dropbox (something to think about).

I had one window open (for more than 6 days) and when trying to launch another tab - the tab was spawned, got a blinking cursor, but it didn't connect. I tried launching in a new window, same thing.

FWIW, I've been connecting & disconnecting dozens of times a day to different sessions, since the app was first launched (6+days).

At first, I was thinking that the server was down ( ), but I launched ZOC & was able to get right in.

I log everything - and when I tried to launch a new session, no log file was created; SCRT just sat there.

I can't reproduce this at will. It just happens.

I was hoping to be able to get you trace options - but nothing was being logged (and raw was grayed out).

I Command+Q'd the app (and all windows / tabs), launched it again & all was well.

Let the questions begin!

[bgagnon]

Hello toloughlin,

I am sorry to hear of the connection behavior you are experiencing with the beta 4 release of SecureCRT for Mac OS (build 247). As a note, the beta 5 release is scheduled for Thursday, September 30.

I had one window open (for more than 6 days) and when trying to launch another tab - the tab was spawned, got a blinking cursor, but it didn't connect. I tried launching in a new window, same thing.

How many tabs were open in the one window before the newly-launched tab failed to connect?

What was the status of the existing tab(s) (ie: connected, idle, disconnected)?

Should SecureCRT get into this state again, could you provide a process dump per the instructions below?

How to create a core dump:

1. Run the Activity Monitor. This can be found by typing "Activity" in Spotlight.
2. In the Activity Monitor, click on SecureCRT.
3. Select "Send Signal to Process" from the View menu.
4. Send the "Abort (SIGABRT)" signal to SecureCRT.
5. When you restart SecureCRT, information will be displayed about where to find the core dump.

Once collected, would you contact us at support@vandyke.com so we can provide you the appropriate information to upload the crash dump file?

Please include "Attn Brenda - Forum Thread #6194" in the subject line.

[toloughlin]

OK, I'm rocking the new beta now.

How many tabs were open in the one window before the newly-launched tab failed to connect?

One (Localhost) - I did have other SCRT windows open - each exhibited the same behavior; even when spawning into a new window & not a tab.

What was the status of the existing tab(s) (ie: connected, idle, disconnected)?

Connected / Idle

Should SecureCRT get into this state again, could you provide a process dump .....

Would be my pleasure.

[bgagnon]

Hi toloughlin,

Thanks for the additional information.

I will await e-mail notification you have been able to create a dump file and we can go from there.

[toloughlin]

Email sent your way. The dump is ~ 114MB - will need a method to send it your way.

[bgagnon]

Hi toloughlin,

E-mail received and I have responded with the file upload information.

[toloughlin]

Sent it this AM. Let me know if you need anything else from me.