[
https://issues.apache.org/jira/browse/KARAF-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15646860#comment-15646860
]
Xilai Dai commented on KARAF-4517:
----------------------------------
This issue happened even from karaf 3.x. The root cause is the changes for
KARAF-2521,
https://github.com/apache/karaf/commit/17dea38acd513f3329697206092f060f6f94c7dc
I really don't understand why bin/client should reuse the parameters from
etc/org.apache.karaf.shell.cfg, especially the sshHost parameter. By default
sshHost = 0.0.0.0 it used by SSH server which means SSH open for all network
interfaces in this host. if no -h arg provided when run bin/client, we
shouldn't use 0.0.0.0 but localhost/127.0.0.1.
> bin/client ends with "Failed to get the session"
> ------------------------------------------------
>
> Key: KARAF-4517
> URL: https://issues.apache.org/jira/browse/KARAF-4517
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 4.0.5
> Environment: Linux
> Reporter: Michal Hlavac
> Labels: cli, client
>
> Steps to reproduce:
> 1. run bin/karaf
> 2. run bin/client in terminal
> It works when I run bin/client -h localhost
> I think it's because sshHost = 0.0.0.0 value in etc/org.apache.karaf.shell.cfg
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
