Displaying 6 results from an estimated 6 matches for "fd13".
Did you mean:
d13
2000 Jun 14
2
TCP connection forwarding troubles
...for fd11 [i1 o128]: Transport endpoint is not connected
Jun 13 13:25:03 tunnel sshd[32378]: error: channel 2: chan_shutdown_read: shutdown() failed for fd10 [i1 o128]: Transport endpoint is not connected
Jun 13 13:25:14 tunnel sshd[32378]: error: channel 5: chan_shutdown_read: shutdown() failed for fd13 [i1 o128]: Transport endpoint is not connected
Jun 13 13:46:02 tunnel sshd[32378]: error: channel 3: chan_shutdown_read: shutdown() failed for fd11 [i1 o128]: Transport endpoint is not connected
This is from the remote end of the tunnel, the machine with the squid
proxy. I see similar messages on...
2000 Jan 31
0
1.2.2 : transport endpoint is not connected.
...0x10
#define CHAN_OUTPUT_WAIT_DRAIN 0x20
#define CHAN_OUTPUT_WAIT_IEOF 0x40
#define CHAN_OUTPUT_CLOSED 0x80
So something seems to be wrong.]
chan_shutdown_read failed for #12/fd16 [i1 o16]: Transport endpoint is
not connected
chan_shutdown_read failed for #9/fd13 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #13/fd17 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #8/fd12 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #12/fd16 [i1 o128]: Transport endpoint is
not conne...
2000 Oct 02
3
still sftp-server problems with Irix?
...y_pid: pid 31997225
debug1: session_exit_message: session 1 channel 2 pid 31997225
debug1: session_exit_message: release channel 2
debug1: channel 2: write failed
debug1: channel 2: output open -> closed
debug1: channel 2: close_write
debug1: channel 2: chan_shutdown_write: shutdown() failed for fd13:
Transport endpoint is not connected
debug1: session_free: session 1 pid 31997225
debug1: channel 2: read<=0 rfd 13 len 0
debug1: channel 2: read failed
debug1: channel 2: input open -> drain
debug1: channel 2: close_read
debug1: channel 2: input: no drain shortcut
debug1: channel 2: ibuf emp...
2000 Jan 20
0
OpenSSH problem report on Linux 2.2.14.
...connected
chan_shutdown_read failed for #8/fd12 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #11/fd15 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #10/fd14 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #9/fd13 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #8/fd12 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #13/fd17 [i1 o128]: Transport endpoint is
not connected
chan_shutdown_read failed for #12/fd16 [i1 o128]: Transport endpoint is
not conne...
2020 Jun 08
0
Can't share a mailbox
...}
}
protocol imap {
mail_plugins = quota acl imap_sieve imap_acl
}
----------------------------------------
Does anyone see what I'm doing wrong here?
Kind regards,
--
Maxime DERCHE Information System Consulting France | NVMQVAM SOLVS
https://www.mdisc.fr/
OpenPGP Key ID: 0x814E02A25697FD13
OpenPGP Key Fingerprint: 8B7B 60C9 1095 A198 C883 5205 814E 02A2 5697 FD13
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://dovecot.org/pipermail/doveco...
2000 Jul 23
2
Work around Linux kernel bug provoked by nchan.c
The Linux implementation of TCP sockets has a bug which causes
shutdown(sock, SHUT_RD) to fail spuriously (ENOTCONN) if the write
side of the socket has already been shut down. If you are using SSH
port forwarding to tunnel HTTP through a firewall, nchan.c will tickle
this bug once for every HTTP exchange. You will therefore get lots of
useless, annoying error messages:
channel 2: