openHab does not start any longer

Setup, Configuration and Use Beginners
1

Hi All,

After years, it is the first time, I am fully lost.

I am running a openHab 5.1.4 installation, with different add-ons on a docker environment (Synology).

After I needed to have a planned shut down, openHab yesterday, due to electricity works in my home, it is not starting up normal again? It eats up all CPU resources and shows the following errors during start-up:

08:40:10.880 [INFO ] [arketplace.MarketplaceBundleInstaller] - Reinstalling missing marketplace bundle: marketplace:152184
08:40:12.601 [INFO ] [org.openhab.core.Activator ] - Starting openHAB 5.1.4 (Release Build)
08:40:14.497 [INFO ] [b.core.internal.i18n.I18nProviderImpl] - Time zone set to ‘Europe/Berlin’.
08:40:14.502 [INFO ] [b.core.internal.i18n.I18nProviderImpl] - Location set to ‘REDACTED’.
08:40:14.503 [INFO ] [b.core.internal.i18n.I18nProviderImpl] - Locale set to ‘de_DE’.
08:40:19.166 [INFO ] [del.core.internal.ModelRepositoryImpl] - Loading DSL model ‘meinHaus.sitemap’
08:40:24.600 [INFO ] [b.core.model.lsp.internal.ModelServer] - Started Language Server Protocol (LSP) service on port 5007
08:40:26.844 [ERROR] [re.automation.internal.RuleEngineImpl] - Failed to compile rule ‘db3bb7536e’ with status ‘UNINITIALIZED’
08:40:26.848 [ERROR] [re.automation.internal.RuleEngineImpl] - Failed to compile rule ‘bdfdc770b2’ with status ‘UNINITIALIZED’
08:40:26.881 [ERROR] [re.automation.internal.RuleEngineImpl] - Failed to compile rule ‘System_Feiertags_und_Urlaubspruefung’ with status ‘UNINITIALIZED’
08:40:26.912 [INFO ] [re.automation.internal.RuleEngineImpl] - Rule engine started.
08:42:57.225 [ERROR] [.core.karaf.internal.FeatureInstaller] - Failed installing ‘openhab-binding-tr064, openhab-binding-exec, openhab-misc-openhabcloud, openhab-binding-amazonechocontrol, openhab-ui-habpanel, openhab-binding-roborock, openhab-automation-jsscripting, openhab-binding-shelly, openhab-binding-harmonyhub, openhab-binding-mqtt, openhab-binding-solaredge, openhab-binding-smartmeter, openhab-binding-homematic, openhab-core-config-discovery-addon-usb, openhab-core-config-discovery-addon-ip, openhab-core-config-discovery-addon-mdns, openhab-core-config-discovery-addon-upnp, openhab-core-config-discovery-addon-sddp, openhab-transformation-regex, openhab-transformation-jsonpath, openhab-binding-miio, openhab-binding-tuya, openhab-persistence-rrd4j, openhab-ui-basic, openhab-binding-ntp, openhab-misc-homekit, openhab-binding-openweathermap, openhab-binding-astro, openhab-binding-unifi, openhab-binding-govee, openhab-binding-weathercompany’: Error:
Error downloading mvn:org.openhab.addons.bundles/org.openhab.binding.tr064/5.1.4

What I did already to solve the solution, but w/o success:

  • cleared the cache (delete tmp/cache-folder)
  • renamed DSL rules files (*.rules.sik) in the rules folder, so that they won’t be used any longer
  • renamed things files (*.things.sik) in the things folder, so that they won’t be used any longer
  • removed one add-in from the add-in folder, which I recently added for outdated marketplace add-in

But still, it does not start up? Where to start? Could I get a better logging somehow, to see if something stuck in the backgroud?

Any help is appreciated..

2

Based on the last line in the logs, I guess there is a DNS or other network-related issue. It appears that the bindings cannot be loaded and installed.

3

Why ever it started to use IP6 instead of IP4.

A EXTRA_JAVA_OPT -Djava.net.preferIPv4Stack=true for the docker container fixed the issue

4

It’s required for Matter.

See AdGuardHome/PiHole in a IPv6 world (plus parental controls) for what I did to overcome those shirts if issues. It’s geared towards opnsense and adguard users but the over all concepts should be applicable to other setups as well, so long as you have a DNS server, DHCP server and firewall on your LAN that you can configure.

Hint, you could copy and paste the tutorial from above into your chat bot of choice and ask for it to cover it to the tools/services in your network.

After all is done you end up with everything using IPv4 DNS in your LAN even if they want to speak IPv6.