Upgrade from 4.3.0 to 4.3.1 - update JSON DB errors

Setup, Configuration and Use Migration
1

When I set up 4.3.0 I reused my .items file for expediency (don’t ask) thinking that I will eventually put it all in the gui. I need to verify that I can ignore the following errors because there would be no items in the JASON DB at the time I upgraded or is there something more sinister I need to address.

 Unpacking openhab (4.3.1-1) over (4.3.0-1) ...
Setting up openhab (4.3.1-1) ...

[openHAB] Running JSON Database upgrade tool (${OPENHAB_RUNTIME}/bin/upgradetool.jar).
[main] INFO org.openhab.core.tools.internal.Upgrader - Copying item unit from state description to metadata in database '/var/lib/openhab/jsondb/org.openhab.core.items.Item.json'
[main] ERROR org.openhab.core.tools.internal.Upgrader - Cannot access item database '/var/lib/openhab/jsondb/org.openhab.core.items.Item.json', check path and access rights.
[main] INFO org.openhab.core.tools.internal.Upgrader - Upgrading JS profile configuration in database '/var/lib/openhab/jsondb/org.openhab.core.thing.link.ItemChannelLink.json'
[main] ERROR org.openhab.core.tools.internal.Upgrader - Cannot access link database '/var/lib/openhab/jsondb/org.openhab.core.thing.link.ItemChannelLink.json', check path and access rights.
[main] INFO org.openhab.core.tools.internal.Upgrader - Upgrading script profile configuration in database '/var/lib/openhab/jsondb/org.openhab.core.thing.link.ItemChannelLink.json'
[main] ERROR org.openhab.core.tools.internal.Upgrader - Cannot access link database '/var/lib/openhab/jsondb/org.openhab.core.thing.link.ItemChannelLink.json', check path and access rights.
[openHAB] JSON Database upgrade completed.
2

This should be fixed but I don’t know where the upgrade tool resides.

Yes, you can ignore these if you’re never had managed items or links. Those files wouldn’t exist in that case so the upgrade tool wouldn’t have any files to upgrade.

But the upgrade tool itself shouldn’t assume that the files will be there.

I think the upgrade tool is in openhab-core but I’m not positive.

3

Perhaps warn instead of error.

4

That makes sense. It could indicate a problem if the user is expecting those files to exist and they don’t. Sounds like a perfect candidate for a warning.

But if the files exist but OH doesn’t have permission that probably is still an error.