Displaying 20 results from an estimated 3000 matches similar to: "ServerAliveCountMax (and Client) waits for TCP timeout before process exit"
2007 Jul 24
1
ssh client does not timeout if the network fails after ssh_connect but before ssh_exchange_identification, even with Alive options set
Hello,
I am testing ssh with occasional network disconnection between server and
client during these days. I found ssh sometimes hangs if the disconnection
happens after the connection is established but before
ssh_exchange_identification completes. The ssh configuration files show that
both client and server alive options are set.
In /etc/ssh/ssh_config:
# Send keepalive messages to the server.
2008 May 15
0
"ServerAliveInterval" and "ServerAliveCountMax" doesnt work in openssh50?
Hi OpenSSH team,
We found that openssh5.0 has a bug with the "ServerAliveInterval" and "ServerAliveCountMax" options.
This function doesnt work at all, which means when the Maxtime reached, the ssh will not kill the connection and prompt the infomation "Connection Timedout" as it used to do.
We built the openssh5.0p1 code on the a Linux box, and use the
2008 May 16
4
[Bug 1465] New: "ServerAliveInterval" and "ServerAliveCountMax" doesnt work in openssh50?
https://bugzilla.mindrot.org/show_bug.cgi?id=1465
Summary: "ServerAliveInterval" and "ServerAliveCountMax" doesnt
work in openssh50?
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.0p1
Platform: Other
OS/Version: HP-UX
Status: NEW
Severity: critical
2018 Feb 12
4
Problem with ssh disconnecting
Running CentOS 7 on workstation and having a problem with ssh disconnects. My ssh_config contains:
Host *
TCPKeepAlive yes
ServerAliveInterval 30
ServerAliveCountMax 300
and sshd_config on the server contains:
TCPKeepAlive yes
ClientAliveInterval 60
ClientAliveCountMax 300
Have I missed any setting needed to prevent these random disconnects? I don't think there is anything wrong with the
2018 Feb 13
4
Problem with ssh disconnecting
On 02/12/2018 07:24 PM, Liam O'Toole wrote:
> On 2018-02-12, H <agents at meddatainc.com> wrote:
>> Running CentOS 7 on workstation and having a problem with ssh
>> disconnects. My ssh_config contains:
>>
>> Host *
>> TCPKeepAlive yes
>> ServerAliveInterval 30
>> ServerAliveCountMax 300
>>
>> and sshd_config on the server contains:
2012 Jun 25
0
Tuneles ssh se caen.
Buenas tardes,
Necesito obtener informaci?n de la cantidad de tuneles ssh que puede tener activo un servidor y adem?s por cuanto tiempo pueden permanecer activos estos tuneles.
Explico mi situaci?n, tengo un servidor centos 5.5, con sistema ssh que viene por defecto la versi?n 4.3. A este servidor se conectan alrededor de 100 terminales, cada uno de estos terminales levantan 3 tuneles contra el
2018 Feb 12
0
Problem with ssh disconnecting
On Mon, Feb 12, 2018 at 6:25 PM H <agents at meddatainc.com> wrote:
> Running CentOS 7 on workstation and having a problem with ssh disconnects.
> My ssh_config contains:
>
> Host *
> TCPKeepAlive yes
> ServerAliveInterval 30
> ServerAliveCountMax 300
>
> and sshd_config on the server contains:
>
> TCPKeepAlive yes
> ClientAliveInterval 60
>
2018 Feb 13
0
Problem with ssh disconnecting
On 2018-02-12, H <agents at meddatainc.com> wrote:
> Running CentOS 7 on workstation and having a problem with ssh
> disconnects. My ssh_config contains:
>
> Host *
> TCPKeepAlive yes
> ServerAliveInterval 30
> ServerAliveCountMax 300
>
> and sshd_config on the server contains:
>
> TCPKeepAlive yes
> ClientAliveInterval 60
> ClientAliveCountMax 300
>
2018 Feb 13
0
Problem with ssh disconnecting
On 2018-02-13, H <agents at meddatainc.com> wrote:
> On 02/12/2018 07:24 PM, Liam O'Toole wrote:
>> On 2018-02-12, H <agents at meddatainc.com> wrote:
>>> Running CentOS 7 on workstation and having a problem with ssh
>>> disconnects. My ssh_config contains:
>>>
>>> Host *
>>> TCPKeepAlive yes
>>> ServerAliveInterval 30
2018 Feb 13
0
Problem with ssh disconnecting
On Mon, 2018-02-12 at 20:13 -0500, H wrote:
> On 02/12/2018 07:24 PM, Liam O'Toole wrote:
> > On 2018-02-12, H <agents at meddatainc.com> wrote:
> > > Running CentOS 7 on workstation and having a problem with ssh
> > > disconnects. My ssh_config contains:
> > >
> > > Host *
> > > TCPKeepAlive yes
> > > ServerAliveInterval 30
2010 Aug 02
7
Persistent SSH sessions
Hi all
I have an ADSL modem which reboots when there is a power cut and the
inverter (UPS) kicks in. Internet access is down for a duration of 1
to 2 minutes while the modem boots.
I have many SSH tunnels and shells active. Due to the default
"TCPKeepAlive On" setting, these sessions are terminated almost
immediately.
I tried the following configuration:
sshd_config on server:
2018 Feb 13
2
Problem with ssh disconnecting
On 02/12/2018 06:34 PM, Stephen John Smoogen wrote:
> On Mon, Feb 12, 2018 at 6:25 PM H <agents at meddatainc.com> wrote:
>
>> Running CentOS 7 on workstation and having a problem with ssh disconnects.
>> My ssh_config contains:
>>
>> Host *
>> TCPKeepAlive yes
>> ServerAliveInterval 30
>> ServerAliveCountMax 300
>>
>> and
2007 Mar 08
1
Tip for SSH users with connection unexpectedly closed troubles
Thanks for rsync - it's great! I use it for all my backups.
I use rsync via SSH. Recently - I was having trouble with my backups:
rsync: connection unexpectedly closed (4968349 bytes received so far)
[receiver]
rsync error: error in rsync protocol data stream (code 12) at
io.c(453) [receiver=2.6.9]
After following all the steps in the FAQ and issues.html on the rsync
website, searching the
2018 Feb 27
3
Established connection timing out
I don't believe you've said: are the disconnects happening during periods
of idleness on the connection, or periods of activity? If idleness, some
device or script could be actively doing a disconnect-on-idle.
On Mon, 26 Feb 2018, Kip Warner wrote:
> Hey list,
>
> I've read the man page for both the client and server daemon, so either
> I missed something or this
2016 Oct 20
8
[Bug 2627] New: Documentation update: semantic of ClientAliveCountMax 0 unclear
https://bugzilla.mindrot.org/show_bug.cgi?id=2627
Bug ID: 2627
Summary: Documentation update: semantic of ClientAliveCountMax
0 unclear
Product: Portable OpenSSH
Version: 7.3p1
Hardware: All
OS: All
Status: NEW
Severity: trivial
Priority: P5
Component: sshd
2012 Jan 25
2
Server/Client Alive mechanism issues
Hello,
I have a bandwidth-constrained connection that I'd like to run rsync
over through an SSH tunnel. I also want to detect any network drops
pretty rapidly.
On the servers I'm setting (via sshd_config):
ClientAliveCountMax 5
ClientAliveInterval 1
TCPKeepAlive no
and on the clients I'm setting (via ssh_config):
ServerAliveCountMax 5
ServerAliveInterval 1
TCPKeepAlive no
After
2001 Mar 28
2
Big bug in vorbis encoder?
I was just compressed a file with vorbis and I get a big
glitch in the file when I play it back.
Here's a picture of the sound (in SoundForge) before/after
vorbis compression: http://www.artlum.com/pub/oggproblem.gif
The top half of the image is the original wave file and
the bottom half is the file after compression/decompression.
The compressor was the latest Windows oggdrop, and
I
2014 Aug 25
13
[Bug 2265] New: ServerAlive{Interval,CountMax} ignored if using an active -R or -L tunnel
https://bugzilla.mindrot.org/show_bug.cgi?id=2265
Bug ID: 2265
Summary: ServerAlive{Interval,CountMax} ignored if using an
active -R or -L tunnel
Product: Portable OpenSSH
Version: -current
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component:
2004 Nov 09
1
survSplit: further exploration and related topics
To Danardonos concern of splitting time for records with delayed entry:
This can fairly easily be accomodated, by simply splitting time in small
intervals of time since entry into the study, and then compute the value
of the other timescales for each of these e.g.:
current.age <- time.from.entry + age.at.entry
but the cut on the other timescales will not be exactly where you may
want
them
2007 Dec 14
3
Enabling ServerAliveInterval by default
Hi,
In the last several years, I noticed an annoying problem with ssh:
Long-running ssh connections are automatically disconnected after just a
few minutes of inactivity. This problem effects both interactive sessions
(using ssh without screen(1) became almost impossible...) as well as ssh port
forwarding and the likes.
I never noticed this problem until about 6 years ago, but since then have