DebMatic - CCU auf Debian Systemen

[deimos]

Hi,

@motopi: Ich habe das Log komplett durchgeschaut. Ich sehe, dass es ein Problem gibt, aber leider loggt der HMServer nicht welches Problem das ist. Du könntest in der Datei /etc/config/log4j.xml das Loglevel für die Category de.eq3 hochdrehen auf Debug und neu starten. Vielleicht sieht man dann mehr. Die Änderung solltest du später aber auf jeden Fall wieder rückgängig machen, das Ding loggt ansonsten wirklich viel.

Viele Grüße
Alex

[carlos]

Hallo,
Ich habe zur Zeit folgende seltsame update Konstellation.
Wie kann das sein?
Gruß
Carlos

[deimos]

Hi,

die Version 3.47.18 wurde von eQ-3 zurückgezogen, weil auf manchen Systemen HmIP erst nach etlichen Neustarts läuft.

Viele Grüße
Alex

[carlos]

Ok, wie komme ich jetzt wieder zurück?
Gruß

Carlos

[deimos]

Hi,

hast du Probleme? Wenn nein, würde ich dir empfehlen einfach auf der Version zu bleiben. Nächste Woche kommt dann hoffentlich sowieso das Update von eQ-3 raus.
Falls du Probleme hast: "apt install debmatic=3.47.15-33"

Viele Grüße
Alex

[carlos]

Hi,
Nein Probleme habe ich keine. Aber gut zu wissen wie das geht.
Ich bin zwar immer gerne auf dem neuesten Stand, aber wenn der fehlerhaft ist dann lieber doch auf dem letzten funktionierenden Stand.
Danke und Gruß
Carlos

[motopi]

Dann auf ein neues: Danke für deine Hilfe.

Code Auswählen Erweitern

