[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771320#comment-16771320
]
Goldstein Lyor commented on SSHD-891:
-
{quote}
Can you please let us know if there is a way to change the configuration of
maxKeyInterval ,i mean can we do it via any configuration file.
{quote}
The answer is in the code you attached
{code:java}
maxKeyInterval = getLongProperty(ServerFactoryManager.REKEY_TIME_LIMIT,
maxKeyInterval);
{code}
The code tries to access a property ({{REKEY_TIME_LIMIT="rekey-time-limit"}})
providing a default value (1 hour) in case the user did not provide an
overriding value for it. There are several ways to override the default value -
one of them (at least in version 2.x) is via a system property that you can
provide when you start the Java application via
{{-D...some-naming-convention=your value}}. Unfortunately, 0.13.0 does not have
this option - the only way to do this is via code:
{code:java}
SshServer server = ...
server.getProperties().put(ServerFactoryManager.REKEY_TIME_LIMIT, "some
value in millis...");
// also recommended
server.getProperties().put(ServerFactoryManager.REKEY_BYTES_LIMIT, "...some
very large long value..." /* e.g. Long.toString(Long.MAX_VALUE / 2L) */);
{code}
> SSh connections gets closed for every one hour with 0.13.0 version
> --
>
> Key: SSHD-891
> URL: https://issues.apache.org/jira/browse/SSHD-891
> Project: MINA SSHD
> Issue Type: Bug
>Reporter: Anudeep
>Assignee: Goldstein Lyor
>Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle
> time even though there are incoming pacets data is not being wriiten to
> client for every one hour and is being idle(10 mins which is default timeout
> of ssh session).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770968#comment-16770968
]
Anudeep commented on SSHD-891:
--
Hi [~lgoldstein],
We see issue to be with ssh client which uses lib-ssh(0.4.5) .
In apache sshd-core(0.13.0) there is a logic to reexchange the keys for every
one hour ,server is able to send the key to client and client is not able to
send it back to server and session gets timeout and closed.
Please find below logs
{code:java}
02019-02-16 11:12:52,438 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(EJB default - 11) Writing 68 bytes
2019-02-16 11:12:52,439 INFO [org.apache.sshd.server.session.ServerSession]
(EJB default - 11) Initiating key re-exchange
2019-02-16 11:12:52,439 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[78670623]-nio2-thread-3) Finished writing
2019-02-16 11:12:52,439 DEBUG [org.apache.sshd.server.session.ServerSession]
(EJB default - 11) Send SSH_MSG_KEXINIT
2019-02-16 11:12:52,439 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session] (EJB
default - 11) Writing 644 bytes
2019-02-16 11:12:52,444 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[78670623]-nio2-thread-1) Finished writing
2019-02-16 11:13:02,438 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 15) Consume server remote window by 4 down to 191444
2019-02-16 11:13:02,439 DEBUG [org.apache.sshd.server.channel.ChannelSession]
(EJB default - 15) Send SSH_MSG_CHANNEL_DATA on channel 0
2019-02-16 11:13:02,440 INFO [org.apache.sshd.server.session.ServerSession]
(EJB default - 15) Start flagging packets as pending until key exchange is done
2019-02-16 11:13:12,439 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 19) Consume server remote window by 4 down to 191440
2019-02-16 11:13:12,439 DEBUG [org.apache.sshd.server.channel.ChannelSession]
(EJB default - 19) Send SSH_MSG_CHANNEL_DATA on channel 0
2019-02-16 11:13:22,439 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 23) Consume server remote window by 4 down to 191436
2019-02-16 11:13:22,439 DEBUG [org.apache.sshd.server.channel.ChannelSession]
(EJB default - 23) Send SSH_MSG_CHANNEL_DATA on channel 0
2019-02-16 11:13:32,438 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 27) Consume server remote window by 4 down to 191432
2019-02-16 11:13:32,438 DEBUG [org.apache.sshd.server.channel.ChannelSession]
(EJB default - 27) Send SSH_MSG_CHANNEL_DATA on channel 0
2019-02-16 11:13:42,439 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 31) Consume server remote window by 4 down to 1:
{code}
{code}
public class ServerSession extends AbstractSession {
protected static final long MAX_PACKETS = (1l << 31);
private long authTimeoutTimestamp;
private long idleTimeoutTimestamp = 0L;
private int authTimeoutMs = 2 * 60 * 1000;// 2 minutes in milliseconds
private int idleTimeoutMs = 10 * 60 * 1000; // 10 minutes in milliseconds
private long maxBytes = 1024 * 1024 * 1024; // 1 GB
private long maxKeyInterval = 60*60*1000 ; // 1 hour
public ServerSession(ServerFactoryManager server, IoSession ioSession)
throws Exception {
super(true, server, ioSession);
authTimeoutMs = getIntProperty(ServerFactoryManager.AUTH_TIMEOUT,
authTimeoutMs);
authTimeoutTimestamp = System.currentTimeMillis() + authTimeoutMs;
idleTimeoutMs = getIntProperty(ServerFactoryManager.IDLE_TIMEOUT,
idleTimeoutMs);
maxBytes = Math.max(32,
getLongProperty(ServerFactoryManager.REKEY_BYTES_LIMIT, maxBytes));
maxKeyInterval = getLongProperty(ServerFactoryManager.REKEY_TIME_LIMIT,
maxKeyInterval);
log.info("Server session created from {}",
ioSession.getRemoteAddress());
sendServerIdentification();
kexState.set(KEX_STATE_INIT);
sendKexInit();
}
{code}
Can you please let us know if there is a way to change the configuration of
maxKeyInterval ,i mean can we do it via any configuration file.
Regards,
Anudeep
> SSh connections gets closed for every one hour with 0.13.0 version
> --
>
> Key: SSHD-891
> URL: https://issues.apache.org/jira/browse/SSHD-891
> Project: MINA SSHD
> Issue Type: Bug
>Reporter: Anudeep
>Assignee: Goldstein Lyor
>Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle
> time even though there are incoming pacets data is not being wriiten to
> client for every one hour and is being idle(10 mins which is default timeout
> of ssh session).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770161#comment-16770161
]
Goldstein Lyor commented on SSHD-891:
-
Sorry - the log you attached is incomplete at best - a lot of crucial
information is lacking so I dare not venture a guess. Furthermore, since I have
no idea whatsoever what your code is trying to achieve and how, I do not want
to mislead you by speculating. However:
* You claim to have upgraded from 0.13.0 to 2.1.0 (actually I recommend you
upgrade to the newly released 2.2.0). This is a huge leap between virtually
incompatible versions. I strongly suggest you
** Recompile the code that invokes SSHD code - I have a feeling the upgrade
from 0.13.0 to 2.1.0 (or 2.2.0) is not as smooth as it may seem
** Read the [documentation|https://github.com/apache/mina-sshd/] - perhaps more
than once since there are may non-trivial concepts - including configurations,
behavior, etc...
** Re-visit key RFC sections (most are mentioned in the documentation) to have
a better understanding of the protocol
** Review your code in view of what you have learned and try to figure out what
is going on and why it is failing
** Open relevant log levels and provide more information - not only the
exception but also what led to it, what was the code trying to do when the
exception occurred, what SSH messages were being exchanged etc,...
Best I can do for now with the limited information I can glean from the issue
and without actually seeing the code in question or have full log information.
My *wild guess* based on the exception is that the client fails to write a
packet to its peer - as to why, your guess is as good as mine...
{quote}
And with respect to setting the state of sshd we are not able to access the
state variable from ssh-server package as state varaible is made protected in
ssh-common package
{quote}
I do not understand why you need access to this variable...
> SSh connections gets closed for every one hour with 0.13.0 version
> --
>
> Key: SSHD-891
> URL: https://issues.apache.org/jira/browse/SSHD-891
> Project: MINA SSHD
> Issue Type: Bug
>Reporter: Anudeep
>Assignee: Goldstein Lyor
>Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle
> time even though there are incoming pacets data is not being wriiten to
> client for every one hour and is being idle(10 mins which is default timeout
> of ssh session).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16770055#comment-16770055
]
Anudeep commented on SSHD-891:
--
Hi [~lgoldstein],
We have uplifted sshd-core version from 0.13.0 to 2.1.0.
But with 2.1.0 we see many impacts
one such is client session is getting closed abruptly after few minutes
Please find below logs
{code:java}
[id=0, recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58516])
by 4 down to 191244
2019-02-16 06:34:10,697 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session] (EJB
default - 44) writePacket(Nio2Session[local=/10.247.
246.100:8345, remote=/141.137.237.205:58516]) Writing 68 bytes
2019-02-16 06:34:10,697 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[5c704bd8]-nio2-thread-3)
handleCompletedWriteCycle(Nio2Session[local=/10.247.246.100:8345,
remote=/141.137.237.205:58516]) finished writing len=68
2019-02-16 06:34:17,050 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
exceptionCaught(Nio2Session[local=/10.247.246.100:8345,
remote=/141.137.237.205:58516]) caught InterruptedByTimeoutException[null] -
calling handler
2019-02-16 06:34:17,050 WARN [org.apache.sshd.server.session.ServerSessionImpl]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
exceptionCaught(ServerSessionImpl[administrator@/141.137.237.205:58516])[state=Opened]
InterruptedByTimeoutException: null
2019-02-16 06:34:17,050 DEBUG
[org.apache.sshd.server.session.ServerSessionImpl]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
exceptionCaught(ServerSessionImpl[administrator@/141.137.237.205:58516])[state=Opened]
details: java.nio.channels.InterruptedByTimeoutException
at
sun.nio.ch.UnixAsynchronousSocketChannelImpl$1.run(UnixAsynchronousSocketChannelImpl.java:456)
[rt.jar:1.8.0_172]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[rt.jar:1.8.0_172]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_172]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[rt.jar:1.8.0_172]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[rt.jar:1.8.0_172]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[rt.jar:1.8.0_172]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[rt.jar:1.8.0_172]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_172]
2019-02-16 06:34:17,053 DEBUG
[org.apache.sshd.common.session.helpers.SessionTimeoutListener]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
sessionException(ServerSessionImpl[administrator@/141.137.237.205:58516])
InterruptedByTimeoutException: null
2019-02-16 06:34:17,053 DEBUG
[org.apache.sshd.common.session.helpers.SessionTimeoutListener]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
sessionClosed(ServerSessionImpl[administrator@/141.137.237.205:58516])
un-tracked
2019-02-16 06:34:17,053 DEBUG
[org.apache.sshd.server.session.ServerSessionImpl]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
close(ServerSessionImpl[administrator@/141.137.237.205:58516]) Closing
immediately
2019-02-16 06:34:17,053 DEBUG
[org.apache.sshd.server.session.ServerConnectionService]
(sshd-SshServer[5c704bd8]-nio2-thread-1)
close(ServerConnectionService[ServerSessionImpl[administrator@/141.137.237.205:58516]])
Closing immediately
2019-02-16 06:34:17,054 DEBUG [org.apache.sshd.server.channel.ChannelSession]
(sshd-SshServer[5c704bd8]-nio2-thread-1) close(ChannelSession[id=0,
recipient=43]-ServerSessionImpl[administrator@/141.137.237.205:58516]) Closing
immediately
2019-02-16 06:34:17,054 DEBUG [org.apache.sshd.server.channel.ChannelSession]
(sshd-SshServer[5c704bd8]-nio2-thread-1) close(Channel:
{code}
And with respect to setting the state of sshd we are not able to access the
state variable from ssh-server package as state varaible is made protected in
ssh-common package
{code}
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
package org.apache.sshd.common.util.closeable;
import java.util.concurrent.atomic.AtomicRef
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[ https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764778#comment-16764778 ] Goldstein Lyor commented on SSHD-891: - Sorry - I don't think I can help much since I don't understand what the code is trying to do. Furthermore, insofar as logging goes, these seem to be *client* side logs and I was referring to *server* side ones originating from the SSHD daemon/server which may help shed some light on whether the server is the one who is closing the session, and if so why. Again, I strongly recommend upgrading as it may either fix the issue or at least provide a more common code-base to discuss... > SSh connections gets closed for every one hour with 0.13.0 version > -- > > Key: SSHD-891 > URL: https://issues.apache.org/jira/browse/SSHD-891 > Project: MINA SSHD > Issue Type: Bug >Reporter: Anudeep >Assignee: Goldstein Lyor >Priority: Blocker > > SSH connections are getting closed for every one hours after 10 mins of idle > time even though there are incoming pacets data is not being wriiten to > client for every one hour and is being idle(10 mins which is default timeout > of ssh session). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764711#comment-16764711
]
Anudeep commented on SSHD-891:
--
Hi [~lgoldstein],
Regarding the message sent that would be a message from server(there is a timer
at server side which sends "HB" message from server for every 30 seconds if
there are no incoming packets from server to client.
Please find below logs
Lsof output :svc-2-sg
Wed Feb 6 05:30:17 CET 2019
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
java 4409 root 502u IPv6 1015404 0t0 TCP svc-2-sg:8345->192.168.42.24:33589
(ESTABLISHED)
java 4409 root 525u IPv6 19463 0t0 TCP *:8345 (LISTEN)
502 is the FD here for the VM
VM Server.log :
{code:java}
Please find Apache being idle in the 10 mins as mentioned (ie 5:29 to 5:39) in
the server.log of VM.
2019-02-06 05:28:27,759 INFO [com.ericsson.oss.itpf.COMMAND_LOGGER]
(pool-7-thread-1888) [omega, Acknowledge, STARTED, BNSI NBI Client, BNSI NBI
Server, NotificationIdentifier = 140154550]
2019-02-06 05:28:57,723 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 8) Consume server remote window by 4 down to 79982
2019-02-06 05:28:57,724 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session] (EJB
default - 8) Writing 68 bytes
2019-02-06 05:28:57,726 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[4166a223]-nio2-thread-3) Finished writing
2019-02-06 05:29:27,721 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 19) Consume server remote window by 4 down to 79978
2019-02-06 05:29:27,722 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session] (EJB
default - 19) Writing 68 bytes
2019-02-06 05:29:27,723 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[4166a223]-nio2-thread-1) Finished writing
2019-02-06 05:29:27,724 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session] (EJB
default - 19) Writing 532 bytes
2019-02-06 05:29:27,725 DEBUG [org.apache.sshd.common.io.nio2.Nio2Session]
(sshd-SshServer[4166a223]-nio2-thread-3) Finished writing
2019-02-06 05:29:57,722 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 32) Consume server remote window by 4 down to 79974
2019-02-06 05:30:27,721 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 42) Consume server remote window by 4 down to 79970
2019-02-06 05:30:57,722 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 53) Consume server remote window by 4 down to 79966
2019-02-06 05:31:27,722 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 65) Consume server remote window by 4 down to 79962
2019-02-06 05:31:57,721 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 75) Consume server remote window by 4 down to 79958
2019-02-06 05:32:10,641 TRACE [org.apache.sshd.common.channel.Window]
(Thread-1259 (HornetQ-client-global-threads-22246058)) Consume server remote
window by 1532 down to 78426
2019-02-06 05:32:40,645 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 91) Consume server remote window by 4 down to 78422
2019-02-06 05:33:10,652 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 101) Consume server remote window by 4 down to 78418
2019-02-06 05:33:30,662 TRACE [org.apache.sshd.common.channel.Window]
(Thread-1260 (HornetQ-client-global-threads-22246058)) Consume server remote
window by 1532 down to 76886
2019-02-06 05:34:00,665 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 121) Consume server remote window by 4 down to 76882
2019-02-06 05:34:30,668 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 3) Consume server remote window by 4 down to 76878
2019-02-06 05:35:00,665 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 15) Consume server remote window by 4 down to 76874
2019-02-06 05:35:30,666 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 27) Consume server remote window by 4 down to 76870
2019-02-06 05:36:00,665 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 37) Consume server remote window by 4 down to 76866
2019-02-06 05:36:30,665 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 51) Consume server remote window by 4 down to 76862
2019-02-06 05:37:00,665 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 59) Consume server remote window by 4 down to 76858
2019-02-06 05:37:30,666 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 70) Consume server remote window by 4 down to 76854
2019-02-06 05:38:00,665 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 84) Consume server remote window by 4 down to 76850
2019-02-06 05:38:30,666 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 90) Consume server remote window by 4 down to 76846
2019-02-06 05:39:00,666 TRACE [org.apache.sshd.common.channel.Window] (EJB
default - 103) Consume server remote window by 4 down to 76842
2019-02-06 05:39:28,487 DEBUG [org.apache.ss
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764468#comment-16764468
]
Goldstein Lyor commented on SSHD-891:
-
* All I can suggest for now is that you open the DEBUG (and perhaps TRACE) log
levels for the SSHD session and see what packets are sent and whether as you
claim
{quote}
after one hour even though server sends a message to client ,it is not able to
write and session is becoming idle for 10 mins
{quote}
* Can you also specify what is this special message that is sent from the
server ? Is it an application message or some SSH special packet ?
In any case, you can configure the idle timeout and perhaps even reset the idle
timeout timer yourself - though as I said, since 0.13 is such an old version I
doubt I can help you locate the exact piece of code.
> SSh connections gets closed for every one hour with 0.13.0 version
> --
>
> Key: SSHD-891
> URL: https://issues.apache.org/jira/browse/SSHD-891
> Project: MINA SSHD
> Issue Type: Bug
>Reporter: Anudeep
>Assignee: Goldstein Lyor
>Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle
> time even though there are incoming pacets data is not being wriiten to
> client for every one hour and is being idle(10 mins which is default timeout
> of ssh session).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764469#comment-16764469
]
Goldstein Lyor commented on SSHD-891:
-
{quote}
Can you please let us know the root cause ,so that we can decide whether to
migrate or not.
{quote}
I recommend you migrate regardless - this will not be the last issue you are
likely to encounter, and as you can see it is very difficult to provide support
for old versions
> SSh connections gets closed for every one hour with 0.13.0 version
> --
>
> Key: SSHD-891
> URL: https://issues.apache.org/jira/browse/SSHD-891
> Project: MINA SSHD
> Issue Type: Bug
>Reporter: Anudeep
>Assignee: Goldstein Lyor
>Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle
> time even though there are incoming pacets data is not being wriiten to
> client for every one hour and is being idle(10 mins which is default timeout
> of ssh session).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[ https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764396#comment-16764396 ] Anudeep commented on SSHD-891: -- Hi [~lgoldstein], I would like to provide a brief note on the issue. There is a client with ssh v2 version (omega) which is connecting to a server .In order to keep the session alive there is a mechanism from sever to send a message to client for every 30 seconds so that if there is not packet which needs to be send from server to client then a message would be sent to client for every 30 seconds. The above scenario is able to withstand for one hour and immediately after one hour even though server sends a message to client ,it is not able to write and session is becoming idle for 10 mins . Since ssh default idle timeout is 10 mins ssh server is killing the session. So we need to understand why exactly after every one hour the message from server is not written. It is not that easy for us now to migrate to latest version ,if we can find the root cause we will try to migrate. Side effect of this issue is for every two days we are not able to open a new ssh connection. connections seems to be in CLOSE_WAIT state and no new connection is established. Regards, Anudeep > SSh connections gets closed for every one hour with 0.13.0 version > -- > > Key: SSHD-891 > URL: https://issues.apache.org/jira/browse/SSHD-891 > Project: MINA SSHD > Issue Type: Bug >Reporter: Anudeep >Assignee: Goldstein Lyor >Priority: Blocker > > SSH connections are getting closed for every one hours after 10 mins of idle > time even though there are incoming pacets data is not being wriiten to > client for every one hour and is being idle(10 mins which is default timeout > of ssh session). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[
https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764342#comment-16764342
]
Goldstein Lyor commented on SSHD-891:
-
Please clarify the description - especially
* What is meant by
{quote}
very one hours after 10 mins of idle time
{quote}
* ditto for
{quote}
incoming pacets data is not being wriiten to client for every one hour and is
being idle(10 mins which is default timeout of ssh session).
{quote}
* The issue also does not specify if the timeout is at the client or server
side - though it seems to be server side...
* Is the client SSHD as well or some other ?
Regardless, here are some facts about the idle timeout:
* It can be configured - see {{FactoryManager#IDLE_TIMEOUT}} - if the set value
is negative, then idle timeout is disabled.
* If you open the DEBUG level of the {{ServerSessionImpl}} (assuming the
problem occurs on the server side) you will be able to see the timeout message
(see {{SessionHelper#checkForTimeouts}})
* I doubt that {quote}there are incoming pacets{quote} since almost any
incoming packet causes idle timeout restart - except for special ones. Please
open the relevant log and show the incoming packets that still cause the idle
timeout to expire.
> SSh connections gets closed for every one hour with 0.13.0 version
> --
>
> Key: SSHD-891
> URL: https://issues.apache.org/jira/browse/SSHD-891
> Project: MINA SSHD
> Issue Type: Bug
>Reporter: Anudeep
>Priority: Blocker
>
> SSH connections are getting closed for every one hours after 10 mins of idle
> time even though there are incoming pacets data is not being wriiten to
> client for every one hour and is being idle(10 mins which is default timeout
> of ssh session).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SSHD-891) SSh connections gets closed for every one hour with 0.13.0 version
[ https://issues.apache.org/jira/browse/SSHD-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764344#comment-16764344 ] Goldstein Lyor commented on SSHD-891: - I just noticed that the issue is for version 0.13 - it is an (extremely) old version - please use 2.1.0 (or even 2.2.0 soon to be released). If it persists in 2.1.0 (or 2.2.0) then we can fix it (assuming all the relevant log data and clarification has been provided). Note that we do not provide backpatches so even if you are correct in this issue I doubt we will be able to provide a fix. > SSh connections gets closed for every one hour with 0.13.0 version > -- > > Key: SSHD-891 > URL: https://issues.apache.org/jira/browse/SSHD-891 > Project: MINA SSHD > Issue Type: Bug >Reporter: Anudeep >Assignee: Goldstein Lyor >Priority: Blocker > > SSH connections are getting closed for every one hours after 10 mins of idle > time even though there are incoming pacets data is not being wriiten to > client for every one hour and is being idle(10 mins which is default timeout > of ssh session). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
