Probleme beim Update von CUxD

Anbindung von FS20-Komponenten, ELV-Wetterstationen, EnOcean und DMX an HomeMatic

Moderator: Co-Administratoren

AlphaZulu
Beiträge: 99
Registriert: 25.05.2015, 17:32

Probleme beim Update von CUxD

Beitrag von AlphaZulu » 20.01.2018, 14:17

Ich habe jetzt mehrfach versucht CUxD 1.12 auf meiner CCU2 zu installieren (immer nachdem eine neue Version der CCU2 herauskam), aber jedesmal stürzt CUxD dann ab und reißt die CCU2 mit. Wenn ich danach wieder auf CUxD 1.9 zurückgehe (dazwischenliegende Versionen habe ich leider nicht), dann läuft alles einwandfrei. - Ist da irgendein Problem bekannt?

Benutzeravatar
uwe111
Beiträge: 3743
Registriert: 26.02.2011, 22:22
Kontaktdaten:

Re: CUxD 1.12 Installationsproblem?

Beitrag von uwe111 » 21.01.2018, 19:36

AlphaZulu hat geschrieben:Ist da irgendein Problem bekannt?
Bisher nicht. Was steht nach dem Absturz im Syslog der CCU?

Viele Grüße

Uwe
Alle sagten: Das geht nicht. Dann kam einer, der wußte das nicht und hat's einfach gemacht.
SPENDEN :wink: Download: CUxD 2.2.0, RFD-Monitor, Vellemann K8055, SSH KeyDir

AlphaZulu
Beiträge: 99
Registriert: 25.05.2015, 17:32

Probleme beim Update von CUxD

Beitrag von AlphaZulu » 08.12.2018, 11:31

Hallo zusammen,

seit geraumer Zeit stresst mein CUxD, wenn ich auf der CCU2 ein Update installieren will. Es scheint zwar alles zu funktionieren, aber nach dem Neustart geht nichts mehr. CUxD friert dann manchmal ein. Gehe ich wieder auf die Version 1.10 b zurück oder spiele das komplette Backup der CCU ein, läuft es wieder, wenn ich mal davon absehe, dass teilweise CUxD-Geräte (Intertechno-Steckdosen) nicht entfernbar sind.

Ich habe jetzt mal versucht, einfach den CUxD zu deinstallieren, bevor ich die die neue Version draufpacke, aber dann sind alle Einstellungen weg.

Hat jemand eine Idee, was ich machen kann, damit ich a) die neueste CUxD-Version nutzen kann und b) auch alte Geräte sauber aus der CCU2 bekomme?

Scriptende Grüße

Axel

Benutzeravatar
uwe111
Beiträge: 3743
Registriert: 26.02.2011, 22:22
Kontaktdaten:

Re: Probleme beim Update von CUxD

Beitrag von uwe111 » 08.12.2018, 13:36

Hallo Axel,

dann beantworte doch bitte erstmal meine Frage.

Viele Grüße

Uwe
Alle sagten: Das geht nicht. Dann kam einer, der wußte das nicht und hat's einfach gemacht.
SPENDEN :wink: Download: CUxD 2.2.0, RFD-Monitor, Vellemann K8055, SSH KeyDir

AlphaZulu
Beiträge: 99
Registriert: 25.05.2015, 17:32

Re: Probleme beim Update von CUxD

Beitrag von AlphaZulu » 08.12.2018, 14:38

Hallo Uwe,

