I found the solution. It had nothing to do with ssh itself. We have build a custom distribution and put a custom /bin/karaf file in filtered-resources. Our build server builds this custom distribution and installs it on an external system. The problem was, that the build server replaced the JAVA_HOME variable in /bin/karaf with a fixed java directory. This directory doesn't exist on the external system, which produced the error.
Thx for your help and time! Regards, sprinz -- View this message in context: http://karaf.922171.n3.nabble.com/3-0-1-snapshot-Unable-to-connect-to-container-using-bin-client-or-ssh-tp4031780p4034220.html Sent from the Karaf - User mailing list archive at Nabble.com.