Okt 18 10:11:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (5f7b60c7-d6ea-42a5-a593-e0799f3381d5)
Okt 18 10:17:03 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [main] State changed from NONE to CONFIGURED
Okt 18 10:17:03 de.eq3.ccu.server.BaseHMServer DEBUG [main] Cloud Ready RFD config file: /var/run/crRFD.conf
Okt 18 10:17:03 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Okt 18 10:17:04 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
Okt 18 10:17:04 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
Okt 18 10:17:04 de.eq3.ccu.server.BaseHMServer DEBUG [main] HM Server config file: /etc/HMServer.conf
Okt 18 10:17:04 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [Thread-0] State changed from CONFIGURED to INITIALIZING
Okt 18 10:17:10 de.eq3.cbcs.vertx.management.VertxManager DEBUG [Thread-0] State changed from NONE to INITIALIZED
Okt 18 10:17:10 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [Thread-0] State changed from INITIALIZING to INITIALIZED
Okt 18 10:17:10 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [Thread-0] State changed from INITIALIZED to STARTING
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1) 
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Okt 18 10:17:40 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) 
Okt 18 10:17:41 de.eq3.cbcs.vertx.management.VertxManager DEBUG [Thread-0] State changed from INITIALIZED to PERFORMING_INITIAL_DEPLOYMENT
Okt 18 10:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Okt 18 10:17:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized
Okt 18 10:17:43 de.eq3.cbcs.server.core.vertx.KeyServerWorker DEBUG [vert.x-worker-thread-0] KeyServerMockWorker started
Okt 18 10:17:43 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler DEBUG [vert.x-worker-thread-4] TransactionSubsystemHandler started
Okt 18 10:17:43 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker DEBUG [vert.x-worker-thread-3] KeyServerMockWorker started
Okt 18 10:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of TransactionSubsystemHandler succeeded (efa832ab-4be7-4dcd-9c39-8aae8175ff66)
Okt 18 10:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (7809db5d-2338-4ea2-8c8d-f22a0b78d538)
Okt 18 10:17:43 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-0] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 18 10:17:43 de.eq3.cbcs.lib.remotecommadapter.device.security.AccessPointKeyServerWorker DEBUG [vert.x-worker-thread-1] Local key map is undefined, start with empty list
Okt 18 10:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointKeyServerWorker succeeded (0aebd5b3-04ef-4409-bfc1-992d5ea3006e)
Okt 18 10:17:43 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 18 10:17:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of RouterKeyServerWorker succeeded (b5be75b2-a002-4e03-b8bf-0f6722a4ff0c)
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration 
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration 
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointAuthorisationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointCommDevice still not met - check deployment configuration  (still unfulfilled: [backend.ready])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LanRoutingWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:48 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][persistent.data.loaded])
Okt 18 10:17:50 de.eq3.cbcs.server.core.persistence.AbstractPersistency DEBUG [vert.x-worker-thread-2] start KryoPersistenceWorker
Okt 18 10:17:54 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: DeviceLiveUpdateSubsystem started
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (09f073f7-b704-4967-8303-9a33e73de73d)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of HMIPTRXWriterWorker succeeded (91025055-eb9d-46fe-a6c4-1aa8eb978b52)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (1f1243e4-f6c0-4c18-9543-fdec7503e1ea)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (7f6a08e1-da99-4c9a-b80a-af3654abfe58)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (a4673f35-847b-4526-8ab4-1d30df6a50e8)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointElectroCardioGram succeeded (6317c511-7cac-48aa-9f63-da56702e7a9c)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (12e6764f-d087-48bb-a226-0430bf3eeb28)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (a20be99a-ffc7-42ea-9b59-4bfb05cf8a66)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointWatchdog still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of WebSocketManager still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (4bb343bd-8571-44a7-947a-18d182665566)
Okt 18 10:17:54 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (d91a0dcc-518d-4611-aab1-044ef43a43db)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 14 out of 32
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-25] SYSTEM: <> Contract condition 'persistent.data.loaded' met for RemoteCommAdapterInitialization
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RemoteCommAdapterInitialization succeeded (a4bb2330-3d56-4dcb-9c5f-25f9a767399d)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-19] SYSTEM: <> Contract condition 'persistent.data.loaded' met for AccessPointMessageDispatcher
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointWatchdog still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointAuthorisationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-20] SYSTEM: <> Contract condition 'persistent.data.loaded' met for AccessPointWatchdog
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-5] SYSTEM: <> Contract condition 'persistent.data.loaded' met for FirmwareLoaderFileSystem
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-9] SYSTEM: <> Contract condition 'persistent.data.loaded' met for DeviceInclusionAcceptHandler
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-21] SYSTEM: <> Contract condition 'persistent.data.loaded' met for WebSocketManager
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-18] SYSTEM: <> Contract condition 'persistent.data.loaded' met for AccessPointAuthorisationHandler
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-11] SYSTEM: <> Contract condition 'persistent.data.loaded' met for IncomingHMIPFrameHandler
Okt 18 10:17:55 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (6ccd4b08-5748-4370-9ebf-04fa1a07031d)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointWatchdog succeeded (861cbf4a-03aa-45bd-a316-ff8211d2a831)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointCommDevice still not met - check deployment configuration  (still unfulfilled: [backend.ready])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointAuthorisationHandler succeeded (ea8f6af5-b37d-405a-b839-4167218828e6)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of IncomingHMIPFrameHandler succeeded (7854d3ac-21c5-4f37-bc4a-9137de1cdc50)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (491adc6f-fb39-447a-92c1-68f0660af680)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of WebSocketManager succeeded (e03e8c9f-9add-4387-b711-580ba1328639)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointMessageDispatcher succeeded (39cbe2be-6a42-41be-8510-d9ee18a46c74)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LanRoutingWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-32] SYSTEM: <> Contract condition 'persistent.data.loaded' met for LegacyInitializion
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-17] SYSTEM: <> Contract condition 'firmware.update.subsystem.started' met for LocalServerFirmwareUpdateInitialization
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-17] SYSTEM: <> Contract condition 'persistent.data.loaded' met for LocalServerFirmwareUpdateInitialization
Okt 18 10:17:55 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])
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-8] SYSTEM: <> Contract condition 'persistent.data.loaded' met for BackendCommandHandler
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-22] SYSTEM: <> Contract condition 'backend.ready' met for AccessPointCommDevice
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (54012324-1bc5-4a05-aef3-5f0e1df97ce6)
Okt 18 10:17:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-7] SYSTEM: <> Contract condition 'persistent.data.loaded' met for LocalServerAdapterInitialization
Okt 18 10:17:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointCommDevice succeeded (fb0614ab-063e-4079-b3e4-f952e300687a)
Okt 18 10:21:06 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [main] State changed from NONE to CONFIGURED
Okt 18 10:21:06 de.eq3.ccu.server.BaseHMServer DEBUG [main] Cloud Ready RFD config file: /var/run/crRFD.conf
Okt 18 10:21:07 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory
Okt 18 10:21:07 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s)
Okt 18 10:21:07 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String]
Okt 18 10:21:07 de.eq3.ccu.server.BaseHMServer DEBUG [main] HM Server config file: /etc/HMServer.conf
Okt 18 10:21:07 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [Thread-0] State changed from CONFIGURED to INITIALIZING
Okt 18 10:21:12 de.eq3.cbcs.vertx.management.VertxManager DEBUG [Thread-0] State changed from NONE to INITIALIZED
Okt 18 10:21:12 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [Thread-0] State changed from INITIALIZING to INITIALIZED
Okt 18 10:21:12 de.eq3.cbcs.server.local.base.LocalServerBase DEBUG [Thread-0] State changed from INITIALIZED to STARTING
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointElectroCardioGram] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointAuthorisationHandler] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointMessageDispatcher] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointWatchdog] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [WebSocketManager] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointCommDevice] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RouterKeyServerWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [AccessPointKeyServerWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterInitialization] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [RemoteCommAdapterFinalization] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LanRoutingWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1) 
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager DEBUG [Thread-0] State changed from INITIALIZED to PERFORMING_INITIAL_DEPLOYMENT
Okt 18 10:21:41 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 32 classes to Vert.x
Okt 18 10:21:42 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 32 VertxDeployers initialized
Okt 18 10:21:43 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler DEBUG [vert.x-worker-thread-1] TransactionSubsystemHandler started
Okt 18 10:21:43 de.eq3.cbcs.server.core.vertx.KeyServerWorker DEBUG [vert.x-worker-thread-1] KeyServerMockWorker started
Okt 18 10:21:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (8511ac15-dd5d-4b8a-9cb6-0db16f7ea1aa)
Okt 18 10:21:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of TransactionSubsystemHandler succeeded (45e42f21-f1f0-4a47-8a27-fda1c7a1ea0c)
Okt 18 10:21:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (534cd250-51a8-4410-a2b7-b5d4ce920ee6)
Okt 18 10:21:43 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker DEBUG [vert.x-worker-thread-4] KeyServerMockWorker started
Okt 18 10:21:43 de.eq3.cbcs.lib.remotecommadapter.device.security.AccessPointKeyServerWorker DEBUG [vert.x-worker-thread-0] Local key map is undefined, start with empty list
Okt 18 10:21:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (2a2553eb-eb7e-414e-95e8-9b6936e4f602)
Okt 18 10:21:43 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-1] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 18 10:21:43 de.eq3.cbcs.lib.remotecommadapter.device.security.RouterKeyServerWorker ERROR [vert.x-worker-thread-4] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL
Okt 18 10:21:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (83e0d262-7876-4038-bc18-2d8792c1a021)
Okt 18 10:21:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RouterKeyServerWorker succeeded (1340f7e5-bfda-41f0-b6c3-ad6d90d998b0)
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration 
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:48 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of WebSocketManager still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:49 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 18 10:21:49 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:21:49 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])
Okt 18 10:21:49 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:50 de.eq3.cbcs.server.core.persistence.AbstractPersistency DEBUG [vert.x-worker-thread-2] start KryoPersistenceWorker
Okt 18 10:21:54 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: DeviceLiveUpdateSubsystem started
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (21e9ccd2-3f08-45a7-8ecb-580c24187719)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (95c5df7b-cecd-4c56-bc1a-37e50b4465bf)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointElectroCardioGram succeeded (be86c8f4-5262-4928-a7bf-2fa4192af322)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointKeyServerWorker succeeded (f1d6970e-9aed-4f1d-a9a6-476e2286e7a0)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (ad30eb2e-066e-49ef-853f-7d0655ff5085)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (a6170f8c-ca71-4d8b-8472-5bdb37193cd2)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (694fa291-4402-4988-94ac-8c5624dbca0c)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerPersistentDataLoader still not met - check deployment configuration 
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointAuthorisationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointWatchdog still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointCommDevice still not met - check deployment configuration  (still unfulfilled: [backend.ready])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LanRoutingWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:21:55 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][persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerPersistentDataLoader succeeded (539369b8-f6c7-46da-b2fd-cab6f074337e)
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 14 out of 32
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open][firmware.update.subsystem.started][persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointAuthorisationHandler still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of AccessPointMessageDispatcher still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointWatchdog still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of WebSocketManager still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded])
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-18] SYSTEM: <> Contract condition 'persistent.data.loaded' met for AccessPointAuthorisationHandler
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-5] SYSTEM: <> Contract condition 'persistent.data.loaded' met for FirmwareLoaderFileSystem
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-11] SYSTEM: <> Contract condition 'persistent.data.loaded' met for IncomingHMIPFrameHandler
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-21] SYSTEM: <> Contract condition 'persistent.data.loaded' met for WebSocketManager
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-19] SYSTEM: <> Contract condition 'persistent.data.loaded' met for AccessPointMessageDispatcher
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-9] SYSTEM: <> Contract condition 'persistent.data.loaded' met for DeviceInclusionAcceptHandler
Okt 18 10:21:55 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-20] SYSTEM: <> Contract condition 'persistent.data.loaded' met for AccessPointWatchdog
Okt 18 10:21:56 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-1] SYSTEM: Firmware update directory is set to /etc/config/firmware
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of FirmwareLoaderFileSystem succeeded (d47fa39a-421d-49ed-9a4a-e532dbb04781)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (955bfd05-24f4-4e49-a041-d9ec88ed30d3)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-25] SYSTEM: <> Contract condition 'persistent.data.loaded' met for RemoteCommAdapterInitialization
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of WebSocketManager succeeded (c0e84bc6-effd-400d-ad8e-ead691f9bb62)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointWatchdog succeeded (77ed8dd9-4651-4a95-bd52-3f5147be98f5)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointAuthorisationHandler succeeded (3deecfdd-bc13-40e4-b007-678dd8c1bfc9)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of IncomingHMIPFrameHandler succeeded (f13d46c3-6029-4e62-85f1-ed0ee8519036)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of RemoteCommAdapterFinalization still not met - check deployment configuration  (still unfulfilled: [connector.ready])
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RemoteCommAdapterInitialization succeeded (7565b780-1bfe-4844-b88f-98163026b6b6)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of AccessPointCommDevice still not met - check deployment configuration  (still unfulfilled: [backend.ready])
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of AccessPointMessageDispatcher succeeded (62540ff1-6e3d-4aff-93ec-2a19bede5e72)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LanRoutingWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration  (still unfulfilled: [connector.open])
Okt 18 10:21:56 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])
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-22] SYSTEM: <> Contract condition 'backend.ready' met for AccessPointCommDevice
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-17] SYSTEM: <> Contract condition 'firmware.update.subsystem.started' met for LocalServerFirmwareUpdateInitialization
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-17] SYSTEM: <> Contract condition 'persistent.data.loaded' met for LocalServerFirmwareUpdateInitialization
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-32] SYSTEM: <> Contract condition 'persistent.data.loaded' met for LegacyInitializion
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-8] SYSTEM: <> Contract condition 'persistent.data.loaded' met for BackendCommandHandler
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointCommDevice succeeded (ba596ab6-0ad7-4b30-a921-b35724c9fbe1)
Okt 18 10:21:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of BackendCommandHandler succeeded (39beb805-88df-4e94-9418-26663ed65126)
Okt 18 10:21:56 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])
Okt 18 10:21:57 de.eq3.cbcs.vertx.management.VertxManager DEBUG [pool-1-thread-7] SYSTEM: <> Contract condition 'persistent.data.loaded' met for LocalServerAdapterInitialization