huch, dass du damals geantwortet hattest, hatte ich gar nicht mitbekommen :-(. Daher habe ich das dann auch so hingenommen und erst jetzt mit der neuen Version noch mal einen Versuch gemacht.

Meinst du das hmserver.log?

Code: Alles auswählen

Dec 8 13:32:59 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Dec 8 13:33:00 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] creating instance of HMServerConfiguration with no-arg constructor 
Dec 8 13:34:07 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_1 subtype=default 
Dec 8 13:34:07 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_POWER_SHORT_CIRCUIT_BUS_2 subtype=default 
Dec 8 13:34:07 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_1 subtype=default 
Dec 8 13:34:07 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_SHORT_CIRCUIT_DATA_LINE_BUS_2 subtype=default 
Dec 8 13:34:07 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter ERROR_BUS_CONFIG_MISMATCH subtype=default 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Dec 8 13:34:08 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 21 classes to Vert.x 
Dec 8 13:34:09 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 21 VertxDeployers initialized 
Dec 8 13:34:14 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Dec 8 13:34:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (8ec0e863-8e03-4325-b876-e8b288accdac) 
Dec 8 13:34:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (e28036ee-3767-48bd-b4a1-d19e82797521) 
Dec 8 13:34:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (5cdd8ebe-533c-4fe1-ae3e-574c0ae5ee32) 
Dec 8 13:34:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of TransactionSubsystemHandler succeeded (53cc3dac-af85-4cf9-8baf-8aae9cfab31a) 
Dec 8 13:34:15 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KeyServerWorker succeeded (aa90f2a5-3576-4bf2-b46c-d12f67e0955b) 
Dec 8 13:34:16 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:16 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]) 
Dec 8 13:34:16 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:16 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] 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]) 
Dec 8 13:34:16 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: [persistent.data.loaded]) 
Dec 8 13:34:16 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: [persistent.data.loaded]) 
Dec 8 13:34:22 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 5 out of 21 
Dec 8 13:34:23 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:23 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]) 
Dec 8 13:34:23 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:23 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] 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]) 
Dec 8 13:34:23 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: [persistent.data.loaded]) 
Dec 8 13:34:23 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: [persistent.data.loaded]) 
Dec 8 13:34:37 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: DeviceLiveUpdateSubsystem started 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:37 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]) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] 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]) 
Dec 8 13:34:37 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: [persistent.data.loaded]) 
Dec 8 13:34:37 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: [persistent.data.loaded]) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 5 out of 21 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:37 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]) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration  (still unfulfilled: [persistent.data.loaded]) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] 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]) 
Dec 8 13:34:37 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: [persistent.data.loaded]) 
Dec 8 13:34:37 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: [persistent.data.loaded]) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (2b3cec5c-6db7-4c05-9dec-f44ba5cb5679) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (8e93bb62-a11c-46f6-8615-3b63d76aa163) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KryoPersistenceWorker succeeded (cf989d06-957c-4d1d-9c7b-dc8919488774) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (28407587-deb5-4ba6-af75-268e4cf5f4d5) 
Dec 8 13:34:37 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (c5e75f6b-f646-439e-a82c-53708c1b6ee2) 
Dec 8 13:34:38 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerPersistentDataLoader succeeded (68f6ab6c-5bb2-4296-b2d5-fcd7c034de60) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 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: [persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open][persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 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: [persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open][persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 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: [persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open][persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 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: [persistent.data.loaded]) 
Dec 8 13:34:38 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]) 
Dec 8 13:34:38 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open][persistent.data.loaded]) 
Dec 8 13:34:42 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBackendNotificationHandler succeeded (a6dc90ee-10d8-4a07-a6d3-69db0d72c770) 
Dec 8 13:34:43 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-1] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Dec 8 13:34:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (fe682eda-a413-4dac-974c-48b5ba7ba23f) 
Dec 8 13:34:43 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (37a4d09e-67b0-4307-884a-effd95aec0b9) 
Dec 8 13:34:44 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration  (still unfulfilled: [connector.open]) 
Dec 8 13:34:45 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LocalServerAdapterInitialization succeeded (ba265596-5280-4c22-b9d7-ead3037c5c8e) 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 11595735... 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A0000352298D28D6 to 3 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.5 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Dec 8 13:34:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of BackendCommandHandler succeeded (0f8a13d0-7878-46b9-86a8-46f983f4ec42) 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: ATmega644pa_AVR 
Dec 8 13:34:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyNotificationHandler succeeded (bd5ef83a-489a-44d6-a3f1-577c79e36d29) 
Dec 8 13:34:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyAPIWorker succeeded (fac1e8a5-a181-44a3-9c67-3b71b22679a4) 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 1.5 
Dec 8 13:34:46 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of IncomingHMIPFrameHandler succeeded (88bac6d4-723b-45d1-964b-22c850be33eb) 
Dec 8 13:34:46 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-1] SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration  (still unfulfilled: [connector.open]) 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 291156487 
Dec 8 13:34:46 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 291168540 
Dec 8 13:34:47 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 11 link partners 
Dec 8 13:34:47 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A0000352298D28D6 initialized 
Dec 8 13:34:47 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Dec 8 13:34:48 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (ebe64be8-4b83-48cd-8edc-9774e10a4f49) 
Dec 8 13:34:48 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Checking all devices on all accesspoints for updates 
Dec 8 13:34:48 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: There are 0 APs queued with updatable devices 
Dec 8 13:34:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of LegacyInitializion succeeded (2525847f-5b1e-4ada-9cad-9b9d47f014b9) 
Dec 8 13:34:49 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Dec 8 13:34:50 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 0 out of 0 
Dec 8 13:34:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Dec 8 13:34:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Dec 8 13:34:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Dec 8 13:34:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 2 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 10 classes to Vert.x 
Dec 8 13:34:51 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 10 VertxDeployers initialized 
Dec 8 13:34:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of BackendWorker succeeded (280a6114-b84b-4d34-a824-89bcb74e897a) 
Dec 8 13:34:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (930ac460-2ee3-4a4c-a0e1-6e5a9bb4435d) 
Dec 8 13:34:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (fcec84af-45af-474e-9c24-d956c70c47d9) 
Dec 8 13:34:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of RegaClientWorker succeeded (eb608f5e-4057-47f8-a15c-1f697afd27a0) 
Dec 8 13:34:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of EnergyPriceRequestWorker succeeded (c0199a08-b77e-4f82-95e8-b0e47c052c43) 
Dec 8 13:34:52 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of StorageRequestWorker succeeded (935fe13d-bd81-49f0-a6e7-9c4b46206ecf) 
Dec 8 13:34:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of DiagramRequestWorker succeeded (ddee0142-2b00-460d-ab75-62523014efee) 
Dec 8 13:34:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of GroupRequestWorker succeeded (5d480147-75f8-4b2b-a9e1-1bc3b742fe87) 
Dec 8 13:34:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (8cb08c0e-d998-475f-866d-38a56e8d9e2d) 
Dec 8 13:35:05 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10 
Dec 8 13:35:17 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 2010 
Dec 8 13:35:19 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10 
Dec 8 13:35:33 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10 
Dec 8 13:35:47 de.eq3.cbcs.vertx.management.VertxManager WARN  [vert.x-eventloop-thread-0] SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10 
Dec 8 13:35:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (f67306c2-b8cf-484a-b74e-baedb2789ea0) 
Dec 8 13:35:56 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Dec 8 13:35:56 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:9292 
Dec 8 13:35:56 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Dec 8 13:36:01 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Dec 8 13:36:03 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Dec 8 13:36:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.66:12010 
Dec 8 13:36:06 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Dec 8 13:36:06 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: hm-rpc.2 
Dec 8 13:36:17 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient hm-rpc.2 -> 61 device addresses will be added 
Dec 8 13:36:27 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Dec 8 13:36:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Dec 8 13:36:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Dec 8 13:36:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Dec 8 13:36:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Dec 8 13:36:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Dec 8 13:36:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Dec 8 13:36:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Dec 8 13:36:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Dec 8 13:36:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Dec 8 13:36:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Dec 8 13:36:40 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Dec 8 13:36:40 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Dec 8 13:36:40 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Dec 8 13:36:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Dec 8 13:36:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Dec 8 13:36:51 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Dec 8 13:36:54 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Dec 8 13:36:54 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Dec 8 13:36:54 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Dec 8 13:36:55 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:9292/bidcos 
Dec 8 13:36:55 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Dec 8 13:36:55 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: HmIP-RF_java 
Dec 8 13:36:56 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Dec 8 13:36:56 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-1] updateDevicesForClient HmIP-RF_java -> 61 device addresses will be added 
Dec 8 13:39:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 13:39:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 13:39:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 13:41:19 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999 
Dec 8 13:41:20 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-3] Added InterfaceId: 1236 
Dec 8 13:41:20 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-11] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Dec 8 13:41:31 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999 
Dec 8 13:41:31 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-4] init finished 
Dec 8 13:41:31 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-3] Added InterfaceId: 6398 
Dec 8 13:44:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 13:44:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 13:44:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 13:49:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 13:49:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 13:49:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 13:54:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 13:54:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 13:54:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 13:59:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 13:59:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 13:59:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:04:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:04:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:04:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:07:31 org.apache.http.impl.client.DefaultHttpClient INFO  [vert.x-worker-thread-0] I/O exception (java.net.SocketException) caught when processing request to {}->http://127.0.0.1:9292: Broken pipe (Write failed) 
Dec 8 14:07:31 org.apache.http.impl.client.DefaultHttpClient INFO  [vert.x-worker-thread-0] Retrying request to {}->http://127.0.0.1:9292 
Dec 8 14:09:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:09:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:09:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:14:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:14:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:14:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:19:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:19:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:19:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:24:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:24:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:24:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:29:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:29:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:29:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Dec 8 14:34:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: 0 Accesspoints in Queue 
Dec 8 14:34:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Dec 8 14:34:37 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-0] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Mehr steht da aktuell nicht drin.

