When exiting an SSH2 session (by typing "exit" at the propmt), I often get the following error:
disconnected: unexpected channel request
The popup error will also appear if I don't properly exit the session and just let it time out. Is there anyway around this? I'm using AT 8.14 on Windows 7, although I've had this problem on previous versions also.
Thanks in advance...
Can you tell me what version of SSH server you're connecting to? I've never seen this before.
When connected, go to Options->SSH Info. Take a screen snapshot and post it here!
Thanks!
Brian
Here's the SSH Info window you asked for:
One other bit of info, if I don't respond to the error popup within about 15 seconds, AT will crash. I submitted the crash report...
Here's a screenshot of the error:
Ah, Cisco.... Tends to be more troublesome than OpenSSH and others. So, there seems to be two problems here. 1. The initial error with the unexpected channel request 2. The crash the follows. I have a beta I'd like you to try. It will help us with both of these problems. First, it gives a better error message about exactly what type of channel request came in, so I can decide how best to handle this. Second, when (if) it crashes this time, I'd like you to send send the error report as you did before. With a fresh error report, I should be able to determine the cause of the crash. Cisco seems to be sending the channel request *after* it closes the channel. When we find out what type of request it is, we'll know how to proceed. I assume it is trying to send you the exit status of the shell or something similar, but we'll see. Here's the download:
http://www.celestialsoftware.net/telnet/beta_software.html
Brian
I could not get 8.27rc11 to crash at all. I do still get the error, but it's not in popup form anymore. Does this screenshot give you the information you need?
In a recent update, I replaced a number of the popups with on-screen messages. This apparently helps to avoid the crash.
I'd like you to do one more thing to help identify the order of events leading up to the error....
In the new beta, just before you type 'exit', go to the Options->Properties->Connection->SSH2->Options tab and select 'enable tracing'. Then, exit as you normally do. As you type, the screen will be filled with extra debug messages. After the disconnect, take a screen snapshot again and send it to me. Make sure the screen is nice and big so I can see all of the info.
Thanks,
Brian
Here you go:
ADC-CORE-S1#SSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 12)
Data: 5E000000030000000165
SSH - PacketDecoder RECEIVED: B1D98230A087162F7670ABCF0313C3283C37D6453CCC076F6CD9A0752EA18F2308B5B00C41C33398E4B9E66B87E52144765D1621
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 12)
Data: 5E000000000000000165
eSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 13)
Data: 5E000000030000000178
SSH - PacketDecoder RECEIVED: 22AC50EB825C123F7C02B8E3C521F2A9628AD25D4A547419E85DBA705935CCB635CBF4E1C368986768A9A9DF9EAA262EBE60437C
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 13)
Data: 5E000000000000000178
xSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 14)
Data: 5E000000030000000169
SSH - PacketDecoder RECEIVED: FF719CAB21FCC082E9F6FDD7ED2B0D38BBFF9DF93719C0F5C3DB8140514CBBA7F66F0AD4BDC3661D5A4B03166F6B181011ED6A6D
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 14)
Data: 5E000000000000000169
iSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 15)
Data: 5E000000030000000174
SSH - PacketDecoder RECEIVED: 9D2C37514DC7D59B2AE0854BE4BE07E6AC7B47AF77957584708E2C6E91FD3A6B573F224A6A0F3A05A6112D311A804288E8293E3B
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 15)
Data: 5E000000000000000174
tSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 16)
Data: 5E00000003000000010D
SSH - PacketDecoder RECEIVED: 4FBFADBA3F7364135E5B3EB83270DB682D2BFF05B824F8C9A81CE4A5717B70ABD4B5B4E3B4694141A00ADA590EBAD1FD463DBDDD
SSH - Received SSH_MSG_CHANNEL_DATA (11 bytes, seq nr 16)
Data: 5E00000000000000020D0A
SSH - PacketDecoder RECEIVED: 8514CE86FBD723FE97DDAE8BB1AD2825E7772F95D19AE854EB8EC240EBFE6709F5EF30CF2560099AC893B949C7F034989AECDB9F0F0CD2133661CB6AD1EC04AD8A1D6A752839D3410E0BC264CFE64BB337CD0EECC6A4B1CD145B1C25C745F66D3CDA9E75CA94A93E5AB5C08CA8B283CFC291A03604CE9EBF86F58A9ADDFC7C6344AEE746392DD44D1C3A1A2FA91CF43FDD062741E025910B7E5348A04FDF84F231DCBD0827DEF977C242D04619D7AF7ACEC7C260F3D44C38ED92C18B537708A18411605A1D1730A45CE8EB45133078F9
SSH - Received SSH_MSG_CHANNEL_REQUEST (25 bytes, seq nr 17)
Data: 62000000000000000B657869742D7374617475730000000000
SSH - Packet not completely processed
SSH - Received SSH_MSG_CHANNEL_EOF (5 bytes, seq nr 18)
Data: 6000000000
SSH - Received SSH_MSG_CHANNEL_CLOSE (5 bytes, seq nr 19)
Data: 6100000000
SSH - Received SSH_MSG_CHANNEL_REQUEST (25 bytes, seq nr 20)
Data: 62000000000000000B657869742D7374617475730000000000
SSH - Sending SSH_MSG_DISCONNECT (54 bytes, seq nr 17)
Data: 010000000200000027756E6578706563746564206368616E6E656C20726571756573743A20657869742D73746174757300000002656E
disconnected: unexpected channel request: exit-status
Thanks, and once more with this version:
http://www.celestialsoftware.net/telnet/beta_software.html
Brian
ADC-CORE-S1#SSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 12)
Data: 5E000000030000000165
SSH - PacketDecoder RECEIVED: 3CA8EC5476E0D88EC4B567A28BDDEBF7550D0877DB9B357E016E56C917E5820D70BBF77460A80C16CDC8E1962DB82ACB2AFF1EBB
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 12)
Data: 5E000000000000000165
eSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 13)
Data: 5E000000030000000178
SSH - PacketDecoder RECEIVED: C1AA77DB093A8FD0EB2A9DC4CFC041863D64740DAE4EE118832CC805DB695777724520541CCCAA0A744446E535E68931266DDFE6
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 13)
Data: 5E000000000000000178
xSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 14)
Data: 5E000000030000000169
SSH - PacketDecoder RECEIVED: C0849237CEA016F3FD38039A3703CF68E97BE5E00FCF1BCE1EF4AA6F8A2DECFF90D8A0E7848F31560A8F0337219BFC531A5B590E
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 14)
Data: 5E000000000000000169
iSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 15)
Data: 5E000000030000000174
SSH - PacketDecoder RECEIVED: 78C926F2DD679363BEED7E14CC549DEEA803776E41C74CD2E142F407A873610507639536E6ACFA544A00AE1012BA1F4FD79842BD
SSH - Received SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 15)
Data: 5E000000000000000174
tSSH - Sending SSH_MSG_CHANNEL_DATA (10 bytes, seq nr 16)
Data: 5E00000003000000010D
SSH - PacketDecoder RECEIVED: F8871C4CFA45AEC67357C9D5D1D5E147BAA41699579BFCE984481776F1FEAFBE0AE5240146332619E31171D54CAE7174964EF796
SSH - Received SSH_MSG_CHANNEL_DATA (11 bytes, seq nr 16)
Data: 5E00000000000000020D0A
SSH - PacketDecoder RECEIVED: C23492F0E670B5A592094205CE031C415CF5F5D30FF3C318CA62EA8551FEF7D38B8D6A4D9020F715EC22FC9AFF5B33CE672DFD21F9B9603D301D175FB5FE0842C4F5EC2BD2B86CD3F56D38DCB2C23C832D2E19AE8D342DB6BF8B2B105FB4A4EC8F20E9D5FCC551E4
SSH - Received SSH_MSG_CHANNEL_REQUEST (25 bytes, seq nr 17)
Data: 62000000000000000B657869742D7374617475730000000000
SSH - Got exit status 0
SSH - Received SSH_MSG_CHANNEL_EOF (5 bytes, seq nr 18)
Data: 6000000000
SSH - PacketDecoder RECEIVED: 298749D543B392DAF70F9215DC8C2822DBDD552CC238B471A10D80FE72C5F8417C18A969912645112EEF581C2313990B56C6ADBC7C4244981916C07BA004880B7E0BB11864B03D7BD82318CD57EB94ED119D92E4FE3D0995979C19DA585274D9CA9FF0EF195E6B05
SSH - Received SSH_MSG_CHANNEL_CLOSE (5 bytes, seq nr 19)
Data: 6100000000
SSH - Received SSH_MSG_CHANNEL_REQUEST (25 bytes, seq nr 20)
Data: 62000000000000000B657869742D7374617475730000000000
SSH - Sending SSH_MSG_DISCONNECT (54 bytes, seq nr 17)
Data: 010000000200000027756E6578706563746564206368616E6E656C20726571756573743A20657869742D73746174757300000002656E
disconnected: unexpected channel request: exit-status
Just as I thought. The server is trying to return an exit status MULTIPLE TIMES! Notice the first SSH_MSG_CHANNEL_REQUEST,
which results in the message 'Got exit status 0'. The second SSH_MSG_CHANNEL_REQUEST comes *after* SSH_MSG_CHANNEL_CLOSE,
which violates the protocol and results in 'unexpected channel request: exit-status'
Received SSH_MSG_CHANNEL_REQUEST
Got exit status 0
Received SSH_MSG_CHANNEL_EOF (5 bytes, seq nr 18)
Received SSH_MSG_CHANNEL_CLOSE (5 bytes, seq nr 19)
Received SSH_MSG_CHANNEL_REQUEST
disconnected: unexpected channel request: exit-status
This really appears to be a Cisco bug. Are you sure you have the latest version of IOS installed?
Can you report this to Cisco?
Brian
I'm definitely not on the latest Cisco IOS, but I'm fairly current. I seem to have this problem on a wide range of IOS's.
One of the features you've implemented in the Release Candidates you've had me testing is the elimination of the pop ups, which pretty much negates this problem for me. How long before this is rolled into a production version?
Pretty soon. Within the next week or two I'm hoping.
Brian
Great! Thanks for your help with this, I appreciate it...
