Displaying 20 results from an estimated 800 matches similar to: "OpenSSH problem report on Linux 2.2.14."
2000 Jan 31
0
1.2.2 : transport endpoint is not connected.
Hi,
Thank you for the great OpenSSH package. I obtained 1.2.2 and
tried it on linux 2.2.14.
I had reported earlier that I saw "Transport endpoint is not connected"
warning messages were observed on the linux 2.2.14 kernel with earlier
release of openssh.
The same happens when I used the port-forwarded HTTP connection.
But this time, after accessing such http connections, I noticed
2002 Feb 05
0
New forkoff() and chan_wont_read/write() API
Markus,
How's this patch?
- a chan_wont_read()/chan_wont_write() API is added that is very much
like chan_read_failed()/chan_write_failed(), but for the debug
messages and chan_wont_*() don't ever call error()
The 3.0.2p1 channel_pre_x11_open() uses chan_*_failed() but looks
like it ought to use chan_wont_*() instead :)
- forkoff() no longer fakes EOF for SSHv2 (still
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:
2001 Sep 28
1
[PATCH] fix for Linux hang on exit bug in 2.9.9p2
As you are now probably aware, the portability team for openssh still
has not fixed the hang-on-exit bug in the 2.9.9p2 release.
Attached is a patch for 2.9.9p2 that fixes the hang-on-exit bug for Linux
systems. It also adds a useful exit delay feature that has also not yet been
incorporated into the main sources.
For more information, see the SNFS (secure NFS) web page:
2001 Nov 14
6
[PATCH]: Patch to fix hang on exit bug under Linux and add optional exit delay
The hang-on-exit bug still hasn't been fixed in OpenSSH-3.0p1... :-(
Here again is the patch to fix this bug under Linux, updated for OpenSSH-3.0p1.
This has been exhaustively tested for six months now. It also add an exit
delay option that can be useful.
The patch does not lead to data loss under Linux.
Please see the Secure NFS page (SNFS) for further details:
2000 Jan 07
2
possible clue on tcp forwarding problems
When I encounter the problem with TCP port forwarding locking up, I'll
see this on the client window (if I haven't invoked ssh with -q):
chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected
chan_shutdown_read failed for #1/fd6: Transport endpoint is not connected
This is with Blowfish encryption. I have to kill and restart the client
when this happens.
Phil
2000 Nov 08
1
internal error: we do not read, but chan_read_failed
Hello,
The error message in the subject line occurs with the new 2.3.0 openssh
version and appeared in the previous snapshots on our Solaris systems. As far
as I remember it was reported, but have not seen any more about this. I have
looked into it a little bit.
First, the file session.c (line 1849 onwards):
debug("session_exit_message: release channel %d", s->chanid);
2010 Jan 14
1
ssh(1) multiplexing rewrite
Hi,
At the n2k10 OpenBSD network hackathon, I finally got some time to clean
up and rewrite the ssh(1) client multiplexing code. The attached diffs
(one for portable OpenSSH, one for OpenBSD) are the result, and they
need some testing.
The revised multiplexing code uses a better protocol between the master
and slave processes and I even bothered to write it up :) It tracks the
control sockets
2001 May 04
19
SSH connection hanging on logout
I am running OpenSSH 2.9p1 on SunOS 5.7 w/4-24-2001 patch cluster.
Like many other users I am seeing the hanging session on logout
with background processes. This is a huge problem for me as
I centrally manage 50+ machines with rdist across ssh.
Instead of just complaining about the problem I thought I would
put my CS degree to use and try to track down the problem myself.
For starters,
2001 Feb 22
3
intermittent stderr
The command "ssh ls -l /doesnotexist" gives various responses:
Running from a 200 MHz PentiumPro with dsa key added to ssh-agent:
Mistakes worst to fast machine:
To a faster 600 MHz dual processor i686 600 MHz machine:
ls: /doesnotexist: No such file or directory -- correct
nothing at all -- wrong
ls: select: Bad file descriptor -- wrong
2000 Nov 15
1
[PATCH]: nchan.c : internal error: we do not read, but chan_read
Attached is the patch I've been using to fix the error message seen in the
subject line. It seems (!) to have caused no problems with the
previous openssh snapshot version openssh-SNAP-20001016, 2.3.0p1 and the
latest snapshot (openssh-SNAP-20001114).
The patch adds 3 lines to nchan.c in a switch stmt (line 100). It simply
caters for the cases where the input channel state is
2000 Jun 14
2
TCP connection forwarding troubles
For some time I have routinely websurfed across a forwarded TCP
connection using SSH. The other end of the TCP tunnel connects to a
Squid proxy cache on the same machine.
This usually works. But I see lots of error messages on each end of
the form
Jun 13 13:22:02 tunnel sshd[32378]: error: channel 0: chan_shutdown_read: shutdown() failed for fd5 [i1 o128]: Transport endpoint is not connected
2002 Jan 27
0
[PATCH] Fix for hang-on-exit bug in OpenSSH-3.0.2p1
Here is a simpler patch (based on Markus Friedl's suggestion posted to this
list) to OpenSSH-3.0.2p1 to fix the hang-on-exit bug (Protocol 2 only). To
date, no data loss has been reported with this patch: it does not break ssh
or scp.
This patch should make OpenSSH work on all operating systems exactly as it
does under FreeBSD.
This patch and others are maintained on the
2001 Sep 05
2
sshd hangs on logout -- is this a bug?
In the changelog, there is an entry:
20001129
- (djm) Back out all the serverloop.c hacks. sshd will now hang again
if there are background children with open fds.
Does this mean that this is regarded as expected (and correct) behavior, that
should not change in the future, or does it mean that this behavior is a
known problem that someone will eventually fix?
--Adam
--
Adam McKenna
2000 Dec 15
1
istate / ostate error?
Log snippet:
channel 10: istate 4 != open
channel 10: ostate 64 != open
channel 11: istate 4 != open
channel 11: ostate 64 != open
channel 12: istate 4 != open
channel 12: ostate 64 != open
channel 13: istate 4 != open
channel 13: ostate 64 != open
channel 14: istate 4 != open
channel 14: ostate 64 != open
channel 15: istate 4 != open
channel 15: ostate 64 != open
% ssh -V
SSH Version
2002 Mar 25
0
[Bug 184] New: 3.1p1 openssh fails to build a working sshd on Trusted HP-UX 10.26
http://bugzilla.mindrot.org/show_bug.cgi?id=184
Summary: 3.1p1 openssh fails to build a working sshd on Trusted
HP-UX 10.26
Product: Portable OpenSSH
Version: -current
Platform: HPPA
OS/Version: HP-UX
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo:
2007 Mar 23
7
4.6p1 chan_read_failed error
The 4.6p1 sshd is logging this error during remote commands or file
transfers:
error: channel 0: chan_read_failed for istate 3
Platform is Solaris 8, 4.6p1 + OpenSSL 0.9.8d.
The commands and transfers work correctly, so the error message appears
to be spurious. The error message does not appear when processing logins.
Otherwise 4.6p1 is running without any apparent problems. This error
2000 Jun 28
1
connection forwarding troubles
I'm still seeing problems when I use TCP connection forwarding across
SSH to surf the web. I see lots of error messages of the form
channel 1: chan_shutdown_read: shutdown() failed for fd7 [i1 o128]: Transport endpoint is not connected
And I see occasional connection lockups.
Both ends are running openssh-2.1.1p1.
Phil
2003 Dec 16
1
[Bug 773] OpenSSH hangs or silently exits on write failure on stdout/stderr
http://bugzilla.mindrot.org/show_bug.cgi?id=773
Summary: OpenSSH hangs or silently exits on write failure on
stdout/stderr
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-bugs
2000 May 15
0
Strange problem with X11 forwarding...
Ok...
This could be cockpit error, but I just don't see it. I've
installed OpenSSH 2.1.0 and I can't get X11 forwarding to work. I
don't recall having this problem under 1.2.3, but I don't use X11
forwarding often enough to really say that I actually saw it work
either.
Both sides are running OpenSSH-2.1.0-1 installed from rpm.
The client side is running RedHat Linux 6.1