Zentralen

Hallo Homematic Profis,

bin neu hier im Forum, obwohl ich meine CCU2 mit 20-25 Aktoren schon seit mehreren Jahren in Betrieb habe. Spricht schon für das Teil, aber jetzt hab ich echt ein Problem. Wollte schon den "Notfall" Knopf drücken, aber ich habe die nächsten 36 Stunden wahrscheinlich keine Gelegenheit mich um das Problem zu kümmern und da wollte ich nicht drängeln. Es ist nur so, daß ein paar meiner Lichtschalter nicht mehr funktionieren und ich weiß nicht wie geduldig meine Frau und die Kids da sind. Also nun zum Problem. Bis ca. 20Uhr heute hatte war mir nichts aufgefallen. Kurz danach wollte ich mal auf die CCU2 über die WebUI schauen und hatte das erste mal überhaupt, keinen Zugriff (Blauer Bildschirm, mit Text "Die Homematic CCu ist noch nicht bereit") Folgendes habe ich probiert.
- Neustart mehrfach,
- Recovery mit neuester FW,
- Netzwerk geprüft, Netfinder findet die CCU unter meiner bekannten IP,
- mit Filezilla habe ich Zugriff (ich könnte logs hochladen, wenn mir einer sagen kann welchen und wo der liegt). Die Power, Netzwerk LED leuchten dauerhaft, Die Info LED blinkt so in 1sec. Takt. So ist das nach jedem Neustart.
ich hoffe es kann mir irgend jemand hier helfen, über USB habe ich noch nicht probiert, ich habe ein Backup, das ist aber schon ein paar Wochen alt.
Vielen Dank schon mal für eure Hilfe

Die Logs liegen unter
/var/log
Files
hmserver.log
messages

Hallo Christian,

danke für Dein Feedback.
Ich habe gestern noch den Log gefunden, werde aber nicht schlau draus. Vielleicht magst Du ja mal drüberschauen.

Danke

Hier der Log (ich glaube anders geht´s nicht)

