Solved OpenHAB not starting after installation

[Robin]

I've installed it, but in the dashboard, it stays in state "Starting..." and the web UI never comes up. Running Cloudron v7.3.4 on 20.04.1 LTS.

Logs says this (in a loop), unfortunately, without more details:

Dec 12 22:20:28 ==> Ensure directories
Dec 12 22:20:28 ==> Changing ownership
Dec 12 22:20:28 ==> Starting OpenHAB
Dec 12 22:20:34 ==> Ensure directories
Dec 12 22:20:34 ==> Changing ownership
Dec 12 22:20:35 ==> Starting OpenHAB
Dec 12 22:20:42 ==> Ensure directories
Dec 12 22:20:42 ==> Changing ownership
Dec 12 22:20:42 ==> Starting OpenHAB
Dec 12 22:20:51 ==> Ensure directories
Dec 12 22:20:51 ==> Changing ownership
Dec 12 22:20:51 ==> Starting OpenHAB

[nebulon]

can you maybe put the app in recovery mode and open a webterminal into the app.
The command which seems to fail from the /app/pkg/start.sh would be gosu cloudron:cloudron /app/code/runtime/bin/karaf daemon maybe run this manually, with debug options (although I don't know from the top of my head what flags this command has for this)

[Robin]

@nebulon said in OpenHAB not starting after installation:

gosu cloudron:cloudron /app/code/runtime/bin/karaf daemon

Weird.. When I ran /app/pkg/start.sh in recovery mode, I got this:

==> Ensure directories
==> Changing ownership
==> Starting OpenHAB
Killed

When I started the last command by hand, it actually seemed to run okay (at least, no output, and it didn't get killed...

I had a hunch that maybe it was getting OOM killed, and sure enough, I raised the memory allocation to 512m, and it now seems to start successfully, so maybe the default allocation (256m I think it was?) is just a little too low to start, sometimes?

[nebulon]

@Robin alright, I will increase the default memory limit then for the next release.

[nebulon]

I see I already upped the memory limit some time ago, just pending a new package release.