OH3 isnt responding randomly

Hi,

randomly OH3 is not reachable anymore. I have to restart it to function again.

In logfile the following is logged:

2021-03-06 07:24:29.677 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.internal.items.ItemUpdater@134c357' takes more than 5000ms.
2021-03-06 07:24:45.028 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.internal.items.ItemUpdater@134c357' takes more than 5000ms.
2021-03-06 07:24:55.641 [WARN ] [ding.smartmeter.internal.MeterDevice] - Timeout occured for smartmeter:meter:10685cbb03; The source did not signal an event for 40000 milliseconds and has been terminated.
2021-03-06 07:25:15.446 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.internal.items.ItemUpdater@134c357' takes more than 5000ms.
2021-03-06 07:25:22.489 [INFO ] [ding.smartmeter.internal.MeterDevice] - Opening connection to smartmeter:meter:10685cbb03
2021-03-06 07:25:30.525 [WARN ] [ab.core.internal.events.EventHandler] - Dispatching event to subscriber 'org.openhab.core.internal.items.ItemUpdater@134c357' takes more than 5000ms.
2021-03-06 07:26:54.166 [ERROR] [io.openhabcloud.internal.CloudClient] - Error connecting to the openHAB Cloud instance

One CPU Core is at 100% on my RPi4 with a openhab Java process.

Could a DSL rule cause this behaviour ?

br

Do you have DSL rules defined in your UI? That’s a known issue, I think it especially hits when your rules throw an error. Quick fix is to put your rules back in files instead of the UI.

2 Likes