yepp, PI has a 64 bit processor that is capable of running that.
And yes, I installed zulu11 now and get one step further.
System is a Debian GNU/Linux 10
BeagleBoard.org Debian Buster IoT Image 2020-04-06
It launches to openhab, but I don’t get the openhab website to be seen. There seems to be an nginx server running, maybe that interferes.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Feb 18 10:33:11 2023 from 192.168.3.20
Launching the openHAB runtime…
Listening for transport dt_socket at address: 5005
_ _ _ ____
___ ___ ___ ___ | | | | / \ | __ )
/ _ \ / _ \ / _ \ / _ \ | || | / _ \ | _ \
| () | () | __/| | | || _ | / ___ \ | |) )
___/| / _/|| |||| ||// _|__/
|| 3.4.2 - Release Build
Use ‘’ for a list of available commands
and ‘[cmd] --help’ for help on a specific command.
To exit, use ‘’ or ‘logout’.
Returns a welcome to nginx
If I stop nginx (“sudo systemctl stop nginx”) before starting openHAB than there is no web-page at all to be seen.
debian@beaglebone:~/openhab$ cat userdata/logs/openhab.log
2023-02-18 10:56:59.984 [INFO ] [.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2023-02-18 10:57:07.270 [INFO ] [e.automation.internal.RuleEngineImpl] - Rule engine started.
2023-02-18 10:57:39.797 [INFO ] [ab.ui.habpanel.internal.HABPanelTile] - Started HABPanel at /habpanel
If I call port 5005 than I get a bunch of errors:
openhab> Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - expected >JDWP-Handshake<
Debugger failed to attach: handshake failed - received >GET / HTTP/1.1< - expected >JDWP-Handshake<
But I don’t know what exactly doesn 5005 and this errors mean. Some outdated protocol?
Seems I just need to bit more patient. Get the openHAB website now. But the nginx needs to be stopped.
Thanks for the hint with zulu!