May 27 22:04:22 de.eq3.lib.util.dynamics.GenericFactory INFO @GenericFactory
May 27 22:04:23 de.eq3.lib.util.dynamics.GenericFactory INFO creating instance of HMServerConfiguration with no-arg constructor
May 27 22:05:28 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:28 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (3) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1)
May 27 22:05:29 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: deploying 22 classes to Vert.x
May 27 22:05:30 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: 22 VertxDeployers initialized
May 27 22:05:35 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (348f14d8-bfbc-4b5c-ae33-7096ff1600c6)
May 27 22:05:35 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of CheckDeviceExistHandler succeeded (a289f022-07c9-4c57-a580-c0ed2c1e0dfa)
May 27 22:05:35 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (8b1bfbe6-8dc1-47c3-b0b0-369daa6860b8)
May 27 22:05:35 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR Missing key server configuration parameter (Network.Key) for mode: KEYSERVER_LOCAL
May 27 22:05:35 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (eee02a00-9e25-49ed-8724-ff5018abf06e)
May 27 22:05:36 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration
May 27 22:05:36 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:36 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:36 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:37 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:37 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:37 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration
May 27 22:05:43 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of KryoPersistenceWorker still not met - check deployment configuration
May 27 22:05:43 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:43 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:43 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:44 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:44 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:44 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of DeviceBackgroundUpdateSubsystem still not met - check deployment configuration
May 27 22:05:50 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:50 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:50 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:51 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:51 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:54 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO SYSTEM: DeviceLiveUpdateSubsystem started
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (7b302696-458e-455b-b2cc-18644d5955aa)
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of AccessPointElectroCardioGram succeeded (1607e6fc-8e28-4ad5-93c8-f7a89001ab3b)
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of TransactionSubsystemHandler succeeded (5709cab0-01de-42ff-91fc-81f36f2e2338)
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of HMIPTRXWriterWorker succeeded (ab8e2f72-0cec-4939-9f01-96a0c3e23b61)
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of KeyServerWorker succeeded (75381988-e2e6-4820-aed3-6f7fa7e29a44)
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of KryoPersistenceWorker succeeded (97757711-1d0f-4821-908e-a3f8310148ff)
May 27 22:05:54 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (8874b97c-f671-46a4-b00d-628901cf5eaf)
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LocalServerPersistentDataLoader succeeded (3fa37356-ca47-41a1-89de-0716d91c58d6)
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 12 out of 22
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:55 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:57 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 12 out of 22
May 27 22:05:57 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of FirmwareLoaderFileSystem still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:57 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of BackendCommandHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:57 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerAdapterInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:57 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of IncomingHMIPFrameHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:58 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of DeviceInclusionAcceptHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:58 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:58 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LocalServerFirmwareUpdateInitialization still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:58 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyAPIWorker still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:58 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyBackendNotificationHandler still not met - check deployment configuration (still unfulfilled: )
May 27 22:05:58 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: )
May 27 22:06:00 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of IncomingHMIPFrameHandler succeeded (e76cc1e3-66e6-41ea-9af8-164966417221)
May 27 22:06:00 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO SYSTEM: Firmware update directory is set to /etc/config/firmware
May 27 22:06:00 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of FirmwareLoaderFileSystem succeeded (eab2f130-f13f-43e9-98e1-508053b4b1e5)
May 27 22:06:01 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LocalServerAdapterInitialization succeeded (94d3cba9-ff46-4d25-b287-732eb05b247a)
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO TRX adapter state 1: HMIP_TRX_App
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO TRX adapter application is already running or started
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO No NWK, try to set address ...
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Try to set radio address 12122906...
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Set max send attempts for 3014F711A00003522998D49C to 3
May 27 22:06:02 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of BackendCommandHandler succeeded (cf3e5b28-ff9d-47ca-8d39-3946cb8bd398)
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Try to get application version...
May 27 22:06:02 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of DeviceInclusionAcceptHandler succeeded (bf871ddf-e715-4e70-a556-a006dbdf6af3)
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Application version 2.8.6
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Bootloader version 1.0.5
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO hmos version 1.20.3
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO MCU type: ATmega644pa_AVR
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Duty Cycle: 1.0
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO set DutyCycle limit to ffffffc8
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Set Duty Cycle Limit
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Current Security Counter: 240174592
May 27 22:06:02 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Update security counter to calculation: 240181832
May 27 22:06:03 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO TRX adapter has 5 link partners
May 27 22:06:03 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO Adapter with Access Point id 3014F711A00003522998D49C initialized
May 27 22:06:03 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO HMIPTRXInitialResponseListener said that Adapter was initialized
May 27 22:06:04 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LegacyBackendNotificationHandler succeeded (b37e2d37-57f2-49cb-941f-2220a28720ca)
May 27 22:06:05 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (29450012-3f32-4541-8418-41a4f2c2c9e2)
May 27 22:06:05 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Checking all devices on all accesspoints for updates
May 27 22:06:05 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: There are 0 APs queued with updatable devices (RF)
May 27 22:06:05 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: There are 0 APs queued with updatable devices (WIRED)
May 27 22:06:05 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: pre-conditions for deployment of LegacyInitializion still not met - check deployment configuration (still unfulfilled: )
May 27 22:06:05 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LegacyNotificationHandler succeeded (b4cf900c-e7ed-474a-8d8b-ef06d013056f)
May 27 22:06:06 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LegacyAPIWorker succeeded (582a7b9c-21e7-4d75-af03-6273b4d7cafd)
May 27 22:06:08 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of LegacyInitializion succeeded (0168c640-2cb4-41c7-aab1-cd1253f066e2)
May 27 22:06:08 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: initial deployment complete _____________________________________________________
May 27 22:06:10 de.eq3.ccu.server.BaseHMServer INFO Default MaxEventLoopExecuteTime: 2000000000
May 27 22:06:10 de.eq3.ccu.server.BaseHMServer INFO Default BlockedThreadCheckInterval: 1000
May 27 22:06:10 de.eq3.ccu.server.BaseHMServer INFO Default MaxWorkerExecuteTime: 60000000000
May 27 22:06:10 de.eq3.ccu.server.BaseHMServer INFO Default EventLoopPoolSize: 2
May 27 22:06:10 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:10 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: added for deployment (1) *worker
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: deploying 10 classes to Vert.x
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: 10 VertxDeployers initialized
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of EnergyPriceRequestWorker succeeded (24d6ed7d-fb7c-4b25-98ad-fdea5cdafc92)
May 27 22:06:11 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of BackendWorker succeeded (e9c79275-60e8-4a99-9b60-536e31a00637)
May 27 22:06:12 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of CouplingRequestWorker succeeded (f4d9c3ad-7e3c-4844-9794-17a4e4c5b227)
May 27 22:06:12 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of RegaClientWorker succeeded (b733feac-3b17-47ee-a67d-3132ce9b61f0)
May 27 22:06:12 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (d267c39f-2a18-4bdf-81a9-5248e28916d1)
May 27 22:06:12 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of StorageRequestWorker succeeded (ad9c9981-a717-4342-8620-1d0da7ddbd87)
May 27 22:06:14 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of GroupRequestWorker succeeded (21fc97bf-9c7e-4a06-8b55-de58747294d6)
May 27 22:06:14 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of DiagramRequestWorker succeeded (850aba6a-869b-4516-bb8e-9c290020463e)
May 27 22:06:14 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of DeviceFirmwareRequestWorker succeeded (bd5ecf2c-a313-4a7e-b7bd-230356dfc7d2)
May 27 22:06:25 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10
May 27 22:06:28 de.eq3.cbcs.server.local.LocalServer INFO SYSTEM: Bind XML-RPC api to port 2010
May 27 22:06:39 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10
May 27 22:06:53 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10
May 27 22:07:07 de.eq3.cbcs.vertx.management.VertxManager WARN SYSTEM ADVICE: long-lasting deployment, check deployment configuration - currently deployed 9 out of 10
May 27 22:07:09 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO (un)registerCallback on LegacyServiceHandler called from url: http://192.168.178.35:2010
May 27 22:07:09 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO init finished
May 27 22:07:10 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO Added InterfaceId: hm-rpc.1
May 27 22:07:12 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (22a2fbab-4390-4cf3-afb8-bfd1efe34ebc)
May 27 22:07:12 de.eq3.cbcs.vertx.management.VertxManager INFO SYSTEM: initial deployment complete _____________________________________________________
May 27 22:07:12 de.eq3.ccu.server.BaseHMServer INFO Starting HMServer at 127.0.0.1:9292
May 27 22:07:12 de.eq3.ccu.server.BaseHMServer INFO Read Configuration
May 27 22:07:18 de.eq3.ccu.server.BaseHMServer INFO Create Bidcos Dispatcher
May 27 22:07:19 de.eq3.ccu.server.BaseHMServer INFO InitBidCosCache
May 27 22:07:23 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO updateDevicesForClient hm-rpc.1 -> 81 device addresses will be added
May 27 22:07:31 de.eq3.ccu.server.BaseHMServer INFO Create groupDefinitionProvider
May 27 22:07:38 de.eq3.ccu.server.BaseHMServer INFO Create VirtualDeviceHolder
May 27 22:07:38 de.eq3.ccu.server.BaseHMServer INFO Create VirtualDeviceHandlerRega
May 27 22:07:38 de.eq3.ccu.server.BaseHMServer INFO Create GroupAdministrationService
May 27 22:07:38 de.eq3.ccu.server.BaseHMServer INFO Create GroupDeviceDispatcher
May 27 22:07:38 de.eq3.ccu.server.BaseHMServer INFO Create GroupDeviceHandler
May 27 22:07:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO @GroupDeviceHandler - initializing...
May 27 22:07:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher))
May 27 22:07:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO --> created virtualDeviceHandler (GroupDeviceService to ReGa)
May 27 22:07:38 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO --> got groupDefinitionProvider
May 27 22:07:38 de.eq3.ccu.server.BaseHMServer INFO Create BidCosGroupMemberProvider
May 27 22:07:39 de.eq3.ccu.server.BaseHMServer INFO Init groupAdministrationService
May 27 22:07:39 de.eq3.ccu.server.BaseHMServer INFO Init Virtual OS Device
May 27 22:07:39 de.eq3.ccu.server.BaseHMServer INFO Init ESHLight Bridge
May 27 22:07:48 de.eq3.ccu.server.BaseHMServer INFO Create RrdDatalogging
May 27 22:07:48 de.eq3.ccu.server.BaseHMServer INFO Create MeasurementService
May 27 22:07:48 de.eq3.ccu.server.BaseHMServer INFO Init MeasurementService
May 27 22:07:51 de.eq3.ccu.server.BaseHMServer INFO Create HTTP Server
May 27 22:07:51 de.eq3.ccu.server.BaseHMServer INFO Create BidCos context and start handler
May 27 22:07:51 de.eq3.ccu.server.BaseHMServer INFO Create group context and start handler
May 27 22:07:51 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:9292/bidcos
May 27 22:07:51 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO Added InterfaceId: HmIP-RF_java
May 27 22:07:51 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO init finished
May 27 22:07:52 de.eq3.ccu.server.BaseHMServer INFO Starting HMServer done
May 27 22:07:53 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO updateDevicesForClient HmIP-RF_java -> 81 device addresses will be added
May 27 22:08:35 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:1999
May 27 22:08:35 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO Added InterfaceId: 1236
May 27 22:08:35 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand
May 27 22:08:45 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO (un)registerCallback on LegacyServiceHandler called from url: xmlrpc_bin://127.0.0.1:1999
May 27 22:08:45 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO Added InterfaceId: 9927
May 27 22:08:45 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO init finished
May 27 22:10:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: 0 Accesspoints in Queue
May 27 22:10:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 27 22:10:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Eventlistener Handler utilization: 0/50 used
May 27 22:15:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: 0 Accesspoints in Queue
May 27 22:15:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 27 22:15:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Eventlistener Handler utilization: 0/50 used
May 27 22:20:41 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyNotificationHandler WARN Remove interface: 9927 http URL: http://127.0.0.1:1999 from client list because of communication problem
May 27 22:20:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: 0 Accesspoints in Queue
May 27 22:20:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 27 22:20:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Eventlistener Handler utilization: 0/50 used
May 27 22:25:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: 0 Accesspoints in Queue
May 27 22:25:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 27 22:25:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Eventlistener Handler utilization: 0/50 used
May 27 22:30:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: 0 Accesspoints in Queue
May 27 22:30:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used
May 27 22:30:54 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO SYSTEM: Eventlistener Handler utilization: 0/50 used

