You’ll see the openHABian configuration menu and can now select all desired actions. The “Manual/Fresh Setup” submenu entry is the right place for you. Execute all entries one after the other to get the full openHABian experience.
After executing all submenu entries I specified “expert” in addons.cfg and rebooted.
After reboot, the dashboard is not reachable. The log says:
2018-01-25 10:31:05.236 [thome.event.ExtensionEvent] - Extension ‘package-expert’ has been installed.
2018-01-25 10:31:30.283 [INFO ] [.dashboard.internal.DashboardService] - Stopped dashboard
The answer to
sudo systemctl status openhab2
is
openhab2.service - openHAB 2 - empowering the smart home
Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Thu 2018-01-25 10:42:56 CET; 3s ago
Docs: http://docs.openhab.org https://community.openhab.org
Process: 18166 ExecStop=/usr/share/openhab2/runtime/bin/karaf stop (code=exited, status=1/FAILURE)
Process: 18075 ExecStart=/usr/share/openhab2/runtime/bin/karaf $OPENHAB_STARTMODE (code=exited, status=1/FAILURE)
Main PID: 18075 (code=exited, status=1/FAILURE)
Running the start.sh script from /usr/share/openhab2 shows mkdir error:
sudo sh -x start.sh
[sudo] password for openhab:
echo Launching the openHAB runtime…
Launching the openHAB runtime…
dirname start.sh
DIRNAME=.
exec ./runtime/bin/karaf
mkdir: cannot create directory â/usr/share/openhab2/userdata/tmpâ: No such file or directory
KARAF_BASE is not valid: /usr/share/openhab2/userdata
To start openHAB as a service when using the Linux packages, you would normally use the command
sudo systemctl start openhab2.service
If this command fails for any reason, there should be some sort of error listed near the bottom of the output when you use the command:
journalctl -u openhab2.service -b
If openHAB starts but suffers an error while running, there may be an error in /var/log/openhab2/openhab.log. Let us know what you find and hopefully we can help out.
Hmm, That’s the same one I’m on, but for a RPi. I wonder if it has anything to do with different processor on the Orange Pi? Does another iteration of Java (such as Oracle JDK do anything differently?