Axel

AlphaZulu
Beiträge: 99
Registriert: 25.05.2015, 17:32

Re: Probleme beim Update von CUxD

Beitrag von AlphaZulu » 08.12.2018, 14:54

oder meintest du das:

https://www.dropbox.com/s/l38kvwy978mtv ... 9.log?dl=0

(Ließ sich hier jetzt nur als Link einfügen)

Benutzeravatar
uwe111
Beiträge: 3743
Registriert: 26.02.2011, 22:22
Kontaktdaten:

Re: Probleme beim Update von CUxD

Beitrag von uwe111 » 08.12.2018, 19:52

Hallo Alex,

ich meinte das 2. Log.
Mit Version 1.10b funktioniert es ja.

Was steht im Log, nachdem Du die aktuellste CUxD-Version installiert hast?

Viele Grüße

Uwe
Alle sagten: Das geht nicht. Dann kam einer, der wußte das nicht und hat's einfach gemacht.
SPENDEN :wink: Download: CUxD 2.2.0, RFD-Monitor, Vellemann K8055, SSH KeyDir

AlphaZulu
Beiträge: 99
Registriert: 25.05.2015, 17:32

Re: Probleme beim Update von CUxD

Beitrag von AlphaZulu » 08.12.2018, 20:38

Hallo Uwe,

