Your message dated Thu, 10 Sep 2020 09:46:35 -0700 with message-id <24b21def-9d3d-d9f7-02ad-9b964ca36cf5@cyberhqz.com> and subject line scripted ssh sessions has caused the Debian Bug report #109717, regarding ssh: scripted ssh sessions tend to hang to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 109717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=109717 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: ssh: scripted ssh sessions tend to hang
- From: Ryan Murray <rmurray@cyberhqz.com>
- Date: Wed, 22 Aug 2001 21:51:24 -0700
- Message-id: <200108230451.VAA06257@straylight.cyberhqz.com>
Package: ssh Version: 1:2.3.0p1-1.13 Severity: important Scripted ssh sessions tend to "hang" from time to time. The source end thinks it has a socket open in the ESTABLISHED state, and the remote end shows the socket in TIME_WAIT. A message like this is seen in the log on the remote end: sshd[27823]: error: channel 0: internal error: we do not read, but chan_read_failed for istate 8 This error message comes up quite soon after the publickey is accepted, with both ssh2 and ssh protocols (3 seconds in the case I have handy). I've reported the ssh server version above, clients have been the same version (for sure), and possibly some of the 2.9 series (not as sure).
--- End Message ---
--- Begin Message ---
- To: 109717-done@bugs.debian.org
- Subject: scripted ssh sessions
- From: Ryan Murray <rmurray@cyberhqz.com>
- Date: Thu, 10 Sep 2020 09:46:35 -0700
- Message-id: <24b21def-9d3d-d9f7-02ad-9b964ca36cf5@cyberhqz.com>
Hi,This was an occasional bug that was hard to reproduce, but I don't think anyone has seen it since the upstream fixes in 2001, so (finally) closing.
--- End Message ---