Hier der Log (ich glaube anders geht´s nicht)

Warum nicht die Datei irgendwo ablegen (eigenen Webspace hat fast jeder ISP) oder "Habe die Dateien gefunden, kann ich sie zumailen?"
Man könnte auch die zyklischen Meldungen entfernen,
aber hier einfach reinschmeissen ist ja einfach. Muß sich ja derjenigen nur rauskopieren und in einen Editor einfügen, damit es lesbar wird.

Das ist m.E. nur das hmserver.log
Die Datei messages könnte man auch auswerten.

Für mich sieht es so aus, als ob die CCU korrekt hochgefahren ist.
Prüfe, ob ein Aktor defekt ist und dauernd sendet (stromlos machen), so das die CCU damit zu tun hat und nicht mehr das WebUI anzeigen kann.

Hallo Christian,

erstmal sorry fürs "einfach reinkopieren". Wollte es natürlich nicht absichtlich beschwerlich machen.
Ja den message log hab ich natürlich auch nicht dazugefügt. Ich komme jetzt nur leider nicht dran, bin im Büro. Meinst du ich kann im message log erkennen welcher aktor das Problem verusachen könnte? Ich schaue mir den am Abend mal an. Viele aktoren sind eingebaut in Schaltdosen das könnte dauern bis ich den richtigen finde.

