[SOLVED] OH does not start after upgrade to 2.5.0 S1560

Hello, my OH 2.5.0 on a RP3 does not start after an upgrade to 1560.

The service status is ok, but no log files was written.

> ● openhab2.service - openHAB 2 - empowering the smart home
>    Loaded: loaded (/usr/lib/systemd/system/openhab2.service; enabled)
>    Active: active (running) since Mo 2019-03-25 18:41:20 CET; 2min 26s ago
>      Docs: https://www.openhab.org/docs/
>            https://community.openhab.org
>   Process: 1869 ExecStop=/usr/share/openhab2/runtime/bin/karaf stop (code=exited, status=0/SUCCESS)
>  Main PID: 2017 (java)
>    CGroup: /system.slice/openhab2.service
>            └─2017 /usr/bin/java -Dopenhab.home=/usr/share/openhab2 -Dopenhab.conf=/etc/openhab2 -Dopenhab.runtime=/usr/share/openhab2/runtime -Do...
> 
> Mär 25 18:41:20 openHABianPi systemd[1]: Started openHAB 2 - empowering the smart home.

The last entrys in the log while the upgrade runs.

> 2019-03-25 18:00:32.717 [INFO ] [io.openhabcloud.internal.CloudClient] - Disconnected from the openHAB Cloud service (UUID = XXXXX, base URL = http://localhost:8080)
> 2019-03-25 18:00:47.941 [INFO ] [control.internal.WebSocketConnection] - Web Socket close 1006. Reason: Disconnected
> 2019-03-25 18:00:52.934 [WARN ] [core.thing.internal.ThingManagerImpl] - Disposing handler for thing 'amazonechocontrol:account:90519a08' takes more than 5000ms.
> 2019-03-25 18:00:59.991 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Stopped ZWave serial handler
> 2019-03-25 18:01:00.883 [ERROR] [core.karaf.internal.FeatureInstaller] - Failed installing 'openhab-misc-restdocs': Error restarting bundles:
> 	Unable to acquire the state change lock for the module: osgi.identity; type="osgi.bundle"; version:Version="2.5.0.201903170725"; osgi.identity="org.openhab.binding.zwave"; singleton:="true" [id=233] STARTED [STOPPED]
> 2019-03-25 18:01:02.826 [INFO ] [assic.internal.servlet.WebAppServlet] - Stopped Classic UI
> 2019-03-25 18:01:03.971 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@1a5b3ab{STOPPING,10<=10<=40,i=0,q=6}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$118/31475811@1d18c5d] Couldn't stop Thread[ESH-httpClient-common-87,5,main]
> 2019-03-25 18:01:03.974 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[ESH-httpClient-common]@1a5b3ab{STOPPING,10<=10<=40,i=0,q=6}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$118/31475811@1d18c5d] Couldn't stop Thread[ESH-httpClient-common-86,5,main]
> 2019-03-25 18:01:04.297 [ERROR] [ng.exec.internal.handler.ExecHandler] - An exception occurred while waiting for the process ('/etc/openhab2/scripts/btping.sh 2') to finish : 'null'
> 2019-03-25 18:01:04.308 [WARN ] [ng.exec.internal.handler.ExecHandler] - Forcibly termininating the process ('/etc/openhab2/scripts/btping.sh 2') after a timeout of 60000 ms
> 2019-03-25 18:01:04.315 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:13d3ece5 tried updating channel run although the handler was already disposed.
> 2019-03-25 18:01:04.317 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:13d3ece5 tried updating channel exit although the handler was already disposed.
> 2019-03-25 18:01:04.320 [WARN ] [ng.exec.internal.handler.ExecHandler] - Couldn't transform response because transformationService of type 'REGEX' is unavailable
> 2019-03-25 18:01:04.322 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:13d3ece5 tried updating channel output although the handler was already disposed.
> 2019-03-25 18:01:04.325 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:13d3ece5 tried updating channel lastexecution although the handler was already disposed.
> 2019-03-25 18:01:05.003 [ERROR] [ng.exec.internal.handler.ExecHandler] - An exception occurred while waiting for the process ('/etc/openhab2/scripts/btping.sh 1') to finish : 'null'
> 2019-03-25 18:01:05.020 [WARN ] [ng.exec.internal.handler.ExecHandler] - Forcibly termininating the process ('/etc/openhab2/scripts/btping.sh 1') after a timeout of 60000 ms
> 2019-03-25 18:01:05.027 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:a7c46ce3 tried updating channel run although the handler was already disposed.
> 2019-03-25 18:01:05.029 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:a7c46ce3 tried updating channel exit although the handler was already disposed.
> 2019-03-25 18:01:05.031 [WARN ] [ng.exec.internal.handler.ExecHandler] - Couldn't transform response because transformationService of type 'REGEX' is unavailable
> 2019-03-25 18:01:05.034 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:a7c46ce3 tried updating channel output although the handler was already disposed.
> 2019-03-25 18:01:05.038 [WARN ] [.core.thing.binding.BaseThingHandler] - Handler ExecHandler of thing exec:command:a7c46ce3 tried updating channel lastexecution although the handler was already disposed.
> 2019-03-25 18:01:17.942 [WARN ] [e.jetty.util.thread.QueuedThreadPool] - QueuedThreadPool[WebSocketClient@10426823]@1e5056a{STOPPING,8<=8<=200,i=0,q=2}[org.eclipse.jetty.util.thread.TryExecutor$$Lambda$118/31475811@1d18c5d] Couldn't stop Thread[WebSocketClient@10426823-537297,5,main]```

Please use How to use code fences for logs and captures from a command prompt.

Next, try Clear the Cache.

2 Likes

Thx so much, i used the following and now it works :grinning:

sudo /etc/init.d/openhab2 stop
sudo rm -rf /var/lib/openhab2/cache/*
sudo rm -rf /var/lib/openhab2/tmp/*
sudo /etc/init.d/openhab2 start
1 Like

Hi,

I am also having this issue everytime an update is executed. OpenHab won’t start with a 502 Bad Gateway error.

I tried stop/start/enable the service and rebooted the my Pi and still won’t start.

The last time I cleared the cached it resulted to longer boot time.

Any idea why is this always happening?

It’s better to start a new thread than reopening an old one a year later.

It takes longer to boot after clearing the cache because it has to download and reinstall all the addons.

To best help with you problem, please post a new thread, provide all the relevant information (e.g. OH version, Java version, how installed, etc.) and post logs.