Hi,
I’ve seen similar behaviour with a recent snapshot (tested builds 1044-1052) starting on a RPi2 using systemd, which then works if started manually from the console AND you wait 2-3mins.
After starting via systemd as a daemon failed, using start_debug.sh gave a console which did not recognise any commands, but presumably the on-line version then downloaded extra modules and started working - but only from the command line via start_debug.sh.
So, I’d suggest trying start_debug.sh with patience (seems to take ~2mins for log:tail to start working).
Starting a recent 2.2 snapshot via systemd gives the following error for me:
sudo systemctl status openhab2.service
Sep 30 09:10:14 hostname start.sh[15088]: / __ \/ __ \/ _ \/ __ \/ /_/ / /| | / __ |
Sep 30 09:10:14 hostname start.sh[15088]: / /_/ / /_/ / __/ / / / __ / ___ |/ /_/ /
Sep 30 09:10:14 hostname start.sh[15088]: \____/ .___/\___/_/ /_/_/ /_/_/ |_/_____/
Sep 30 09:10:14 hostname start.sh[15088]: /_/ 2.2.0-SNAPSHOT
Sep 30 09:10:14 hostname start.sh[15088]: Build #1052
Sep 30 09:10:14 hostname start.sh[15088]: Hit '<tab>' for a list of available commands
Sep 30 09:10:14 hostname start.sh[15088]: and '[cmd] --help' for help on a specific command.
Sep 30 09:10:14 hostname start.sh[15088]: Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown openHAB.
Sep 30 09:10:14 hostname start.sh[15088]: Error in initialization script: /opt/openhab/userdata/etc/shell.init.script: String index out of range: 0
Sep 30 09:10:16 hostname start.sh[15088]: openhab>
Searching for the error message found an issue with docker apparently related to the console - could it be that there is a bug that requires Karaf to start in the foreground connected to a console?