[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16296936#comment-16296936
]
masc edited comment on SSHD-786 at 12/19/17 3:13 PM:
-
interesting. the behaviour seems to occur only when latency gets bad. and
today's ddos was basically "perfect" for replicating it. so the results are in,
your patch appears to work well. the error is now merely logged and the server
seems to properly recover from it,. the error may occur repeatedly but not
indefinitely.
{code}
2017-12-19 15:42:07,189 209499 pool-2-thread-14
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51402])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-9
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51412])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-21
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51410])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,220 209530 pool-2-thread-23
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51413])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-17
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51410])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-24
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51402])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-27
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51409])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-18
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51409])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,189 209499 pool-2-thread-12
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51412])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,220 209530 pool-2-thread-11
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51411])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,220 209530 pool-2-thread-13
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51413])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,220 209530 pool-2-thread-25
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51404])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,252 209562 pool-2-thread-29
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51408])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,252 209562 pool-2-thread-14
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51411])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,252 209562 pool-2-thread-28
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51404])[state=Opened]
IOException: The specified network name is no longer available.
2017-12-19 15:42:07,252 209562 pool-2-thread-30
org.apache.sshd.server.session.ServerSessionImpl WARN -
exceptionCaught(ServerSessionImpl[leoz@/185.17.204.111:51408])[state=Opened]
IOException: The specified network name is no longer available.
{code}
was (Author: masc3d):
interesting. the behaviour seems to occur only when latency gets bad. and
today's ddos was basically "perfect" for replicating it. so the results are in,
your patch appears to work well. the error is now merely logged and the server
seems to properly recover from it,. the error may occur repeatedly but not
indefinitely.
{{code}}
2017-12-19 15:42:07,189 209499 pool
[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285916#comment-16285916
]
masc edited comment on SSHD-786 at 12/11/17 1:43 PM:
-
and thanks for the recommendations, the ipv6 address also caught my eye,
especially since ipv6 is not enabled on this server. I already added {{
System.setProperty("java.net.preferIPv4Stack", "true")}} for our next test run
and I will also try {{server.setHost("0.0.0.0");}} to see if it mitigates the
issue.
unfortunately it occurs fairly sporadically, there's no straight replication
path. so it may take a while until the results are in.
was (Author: masc3d):
and thanks for the recommendations, the ipv6 address also caught my eye,
especially since ipv6 is not enabled on this server. I already added {{
System.setProperty("java.net.preferIPv4Stack", "true")}} for our next test run
and I will also try {{server.setHost("0.0.0.0");}} to see if it mitigates the
issue.
unfortunately the it occurs fairly sporadically, there's no straight
replication path. so it may take a while until the results are in.
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> -
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
>Reporter: masc
>Assignee: Goldstein Lyor
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285916#comment-16285916
]
masc edited comment on SSHD-786 at 12/11/17 1:43 PM:
-
and thanks for the recommendations, the ipv6 address also caught my eye,
especially since ipv6 is not enabled on this server. I already added
{{System.setProperty("java.net.preferIPv4Stack", "true")}} for our next test
run and I will also try {{server.setHost("0.0.0.0");}} to see if it mitigates
the issue.
unfortunately it occurs fairly sporadically, there's no straight replication
path. so it may take a while until the results are in.
was (Author: masc3d):
and thanks for the recommendations, the ipv6 address also caught my eye,
especially since ipv6 is not enabled on this server. I already added {{
System.setProperty("java.net.preferIPv4Stack", "true")}} for our next test run
and I will also try {{server.setHost("0.0.0.0");}} to see if it mitigates the
issue.
unfortunately it occurs fairly sporadically, there's no straight replication
path. so it may take a while until the results are in.
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> -
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
>Reporter: masc
>Assignee: Goldstein Lyor
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16279992#comment-16279992
]
Goldstein Lyor edited comment on SSHD-786 at 12/6/17 10:44 AM:
---
Interesting, but doesn't it create an infinite loop if continued failures ?
Perhaps we should have some stateful counter that limits this number (and is
zero-ed on success). Maybe even a sleep time between successive attempts to
listen again...
was (Author: lgoldstein):
Interesting, but doesn't it create an infinite loop if continued failures ?
Perhaps we should have some stateful counter that limits this number (and is
zero-ed on success).
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> -
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
>Reporter: masc
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277112#comment-16277112
]
masc edited comment on SSHD-786 at 12/4/17 5:21 PM:
maybe it's worth to check against {{3.0.0}} first. I believe currently
{{sshd-core}} still depends on {{2.0.x}} right?
was (Author: masc3d):
maybe it's worth to check against {{3.0.0}} first. I believe currently
{{sshd-core}} still depends on {2.0.x} right?
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> -
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
>Reporter: masc
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277112#comment-16277112
]
masc edited comment on SSHD-786 at 12/4/17 5:21 PM:
maybe it's worth to check against {{3.0.0}} first. I believe currently
{{sshd-core}} still depends on {2.0.x} right?
was (Author: masc3d):
maybe it's worth to check against {3.0.0} first. I believe currently
{sshd-core} still depends on {2.0.x} right?
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> -
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
>Reporter: masc
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SSHD-786) Clients can't authenticate after unexpected exception in Nio2Acceptor
[
https://issues.apache.org/jira/browse/SSHD-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276561#comment-16276561
]
masc edited comment on SSHD-786 at 12/4/17 9:59 AM:
maybe. however this process hosts other tcp services which never have been
similarly affected for years.
so even if a third party software would be the catalyst for this bug, this is
something that needs to be fixed in {{sshd-core}}
was (Author: masc3d):
maybe. however this process hosts other tcp services which are and never have
been similarly affected for years.
so even if a third party software would be the catalyst for this bug, this is
something that needs to be fixed in {{sshd-core}}
> Clients can't authenticate after unexpected exception in Nio2Acceptor
> -
>
> Key: SSHD-786
> URL: https://issues.apache.org/jira/browse/SSHD-786
> Project: MINA SSHD
> Issue Type: Bug
>Affects Versions: 1.2.0, 1.3.0, 1.4.0, 1.6.0
> Environment: Windows
>Reporter: masc
>
> {code}
> 2017-11-28 15:26:54,808 11566202 sshd-SshServer[434a2a10]-nio2-thread-4
> org.apache.sshd.common.io.nio2.Nio2Acceptor WARN - Caught IOException while
> accepting incoming connection from /0:0:0:0:0:0:0:0:13003: The specified
> network name is no longer available.
> java.io.IOException: The specified network name is no longer available.
> at sun.nio.ch.Iocp.translateErrorToIOException(Iocp.java:309)
> at sun.nio.ch.Iocp.access$700(Iocp.java:46)
> at sun.nio.ch.Iocp$EventHandlerTask.run(Iocp.java:399)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> As soon as this exception occurs once, clients can still connect but will
> fail to authenticate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
