OpenHAB not starting after installation
-
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 -
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.shwould begosu cloudron:cloudron /app/code/runtime/bin/karaf daemonmaybe run this manually, with debug options (although I don't know from the top of my head what flags this command has for this) -
N nebulon marked this topic as a question on
-
@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
KilledWhen 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 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
KilledWhen 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?
-
N nebulon has marked this topic as solved on
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login