[deimos]

Hi,

@motopi: Wie sehen deine Dateien /var/run/crRFD.conf, /etc/HMServer.conf und /etc/crRFD.conf aus?

Viele Grüße
Alex

[motopi]

/var/run/crRFD.conf

Code Auswählen Erweitern


# USB HM/IP TRX Adapter Configuration
Adapter.1.Type=HMIP_CCU2
Adapter.1.Port=/dev/mmd_hmip

Config.Dir=/etc/config/crRFD
Config.Include=hmip_user.conf

# Directory Configuration
Persistence.Home=/etc/config/crRFD/data
FirmwareUpdate.BG.OTAU.Home=/etc/config/firmware
FirmwareUpdate.BG.OTAU.divergent.device.type.definition.file=/opt/HmIP/crrfd.fwfix

# Legacy API Configuration
API.1.Type=XML-RPC
Legacy.Encoding=ISO-8859-1
Legacy.ResponseTimeout=20
Legacy.ReplacementURL=127.0.0.1
Legacy.Parameter.Definition.File=/opt/HmIP/legacy-parameter-definition.config

# Legacy.RemoveUnreachableClients=false
Legacy.AddressPrefix=3014F711A0
Legacy.SwitchTypeAndSubtype=true
Legacy.HandlersFilename=/var/LegacyService.handlers
Legacy.DiscardDutyCycleEvents=true
Legacy.SendUDPServiceMessages=true
Legacy.Port=32010
Legacy.VirtualRemoteControl.Enabled=true