mit der 1.10b klappt alles, bis auf das Löschen von ausgemusterten Intertechno-Steckdosen. Die lassen sich nur mit zig Anläufen und getrenntem Löschen in der WebGUI und in CUxD löschen. Manchmal gibt es dann danach auch einen Komplettabsturz und die CCU2 fährt mit Werksreset hoch. Wenn ich dann nicht vorher ein Backup gemacht habe, dann geht das Löschen von vorne los.

Bevor jetzt andere im Forum meinen, ich würde wie bescheuert Geräte löschen: Ich stelle nur die Interchnos auf Sonoff-Steckdosen um.

Ich packe nächste Woche nochmal die aktuelle CUxD-Version drauf und ziehe dann nochmal das Log. Wenn ich die CCU heute noch ein paarmal boote, dann gibt es - glaube ich - Ärger :-).

Für den Umzug auf einen Raspi hätte ich das Ganze dann schon gerne in sauber, denn auf eine komplette Neueinrichtung habe ich eigentlich keine Lust :-).

Besten Dank auf jeden fall schonmal für die schnellen Antworten.

Benutzeravatar
uwe111
Beiträge: 3743
Registriert: 26.02.2011, 22:22
Kontaktdaten:

Re: Probleme beim Update von CUxD

Beitrag von uwe111 » 09.12.2018, 15:25

Versuche dann auch gleich mal, Deine ganzen HM-Script Fehler zu reparieren.

Viele Grüße

Uwe
Alle sagten: Das geht nicht. Dann kam einer, der wußte das nicht und hat's einfach gemacht.
SPENDEN :wink: Download: CUxD 2.2.0, RFD-Monitor, Vellemann K8055, SSH KeyDir

AlphaZulu
Beiträge: 99
Registriert: 25.05.2015, 17:32

Re: Probleme beim Update von CUxD

Beitrag von AlphaZulu » 09.12.2018, 19:58

Hallo Uwe,

wo habe ich die denn? Aktuell läuft eigentlich alles so, wie es soll :-) (von dem CUxD-Problem mal abgesehen).

Scriptende Grüße

Axel

Antworten

Zurück zu „CUxD“