ich habe mir ein Ersatz System gebaut. Dieses besteht genau wie das Produktivsystem aus einem Pi4 Model B mit 4 GB. Installiert ist piVCCU3 3.53.34-49 und auf beiden Systemen sind die alten Funkmodule installiert. Dieses neue System funktioniert für sich problemlos, d. h. ich kann Geräte anlernen und es gibt damit keine erkennbaren Probleme. Auch das Produktivsystem funktioniert problemlos. Ich habe nur klassische HM Geräte (> 100), keine Add-Ons installiert und nur 4 kleine Programme am Laufen, da das System ansonsten über IP-Symcon gesteuert wird.
Seit gestern versuche ich eine Datensicherung vom Produktivsystem auf das neue System einzuspielen - bislang ohne Erfolg Auch der Versuch ein komplettes Image zu übernehmen schlug fehl. In der Vergangenheit mit 2 Pi3 System hat das immer problemlos funktioniert. Eine Verbindung zum Internet bestand jeweils.
Anbei das Log auf dem man die auftretenden Fehler erkennen kann.
Code: Alles auswählen
***** hmserver.log *****
Jan 7 15:51:13 de.eq3.lib.util.dynamics.GenericFactory INFO [main] @GenericFactory
Jan 7 15:51:13 de.eq3.lib.util.dynamics.GenericFactory INFO [main] created instance of HMServerConfiguration with parameter(s)
Jan 7 15:51:13 de.eq3.lib.util.dynamics.GenericFactory INFO [main] passed 1 parameter(s), in declarative order [String]
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)
Jan 7 15:51:16 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: deploying 22 classes to Vert.x
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [Thread-0] SYSTEM: 22 VertxDeployers initialized
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of HMIPTRXWriterWorker succeeded (b135e3ca-9772-4a9f-a8f4-4f99d07271f2)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (ef3e0854-2b73-4591-88ce-1b19b23740a0)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of CheckDeviceExistHandler succeeded (597509d1-a7bf-4ab8-9cd8-18757820ba51)
Jan 7 15:51:17 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-6] SYSTEM: start of KeyServerWorker succeeded (5ff174be-e1a0-4f2f-88ef-87bcfa092f90)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of TransactionSubsystemHandler succeeded (07a9dcc0-8e50-4772-8d1c-1a07bf6b2280)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-4] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (5a01cb2e-d5b0-484e-88ef-e042a0ad3fef)
Jan 7 15:51:17 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (69351758-6196-4996-8806-5159fd5732ef)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (fb9c8880-9dc8-4dd2-98cf-2c78025c5c85)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (4f2e3c2b-df46-4186-a6c8-64146c8df649)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (1c80ac36-f70a-49fd-b124-2f1df5140464)
Jan 7 15:51:17 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (9d3fc3b6-0bd7-4a3b-a88a-ec06eff80476)
Jan 7 15:51:18 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Jan 7 15:51:18 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of FirmwareLoaderFileSystem succeeded (59261927-2887-4195-b38c-a87c1a7af6a8)
Jan 7 15:51:18 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (5db5efed-70b3-45ea-aac8-75c323f15dc5)
Jan 7 15:51:18 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of IncomingHMIPFrameHandler succeeded (6fd131d4-9fa5-40fb-bb98-f610292b37fe)
Jan 7 15:51:18 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-7] SYSTEM: start of TransactionManagementVerticle succeeded (4fce94ce-5973-4c33-aa45-416a3d43de44)
Jan 7 15:51:18 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (04e2ea45-158f-4deb-9846-cef5669f8fb4)
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter state 1: HMIP_TRX_App
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] TRX adapter application is already running or started
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] No NWK, try to set address ...
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to set radio address 12111507...
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Set max send attempts for 3014F711A061A7D70992B75F to 3
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Try to get application version...
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Application version 2.8.6
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Bootloader version 1.0.3
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] hmos version 1.20.3
Jan 7 15:51:18 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO [Thread-6] Exchanging adapter from 3014F711A061A7xxxxxxx to 3014F711A061A7D709xxxxxxxx ...
Jan 7 15:51:20 de.eq3.cbcs.vertx.management.VertxManager INFO [vert.x-eventloop-thread-2] SYSTEM: start of BackendCommandHandler succeeded (a6b6e1aa-9bc8-4e67-8b7a-cde3f715014b)
Jan 7 15:51:24 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Jan 7 15:51:24 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: [legacy.api.worker][connector.open])
Jan 7 15:51:24 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-2] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: [connector.open])
Jan 7 15:51:24 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-3] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: [connector.open])
Jan 7 15:51:24 de.eq3.cbcs.vertx.management.VertxManager WARN [vert.x-eventloop-thread-5] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: [connector.open])
Jan 7 15:51:24 de.eq3.cbcs.server.core.vertx.keyserver.KeyServerOperation WARN [vert.x-eventloop-thread-1] AP 3014F711A061A7D7098E0870: Exception while communicating to Frontend Server:
java.net.UnknownHostException: failed to resolve 'secgtw.homematic.com'. Exceeded max queries per resolve 4
at io.netty.resolver.dns.DnsNameResolverContext.finishResolve(DnsNameResolverContext.java:473)
at io.netty.resolver.dns.DnsNameResolverContext.tryToFinishResolve(DnsNameResolverContext.java:393)
at io.netty.resolver.dns.DnsNameResolverContext.query(DnsNameResolverContext.java:157)
at io.netty.resolver.dns.DnsNameResolverContext.query(DnsNameResolverContext.java:531)
at io.netty.resolver.dns.DnsNameResolverContext.tryToFinishResolve(DnsNameResolverContext.java:387)
at io.netty.resolver.dns.DnsNameResolverContext.query(DnsNameResolverContext.java:157)
at io.netty.resolver.dns.DnsNameResolverContext.access$900(DnsNameResolverContext.java:54)
at io.netty.resolver.dns.DnsNameResolverContext$3.operationComplete(DnsNameResolverContext.java:185)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:507)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:481)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:420)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:122)
at io.netty.resolver.dns.DnsQueryContext.setFailure(DnsQueryContext.java:216)
at io.netty.resolver.dns.DnsQueryContext.access$300(DnsQueryContext.java:41)
at io.netty.resolver.dns.DnsQueryContext$4.run(DnsQueryContext.java:159)
at io.netty.util.concurrent.PromiseTask$RunnableAdapter.call(PromiseTask.java:38)
at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:120)
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:403)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:445)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858)
at java.lang.Thread.run(Thread.java:748)
Merkwürdigerweise kann ich eine ältere Datensicherung unter piVCCU 3.51.6-40 einlesen. Diese Sicherung ist mit 3.920 kB doppelt so groß wie die Sicherungen unter piVCCU3 3.53.34-49 mit 1.970 kB. Der Unterschied besteht darin, dass in der alten Sicherung unter \usr_local.tar.gz\usr_local.tar\usr\local\ noch ein Ordner eQ-3-Backup mit Unterverzeichnissen zu finden ist, der den Größenunterschied erklärt.
Wie kann es mir gelingen, die aktuelle Sicherung auf den neuen Pi4 zu bekommen?
Gruß
Hans