# HmIP-Routing
Adapter.Remote.Enabled=true
AccessPoint.WebSocket.Port=9293
IPServices.Firmware.Update.URL=http://drap-update.homematic.com:80/firmware/hap/

# Miscellaneous Configuration
CyclicTimeout.TimerStartMaxDelay=90
CyclicTimeout.TimerCycleTime=600
Legacy.Parameter.ReplaceEnumValueWithOrdinal=true

### Configuration for Inclusion with key server (internet) or local key (offline)
KeyServer.Mode=KEYSERVER_LOCAL
KeyServer.Gateway.URL=secgtw.homematic.com
Vertx.WorkerPoolSize=5



/etc/crRFD.conf

Code Auswählen Erweitern

# USB HM/IP TRX Adapter Configuration
Adapter.1.Type=HMIP_CCU2
Adapter.1.Port=/dev/mmd_hmip

Config.Dir=/etc/config/crRFD
Config.Include=hmip_user.conf

# Directory Configuration
Persistence.Home=/etc/config/crRFD/data
FirmwareUpdate.BG.OTAU.Home=/etc/config/firmware
FirmwareUpdate.BG.OTAU.divergent.device.type.definition.file=/opt/HmIP/crrfd.fwfix

# Legacy API Configuration
API.1.Type=XML-RPC
Legacy.Encoding=ISO-8859-1
Legacy.ResponseTimeout=20
Legacy.ReplacementURL=127.0.0.1
Legacy.Parameter.Definition.File=/opt/HmIP/legacy-parameter-definition.config

