I forgot, it was a connection to Cent OS.
SSH-2.0-OpenSSH_7.4
ssh_packet_channel_failure: SSH_CHANNEL_FAILURE received in incorrect state
0
Unfortunately, I cannot reproduce this in my environment.

2018-06-22 17:39 GMT+03:00 Yanis Kurganov <yanis.kurga...@gmail.com>:

> Hi, Andreas!
>
> Done, now I use SFTP.
> Everything is OK, but today i got this log (after that libssh freezes up
> completely):
>
> channel_open: Creating a channel 53 with 64000 window and 32768 max packet
> ssh_socket_unbuffered_write: Enabling POLLOUT for socket
> packet_send2: packet: wrote [len=44,padding=19,comp=24,payload=24]
> channel_open: Sent a SSH_MSG_CHANNEL_OPEN type session for channel 53
> ssh_packet_socket_callback: packet: read type 92
> [len=44,padding=15,comp=28,payload=28]
> ssh_packet_process: Dispatching handler for packet type 92
> ssh_packet_channel_open_fail: Channel opening failure: channel 53 error
> (1) open failed
> ssh_socket_unbuffered_write: Enabling POLLOUT for socket
> packet_send2: packet: wrote [len=44,padding=16,comp=27,payload=27]
> channel_request: Sent a SSH_MSG_CHANNEL_REQUEST subsystem
> ssh_packet_socket_callback: packet: read type 100 [len=12,padding=6,comp=5,
> payload=5]
> ssh_packet_process: Dispatching handler for packet type 100
> ssh_packet_channel_failure: Received SSH_CHANNEL_FAILURE on channel (43:0)
> ssh_packet_channel_failure: SSH_CHANNEL_FAILURE received in incorrect
> state 0
>
>
> 2018-04-17 18:54 GMT+03:00 Andreas Schneider <a...@cryptomilk.org>:
>
>> On Tuesday, 17 April 2018 15:47:58 CEST Yanis Kurganov wrote:
>> > Moreover, after
>> >
>> > ssh_packet_channel_failure: SSH_CHANNEL_FAILURE received in incorrect
>> state
>> > 0
>> >
>> > libssh didn't return control and totaly freezed.
>> >
>>
>> I'm sorry, I've never really looked into scp (which is a really broken
>> protocol). You should use sftp which we support.
>>
>>
>> Cheers,
>>
>>
>>         Andreas
>>
>>
>> --
>> Andreas Schneider                   GPG-ID: CC014E3D
>> www.cryptomilk.org                a...@cryptomilk.org
>>
>>
>>
>>
>

Reply via email to