using the ubuntu 24.04 snap. I already have a services running on ports 8080 and 8843, so I want openhab to use different ports (I temporarily disabled those services while installing openhab).
$ sudo snap install openhab
openhab 4.1.1 from openHAB Foundation e.V. (openhab) installed
I need to change the http port, so
$ sudo snap set openhab openhab.http-port.value='8088'
2024-06-01T10:16:49+02:00 INFO Waiting for "snap.openhab.openhab.service" to stop.
$ sudo snap set openhab openhab.https-port.value='8843'
2024-06-01T10:18:40+02:00 INFO Waiting for "snap.openhab.openhab.service" to stop.
but the service is still configured on port 8080/8443:
it was still using ports 8080 and 8843. I tried to restart, getting error messages mostly:
$ openhab.stop
/snap/openhab/2629/runtime/bin/stop: 75: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/stop: 81: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/karaf: 75: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/karaf: 81: [: {: unexpected operator
$ openhab.start
/snap/openhab/2629/runtime/bin/karaf: 75: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/karaf: 81: [: {: unexpected operator
There is a Root instance already running with name openhab and pid 494419. If you know what you are doing and want to force the run anyway, export CHECK_ROOT_INSTANCE_RUNNING=false and re run the command.
fraco@froidcoeur-pc:~/ws/openhab-snap$ sudo snap restart openhab
2024-06-01T10:36:33+02:00 INFO Waiting for "snap.openhab.openhab.service" to stop.
Restarted.
$ openhab.status
/snap/openhab/2629/runtime/bin/status: 75: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/status: 81: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/karaf: 75: [: {: unexpected operator
/snap/openhab/2629/runtime/bin/karaf: 81: [: {: unexpected operator
using the ubuntu 24.04 snap. I already have a services running on ports 8080 and 8843, so I want openhab to use different ports (I temporarily disabled those services while installing openhab).
I need to change the http port, so
but the service is still configured on port 8080/8443:
apparently 8088 is the port internally used by influxdb, at least I think thats why this fails:
I guess it would be good to at least document that this port is reserved
I started over again:
it was still using ports 8080 and 8843. I tried to restart, getting error messages mostly:
but still running on port 8080/8843