# Legacy.RemoveUnreachableClients=false
Legacy.AddressPrefix=3014F711A0
Legacy.SwitchTypeAndSubtype=true
Legacy.HandlersFilename=/var/LegacyService.handlers
Legacy.DiscardDutyCycleEvents=true
Legacy.SendUDPServiceMessages=true
Legacy.Port=32010
Legacy.VirtualRemoteControl.Enabled=true

# HmIP-Routing
Adapter.Remote.Enabled=true
AccessPoint.WebSocket.Port=9293
IPServices.Firmware.Update.URL=http://drap-update.homematic.com:80/firmware/hap/

# Miscellaneous Configuration
CyclicTimeout.TimerStartMaxDelay=90
CyclicTimeout.TimerCycleTime=600
Legacy.Parameter.ReplaceEnumValueWithOrdinal=true

### Configuration for Inclusion with key server (internet) or local key (offline)
KeyServer.Mode=KEYSERVER_LOCAL
KeyServer.Gateway.URL=secgtw.homematic.com
Vertx.WorkerPoolSize=5



HMServer.conf

Code Auswählen Erweitern


hmServerPort=39292
regaPort=31999


[motopi]

habe weitergesucht und sehr genau dieses Verhalten: https://homematic-forum.de/forum/viewtopic.php?f=26&t=53215&start=30#p530777  - Lösung noch unklar.

