[SOLVED] OH2.3S1264: Warning "Could not persist tags of item" during Start-Up

Hello,
during start-Up I get for each persisted item an warning entry in the logfile “Could not persist tags of item”. But I’m wondering why, because the persistence models are loaded later … (I assume this is wanted).

Does it make sense to suppress the checking of this, which is causing these messages during start-up? (-> reduce lots of lines from logfile, which more confuse someone than help anything).

Regards, Siggi
(OpenHAB2, Snapshot from 27.4.18)

Start with Loading items:

2018-04-26 18:16:22.270 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Alles.rules'
2018-04-26 18:16:23.948 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'all.items'
2018-04-26 18:16:24.174 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'Alles.items'
2018-04-26 18:16:24.332 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'gDummy', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:24.362 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'gO_Alles', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:24.368 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'gO_EG', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:24.373 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'gO_OG', presumably no ManagedMetadataProvider was available

… ongoing until then loading persistence …

2018-04-26 18:16:25.592 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'WZ_Battery_Level', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:25.595 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'PIP_WZ_Helligkeit_rel', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:25.599 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'PIP_WZ_Helligkeit', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:25.602 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'PIP_WZ_rel_Luftfeuchtigkeit', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:25.606 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'PIP_WZ_Temperatur', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:25.610 [WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'PIT_Cyrus_4fach_Sensor_4_Battery_Level', presumably no ManagedMetadataProvider was available
2018-04-26 18:16:31.633 [INFO ] [thome.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
2018-04-26 18:16:33.059 [INFO ] [el.core.internal.ModelRepositoryImpl] - Validation issues found in configuration model 'immels.sitemap', using it anyway:
Frames must not contain other frames
2018-04-26 18:16:33.072 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'immels.sitemap'
2018-04-26 18:16:43.385 [INFO ] [e.smarthome.model.script.Initializer] - Started Timer ...
2018-04-26 18:16:43.566 [ERROR] [ntime.internal.engine.RuleEngineImpl] - Error during the execution of startup rule 'Initialize all items': 'plusSeconds' is not a member of 'org.joda.time.DateTime'; line 374, column 14, length 19
2018-04-26 18:16:43.793 [INFO ] [el.core.internal.ModelRepositoryImpl] - **Loading model 'rrd4j.persist**'
2018-04-26 18:16:43.837 [INFO ] [el.core.internal.ModelRepositoryImpl] - **Loading model 'mapdb.persist**'

I am seeing the same with OH 2.3 S 1264

[WARN ] [core.internal.items.ItemRegistryImpl] - Could not persist tags of item 'mP6_02_05_E', presumably no ManagedMetadataProvider was available (multiple entries)

This seems to be a bug… maybe an issue on github should be raised? (@Kai)

not sure where it belongs:


or

?

Yes, please report it at https://github.com/eclipse/smarthome/issues - thanks!

1 Like

The message should be harmless, though, I do not expect any malfunctions. But I agree that it is annoying and should either be suppressed completely or reduced to debug (and thus not be logged by default either).

1 Like

done

1 Like

I can confirm that functionality is normal even with this warning.
btw: I tried to clean up tmp & cache but this didn’t make any difference :slight_smile:

after startup, if I modify an *.items file and it gets refreshed by OH, the warning doesn’t appear when the file is loaded.

@Dim thanks for opening the issue!

1 Like

Hi, with openHAB 2.4.0 Build #1400 the issue is solved (not knowing which earlier snapshot it solved :slight_smile: )