Danke nochmal für Deine geduldige Hilfe. Bin nicht so oft in Foren unterwegs (als Schreiber)

Meinst du ich kann im message log erkennen welcher aktor das Problem verusachen könnte?

Könnte sein. Wenn Aktoren Fehler verursachen steht das da drin

Hallo,

ich habe jetzt alle verfügbaren logs zur Hand und hab auch selbst schon intensiv versucht da was rauszulesen. Für mich sieht alles normal aus. Die Sensoren geben Daten raus, das kann ich sehen. Aber meine Unterputzschalter gehen alle nicht und natürlich die Web UI. ich steh komplett am Schlauch. ich hätte einen lighttpd-error.log, lighttpd-access.log, den hmserver.log und den message.log.
Wäre toll, wenn sich jemand noch finden würde der mir helfen kann. Die Aktzeptanz meiner Familie eine Hausatomation zu betreiben sinkt von Tag zu Tag.:)
Danke

Hallo,

CCU2 läuft wieder. Ich habe heute das 3te mal die CCU2 auf Werkzustand zurückgesetzt. Jetzt geht alles wieder (Backup hatte auch funktioniert. Das einzige was ich anders gemacht habe dieses mal, ich habe anstatt der neuen FW 2.45.7 die etwas ältere 2.41.5 installiert. Will damit nicht sagen die FW ist fehlerhaft. Aber ich wusste die 2.41 läuft stabil. War ein Test
Danke nochmal und schönen Vatertag