ssh2: "sftp: Unexpected end event raised by server" after inbound request for a channel window adjust
Hi there, I am facing a strange issue where I am trying to connect to an sftp server and grab a file. Im able to connect to the sftp server but it makes a request to adjust the channel window size and then fails 5 minutes after receiving the request. I have been able to connect to multiple other servers without issue, some of which also made requests to adjust the window size and this is the first instance where its failed. I think this may be some sort of misconfiguration on the SFTP server but I have no idea what that could be. Im hoping that someone more familiar with the project might be able to help me figure out what is going wrong here. Any suggestions as to what I could try?
Here are the relevant logs:
"Handshake completed"
"Outbound: Sending SERVICE_REQUEST (ssh-userauth)"
"Inbound: Received SERVICE_ACCEPT (ssh-userauth)"
"Outbound: Sending USERAUTH_REQUEST (none)"
"Inbound: Received USERAUTH_FAILURE (publickey,password)"
"Client: none auth failed"
"Outbound: Sending USERAUTH_REQUEST (publickey -- check)"
"Inbound: Received USERAUTH_PK_OK"
"Outbound: Sending USERAUTH_REQUEST (publickey)"
"Inbound: Received USERAUTH_SUCCESS"
"CLIENT[sftp]: Removing listener from ready"
"CLIENT[sftp]: sftp: Removing end listener"
"CLIENT[sftp]: sftp: Removing close listener"
"CLIENT[sftp]: sftp: Removing error listener"
"Outbound: Sending CHANNEL_OPEN (r:0, session)"
"Inbound: CHANNEL_OPEN_CONFIRMATION (r:0, s:0)"
"Outbound: Sending CHANNEL_REQUEST (r:0, subsystem: sftp)"
"Inbound: CHANNEL_SUCCESS (r:0)"
"Inbound: CHANNEL_WINDOW_ADJUST (r:0, 524288)"
"Socket ended"
"CLIENT[sftp]: sftp: Unexpected end event raised by server"
"Socket closed"
"CLIENT[sftp]: sftp: Unexpected close event raised by server"
"CLIENT[sftp]: SFTP Channel Error: Received unexpected SFTP session termination"
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (10 by maintainers)
@richard-peters It will be merged. I wanted to confirm the fix with @kelly1266 first.