On Sat, Nov 16, 2024 at 01:25:11PM +0000, Helge Kreutzmann wrote: > I'm using ssh a lot, usually having several ssh connections open the > entire day. > > About a week ago the connections started to terminate quickly, i.e. > after a few minutes (I can time this, if this is of any importance). > So I return to the ssh client, and on the first key I hit, the session > is terminated and I get a message like: > > Connection to 142.132.201.35 closed. > client_loop: send disconnect: Broken pipe > > The (very) bad thing is that the session is not closed ordinarily, > e.g. bash_history does not contain the last commands (fortunately I > did not have any other data loss so far). > > If I work in the ssh session, the the dying is delayed, so it seems > like the sssion dies after a certain inactivity time. > > But this is very annoying, I'm in the middle of some work, read a man > page or a web page just to find out, that the session died, I have to > login again, cd to the correct directory etc. > > The ssh target configuration is unchanged (running Debian stable) as > well. > > If you need any further information, I'm glad to provide it.
I think this is quite likely to be a network-level problem rather than anything to do with OpenSSH. But perhaps running with at least `ssh -v` (or `ssh -vvv` if the extra output isn't too annoying) would at least get a bit more information. -- Colin Watson (he/him) [cjwat...@debian.org]
