[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=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
[GitHub] The-Yoda opened a new pull request #88: Fix download with pattern issue in rooted filesystem
The-Yoda opened a new pull request #88: Fix download with pattern issue in rooted filesystem URL: https://github.com/apache/mina-sshd/pull/88 Right now, download with pattern doesn't work when the underlying filesystem is virtual filesystem. Also, the tests were masking the behaviour by providing working location as rooted filesystem path. This patch fixes the issue, by providing absolute path to retrieve files matching the pattern. cc @lgoldstein @thefourtheye This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[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=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=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=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] [Comment Edited] (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=16764397#comment-16764397 ] Anudeep edited comment on SSHD-891 at 2/10/19 12:52 PM: Can you please let us know the root cause ,so that we can decide whether to migrate or not. was (Author: anudeep): Please can you please let us know the root cause ,so that we can decide whether to migrate or not. > 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] [Reopened] (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:all-tabpanel ] Anudeep reopened SSHD-891: -- Please can you please let us know the root cause ,so that we can decide whether to migrate or not. > 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] [Resolved] (SSHD-871) Split README file into several subject-oriented files
[
https://issues.apache.org/jira/browse/SSHD-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-871.
-
Resolution: Fixed
Fix Version/s: 2.3.0
> Split README file into several subject-oriented files
> -
>
> Key: SSHD-871
> URL: https://issues.apache.org/jira/browse/SSHD-871
> Project: MINA SSHD
> Issue Type: Improvement
>Affects Versions: 2.1.1
>Reporter: Goldstein Lyor
>Assignee: Goldstein Lyor
>Priority: Major
> Labels: documentation, wiki
> Fix For: 2.3.0
>
>
> The current file is a single "monolithic" text covering many subjects. As it
> becomes more detailed, we need to split it into several files with a {{Table
> of contents}} that contains links to each subject. There are several options:
> h5. Use the [Github Wiki
> repository|https://gist.github.com/subfuzion/0d3f19c4f780a7d75ba2] capability
> The problem with this capability is that the WIKI pages require a *separate*
> repository, whereas we would like to have all of the contained in this
> project (e.g., under the _wiki_ folder). We could have a partial solution by
> using perhaps [git
> subtree(s)|https://www.atlassian.com/blog/git/alternatives-to-git-submodule-git-subtree],
> but it would still require 2 repositories.
> Another problem with this solution is that it is tightly coupled with
> _github_ and thus migrating to another GIT host (e.g., _Bitbucket_) would be
> much more difficult.
> h5. Try using relative URL links in the markdown code
> We need to see if links such as:
> {code}
> [This is a link to an SSHD subject](./wiki/TheSubject.md)
> {code}
> would work. If so, then we could consider adding a {{src/main/wiki}} folder
> to each subproject to host wiki pages related to the specific module.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SSHD-872) Split CHANGES file into per-version file(s)
[
https://issues.apache.org/jira/browse/SSHD-872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor resolved SSHD-872.
-
Resolution: Fixed
Fix Version/s: 2.3.0
> Split CHANGES file into per-version file(s)
> ---
>
> Key: SSHD-872
> URL: https://issues.apache.org/jira/browse/SSHD-872
> Project: MINA SSHD
> Issue Type: Improvement
>Affects Versions: 2.1.1
>Reporter: Goldstein Lyor
>Assignee: Goldstein Lyor
>Priority: Major
> Labels: documentation, versions
> Fix For: 2.3.0
>
>
> The {{CHANGES.md}} file was established in version 2.1.1 so for now it
> contains only its changes. Once we release the next version, we should
> consider splitting it into per-version file so it would be easier to
> navigate. We should see if we can use relative links in the markdown - e.g.:
> {code}
> * [Version 2.1.1](./doc/versions/2.1.1.MD)
> * [Version 2.2.5](./doc/versions/2.1.5.MD)
> etc...
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work started] (SSHD-892) Inform user about session timeout and allow intervention
[ https://issues.apache.org/jira/browse/SSHD-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SSHD-892 started by Goldstein Lyor. --- > Inform user about session timeout and allow intervention > > > Key: SSHD-892 > URL: https://issues.apache.org/jira/browse/SSHD-892 > Project: MINA SSHD > Issue Type: Improvement >Affects Versions: 2.2.0 >Reporter: Goldstein Lyor >Assignee: Goldstein Lyor >Priority: Major > > The current code automatically disconnects the session if one of the > idle/authentication timeouts has expired. We would like to be able to inform > the user about the pending disconnect and allow a last-minute intervention > that can cancel the disconnect and reset the timeout measurement. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] thefourtheye commented on issue #87: clear response buffer with unsupported extension
thefourtheye commented on issue #87: clear response buffer with unsupported extension URL: https://github.com/apache/mina-sshd/pull/87#issuecomment-462119454 @lgoldstein Thanks for your help with this fix This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] thefourtheye closed pull request #87: clear response buffer with unsupported extension
thefourtheye closed pull request #87: clear response buffer with unsupported extension URL: https://github.com/apache/mina-sshd/pull/87 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (SSHD-892) Inform user about session timeout and allow intervention
Goldstein Lyor created SSHD-892: --- Summary: Inform user about session timeout and allow intervention Key: SSHD-892 URL: https://issues.apache.org/jira/browse/SSHD-892 Project: MINA SSHD Issue Type: Improvement Affects Versions: 2.2.0 Reporter: Goldstein Lyor Assignee: Goldstein Lyor The current code automatically disconnects the session if one of the idle/authentication timeouts has expired. We would like to be able to inform the user about the pending disconnect and allow a last-minute intervention that can cancel the disconnect and reset the timeout measurement. -- 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=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] [Resolved] (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:all-tabpanel ] Goldstein Lyor resolved SSHD-891. - Resolution: Won't Fix Please re-open if issue still occurs with version 2.1.0 (or beyond) > 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=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)
[jira] [Assigned] (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:all-tabpanel ] Goldstein Lyor reassigned SSHD-891: --- Assignee: Goldstein Lyor > 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)
