I am running Openhab on Synology (docker) for quiet some time.
After upgrading to Openhab 5.0.x I am not able to log in to karaf shell to execute commands there:
When starting
docker exec -it openhab-openhab-1-1 /openhab/runtime/bin/client
on my Synolgy I am running into a timeout:
[ssh-connection]: Failed (IOException) to execute: Broken pipe
starting the client with additional logging:
./client -a 8101 -h localhost -u openhab -p habopen -v -l 4
Brings up this log line:
150410 [sshd-SshClient[482cd91f]-timer-thread-1] DEBUG org.apache.sshd.client.session.ClientSessionImpl - checkForTimeouts(ClientSessionImpl[openhab@localhost/127.0.0.1:8101]) disconnect - reason=TimeoutIndicator[status=AuthTimeout, threshold=120000, expired=120364]
150413 [sshd-SshClient[482cd91f]-timer-thread-1] INFO org.apache.sshd.client.session.ClientSessionImpl - Disconnecting(ClientSessionImpl[openhab@localhost/127.0.0.1:8101]): SSH2_DISCONNECT_PROTOCOL_ERROR - Detected AuthTimeout after 120364/120000 ms.
In version 4.x I was not experiencing this issue.
I did implement the configuration advise in Synology DiskStation | openHAB now, but need to mention that my openhab installation was working fine even without those changes.
I tried Synology DS920+ running latest 7.2.2-72806 Update 5 and DS918 running 7.2.64570 Update 4 with the same result - ssh connection is timing out.
I tried starting client from bash as well:
docker exec -it openhab-openhab-1-1 /openhab/runtime/bin/bash
root@openhab-openhab-1:/openhab/runtime/bin# ./client
Logging in as openhab
[ssh-connection]: Failed (IOException) to execute: Broken pipe
What works is:
root@openhab-openhab-1-1:/openhab/runtime/bin# ./shell
_ _ _ ____
___ ___ ___ ___ | | | | / \ | __ )
/ _ \ / _ \ / _ \ / _ \ | |_| | / _ \ | _ \
| (_) | (_) | __/| | | || _ | / ___ \ | |_) )
\___/| __/ \___/|_| |_||_| |_|/_/ \_\|____/
|_| 5.0.3 - Release Build
Use '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
To exit, use '<ctrl-d>' or 'logout'.
openhab> logout
A couple of additional observations:
- Terminal in Synology Container Manager works (but is not convient to use)
- fresh deployment of both latest and latest-apline tag shows the same issue
- fresh deployment of tag 5.1.0.M3-alpine does not show the issue
Any suggestions