ACHSO: bin auf nem PI 2 b mit stretch + FHEM, das sollte aber okay sein, denke ich.

[motopi]

habe jetzt meinen Raspi 3 genommen (Hifiberry abgebaut) und mit Buster alles neu installiert und es geht problemlos. -- jetzt mach ich den clean Install nochmal auf dem RPI 2 .....

[motopi]

@ALEX: wenn du mit den Infos oben eine Idee hast nur zu. Sonst begrabe ich den RPI 2b und mach alles neu. Nervt ein wenig wegen FHEM, aber ist am Ende auch egal. In Summe deutlich schneller...

[deimos]

Hi,

@motopi: Ist mir ein Rätsel, was da schief geht und ich fluche leider wieder einmal über die wenig aussagekräftigen Logs vom HMServer...

Viele Grüße
Alex

[motopi]

hi,
keine Ahnung ob es da ein b gibt)
Danke fürs nachsehen.

ich habe jetzt: auf

Pie 3b -> raspbian buster neu installation + DEBMATIC läuft
Pie 2b 1.2 -> raspbian buster neu installation + DEBMATIC läuft -- fehler mit JAVA bei Neuinstallation -- siehe: https://pastebin.com/e6HEiHtH 

hast du da eine Idee? Irgendwie scheint das auch nur ein abhängiges Paket zu sein, was auf dem 2er RPI nicht läuft...   habe es auch mal mit JRE-default versucht, ebenfalls erfolglos.

Code Auswählen Erweitern

update-alternatives: using /usr/lib/jvm/java-9-openjdk-armhf/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-armhf/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-armhf/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-armhf/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode
update-alternatives: using /usr/lib/jvm/java-9-openjdk-armhf/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode
Setting up ca-certificates-java (20190405) ...
head: cannot open '/etc/ssl/certs/java/cacerts' for reading: No such file or directory
Error occurred during initialization of VM
Server VM is only supported on ARMv7+ VFP
dpkg: error processing package ca-certificates-java (--configure):
installed ca-certificates-java package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
ca-certificates-java

Update: scheinbar will mir (irgendwer) auf dem 1.2 Pakete für ARMv7 installieren, obwohl der ARMv8 hat, lt. Wikipedia.

Update #2:
RPI 2 B 1.1 : Buster + Debmatic läuft auch - auch mit Homematic IP

ABER WARUM - ist das bzgl. der Architektur was, was mit debmatic kommt?

Update #3:
schiebe ich die alte oben genutzte Installation (strech) in den Pi 2b 1.1 -> Funktioniert Homematic incl. des anlernen für Homematic IP!



Aber: was mach ich nun mit der Erkenntnis?  -> Alex: ist das ein Raspbian Bug oder hängt das mit DEBMATIC zusammen? kann ich noch irgendwas zur Analyse / Lösung beitragen?

[Jamo]

Hallo amenomade, Werniemann,

Zitat von amenomade, Antwort #193 am: 17 Oktober 2019, 23:15:17

Hab die Doku wieder gelesen. Wants + After sollte gehen, genauso wie bei network

Ich habe jetzt folgendes versucht (also wants + after wie bei network.target), um den start von FHEM zu verzögern bis debmatic gestarted ist. Das funktioniert aber nicht. FHEM started nicht. Kann mir jemand helfen?

Code Auswählen Erweitern

cat /etc/systemd/system/fhem.service
# $Id: fhem.service 16001 2018-01-26 11:54:41Z betateilchen $

[Unit]
Description=FHEM Home Automation
Wants=network.target
After=network.target
Wants=debmatic-startupfinished.service
After=debmatic-startupfinished.service

[Service]
Type=forking
User=fhem
Group=dialout
WorkingDirectory=/opt/fhem
ExecStart=/usr/bin/perl fhem.pl fhem.cfg
#ExecStart=/usr/bin/perl fhem.pl configDB
Restart=always

[Install]
WantedBy=multi-user.target