Solved :Updating to latest stabile 2.5.4 .UIs dont start

Hi

System is Raspberry pi 4
Openhabien latest stabile 2.5.4 (opgrading from 2.5.3)

after updating i have cleaned cache and tmp a few times,and rebooted but UIs doesn’t start. so cant acces BASIC UI or PAPERUI

Log is running ,but no errors are listed ,although it seems no config files or addons are loading .

not sure how to proceed.

Try clearing the cache. Some people say it takes up to 3 restarts of OH after upgrading before it becomes stable.

Which log are you looking in?

How long are you waiting after clearing the cache for OH to start up?

Is OH crashing before it can start up? Run sudo systemctl status openhab2 to see if there are errors there.

After clearing the cache, (NOTE on a upgrade the cache is cleared automatically) give OH time to fully restart and come up (how ever long that usually takes on your machine). Then restart OH. Don’t clear the cache.

hi guys

output is

● openhab2.service - openHAB 2 - empowering the smart home
   Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor pre
   Active: activating (auto-restart) (Result: exit-code) since Fri 2020-05-08 21
     Docs: https://www.openhab.org/docs/
           https://community.openhab.org
  Process: 7351 ExecStart=/usr/share/openhab2/runtime/bin/karaf ${OPENHAB_STARTM
 Main PID: 7351 (code=exited, status=127)
lines 1-7/7 (END)...skipping...
● openhab2.service - openHAB 2 - empowering the smart home
   Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Fri 2020-05-08 21:45:32 CEST; 763ms ago
     Docs: https://www.openhab.org/docs/
           https://community.openhab.org
  Process: 7351 ExecStart=/usr/share/openhab2/runtime/bin/karaf ${OPENHAB_STARTMODE} (code=exited, status=127)
 Main PID: 7351 (code=exited, status=127)

I’m getting the same message when running the command sudo systemctl status openhab2.
What message do you get when you run java -version

Hi Tim

I get

java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory

Oke, same issue as the post I just created.
Hopefully an answer to this issue soon in your topic or mine.

Ok thanks.

I considered starting over ,but you saved me the time .

I have just discovered the same problem… no access to my UIs.
I upgraded from 2.4 to 2.5.4 last week but now, after a (possibly unrelated edit to addon.cfg file) a couple of days I get “Error 404” when trying to access https://openhabianpi:8080.
As suggested by @rlkoshak i completed command: sudo systemctl status openhab2

Below is copy/paste of results. Any ideas?

[11:55:23] openhabian@openHABianPi:/$ sudo systemctl status openhab2
● openhab2.service - openHAB 2 - empowering the smart home
   Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2020-05-10 11:53:04 UTC; 8min ago
     Docs: https://www.openhab.org/docs/
           https://community.openhab.org
 Main PID: 560 (java)
    Tasks: 106 (limit: 4915)
   CGroup: /system.slice/openhab2.service
           └─560 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/sh

May 10 11:53:04 openHABianPi systemd[1]: Started openHAB 2 - empowering the smart home.
lines 1-11/11 (END)

not sure if your issue is related to mine

but i fixed mine by

All to have this problem, please restart openhabian-config , let it update, and select 02 - Upgrade again.

Thank you. My system has self cured also. I restarted everything (Pi and remotely connected laptop) and edited the addons.cfg file through by SSH terminal, as file editing through Visual Code and access through the UI was not working. That file issue might have been related to losing my access, but not sure.
Anyway - as we were!!!

Restarts after an upgrade are very common, sometimes up to 3 times before things settle down.

This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.