After openhabian upgrade of openhab 5.1.0 to 5.1.1. log full of errors

1

The openhabian upgrade to bookworm went fine and after this I tried the new option 3 in the menu to upgrade from 5.1.0 to 5.1.1 which seems to have broken my system.

I get the log flooded with errors of

2026-02-10 13:51:16.055 [ERROR] [xbase.resource.BatchLinkableResource] - resolution of uriFragment ‘|::0.1.1.1::1::/0’ failed.

java.lang.NullPointerException: Cannot read field “actionServices” because the return value of “org.openhab.core.model.script.ScriptServiceUtil.getInstance()” is null

which doesn’t ring any bell. Any help much appreciated. Had to revert to a backup.

2
  1. clear the cache
  2. wait for OH to settle after that first boot after clearing the cache
  3. restart OH
  4. watch the logs for errors

There are very few changes between 5.1.0 and 5.1.1 and none of them would cause this. So most likely something went off during the upgrade.

If the errors persist, please post the the full error with some of the log statements before and after the error so it’s possible to see more of the context.

Use code fences.

```
logs and code goe here
```
3

I now have this problem with every openhab update. I haven’t yet found the exact cause.
My workaround:

  1. Stop openhab
  2. Clean cache
  3. Deactivate all file-based rules (rename to *.rules.old)
  4. Start openhab
  5. Wait until openhab has started completely
  6. Then reactivate the rules
4

I did exactly the steps proposed by @rlkoshak and after the second boot it worked fine. Was difficult to see “for OH to settle” as the log gets spammed with these entries but from the ClassicUI working I assumed it is “settled”. Let’s see with the next minor upgrade of openHAB.

5

This is already done as part of the update.

You can set openhab.event.StartLevel to INFO and see when OH reaches start level 70. I just watch the Things and when they stop changing status I wait another minute or so and then restart. Enabling the Things is the last big step during OH startup. It’s also the step most likely to throw errors after an upgrade because the cache was cleared meaning OH is trying to install all the addons at the same time that everything else is coming online. So rules may try to run before the automation add-on is installed, or Things may try to come online before the bindings are installed.

The process above basically gives OH enough time to install all the add-ons, and then when you restart the add-ons are already there.