RegaHss , Watchdog Hilfe :(

Einrichtung, Nutzung und Hilfe zu RaspberryMatic (OCCU auf Raspberry Pi)

Moderatoren: jmaus, Co-Administratoren

Olli_HM
Beiträge: 15
Registriert: 16.01.2018, 13:14
Hat sich bedankt: 1 Mal

RegaHss , Watchdog Hilfe :(

Beitrag von Olli_HM » 03.04.2021, 20:58

Hi,
ich benutze Raspberrymatic auf einem Raspberry 3B, auf einer Synology läuft Homeassistant im Docker.

Seit einigen Tagen habe ich ziemliche Probleme und weiß nicht mehr weiter, RegaHss startet neu, Raspberrymatic ist nicht oder langsam erreichbar. Entsprechend kann HA nicht darauf zugreifen. Es hat vorher ziemlich lange unproblematisch funktioniert.
Erst hatte ich einige Autoren von HM IP im Verdacht aber ich kann nicht feststellen, welcher Autor. Auch HM ohne IP ist im Einsatz.

Ich benutzte eine Version vom Januar 2020, jeder Versuch, ein Update einzuspielen schlug fehl, der Upload wurde nie fertig. Egal mit welchem Browser.
SSH einloggen, reboot oder auch regahss Neustart. Ja, ging alles aber der Fehler blieb.

Grad eben habe ich eine frische SD Karte geflasht, das Backup eingespielt und in die Logdatei geschaut - wieder die vermutliche Ursache des ganzen. Ich verzweifle langsam.
Das Untere "Apr 3 20:41:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data " wiederholt sich
für die nächsten 2300 (!) Zeilen, alles innerhalb von ein paar Sekunden.

HomeAssistant ist abgeschaltet, um eine Beeinflussung auszuschließen.

Was soll ich tun ??

Logdatei:

Code: Alles auswählen

***** hmserver.log *****
Apr 3 20:41:20 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Apr 3 20:41:20 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Apr 3 20:41:20 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Apr 3 20:41:31 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter LOCK_STATE_STATUS subtype=default 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 22 classes to Vert.x 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 22 VertxDeployers initialized 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.CyclicSmokeDetectorAwakening INFO  [vert.x-eventloop-thread-4] SYSTEM: CyclicSmokeDetectorAwakening Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.DeviceInclusionDefaultConfigurationChanger INFO  [vert.x-eventloop-thread-6] SYSTEM: DeviceInclusionDefaultConfigurationChanger Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.CheckDeviceExistHandler INFO  [vert.x-eventloop-thread-0] SYSTEM: CheckDeviceExistHandler Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (2ad5ba04-82c8-44a3-9329-129ad1c46f09) 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (80c23484-9057-4811-94d7-b4d73a219b8b) 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler INFO  [vert.x-worker-thread-0] SYSTEM: TransactionSubsystemHandler Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of TransactionSubsystemHandler succeeded (c3600975-5da8-4469-a492-e73715cf9a05) 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-2] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.HMIPAbstractWriterWorker INFO  [vert.x-worker-thread-3] SYSTEM: HMIPTRXWriterWorker Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of HMIPTRXWriterWorker succeeded (f8f2dc79-e35d-4f3a-a65a-7421283b896e) 
Apr 3 20:41:32 de.eq3.cbcs.server.core.vertx.KeyServerWorker INFO  [vert.x-worker-thread-2] SYSTEM: KeyServerWorker Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of KeyServerWorker succeeded (2ba8480c-2d94-4db4-9d0c-936a93f09b2a) 
Apr 3 20:41:32 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBlindLevelCorrectionHandler INFO  [vert.x-worker-thread-1] SYSTEM: LegacyBlindLevelCorrectionHandler Verticle or Worker started 
Apr 3 20:41:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (b2e1daa9-6150-4db1-bca2-a5b02f81e264) 
Apr 3 20:41:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (15e63b4d-bf1e-41d5-a10f-8c1c57e80669) 
Apr 3 20:41:33 de.eq3.cbcs.server.local.base.internal.LocalServerPersistentDataLoader INFO  [vert.x-eventloop-thread-4] SYSTEM: LocalServerPersistentDataLoader Verticle or Worker started 
Apr 3 20:41:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (9c159e1f-3418-477c-b357-1be6c93f53e0) 
Apr 3 20:41:33 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: DeviceLiveUpdateSubsystem Verticle or Worker started 
Apr 3 20:41:33 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: DeviceBackgroundUpdateSubsystem Verticle or Worker started 
Apr 3 20:41:33 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-1] SYSTEM: DeviceLiveUpdateSubsystem started 
Apr 3 20:41:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (2e964745-3d37-45c4-8932-ced8c76b4fdd) 
Apr 3 20:41:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of CheckDeviceExistHandler succeeded (90d619a3-d806-42bb-8882-5696424fae73) 
Apr 3 20:41:33 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (5b95ad39-2139-43bc-8389-e6cd7829abd5) 
Apr 3 20:41:35 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 3 20:41:35 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-2] SYSTEM: FirmwareLoaderFileSystem Verticle or Worker started 
Apr 3 20:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of FirmwareLoaderFileSystem succeeded (cc661de8-f485-48d1-9a80-505b4cb98162) 
Apr 3 20:41:35 de.eq3.cbcs.server.core.vertx.DeviceInclusionAcceptHandler INFO  [vert.x-eventloop-thread-0] SYSTEM: DeviceInclusionAcceptHandler Verticle or Worker started 
Apr 3 20:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (a592a276-81b4-44e9-90c3-167b34095345) 
Apr 3 20:41:35 de.eq3.cbcs.server.core.vertx.IncomingHMIPFrameHandler INFO  [vert.x-eventloop-thread-1] SYSTEM: IncomingHMIPFrameHandler Verticle or Worker started 
Apr 3 20:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of IncomingHMIPFrameHandler succeeded (555763da-55e1-42f0-b6df-47aad74b2dbd) 
Apr 3 20:41:35 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle INFO  [vert.x-eventloop-thread-4] SYSTEM: TransactionManagementVerticle Verticle or Worker started 
Apr 3 20:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of TransactionManagementVerticle succeeded (a3293d91-cf6b-4e0a-9d77-edc759d99533) 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [vert.x-eventloop-thread-7] SYSTEM: LocalServerAdapterInitialization Verticle or Worker started 
Apr 3 20:41:35 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (a4797608-5307-446d-b26f-760e734d5754) 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12395411... 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D7098E2061 to 3 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 1.0 
Apr 3 20:41:35 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 429901824 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 429904629 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has no linkpartner 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D7098E2061 initialized 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Apr 3 20:41:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-1] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 3 20:41:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-4] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 3 20:41:36 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-3] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 3 20:41:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyBackendNotificationHandler succeeded (62412823-3a8b-4fe5-8e01-84f4e4ad4bb6) 
Apr 3 20:41:36 de.eq3.cbcs.server.core.vertx.BackendCommandHandler INFO  [vert.x-eventloop-thread-6] SYSTEM: BackendCommandHandler Verticle or Worker started 
Apr 3 20:41:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of BackendCommandHandler succeeded (61c72e71-dd9f-4502-86ea-90f5e9341922) 
Apr 3 20:41:36 de.eq3.cbcs.server.local.base.internal.LocalServerFirmwareUpdateInitialization INFO  [vert.x-eventloop-thread-6] SYSTEM: LocalServerFirmwareUpdateInitialization Verticle or Worker started 
Apr 3 20:41:36 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (4cf69a93-4707-42c3-96c0-24b2d860719a) 
Apr 3 20:41:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data 
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: /etc/config/crRFD/data/linkData.conf; line: 1, column: 0]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:255)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3851)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3792)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2691)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.load(LinkUtil.java:123)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.getLinkInfo(LinkUtil.java:69)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.fillLinksOfChannel(DeviceUtil.java:2509)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getLinksOfChannel(DeviceUtil.java:2464)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getAllLinks(DeviceUtil.java:2407)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:808)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.<init>(VirtualRemoteControl.java:132)
	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.<init>(LegacyServiceHandler.java:113)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.initializeService(LegacyAPIWorker.java:24)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.start(AbstractLegacyAPIWorker.java:63)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.start(LegacyAPIWorker.java:18)
	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Apr 3 20:41:37 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data
Zuletzt geändert von alchy am 03.04.2021, 21:12, insgesamt 1-mal geändert.
Grund: Code in Codetags posten

Hütte
Beiträge: 702
Registriert: 08.02.2017, 11:08
Hat sich bedankt: 29 Mal
Danksagung erhalten: 70 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Hütte » 03.04.2021, 21:33

1. Bitte den Text Inhalt des Logs als "Code" einbetten (5. Symbol von links über das Texteingabe-Fenster), also bitte ändern. Sonst ist das schwer lesbar.
2. Hattest du auf der Version von Januar 2020 das Watchdog-AddOn von Jens installiert gehabt? Wenn ja, dann noch einmal eine frische Karte mit der Version von Januar 2020 flaschen (sind alle auf der Github-Seite von Jens verfügbar), dort das Backup einspielen und wenn das System neu gestartet ist, dann dieses Addon deinstallieren und ein neues Backup erstellen. Dieses AddOn wird nicht mehr benötigt, da Jens inzwischen eine andere Lösung direkt in Raspberrymatik implementiert hat.
3. Sollte die frische Karte mit der Version von Janaur 2020 und deinem aktuellen Backup auch nicht mehr starten, dann hast du wohl eher ein größeres Problem, weil dann wohl der Inhalt des Backups korrupt ist. Kannst du dann noch auf ältere Backups zurückgreifen und diese dann testen?
4. Wenn Schritt 3 erfolgreich war, dann würde ich an deiner Stelle ab jetzt eine weitere SD-Karte benutzen. Diese dann ebenfalls mit der Version von Januar 2020 flashen und das frische Backup einspielen. Entweder wagst du dann gleich den Sprung auf die aktuelle Version oder gehst in kleineren Schritten (Versionen) vor.

Da du mit einem Pi 3B arbeitest, ist es immer besser, wenn man eine zweite Karte neu flashed, dort das Backup einspielt und dann die Karten tauscht. Dadurch hast du immer noch die "alte" Karte als Fallback-Sicherung.

Hütte
Beiträge: 702
Registriert: 08.02.2017, 11:08
Hat sich bedankt: 29 Mal
Danksagung erhalten: 70 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Hütte » 03.04.2021, 21:33

@alchy

Danke für das Einbetten als Code.

Olli_HM
Beiträge: 15
Registriert: 16.01.2018, 13:14
Hat sich bedankt: 1 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Olli_HM » 03.04.2021, 22:20

Hi und vielen Dank für die Antwort.

Sorry, das mit dem Code wusste ich nicht, danke an alchy.

Im Januar 2020 hatte ich nichts installiert, soweit ich noch weiß.

Ich habe jetzt den Schritt auf die neueste Version 3.57.4.20210320 gemacht, ein Backup eingespielt. Komischerweise waren da Backups, deren Größe anders war man beachte die Unterschiede, 16 zu 48 MB. Ich habe das größere von gestern eingespielt auf eine frische SD Karte.
Bildschirmfoto 2021-04-03 um 22.08.43.png
Die alte Karte habe ich, wie du geraten hast, als Fallback.

Doch auch hier gibt es wieder diese Meldung :(
Ein Blick in die Logdatei zeigt mir wieder diese Zeilen: Allerdings nicht so oft und der böse WatchDog kam noch nicht.
Woran kann ich erkennen ob ich das Aden installiert habe ?

Code: Alles auswählen

Apr 3 21:43:12 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-4] Could not read link data 
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: /etc/config/crRFD/data/linkData.conf; line: 1, column: 0]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:255)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3851)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3792)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2691)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.load(LinkUtil.java:123)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.getLinkInfo(LinkUtil.java:69)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.fillLinksOfChannel(DeviceUtil.java:2509)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getLinksOfChannel(DeviceUtil.java:2464)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getLinks(DeviceUtil.java:2441)
	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.getLinks(LegacyServiceHandler.java:724)
	at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at de.eq3.cbcs.legacy.communication.rpc.internal.rpc.AnnotationAwareRpcHandler.execute(AnnotationAwareRpcHandler.java:80)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:82)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30)
	at io.vertx.core.eventbus.impl.HandlerRegistration.deliver(HandlerRegistration.java:212)
	at io.vertx.core.eventbus.impl.HandlerRegistration.handle(HandlerRegistration.java:191)
	at io.vertx.core.eventbus.impl.EventBusImpl.lambda$deliverToHandler$3(EventBusImpl.java:505)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Apr 3 21:43:21 org.apache.http.impl.client.DefaultHttpClient INFO  [HmIP-RF_java_WorkerPool-1] I/O exception (java.net.SocketException) caught when processing request to {}->http://127.0.0.1:39292: Broken pipe (Write failed) 
Apr 3 21:43:21 org.apache.http.impl.client.DefaultHttpClient INFO  [HmIP-RF_java_WorkerPool-1] Retrying request to {}->http://127.0.0.1:39292 


Hütte hat geschrieben:
03.04.2021, 21:33
1. Bitte den Text Inhalt des Logs als "Code" einbetten (5. Symbol von links über das Texteingabe-Fenster), also bitte ändern. Sonst ist das schwer lesbar.
2. Hattest du auf der Version von Januar 2020 das Watchdog-AddOn von Jens installiert gehabt? Wenn ja, dann noch einmal eine frische Karte mit der Version von Januar 2020 flaschen (sind alle auf der Github-Seite von Jens verfügbar), dort das Backup einspielen und wenn das System neu gestartet ist, dann dieses Addon deinstallieren und ein neues Backup erstellen. Dieses AddOn wird nicht mehr benötigt, da Jens inzwischen eine andere Lösung direkt in Raspberrymatik implementiert hat.
3. Sollte die frische Karte mit der Version von Janaur 2020 und deinem aktuellen Backup auch nicht mehr starten, dann hast du wohl eher ein größeres Problem, weil dann wohl der Inhalt des Backups korrupt ist. Kannst du dann noch auf ältere Backups zurückgreifen und diese dann testen?
4. Wenn Schritt 3 erfolgreich war, dann würde ich an deiner Stelle ab jetzt eine weitere SD-Karte benutzen. Diese dann ebenfalls mit der Version von Januar 2020 flashen und das frische Backup einspielen. Entweder wagst du dann gleich den Sprung auf die aktuelle Version oder gehst in kleineren Schritten (Versionen) vor.

Da du mit einem Pi 3B arbeitest, ist es immer besser, wenn man eine zweite Karte neu flashed, dort das Backup einspielt und dann die Karten tauscht. Dadurch hast du immer noch die "alte" Karte als Fallback-Sicherung.

Hütte
Beiträge: 702
Registriert: 08.02.2017, 11:08
Hat sich bedankt: 29 Mal
Danksagung erhalten: 70 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Hütte » 04.04.2021, 01:34

Über "Einstellungen -> Systemsteuerung -> Zusatzsoftware" werden dir deine installierten AddOn aufgelistet. Ebenso deren installierte Version und welches deren aktuelle Version ist. Ausser bei dem AddOn "Programmedrucken", falls du es instaliert haben solltest. Da kann kann die alte Version (ich glaube es war die Version 1.2 oder so) nicht feststellen, dass es eine neue Verion gibt, da die URL in Github sich geändert hat.

Mach bitte entweder einfach mal einen Screenshot der Liste der installierten AddOns oder gebe die Liste, inkl. der Versionen, hier an.

Aber die Frage ist auch, wieviel und was hast du seit Januar 2020 am System geändert. Und hast du andere Systeme wie IOBroker, NodeRed, eine Mediola App oder sonst dergleichen im Einsatz, die auf dein System zugreift, um entweder Daten abzufragen oder Aktionen auszulösen?

Was mir aber bei deiner Liste an Backups auffällt, sind die merkwürdigen Sprünge im Zeitstempel, da ich davon ausgehe, dass diese Liste nach Datum sortiert ist. Da gibt es einmal eine Lücke zwischen dem 05.03. und 08.03. (2 Tage fehlen), dann wieder zwischen dem 14.03. und 20.03. (5 Tage fehlen), 20.03, und 26.03. (wieder fehlen 5 Tage), dem 26.03. und 30.03. (3 Tage fehlen) und dann wieder zwischen dem 30.03. und 02.04. (2 Tage fehlen). Hast du eine Idee, was da los war? Oder war in diesen Zeiträumen das System heruntergefahren?

Diese Unterschiede in der Größe kann ich mir im Moment absolut nicht erklären. Denn wenn du seit Januar 2020 weder irgendein AddOn noch Komponenten oder etwas anderes eingerichtet hast, die dein System verändert haben, dann habe ich dafür erst einmal keine Erklärung. Aber der erste kleine Spung in der Größe zeigt sich ja schon im Backup vom 20.03., sind zwar "nur" 100 kB, aberschon erst einmal auffällig. Eventuell ist also schon in der Zeit zwischen dem 14.03. und dem 20.03. etwas passiert, was die Größe des BackUps anwachsen ließ. Aber dann ist auf einmal so ziemlich genauch die dreifache Größe im Backup ab dem 26.03. auffallend. Also hier muss in der Zwischenzeit etwas auf deinem System passiert sein.

Wie groß ist denn der USB-Stick, der angeschlossen ist und auf dem die BackUps geschrieben werden? Und wie groß ist die SD-Karte, die du bisher benutzt hattest?

Bekommst du auch Fehlermeldungen, wenn du eines der älteren BackUps, z.B. das vom 05.03., wieder einspielst?

Eventuell kann Jens (@jmaus) aus den Fehlermeldungen erkennen, wo die Ursache liegt.

Im Moment habe ich bezüglich der Fehlermeldungen keine Idee, was es sein könnte.

Olli_HM
Beiträge: 15
Registriert: 16.01.2018, 13:14
Hat sich bedankt: 1 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Olli_HM » 04.04.2021, 11:14

Hey,
vielen Dank für deine Nachrichten. Hier eine Liste der Zusatzsoftware.
Ich muss zugeben, recht alte Versionen. Keine Ahnung, warum ich den NEO SERVER habe.
Bildschirmfoto 2021-04-04 um 10.44.59.png
Ich hab keine anderen Systeme im Netz außer dem HomeAssistant, der ja abgeschaltet war testweise.
Diesen Backup-Cronjob hatte ich mal irgendwann nach Anleitung auf dem Pi eingerichtet.

Code: Alles auswählen

root@homematic-raspi:~# crontab -e

*/11 * * * * [ -c /dev/rtc0 ] && /sbin/hwclock --systohc --utc                                                                                                                                                             
1 */6 * * * /bin/SetInterfaceClock                                                                                                                                                                                         
0 4 * * * /usr/sbin/logrotate /etc/logrotate.conf || logger -p error -t "logrotate" "logrotate aborted with error $?"                                                                                                      
*/1 * * * * /bin/updateDCVars.tcl >/dev/null 2>/dev/null                                                                                                                                                                   
7 0 * * * /bin/nice /bin/cronBackup.sh >/dev/null 2>/dev/null                                                                                                                                                              
0 3 * * 0 [ ! -e /etc/config/NoFSTRIM ] && /bin/nice /sbin/fstrim --all --quiet >/dev/null 2>/dev/null                                                                                                                     
0 2 * * * [ ! -e /etc/config/NoBadBlocksCheck ] && /bin/nice /bin/checkBadBlocks.sh >/dev/null 2>/dev/null                                                                                                                 
*/10 * * * * [ -d /media/usb0/measurement ] && /bin/nice /usr/bin/rsync -aogX --delete-after --no-whole-file --checksum /tmp/measurement/ /media/usb0/measurement/ >/dev/null 2>/dev/null                                  
0 1 * * * /usr/local/addons/makeBackup.sh > /var/log/backup.log                                                                                                                                                            
*/5 * * * * /usr/local/addons/mediola/bin/watchdog       
Vor allem dieser mediola cronjob - wo kommt der denn her ?? Was ist mediola ? Ich benutze eigentlich nichts davon.. glaube ich.

Hier der Cronjob, der auf der Synology das Backup erstellt. Platz sollte kein Problem darstellen.

Code: Alles auswählen

echo "Mounte Dateisystem"
mount -t cifs -o username=*****,password=***** //192.168.0.136/Backups/Raspmatic /mnt
echo "Erstelle Backup"
/usr/local/addons/cuxd/extra/ccu_backup
echo "Kopiere Backup"
cp /var/tmp/*.sbk /mnt
echo "Loesche lokale alte Backups lokal"
rm -rf /var/tmp/*.sbk
echo "Loesche lokale alte Backups auf mount"
find /mnt -name "*.sbk" -mtime +30 -exec rm -f {} \;
echo "Unmounte Dateisystem"
Warum die Zeitabstände zwischen den Dateien vorhanden sind, weiß ich auch nicht. Bin aber froh, dass das soweit funktioniert und ich ein Backup habe.
Ausgeschaltet war das System ganz sicher nicht. Im Gegenteil, es lief sehr zuverlässig.

Seit gestern habe ich übrigens in der Logdatei keine Auffälligkeiten mehr. Obwohl nach dem Einspielen des Backups der besagte Fehler noch mal auftrat ist jetzt Ruhe. Trotzdem ein ungutes Gefühl, wenn man nicht so genau weiß, woran es lag.

Heute Nacht hat der Job allerdings kein Backup gemacht :(

Das Mediola / NEO SERVER Addon hab ich erstmal deinstalliert und die Zeile /usr/local/addons/mediola/bin/watchdog im cronjob gelöscht.

Vielen Dank schon mal für den Hinweis.


Gruß,
Olli

Hütte
Beiträge: 702
Registriert: 08.02.2017, 11:08
Hat sich bedankt: 29 Mal
Danksagung erhalten: 70 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Hütte » 04.04.2021, 12:03

Hallo Olli,

Das Mediola AddOn (NEO Server) ist aufgrund einer Zusammenarbeit von eQ-3 und Mediola seit einiger Zeit Bestandteil der Original CCU3-FW und somit auch von RaspberryMatic. Eigentlich liegt es da erst einmal nur so rum und ist inaktiv. Und das aktiv zu nutzen, benötigst du die Zusatzsoftware "AIO Creator Neo" der Firma Mediola, mit der du Fernbedienungen für ein Handy, Tablet oder PC bauen kannst. Allerdings musst du dann zusätzliche Plugins erwerben, die je nach Menge der benutzten Plugins auf Dauer so einiges kosten.
Der Cron-Job für Mediola sollte eigenlich mit der Deinstallation des AddOns auch verschwinden.

Auch wenn du jetzt das AddOn deinstalliert hast, so wird es mit dem nächsten Update von RaspberryMatic wieder drauf sein. Ist halt so.

Das CUxD-AddOn solltest du auf jeden Fall aktualisieren, einfach drüber installieren und gut ist. Eventuell das System noch einmal neu starten.
Dann kannst du über CUxD direkt deinen Mount zur NAS anlegen. Und hier ist beschrieben, was du ganz einfach einstellen musst, damit das automatische Backup von RaspberryMatic dein Backup direkt auf die NAS schreibt. Damit kannst du dir deinen eigenen Job komplett sparen

Und nun noch zum AddOn "Programmedrucken". Die Version 1.2 ist nicht mehr kompatibel mit der aktuellen RaspberryMatic Version. Dazu musst du es erst deinstallieren, das System neu starten und danach kannst du die neue Version installieren. Danach ist unter Umständen auch noch einmal ein Neustart des Systems notwendig

Olli_HM
Beiträge: 15
Registriert: 16.01.2018, 13:14
Hat sich bedankt: 1 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Olli_HM » 04.04.2021, 12:34

Hey Hütte,
du gibst dir echt ne Menge Mühe mit mir, danke !

Also jetzt sieht das so aus:
Bildschirmfoto 2021-04-04 um 12.13.41.png
Das Mediola-Addon werde ich erst mal nicht benutzen, der HomeAssistant ist da momentan bevorzugt.

Das mit dem selbstständigen Backup wusste ich garnicht mehr, dass ich das aktiviert hatte ! Ein USB-Stick ist tatsächlich angesteckt und enthält auch Backups :D, brav jeden Tag um 0:07 erstellt. Danke an Jens Maus.
Dann kann ich den Cronjob auf die Syno auch deaktivieren.

Nach dem Neustart sind aber wieder diese Logeinträge zu sehen, die mich nervös machen. Was in aller Welt will er dort finden ?

Der Eintrag unten in der Logdatei mit dem Datum Apr 4 12:09:27 "Could not read link data " wiederholt sich immer wieder ab Zeile 616 bis 2900, also wirklich x-mal.

Im zweiten Codeschnipsel - siehe unten - geht es dann normal weiter.

Code: Alles auswählen


***** messages *****
Jan  1 01:00:10 localhost syslog.info syslogd started: BusyBox v1.33.0
Jan  1 01:00:10 localhost user.notice kernel: klogd started: BusyBox v1.33.0 (2021-03-20 10:35:15 UTC)
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Jan  1 01:00:10 localhost user.notice kernel: [    0.000000] Linux version 5.10.11 (builder@3130d89252dc) (aarch64-buildroot-linux-gnu-gcc.br_real (Buildroot -g5c0357b) 9.3.0, GNU ld (GNU Binutils) 2.35.2) #1 SMP PREEMPT Sat Mar 20 11:12:37 UTC 2021
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Machine model: Raspberry Pi 3 Model B Rev 1.2
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] efi: UEFI not found.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Reserved memory: created CMA memory pool at 0x000000003a000000, size 64 MiB
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Zone ranges:
Jan  1 01:00:10 localhost user.info kernel: [    0.000000]   DMA      [mem 0x0000000000000000-0x000000003dffffff]
Jan  1 01:00:10 localhost user.info kernel: [    0.000000]   DMA32    empty
Jan  1 01:00:10 localhost user.info kernel: [    0.000000]   Normal   empty
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Movable zone start for each node
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Early memory node ranges
Jan  1 01:00:10 localhost user.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000003dffffff]
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003dffffff]
Jan  1 01:00:10 localhost user.debug kernel: [    0.000000] On node 0 totalpages: 253952
Jan  1 01:00:10 localhost user.debug kernel: [    0.000000]   DMA zone: 3968 pages used for memmap
Jan  1 01:00:10 localhost user.debug kernel: [    0.000000]   DMA zone: 0 pages reserved
Jan  1 01:00:10 localhost user.debug kernel: [    0.000000]   DMA zone: 253952 pages, LIFO batch:63
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] percpu: Embedded 30 pages/cpu s83224 r8192 d31464 u122880
Jan  1 01:00:10 localhost user.debug kernel: [    0.000000] pcpu-alloc: s83224 r8192 d31464 u122880 alloc=30*4096
Jan  1 01:00:10 localhost user.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Detected VIPT I-cache on CPU0
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] CPU features: detected: ARM erratum 845719
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] CPU features: detected: ARM erratum 843419
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 249984
Jan  1 01:00:10 localhost user.notice kernel: [    0.000000] Kernel command line: dwc_otg.lpm_enable=0 sdhci_bcm2708.enable_llm=0 console=tty2 kgdboc=tty2 scandelay=5 root=PARTUUID=deedbeef-02 ro rootfstype=ext4 elevator=deadline fsck.repair=yes lapic rootwait rootdelay=5 consoleblank=120 logo.nologo quiet loglevel=0 net.ifnames=0 usb-storage.quirks=  coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  empty
Jan  1 01:00:10 localhost user.warn kernel: [    0.000000] Kernel parameter elevator= does not have any effect anymore.
Jan  1 01:00:10 localhost user.warn kernel: [    0.000000] Please use sysfs to set IO scheduler for individual devices.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] Memory: 909860K/1015808K available (9984K kernel code, 1688K rwdata, 3448K rodata, 3328K init, 1233K bss, 40412K reserved, 65536K cma-reserved)
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] ftrace: allocating 32389 entries in 127 pages
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] ftrace: allocated 127 pages with 7 groups
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] rcu: Preemptible hierarchical RCU implementation.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] rcu: 	RCU event tracing is enabled.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] 	Trampoline variant of Tasks RCU enabled.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] 	Rude variant of Tasks RCU enabled.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
Jan  1 01:00:10 localhost user.notice kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x3b8/0x574 with crng_init=0
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Jan  1 01:00:10 localhost user.info kernel: [    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Jan  1 01:00:10 localhost user.info kernel: [    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Jan  1 01:00:10 localhost user.info kernel: [    0.000299] Console: colour dummy device 80x25
Jan  1 01:00:10 localhost user.info kernel: [    0.000368] printk: console [tty2] enabled
Jan  1 01:00:10 localhost user.info kernel: [    0.000431] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=76800)
Jan  1 01:00:10 localhost user.info kernel: [    0.000466] pid_max: default: 32768 minimum: 301
Jan  1 01:00:10 localhost user.info kernel: [    0.000673] LSM: Security Framework initializing
Jan  1 01:00:10 localhost user.info kernel: [    0.000706] Yama: becoming mindful.
Jan  1 01:00:10 localhost user.info kernel: [    0.000985] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    0.001023] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    0.002652] Disabling memory control group subsystem
Jan  1 01:00:10 localhost user.info kernel: [    0.005460] rcu: Hierarchical SRCU implementation.
Jan  1 01:00:10 localhost user.info kernel: [    0.006622] EFI services will not be available.
Jan  1 01:00:10 localhost user.info kernel: [    0.007307] smp: Bringing up secondary CPUs ...
Jan  1 01:00:10 localhost user.info kernel: [    0.008702] Detected VIPT I-cache on CPU1
Jan  1 01:00:10 localhost user.info kernel: [    0.008789] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
Jan  1 01:00:10 localhost user.info kernel: [    0.010375] Detected VIPT I-cache on CPU2
Jan  1 01:00:10 localhost user.info kernel: [    0.010432] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
Jan  1 01:00:10 localhost user.info kernel: [    0.011965] Detected VIPT I-cache on CPU3
Jan  1 01:00:10 localhost user.info kernel: [    0.012020] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
Jan  1 01:00:10 localhost user.info kernel: [    0.012235] smp: Brought up 1 node, 4 CPUs
Jan  1 01:00:10 localhost user.info kernel: [    0.012258] SMP: Total of 4 processors activated.
Jan  1 01:00:10 localhost user.info kernel: [    0.012277] CPU features: detected: 32-bit EL0 Support
Jan  1 01:00:10 localhost user.info kernel: [    0.012295] CPU features: detected: CRC32 instructions
Jan  1 01:00:10 localhost user.info kernel: [    0.048023] CPU: All CPU(s) started at EL2
Jan  1 01:00:10 localhost user.info kernel: [    0.048128] alternatives: patching kernel code
Jan  1 01:00:10 localhost user.info kernel: [    0.049898] devtmpfs: initialized
Jan  1 01:00:10 localhost user.notice kernel: [    0.072096] Enabled cp15_barrier support
Jan  1 01:00:10 localhost user.notice kernel: [    0.072146] Enabled setend support
Jan  1 01:00:10 localhost user.info kernel: [    0.072482] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
Jan  1 01:00:10 localhost user.info kernel: [    0.072518] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    0.075815] pinctrl core: initialized pinctrl subsystem
Jan  1 01:00:10 localhost user.info kernel: [    0.077079] DMI not present or invalid.
Jan  1 01:00:10 localhost user.info kernel: [    0.077617] NET: Registered protocol family 16
Jan  1 01:00:10 localhost user.info kernel: [    0.089145] DMA: preallocated 1024 KiB GFP_KERNEL pool for atomic allocations
Jan  1 01:00:10 localhost user.info kernel: [    0.090064] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
Jan  1 01:00:10 localhost user.info kernel: [    0.091634] DMA: preallocated 1024 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
Jan  1 01:00:10 localhost user.info kernel: [    0.092512] thermal_sys: Registered thermal governor 'step_wise'
Jan  1 01:00:10 localhost user.info kernel: [    0.092854] cpuidle: using governor ladder
Jan  1 01:00:10 localhost user.info kernel: [    0.092930] cpuidle: using governor menu
Jan  1 01:00:10 localhost user.info kernel: [    0.093855] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
Jan  1 01:00:10 localhost user.info kernel: [    0.094116] ASID allocator initialised with 65536 entries
Jan  1 01:00:10 localhost user.info kernel: [    0.122542] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Jan  1 01:00:10 localhost user.info kernel: [    0.128582] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-01-27T22:26:53, variant start
Jan  1 01:00:10 localhost user.info kernel: [    0.132597] raspberrypi-firmware soc:firmware: Firmware hash is 99d9a48302e4553cff3688692bb7e9ac760a03fa
Jan  1 01:00:10 localhost user.info kernel: [    0.178355] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Jan  1 01:00:10 localhost user.notice kernel: [    0.181626] SCSI subsystem initialized
Jan  1 01:00:10 localhost user.debug kernel: [    0.181998] libata version 3.00 loaded.
Jan  1 01:00:10 localhost user.info kernel: [    0.182332] usbcore: registered new interface driver usbfs
Jan  1 01:00:10 localhost user.info kernel: [    0.182412] usbcore: registered new interface driver hub
Jan  1 01:00:10 localhost user.info kernel: [    0.182516] usbcore: registered new device driver usb
Jan  1 01:00:10 localhost user.info kernel: [    0.183742] NetLabel: Initializing
Jan  1 01:00:10 localhost user.info kernel: [    0.183759] NetLabel:  domain hash size = 128
Jan  1 01:00:10 localhost user.info kernel: [    0.183773] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
Jan  1 01:00:10 localhost user.info kernel: [    0.183900] NetLabel:  unlabeled traffic allowed by default
Jan  1 01:00:10 localhost user.info kernel: [    0.185215] clocksource: Switched to clocksource arch_sys_counter
Jan  1 01:00:10 localhost user.notice kernel: [    1.924978] VFS: Disk quotas dquot_6.6.0
Jan  1 01:00:10 localhost user.info kernel: [    1.925104] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jan  1 01:00:10 localhost user.notice kernel: [    1.925387] FS-Cache: Loaded
Jan  1 01:00:10 localhost user.info kernel: [    1.925775] CacheFiles: Loaded
Jan  1 01:00:10 localhost user.info kernel: [    1.926056] simple-framebuffer 3eaa9000.framebuffer: framebuffer at 0x3eaa9000, 0x151800 bytes, mapped to 0x(____ptrval____)
Jan  1 01:00:10 localhost user.info kernel: [    1.926080] simple-framebuffer 3eaa9000.framebuffer: format=a8r8g8b8, mode=720x480x32, linelength=2880
Jan  1 01:00:10 localhost user.info kernel: [    1.926638] Console: switching to colour frame buffer device 90x30
Jan  1 01:00:10 localhost user.info kernel: [    1.932454] simple-framebuffer 3eaa9000.framebuffer: fb0: simplefb registered!
Jan  1 01:00:10 localhost user.info kernel: [    1.947291] NET: Registered protocol family 2
Jan  1 01:00:10 localhost user.info kernel: [    1.948460] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    1.948513] TCP established hash table entries: 8192 (order: 4, 65536 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    1.948780] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    1.948985] TCP: Hash tables configured (established 8192 bind 8192)
Jan  1 01:00:10 localhost user.info kernel: [    1.949355] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    1.949417] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Jan  1 01:00:10 localhost user.info kernel: [    1.949872] NET: Registered protocol family 1
Jan  1 01:00:10 localhost user.info kernel: [    1.951016] RPC: Registered named UNIX socket transport module.
Jan  1 01:00:10 localhost user.info kernel: [    1.951033] RPC: Registered udp transport module.
Jan  1 01:00:10 localhost user.info kernel: [    1.951048] RPC: Registered tcp transport module.
Jan  1 01:00:10 localhost user.info kernel: [    1.951063] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan  1 01:00:10 localhost user.info kernel: [    1.954005] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
Jan  1 01:00:10 localhost user.notice kernel: [    1.959303] Initialise system trusted keyrings
Jan  1 01:00:10 localhost user.info kernel: [    1.959812] workingset: timestamp_bits=46 max_order=18 bucket_order=0
Jan  1 01:00:10 localhost user.info kernel: [    1.970265] zbud: loaded
Jan  1 01:00:10 localhost user.notice kernel: [    1.973227] FS-Cache: Netfs 'nfs' registered for caching
Jan  1 01:00:10 localhost user.notice kernel: [    1.974282] NFS: Registering the id_resolver key type
Jan  1 01:00:10 localhost user.notice kernel: [    1.974334] Key type id_resolver registered
Jan  1 01:00:10 localhost user.notice kernel: [    1.974350] Key type id_legacy registered
Jan  1 01:00:10 localhost user.info kernel: [    1.974524] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Jan  1 01:00:10 localhost user.notice kernel: [    1.976272] Key type asymmetric registered
Jan  1 01:00:10 localhost user.notice kernel: [    1.976291] Asymmetric key parser 'x509' registered
Jan  1 01:00:10 localhost user.info kernel: [    1.976359] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Jan  1 01:00:10 localhost user.info kernel: [    1.976733] io scheduler mq-deadline registered
Jan  1 01:00:10 localhost user.info kernel: [    1.976752] io scheduler kyber registered
Jan  1 01:00:10 localhost user.info kernel: [    1.987002] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Jan  1 01:00:10 localhost user.info kernel: [    1.990373] bcm2835-rng 3f104000.rng: hwrng registered
Jan  1 01:00:10 localhost user.info kernel: [    1.991012] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Jan  1 01:00:10 localhost user.info kernel: [    1.992190] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Jan  1 01:00:10 localhost user.warn kernel: [    1.992710] cacheinfo: Unable to detect cache hierarchy for CPU 0
Jan  1 01:00:10 localhost user.info kernel: [    2.010675] brd: module loaded
Jan  1 01:00:10 localhost user.info kernel: [    2.028885] loop: module loaded
Jan  1 01:00:10 localhost user.info kernel: [    2.030548] Loading iSCSI transport class v2.0-870.
Jan  1 01:00:10 localhost user.info kernel: [    2.032791] libphy: Fixed MDIO Bus: probed
Jan  1 01:00:10 localhost user.info kernel: [    2.033100] tun: Universal TUN/TAP device driver, 1.6
Jan  1 01:00:10 localhost user.info kernel: [    2.033529] usbcore: registered new interface driver lan78xx
Jan  1 01:00:10 localhost user.info kernel: [    2.033616] usbcore: registered new interface driver smsc95xx
Jan  1 01:00:10 localhost user.info kernel: [    2.033645] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jan  1 01:00:10 localhost user.warn kernel: [    2.234486] Core Release: 2.80a
Jan  1 01:00:10 localhost user.warn kernel: [    2.234508] Setting default values for core params
Jan  1 01:00:10 localhost user.warn kernel: [    2.234543] Finished setting default values for core params
Jan  1 01:00:10 localhost user.warn kernel: [    2.435009] Using Buffer DMA mode
Jan  1 01:00:10 localhost user.warn kernel: [    2.435027] Periodic Transfer Interrupt Enhancement - disabled
Jan  1 01:00:10 localhost user.warn kernel: [    2.435042] Multiprocessor Interrupt Enhancement - disabled
Jan  1 01:00:10 localhost user.warn kernel: [    2.435058] OTG VER PARAM: 0, OTG VER FLAG: 0
Jan  1 01:00:10 localhost user.warn kernel: [    2.435079] Dedicated Tx FIFOs mode
Jan  1 01:00:10 localhost user.warn kernel: [    2.439843] 
Jan  1 01:00:10 localhost user.warn kernel: [    2.439869] WARN::dwc_otg_hcd_init:1072: FIQ DMA bounce buffers: virt = ffffffc0117bb000 dma = 0x00000000fa400000 len=9024
Jan  1 01:00:10 localhost user.warn kernel: [    2.439905] FIQ FSM acceleration enabled for :
Jan  1 01:00:10 localhost user.warn kernel: [    2.439905] Non-periodic Split Transactions
Jan  1 01:00:10 localhost user.warn kernel: [    2.439905] Periodic Split Transactions
Jan  1 01:00:10 localhost user.warn kernel: [    2.439905] High-Speed Isochronous Endpoints
Jan  1 01:00:10 localhost user.warn kernel: [    2.439905] Interrupt/Control Split Transaction hack enabled
Jan  1 01:00:10 localhost user.debug kernel: [    2.439923] dwc_otg: Microframe scheduler enabled
Jan  1 01:00:10 localhost user.warn kernel: [    2.439972] 
Jan  1 01:00:10 localhost user.warn kernel: [    2.439990] WARN::hcd_init_fiq:496: MPHI regs_base at ffffffc0113c5000
Jan  1 01:00:10 localhost user.info kernel: [    2.440081] dwc_otg 3f980000.usb: DWC OTG Controller
Jan  1 01:00:10 localhost user.info kernel: [    2.440126] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Jan  1 01:00:10 localhost user.info kernel: [    2.440192] dwc_otg 3f980000.usb: irq 74, io mem 0x00000000
Jan  1 01:00:10 localhost user.warn kernel: [    2.440249] Init: Port Power? op_state=1
Jan  1 01:00:10 localhost user.warn kernel: [    2.440264] Init: Power Port (0)
Jan  1 01:00:10 localhost user.info kernel: [    2.440774] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
Jan  1 01:00:10 localhost user.info kernel: [    2.440795] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  1 01:00:10 localhost user.info kernel: [    2.440814] usb usb1: Product: DWC OTG Controller
Jan  1 01:00:10 localhost user.info kernel: [    2.440833] usb usb1: Manufacturer: Linux 5.10.11 dwc_otg_hcd
Jan  1 01:00:10 localhost user.info kernel: [    2.440851] usb usb1: SerialNumber: 3f980000.usb
Jan  1 01:00:10 localhost user.info kernel: [    2.441883] hub 1-0:1.0: USB hub found
Jan  1 01:00:10 localhost user.info kernel: [    2.441971] hub 1-0:1.0: 1 port detected
Jan  1 01:00:10 localhost user.debug kernel: [    2.443275] dwc_otg: FIQ enabled
Jan  1 01:00:10 localhost user.debug kernel: [    2.443292] dwc_otg: NAK holdoff enabled
Jan  1 01:00:10 localhost user.debug kernel: [    2.443306] dwc_otg: FIQ split-transaction FSM enabled
Jan  1 01:00:10 localhost user.debug kernel: [    2.443327] Module dwc_common_port init
Jan  1 01:00:10 localhost user.info kernel: [    2.444587] usbcore: registered new interface driver uas
Jan  1 01:00:10 localhost user.info kernel: [    2.444713] usbcore: registered new interface driver usb-storage
Jan  1 01:00:10 localhost user.info kernel: [    2.445165] mousedev: PS/2 mouse device common for all mice
Jan  1 01:00:10 localhost user.info kernel: [    2.447127] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Jan  1 01:00:10 localhost user.info kernel: [    2.451545] sdhci: Secure Digital Host Controller Interface driver
Jan  1 01:00:10 localhost user.info kernel: [    2.451565] sdhci: Copyright(c) Pierre Ossman
Jan  1 01:00:10 localhost user.info kernel: [    2.452381] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Jan  1 01:00:10 localhost user.info kernel: [    2.453567] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Jan  1 01:00:10 localhost user.info kernel: [    2.453923] sdhci-pltfm: SDHCI platform and OF driver helper
Jan  1 01:00:10 localhost user.info kernel: [    2.457586] ledtrig-cpu: registered to indicate activity on CPUs
Jan  1 01:00:10 localhost user.info kernel: [    2.457657] hid: raw HID events driver (C) Jiri Kosina
Jan  1 01:00:10 localhost user.info kernel: [    2.457799] usbcore: registered new interface driver usbhid
Jan  1 01:00:10 localhost user.info kernel: [    2.457807] usbhid: USB HID core driver
Jan  1 01:00:10 localhost user.info kernel: [    2.462176] NET: Registered protocol family 17
Jan  1 01:00:10 localhost user.notice kernel: [    2.462466] Key type dns_resolver registered
Jan  1 01:00:10 localhost user.info kernel: [    2.463192] registered taskstats version 1
Jan  1 01:00:10 localhost user.notice kernel: [    2.463210] Loading compiled-in X.509 certificates
Jan  1 01:00:10 localhost user.info kernel: [    2.476979] 3f215040.serial: ttyS0 at MMIO 0x3f215040 (irq = 71, base_baud = 31250000) is a 16550
Jan  1 01:00:10 localhost user.info kernel: [    2.477865] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Jan  1 01:00:10 localhost user.info kernel: [    2.479128] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Jan  1 01:00:10 localhost user.info kernel: [    2.479139] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Jan  1 01:00:10 localhost user.info kernel: [    2.503402] sdhost: log_buf @ (____ptrval____) (c2ec1000)
Jan  1 01:00:10 localhost user.warn kernel: [    2.523412] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Jan  1 01:00:10 localhost user.warn kernel: [    2.525105] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan  1 01:00:10 localhost user.warn kernel: [    2.526846] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Jan  1 01:00:10 localhost user.warn kernel: [    2.529876] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Jan  1 01:00:10 localhost user.info kernel: [    2.552742] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jan  1 01:00:10 localhost user.info kernel: [    2.557403] of_cfs_init
Jan  1 01:00:10 localhost user.info kernel: [    2.557462] of_cfs_init: OK
Jan  1 01:00:10 localhost user.info kernel: [    2.559043] Waiting 5 sec before mounting root device...
Jan  1 01:00:10 localhost user.notice kernel: [    2.596246] random: fast init done
Jan  1 01:00:10 localhost user.warn kernel: [    2.647231] mmc0: host does not support reading read-only switch, assuming write-enable
Jan  1 01:00:10 localhost user.warn kernel: [    2.650111] Indeed it is in host mode hprt0 = 00021501
Jan  1 01:00:10 localhost user.info kernel: [    2.662971] mmc0: new high speed SDHC card at address aaaa
Jan  1 01:00:10 localhost user.info kernel: [    2.664825] mmc1: new high speed SDIO card at address 0001
Jan  1 01:00:10 localhost user.info kernel: [    2.665842] mmcblk0: mmc0:aaaa SL16G 14.8 GiB
Jan  1 01:00:10 localhost user.info kernel: [    2.719677]  mmcblk0: p1 p2 p3
Jan  1 01:00:10 localhost user.info kernel: [    2.837329] usb 1-1: new high-speed USB device number 2 using dwc_otg
Jan  1 01:00:10 localhost user.warn kernel: [    2.837554] Indeed it is in host mode hprt0 = 00001101
Jan  1 01:00:10 localhost user.info kernel: [    3.045788] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
Jan  1 01:00:10 localhost user.info kernel: [    3.045810] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan  1 01:00:10 localhost user.info kernel: [    3.046937] hub 1-1:1.0: USB hub found
Jan  1 01:00:10 localhost user.info kernel: [    3.047104] hub 1-1:1.0: 5 ports detected
Jan  1 01:00:10 localhost user.info kernel: [    3.333302] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Jan  1 01:00:10 localhost user.info kernel: [    3.433775] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
Jan  1 01:00:10 localhost user.info kernel: [    3.433797] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan  1 01:00:10 localhost user.info kernel: [    3.436794] smsc95xx v2.0.0
Jan  1 01:00:10 localhost user.info kernel: [    3.485634] libphy: smsc95xx-mdiobus: probed
Jan  1 01:00:10 localhost user.info kernel: [    3.487175] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:8a:c0:cc
Jan  1 01:00:10 localhost user.info kernel: [    3.709295] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
Jan  1 01:00:10 localhost user.notice kernel: [    3.810038] random: crng init done
Jan  1 01:00:10 localhost user.info kernel: [    3.811204] usb 1-1.3: New USB device found, idVendor=8564, idProduct=1000, bcdDevice=11.00
Jan  1 01:00:10 localhost user.info kernel: [    3.811227] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  1 01:00:10 localhost user.info kernel: [    3.811246] usb 1-1.3: Product: Mass Storage Device
Jan  1 01:00:10 localhost user.info kernel: [    3.811265] usb 1-1.3: Manufacturer: JetFlash
Jan  1 01:00:10 localhost user.info kernel: [    3.811284] usb 1-1.3: SerialNumber: 32CRD238ERWAJF9L
Jan  1 01:00:10 localhost user.info kernel: [    3.812387] usb-storage 1-1.3:1.0: USB Mass Storage device detected
Jan  1 01:00:10 localhost user.info kernel: [    3.813490] scsi host0: usb-storage 1-1.3:1.0
Jan  1 01:00:10 localhost user.notice kernel: [    5.148909] scsi 0:0:0:0: Direct-Access     JetFlash Transcend 16GB   1100 PQ: 0 ANSI: 4
Jan  1 01:00:10 localhost user.notice kernel: [    5.150949] sd 0:0:0:0: [sda] 30818304 512-byte logical blocks: (15.8 GB/14.7 GiB)
Jan  1 01:00:10 localhost user.notice kernel: [    5.151749] sd 0:0:0:0: [sda] Write Protect is off
Jan  1 01:00:10 localhost user.debug kernel: [    5.151773] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Jan  1 01:00:10 localhost user.notice kernel: [    5.152488] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan  1 01:00:10 localhost user.info kernel: [    5.157118]  sda: sda1
Jan  1 01:00:10 localhost user.notice kernel: [    5.162127] sd 0:0:0:0: [sda] Attached SCSI removable disk
Jan  1 01:00:10 localhost user.info kernel: [    7.662007] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 01:00:10 localhost user.info kernel: [    7.662115] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jan  1 01:00:10 localhost user.info kernel: [    7.663206] devtmpfs: mounted
Jan  1 01:00:10 localhost user.info kernel: [    7.671056] Freeing unused kernel memory: 3328K
Jan  1 01:00:10 localhost user.info kernel: [    7.671198] Run /sbin/init as init process
Jan  1 01:00:10 localhost user.debug kernel: [    7.671210]   with arguments:
Jan  1 01:00:10 localhost user.debug kernel: [    7.671222]     /sbin/init
Jan  1 01:00:10 localhost user.debug kernel: [    7.671234]     lapic
Jan  1 01:00:10 localhost user.debug kernel: [    7.671245]     empty
Jan  1 01:00:10 localhost user.debug kernel: [    7.671256]   with environment:
Jan  1 01:00:10 localhost user.debug kernel: [    7.671268]     HOME=/
Jan  1 01:00:10 localhost user.debug kernel: [    7.671280]     TERM=linux
Jan  1 01:00:10 localhost user.debug kernel: [    7.671291]     kgdboc=tty2
Jan  1 01:00:10 localhost user.debug kernel: [    7.671303]     scandelay=5
Jan  1 01:00:10 localhost user.warn kernel: [    8.357655] EXT4-fs: Warning: mounting with data=journal disables delayed allocation, dioread_nolock, O_DIRECT and fast_commit support!
Jan  1 01:00:10 localhost user.info kernel: [    8.364928] EXT4-fs (mmcblk0p3): mounted filesystem with journalled data mode. Opts: data=journal
Jan  1 01:00:10 localhost user.info kernel: [    9.915611] zram: Added device: zram0
Jan  1 01:00:10 localhost user.info kernel: [    9.958922] zram0: detected capacity change from 0 to 1052327936
Jan  1 01:00:10 localhost user.info kernel: [   10.025266] Adding 1027660k swap on /dev/zram0.  Priority:75 extents:1 across:1027660k SSFS
Jan  1 01:00:10 localhost user.info kernel: [   10.105554] i2c /dev entries driver
Jan  1 01:00:10 localhost daemon.info kernel: [   10.609719] udevd[276]: starting version 3.2.9
Jan  1 01:00:10 localhost daemon.info kernel: [   10.663934] udevd[277]: starting eudev-3.2.9
Jan  1 01:00:10 localhost user.warn kernel: [   10.835688] generic_raw_uart: loading out-of-tree module taints kernel.
Jan  1 01:00:10 localhost user.info kernel: [   10.839388] pl011_raw_uart 3f201000.serial: there is not valid maps for state default
Jan  1 01:00:10 localhost user.info kernel: [   10.840968] pl011_raw_uart 3f201000.serial: No valid reset pin configured
Jan  1 01:00:10 localhost user.info kernel: [   10.841299] pl011_raw_uart 3f201000.serial: Initialized pl011 device; mapbase=0x3f201000; irq=99; clockrate=47999625
Jan  1 01:00:10 localhost user.err kernel: [   10.871289] rtc-rx8130 1-0032: Unable to read registers #28..#30
Jan  1 01:00:10 localhost user.err kernel: [   10.871309] i2c i2c-1: probing for rx8130 failed
Jan  1 01:00:10 localhost user.warn kernel: [   10.871344] rtc-rx8130: probe of 1-0032 failed with error -121
Jan  1 01:00:11 localhost user.notice kernel: [   11.084602] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Jan  1 01:00:11 localhost user.info usbmount[299]: /dev/sda does not contain a filesystem or disklabel
Jan  1 01:00:11 localhost user.notice kernel: [   11.124567] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Jan  1 01:00:11 localhost user.warn kernel: [   11.128671] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Jan  1 01:00:11 localhost user.info kernel: [   11.128699] cfg80211: failed to load regulatory.db
Jan  1 01:00:11 localhost user.debug kernel: [   11.170063] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
Jan  1 01:00:11 localhost user.err kernel: [   11.176292] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Jan  1 01:00:11 localhost user.info kernel: [   11.176539] usbcore: registered new interface driver brcmfmac
Jan  1 01:00:11 localhost user.warn kernel: [   11.199360] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
Jan  1 01:00:11 localhost user.info usbmount[325]: executing command: mount -tvfat -onoexec,nodev,noatime,nodiratime,utf8 /dev/sda1 /media/usb1
Jan  1 01:00:11 localhost user.warn kernel: [   11.261756] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Jan  1 01:00:11 localhost user.info usbmount[325]: executing command: run-parts /etc/usbmount/mount.d
Jan  1 01:00:11 localhost user.err kernel: [   11.387125] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
Jan  1 01:00:11 localhost user.err kernel: [   11.387237] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
Jan  1 01:00:11 localhost user.err kernel: [   11.388236] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f00b880.mailbox(2) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ doorbell(3) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_sim-fiq(51) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(60) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(62) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(63) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ IRQ(66) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_hcd:usb1(74) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f804000.i2c(95) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ 3f204000.spi(96) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ mmc0(98) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ mmc1(104) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ arch_timer(180) guessed as class 0
Jan  1 01:00:11 localhost daemon.debug /usr/sbin/irqbalance: IRQ arm-pmu(183) guessed as class 0
Jan  1 01:00:11 localhost user.notice rfkill: block set for type bluetooth
Jan  1 01:00:11 localhost user.info kernel: [   11.832054] Bluetooth: Core ver 2.22
Jan  1 01:00:11 localhost user.info kernel: [   11.832190] NET: Registered protocol family 31
Jan  1 01:00:11 localhost user.info kernel: [   11.832199] Bluetooth: HCI device and connection manager initialized
Jan  1 01:00:11 localhost user.info kernel: [   11.832223] Bluetooth: HCI socket layer initialized
Jan  1 01:00:11 localhost user.info kernel: [   11.832239] Bluetooth: L2CAP socket layer initialized
Jan  1 01:00:11 localhost user.info kernel: [   11.832265] Bluetooth: SCO socket layer initialized
Jan  1 01:00:11 localhost daemon.info bluetoothd[420]: Bluetooth daemon 5.55
Jan  1 01:00:11 localhost daemon.warn bluetoothd[420]: src/main.c:parse_controller_config() Key file does not have group “Controller”
Jan  1 01:00:11 localhost daemon.info bluetoothd[420]: Starting SDP server
Jan  1 01:00:11 localhost user.info kernel: [   11.900601] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Jan  1 01:00:11 localhost user.info kernel: [   11.900618] Bluetooth: BNEP filters: protocol multicast
Jan  1 01:00:11 localhost user.info kernel: [   11.900647] Bluetooth: BNEP socket layer initialized
Jan  1 01:00:11 localhost daemon.info bluetoothd[420]: Bluetooth management interface 1.18 initialized
Jan  1 01:00:11 localhost user.info kernel: [   11.995118] SMSC LAN8700 usb-001:003:01: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=usb-001:003:01, irq=POLL)
Jan  1 01:00:11 localhost user.info kernel: [   11.995475] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 01:00:12 localhost user.info kernel: [   12.010294] smsc95xx 1-1.1:1.0 eth0: Link is Down
Jan  1 01:00:14 localhost user.info kernel: [   14.046257] smsc95xx 1-1.1:1.0 eth0: Link is Up - 100Mbps/Full - flow control off
Jan  1 01:00:16 localhost syslog.info syslogd exiting
Jan  1 01:00:16 homematic-raspi syslog.info syslogd started: BusyBox v1.33.0
Jan  1 01:00:16 homematic-raspi user.notice kernel: klogd started: BusyBox v1.33.0 (2021-03-20 10:35:15 UTC)
Jan  1 01:00:16 homematic-raspi user.info kernel: [   16.555091] NET: Registered protocol family 10
Jan  1 01:00:16 homematic-raspi user.info kernel: [   16.562074] Segment Routing with IPv6
Jan  1 01:00:19 homematic-raspi user.info firewall: configuration set
Jan  1 01:00:19 homematic-raspi user.notice rfkill: block set for type wlan
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(eth0)[595]: ifplugd 0.28 initializing.
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(eth0)[595]: Using interface eth0/B8:27:EB:8A:C0:CC with driver <smsc95xx> (version: 5.10.11)
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(eth0)[595]: Using detection mode: SIOCETHTOOL
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(eth0)[595]: Initialization complete, link beat detected.
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(eth0)[595]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Jan  1 01:00:19 homematic-raspi daemon.warn ifplugd(eth0)[595]: client: ifup: interface eth0 already configured
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(eth0)[595]: Program executed successfully.
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(wlan0)[600]: ifplugd 0.28 initializing.
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(wlan0)[600]: Using interface wlan0/B8:27:EB:DF:95:99 with driver <brcmfmac> (version: 7.45.98.94)
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(wlan0)[600]: Using detection mode: IFF_RUNNING
Jan  1 01:00:19 homematic-raspi daemon.info ifplugd(wlan0)[600]: Initialization complete, link beat not detected.
Apr  4 12:08:52 homematic-raspi daemon.notice ntpdate[605]: step time server 192.168.0.1 offset +1617530906.450076 sec
Apr  4 12:08:52 homematic-raspi daemon.info chronyd[609]: chronyd version 4.0 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SIGND +ASYNCDNS -NTS -SECHASH +IPV6 -DEBUG)
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f00b880.mailbox(2) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ doorbell(3) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_sim-fiq(51) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(60) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(62) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(63) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ IRQ(66) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ dwc_otg_hcd:usb1(74) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f804000.i2c(95) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f204000.spi(96) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ mmc0(98) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ 3f201000.serial(99) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ mmc1(104) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ arch_timer(180) guessed as class 0
Apr  4 12:08:58 homematic-raspi daemon.debug /usr/sbin/irqbalance: IRQ arm-pmu(183) guessed as class 0
Apr  4 12:09:01 homematic-raspi daemon.err xinetd[694]: Unable to read included directory: /etc/config/xinetd.d [file=/etc/xinetd.conf] [line=14]
Apr  4 12:09:01 homematic-raspi daemon.crit xinetd[694]: 694 {init_services} no services. Exiting...
Apr  4 12:09:02 homematic-raspi auth.info sshd[726]: Server listening on 0.0.0.0 port 22.
Apr  4 12:09:02 homematic-raspi auth.info sshd[726]: Server listening on :: port 22.
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: write_pid /var/run/cuxd.pid [775]
Apr  4 12:09:02 homematic-raspi user.info cuxd: started cux-daemon
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: CUx-Daemon(2.5.1) on CCU(3.57.4.20210320) start PID:775
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: load paramsets(/usr/local/addons/cuxd/cuxd.ps) size:789 update(-74s):Sun Apr  4 12:07:48 2021
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: 2 device-paramset(s) loaded ok!
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: write_proxy /var/cache/cuxd_proxy.ini (775 /usr/local/addons/cuxd/ 2.5.1 3.57.4.20210320 0)
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: add interface 'CUxD'
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: write interface(1) 'BidCos-RF' to /usr/local/etc/config/InterfacesList.xml
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: write interface(2) 'VirtualDevices' to /usr/local/etc/config/InterfacesList.xml
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: write interface(3) 'HmIP-RF' to /usr/local/etc/config/InterfacesList.xml
Apr  4 12:09:02 homematic-raspi daemon.info cuxd[775]: write interface(4) 'CUxD' to /usr/local/etc/config/InterfacesList.xml
Apr  4 12:09:02 homematic-raspi user.info root: Updating RF Lan Gateway Coprocessor Firmware
Apr  4 12:09:02 homematic-raspi user.debug update-coprocessor: firmware filename is: coprocessor_update_hm_only.eq3
Apr  4 12:09:02 homematic-raspi user.info root: Updating RF Lan Gateway Firmware
Apr  4 12:09:02 homematic-raspi user.info update-lgw-firmware: No gateway found in config file /etc/config/rfd.conf
Apr  4 12:09:02 homematic-raspi user.info kernel: [   36.255217] eq3loop: created slave mmd_hmip
Apr  4 12:09:02 homematic-raspi user.info kernel: [   36.256892] eq3loop: created slave mmd_bidcos
Apr  4 12:09:04 homematic-raspi user.info kernel: [   38.421816] eq3loop: eq3loop_open_slave() mmd_bidcos
Apr  4 12:09:26 homematic-raspi user.info kernel: [   59.884179] eq3loop: eq3loop_open_slave() mmd_hmip
Apr  4 12:09:26 homematic-raspi user.info kernel: [   59.884564] eq3loop: eq3loop_close_slave() mmd_hmip
Apr  4 12:09:26 homematic-raspi user.info kernel: [   59.898096] eq3loop: eq3loop_open_slave() mmd_hmip
Apr  4 12:09:35 homematic-raspi daemon.warn cuxd[775]: process_rpc_request(127.0.0.1) - illegal XMLRPC(listDevices) request
Apr  4 12:09:39 homematic-raspi daemon.warn cuxd[775]: process_rpc_request(127.0.0.1) - illegal XMLRPC(init) request
Apr  4 10:09:43 homematic-raspi daemon.info : starting pid 1102, tty '/dev/null': '/usr/bin/monit -Ic /etc/monitrc'
Apr  4 12:09:43 homematic-raspi user.info monit[1102]: Starting Monit 5.27.2 daemon with http interface at /var/run/monit.sock
Apr  4 12:09:43 homematic-raspi user.info monit[1102]: 'homematic-raspi' Monit 5.27.2 started
Apr  4 12:09:59 homematic-raspi daemon.info chronyd[609]: Selected source 192.168.0.1
Apr  4 12:10:03 homematic-raspi user.err monit[1102]: 'hs485dEnabled' status failed (2) -- grep: /var/etc/hs485d.conf: No such file or directory
Apr  4 12:10:03 homematic-raspi user.err monit[1102]: 'hmlangwEnabled' status failed (1) -- no output
Apr  4 12:10:04 homematic-raspi user.err monit[1102]: 'hb_rf_eth-CheckEnabled' status failed (1) -- no output
Apr  4 12:10:04 homematic-raspi user.warn monit[1102]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C576A:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C576A:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","DUTY_CYCLE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: DUTY_CYCLE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","DUTY_CYCLE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085709A3E981:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085709A3E981:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C576A:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C576A:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","ERROR_CODE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ERROR_CODE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","ERROR_CODE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085709A3EE73:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085709A3EE73:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085709A3E981:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085709A3E981:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: object chn = dom.GetObject('1287'); object oOverflow = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER_OVERFLOW'); object oEnergyCounter = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER'); object oSysVarEnergyCounter = dom.GetObject('svEnergyCounter_1287_000855699C576A:7'); object oSysVarEnergyCounterOldVal = dom.GetObject('svEnergyCounterOldVal_1287'); boolean overFlowFlag = oOverflow.Value(); real devVal = oEnergyCounter.Value(); real devValMax = oEnergyCounter.ValueMax(); real oldDevVal = oSysVarEnergyCounterOldVal.Value(); real diffVal = 0.0; real sysVarVal = oSysVarEnergyCounter.Value(); integer tmp_devVal = (devVal.ToString().ToFloat() * 1000).ToInteger(); integer tmp_oldDevVal = (oldDevVal.ToString().ToFloat() * 1000).ToInteger(); if (overFlowFlag == false) { ! Normal conditions if (tmp_oldDevVal <= tmp_devVal) { diffVal = devVal - oldDevVal; } ! Device has rebooted if (tmp_oldDevVal > tmp_devVal) { diffVal = devVal; } } else { !overFlow is true
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","LOW_BAT"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: LOW_BAT"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","LOW_BAT"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D7098D9BED:6","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D7098D9BED:6","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00085709A3EE73:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00085709A3EE73:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","OPERATING_VOLTAGE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: OPERATING_VOLTAGE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","OPERATING_VOLTAGE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D8A98EFE9F:6","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D8A98EFE9F:6","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D7098D9BED:6","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D7098D9BED:6","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","OPERATING_VOLTAGE_STATUS"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: OPERATING_VOLTAGE_STATUS"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","OPERATING_VOLTAGE_STATUS"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: object chn = dom.GetObject('1398'); object oOverflow = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER_OVERFLOW'); object oEnergyCounter = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER'); object oSysVarEnergyCounter = dom.GetObject('svEnergyCounter_1398_000855699C5724:7'); object oSysVarEnergyCounterOldVal = dom.GetObject('svEnergyCounterOldVal_1398'); boolean overFlowFlag = oOverflow.Value(); real devVal = oEnergyCounter.Value(); real devValMax = oEnergyCounter.ValueMax(); real oldDevVal = oSysVarEnergyCounterOldVal.Value(); real diffVal = 0.0; real sysVarVal = oSysVarEnergyCounter.Value(); integer tmp_devVal = (devVal.ToString().ToFloat() * 1000).ToInteger(); integer tmp_oldDevVal = (oldDevVal.ToString().ToFloat() * 1000).ToInteger(); if (overFlowFlag == false) { ! Normal conditions if (tmp_oldDevVal <= tmp_devVal) { diffVal = devVal - oldDevVal; } ! Device has rebooted if (tmp_oldDevVal > tmp_devVal) { diffVal = devVal; } } else { !overFlow is true
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000858A99D877F:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000858A99D877F:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","RSSI_DEVICE"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: RSSI_DEVICE"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","RSSI_DEVICE"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D8A98EFE9F:6","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D8A98EFE9F:6","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D7098D9B66:6","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D7098D9B66:6","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","RSSI_PEER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: RSSI_PEER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","RSSI_PEER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000858A99D877F:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000858A99D877F:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: object chn = dom.GetObject('2066'); object oOverflow = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER_OVERFLOW'); object oEnergyCounter = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER'); object oSysVarEnergyCounter = dom.GetObject('svEnergyCounter_2066_000855699C5671:7'); object oSysVarEnergyCounterOldVal = dom.GetObject('svEnergyCounterOldVal_2066'); boolean overFlowFlag = oOverflow.Value(); real devVal = oEnergyCounter.Value(); real devValMax = oEnergyCounter.ValueMax(); real oldDevVal = oSysVarEnergyCounterOldVal.Value(); real diffVal = 0.0; real sysVarVal = oSysVarEnergyCounter.Value(); integer tmp_devVal = (devVal.ToString().ToFloat() * 1000).ToInteger(); integer tmp_oldDevVal = (oldDevVal.ToString().ToFloat() * 1000).ToInteger(); if (overFlowFlag == false) { ! Normal conditions if (tmp_oldDevVal <= tmp_devVal) { diffVal = devVal - oldDevVal; } ! Device has rebooted if (tmp_oldDevVal > tmp_devVal) { diffVal = devVal; } } else { !overFlow is true
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C5724:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C5724:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","SENSOR_ERROR"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SENSOR_ERROR"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","SENSOR_ERROR"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C5671:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C5671:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"0001D7098D9B66:6","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"0001D7098D9B66:6","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","UNREACH"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: UNREACH"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","UNREACH"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C5694:7","ENERGY_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C5694:7","ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi user.err rfd: HSSParameter::GetValue() id=GAS_ENERGY_COUNTER failed getting physical value.
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc_bin://127.0.0.1:32001, params: {"NEQ0861379:1","GAS_ENERGY_COUNTER"}, result: [faultCode:-1,faultString:"Failure"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1007, params: {"NEQ0861379:1","GAS_ENERGY_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C5724:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C5724:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00181709ADB3D5:1","RAIN_COUNTER"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: RAIN_COUNTER"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00181709ADB3D5:1","RAIN_COUNTER"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C5671:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C5671:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: ScriptRuntimeError: object chn = dom.GetObject('5785'); object oOverflow = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER_OVERFLOW'); object oEnergyCounter = chn.DPByControl('POWERMETER_PSM.ENERGY_COUNTER'); object oSysVarEnergyCounter = dom.GetObject('svEnergyCounter_5785_000855699C5694:7'); object oSysVarEnergyCounterOldVal = dom.GetObject('svEnergyCounterOldVal_5785'); boolean overFlowFlag = oOverflow.Value(); real devVal = oEnergyCounter.Value(); real devValMax = oEnergyCounter.ValueMax(); real oldDevVal = oSysVarEnergyCounterOldVal.Value(); real diffVal = 0.0; real sysVarVal = oSysVarEnergyCounter.Value(); integer tmp_devVal = (devVal.ToString().ToFloat() * 1000).ToInteger(); integer tmp_oldDevVal = (oldDevVal.ToString().ToFloat() * 1000).ToInteger(); if (overFlowFlag == false) { ! Normal conditions if (tmp_oldDevVal <= tmp_devVal) { diffVal = devVal - oldDevVal; } ! Device has rebooted if (tmp_oldDevVal > tmp_devVal) { diffVal = devVal; } } else { !overFlow is true
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:1","MOTION"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: MOTION"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:1","MOTION"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00181709ADB3D5:1","ILLUMINATION"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ILLUMINATION"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00181709ADB3D5:1","ILLUMINATION"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000855699C5694:7","ENERGY_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ENERGY_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000855699C5694:7","ENERGY_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000955699D3DB7:1","ILLUMINATION"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: ILLUMINATION"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000955699D3DB7:1","ILLUMINATION"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0.000000 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00181709ADB3D5:1","RAIN_COUNTER_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: RAIN_COUNTER_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00181709ADB3D5:1","RAIN_COUNTER_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00181709ADB3D5:1","SUNSHINEDURATION_OVERFLOW"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SUNSHINEDURATION_OVERFLOW"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00181709ADB3D5:1","SUNSHINEDURATION_OVERFLOW"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"00181709ADB3D5:1","SUNSHINEDURATION"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SUNSHINEDURATION"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"00181709ADB3D5:1","SUNSHINEDURATION"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
Apr  4 12:10:19 homematic-raspi daemon.info cuxd[775]: INIT 'xmlrpc_bin://127.0.0.1:31999' '3931'
Apr  4 12:10:22 homematic-raspi user.err monit[1102]: 'wlan0CheckEnabled' status failed (1) -- no output
Apr  4 12:10:22 homematic-raspi user.warn monit[1102]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Apr  4 12:10:40 homematic-raspi user.err monit[1102]: 'eMMCLifeTimeCheck' status failed (1) -- no output
Apr  4 12:11:47 homematic-raspi auth.info sshd[1436]: Accepted password for root from 192.168.0.3 port 62975 ssh2
Apr  4 12:12:13 homematic-raspi user.notice kernel: [  227.092589] FS-Cache: Netfs 'cifs' registered for caching
Apr  4 12:12:13 homematic-raspi user.notice kernel: [  227.093107] Key type cifs.spnego registered
Apr  4 12:12:13 homematic-raspi user.notice kernel: [  227.093128] Key type cifs.idmap registered
Apr  4 12:12:13 homematic-raspi user.info kernel: [  227.094839] CIFS: Attempting to mount //192.168.0.136/Backups/Raspmatic
Apr  4 12:12:13 homematic-raspi user.warn kernel: [  227.094929] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
Apr  4 12:12:13 homematic-raspi user.info kernel: [  227.173117] cryptd: max_cpu_qlen set to 1000


***** hmserver.log *****
Apr 4 12:09:11 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] @GenericFactory 
Apr 4 12:09:11 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] created instance of HMServerConfiguration with parameter(s) 
Apr 4 12:09:11 de.eq3.lib.util.dynamics.GenericFactory INFO  [main] passed 1 parameter(s), in declarative order [String] 
Apr 4 12:09:22 de.eq3.cbcs.devicedescription.ChannelTypeDescription WARN  [Thread-0] Invalid state parameter or subtype: Parameter LOCK_STATE_STATUS subtype=default 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [HMIPTRXWriterWorker] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KeyServerWorker] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [KryoPersistenceWorker] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionSubsystemHandler] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [FirmwareLoaderFileSystem] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerPersistentDataLoader] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerAdapterInitialization] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [TransactionManagementVerticle] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [BackendCommandHandler] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionAcceptHandler] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CheckDeviceExistHandler] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [IncomingHMIPFrameHandler] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceBackgroundUpdateSubsystem] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceLiveUpdateSubsystem] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [DeviceInclusionDefaultConfigurationChanger] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [CyclicSmokeDetectorAwakening] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LocalServerFirmwareUpdateInitialization] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyNotificationHandler] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyAPIWorker] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBackendNotificationHandler] (3) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyBlindLevelCorrectionHandler] (1) *worker 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: added for deployment [LegacyInitializion] (1)  
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: deploying 22 classes to Vert.x 
Apr 4 12:09:22 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: 22 VertxDeployers initialized 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.CyclicSmokeDetectorAwakening INFO  [vert.x-eventloop-thread-1] SYSTEM: CyclicSmokeDetectorAwakening Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.CheckDeviceExistHandler INFO  [vert.x-eventloop-thread-6] SYSTEM: CheckDeviceExistHandler Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBlindLevelCorrectionHandler INFO  [vert.x-worker-thread-1] SYSTEM: LegacyBlindLevelCorrectionHandler Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.TransactionSubsystemHandler INFO  [vert.x-worker-thread-2] SYSTEM: TransactionSubsystemHandler Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.DeviceInclusionDefaultConfigurationChanger INFO  [vert.x-eventloop-thread-2] SYSTEM: DeviceInclusionDefaultConfigurationChanger Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.HMIPAbstractWriterWorker INFO  [vert.x-worker-thread-0] SYSTEM: HMIPTRXWriterWorker Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of CheckDeviceExistHandler succeeded (9d9cb84b-6a7e-4c6e-80a6-a2eb2eb294b1) 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.KeyServerWorker ERROR [vert.x-worker-thread-3] Missing key server configuration parameter (Network.Key) for  mode: KEYSERVER_LOCAL 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of DeviceInclusionDefaultConfigurationChanger succeeded (f72baf0b-d0df-44e7-b4d4-a9c03b48e05c) 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of TransactionSubsystemHandler succeeded (f4d6403c-0776-443a-b4a6-374204340b37) 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of CyclicSmokeDetectorAwakening succeeded (44128e5b-250d-4829-979a-cb978720d4d8) 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyBlindLevelCorrectionHandler succeeded (b5b05284-695f-4e8c-a21d-f187859e6a52) 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of HMIPTRXWriterWorker succeeded (29b8531b-767f-4535-b795-d1d2fa3f56cb) 
Apr 4 12:09:23 de.eq3.cbcs.server.core.vertx.KeyServerWorker INFO  [vert.x-worker-thread-3] SYSTEM: KeyServerWorker Verticle or Worker started 
Apr 4 12:09:23 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of KeyServerWorker succeeded (871859ff-9935-4a6e-af82-ed506d21ac9e) 
Apr 4 12:09:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of KryoPersistenceWorker succeeded (b002f0e4-492e-4123-b75d-2be7e17f5cc3) 
Apr 4 12:09:24 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: DeviceLiveUpdateSubsystem Verticle or Worker started 
Apr 4 12:09:24 de.eq3.cbcs.server.core.otau.AbstractUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: DeviceBackgroundUpdateSubsystem Verticle or Worker started 
Apr 4 12:09:24 de.eq3.cbcs.server.core.live_otau.DeviceLiveUpdateSubsystem INFO  [vert.x-eventloop-thread-4] SYSTEM: DeviceLiveUpdateSubsystem started 
Apr 4 12:09:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceBackgroundUpdateSubsystem succeeded (ed0e47a3-5c57-440a-94eb-c71a725b5cde) 
Apr 4 12:09:24 de.eq3.cbcs.server.local.base.internal.LocalServerPersistentDataLoader INFO  [vert.x-eventloop-thread-4] SYSTEM: LocalServerPersistentDataLoader Verticle or Worker started 
Apr 4 12:09:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of LocalServerPersistentDataLoader succeeded (0f01ec18-c8c9-451a-9f56-b1cdb0fa2a09) 
Apr 4 12:09:24 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceLiveUpdateSubsystem succeeded (1b2ff160-a596-4f84-b44c-e9098b7a495c) 
Apr 4 12:09:26 de.eq3.cbcs.server.core.vertx.DeviceInclusionAcceptHandler INFO  [vert.x-eventloop-thread-7] SYSTEM: DeviceInclusionAcceptHandler Verticle or Worker started 
Apr 4 12:09:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of DeviceInclusionAcceptHandler succeeded (ebb4e4a4-02ea-454f-ac3a-25d8feebd621) 
Apr 4 12:09:26 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 4 12:09:26 de.eq3.cbcs.server.core.otau.util.FirmwareLoaderFileSystem INFO  [vert.x-worker-thread-0] SYSTEM: FirmwareLoaderFileSystem Verticle or Worker started 
Apr 4 12:09:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of FirmwareLoaderFileSystem succeeded (201a2953-5c0c-4d22-836b-179b517109df) 
Apr 4 12:09:26 de.eq3.cbcs.server.core.transaction.TransactionManagementVerticle INFO  [vert.x-eventloop-thread-2] SYSTEM: TransactionManagementVerticle Verticle or Worker started 
Apr 4 12:09:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of TransactionManagementVerticle succeeded (32f32d9d-ff78-4495-a730-3d9db9b0d06d) 
Apr 4 12:09:26 de.eq3.cbcs.server.core.vertx.IncomingHMIPFrameHandler INFO  [vert.x-eventloop-thread-4] SYSTEM: IncomingHMIPFrameHandler Verticle or Worker started 
Apr 4 12:09:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of IncomingHMIPFrameHandler succeeded (16af2b76-f8f1-4784-8d93-94c97e0cfb59) 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [vert.x-eventloop-thread-6] SYSTEM: LocalServerAdapterInitialization Verticle or Worker started 
Apr 4 12:09:26 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of LocalServerAdapterInitialization succeeded (7ed9a42c-003e-4193-9b6f-fd607e571bdb) 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter state 1: HMIP_TRX_App 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter application is already running or started 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] No NWK, try to set address ... 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to set radio address 12395411... 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set max send attempts for 3014F711A061A7D7098E2061 to 3 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Try to get application version... 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Application version 2.8.6 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Bootloader version 1.0.3 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] hmos version 1.20.3 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] MCU type: Si1002_8051 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Duty Cycle: 1.5 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] set DutyCycle limit to ffffffc8 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Set Duty Cycle Limit 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Current Security Counter: 429906441 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Update security counter to calculation: 430090198 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] TRX adapter has 56 link partners 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.HMIPTRXInitialResponseListener INFO  [Thread-6] Adapter with Access Point id 3014F711A061A7D7098E2061 initialized 
Apr 4 12:09:26 de.eq3.cbcs.server.local.base.internal.LocalServerAdapterInitialization INFO  [Thread-6] HMIPTRXInitialResponseListener said that Adapter was initialized 
Apr 4 12:09:27 de.eq3.cbcs.server.local.base.internal.LocalServerFirmwareUpdateInitialization INFO  [vert.x-eventloop-thread-0] SYSTEM: LocalServerFirmwareUpdateInitialization Verticle or Worker started 
Apr 4 12:09:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-6] SYSTEM: start of LocalServerFirmwareUpdateInitialization succeeded (a4d83b3a-9a62-4581-97bd-56def7f1bf58) 
Apr 4 12:09:27 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-3] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 4 12:09:27 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-3] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 4 12:09:27 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [vert.x-worker-thread-4] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 4 12:09:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of LegacyBackendNotificationHandler succeeded (488d4d03-4f61-4113-bec7-c61768452e4d) 
Apr 4 12:09:27 de.eq3.cbcs.server.core.vertx.BackendCommandHandler INFO  [vert.x-eventloop-thread-1] SYSTEM: BackendCommandHandler Verticle or Worker started 
Apr 4 12:09:27 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-7] SYSTEM: start of BackendCommandHandler succeeded (b138a015-5b73-4710-bf45-ff13377100fc) 
Apr 4 12:09:27 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data 
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: /etc/config/crRFD/data/linkData.conf; line: 1, column: 0]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:255)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3851)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3792)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2691)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.load(LinkUtil.java:123)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.getLinkInfo(LinkUtil.java:69)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.fillLinksOfChannel(DeviceUtil.java:2509)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getLinksOfChannel(DeviceUtil.java:2464)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getAllLinks(DeviceUtil.java:2407)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:808)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.<init>(VirtualRemoteControl.java:132)
	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.<init>(LegacyServiceHandler.java:113)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.initializeService(LegacyAPIWorker.java:24)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.start(AbstractLegacyAPIWorker.java:63)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.start(LegacyAPIWorker.java:18)
	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
... Wiederholung grob etwa 80 mal...der Zeile
Apr 4 12:09:27 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data
innerhalb von 2 Sekunden.

Code: Alles auswählen

Apr 4 12:09:28 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data 
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: /etc/config/crRFD/data/linkData.conf; line: 1, column: 0]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:255)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3851)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3792)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2691)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.load(LinkUtil.java:123)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.getLinkInfo(LinkUtil.java:69)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.fillLinksOfChannel(DeviceUtil.java:2499)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getLinksOfChannel(DeviceUtil.java:2464)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getAllLinks(DeviceUtil.java:2407)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:808)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.<init>(VirtualRemoteControl.java:132)
	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.<init>(LegacyServiceHandler.java:113)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.initializeService(LegacyAPIWorker.java:24)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.start(AbstractLegacyAPIWorker.java:63)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.start(LegacyAPIWorker.java:18)
	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Apr 4 12:09:28 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker INFO  [vert.x-worker-thread-2] SYSTEM: LegacyAPIWorker Verticle or Worker started 
Apr 4 12:09:28 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of LegacyAPIWorker succeeded (051af8fe-dcf3-43f4-b9ff-1913877f3e30) 
Apr 4 12:09:29 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyInitializion INFO  [vert.x-eventloop-thread-1] SYSTEM: LegacyInitializion Verticle or Worker started 
Apr 4 12:09:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of LegacyInitializion succeeded (c23adb87-5e15-45ed-b088-33a3befd2fea) 
Apr 4 12:09:29 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-0] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 4 12:09:30 de.eq3.cbcs.server.local.LocalServer INFO  [Thread-0] SYSTEM: Bind XML-RPC api to port 32010 
Apr 4 12:09:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxEventLoopExecuteTime: 2000000000 
Apr 4 12:09:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default BlockedThreadCheckInterval: 1000 
Apr 4 12:09:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default MaxWorkerExecuteTime: 60000000000 
Apr 4 12:09:31 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Default EventLoopPoolSize: 8 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [BackendWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DiagramRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [StorageRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [DeviceFirmwareRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [EnergyPriceRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [CouplingRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [RegaClientWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [GroupConfigurationPersistenceFileSystem] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [HmIPGatewayManagementRequestWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [AccessPointUpdateServerWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: added for deployment [AccessPointUpdateLoaderWorker] (1) *worker 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: deploying 12 classes to Vert.x 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: 12 VertxDeployers initialized 
Apr 4 12:09:31 de.eq3.ccu.hmip.accesspoint.update.AccessPointUpdateLoaderWorker INFO  [vert.x-worker-thread-6] SYSTEM: Firmware update directory is set to /etc/config/firmware 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-1] SYSTEM: start of AccessPointUpdateLoaderWorker succeeded (0ba0ae17-40d6-4031-acc1-63bade558f85) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of BackendWorker succeeded (4a50a23b-caa2-4290-bef3-544b83971ee9) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of GroupConfigurationPersistenceFileSystem succeeded (b40edeab-c5c6-4e21-aaa5-141606248338) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of EnergyPriceRequestWorker succeeded (24059e3a-6a70-496c-9375-06418abb8c89) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of RegaClientWorker succeeded (6f9f0b13-5ce4-48f7-add7-07fc6815505d) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of CouplingRequestWorker succeeded (68bd8675-59dc-427f-8854-f1c810b36ef3) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-3] SYSTEM: start of AccessPointUpdateServerWorker succeeded (4ea97fc3-91a6-4c71-839b-fcad53ab4d3c) 
Apr 4 12:09:31 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-5] SYSTEM: start of StorageRequestWorker succeeded (7dfd63a1-3eac-4143-b151-6be276dac568) 
Apr 4 12:09:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of GroupRequestWorker succeeded (5396e6e4-d2ef-48d6-a785-da8ad85b3acc) 
Apr 4 12:09:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-0] SYSTEM: start of DiagramRequestWorker succeeded (374c5f5e-f1da-4aec-a484-00af9b050c39) 
Apr 4 12:09:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-4] SYSTEM: start of DeviceFirmwareRequestWorker succeeded (39a8bd2a-bc5c-48d9-82b0-266d9e2dbbd8) 
Apr 4 12:09:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [vert.x-eventloop-thread-2] SYSTEM: start of HmIPGatewayManagementRequestWorker succeeded (bb5468dd-98dd-4aed-84a8-4bcb803a4d3f) 
Apr 4 12:09:32 de.eq3.cbcs.vertx.management.VertxManager INFO  [Thread-1] SYSTEM: initial deployment complete _____________________________________________________ 
Apr 4 12:09:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer at 127.0.0.1:39292 
Apr 4 12:09:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Read Configuration 
Apr 4 12:09:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create Bidcos Dispatcher 
Apr 4 12:09:32 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] InitBidCosCache 
Apr 4 12:09:35 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create groupDefinitionProvider 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHolder 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create VirtualDeviceHandlerRega 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupAdministrationService 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceDispatcher 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create GroupDeviceHandler 
Apr 4 12:09:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] @GroupDeviceHandler - initializing... 
Apr 4 12:09:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created groupDeviceDispatcher (GroupDeviceService to BidCoS (via Dispatcher)) 
Apr 4 12:09:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> created virtualDeviceHandler (GroupDeviceService to ReGa) 
Apr 4 12:09:36 de.eq3.ccu.groupdevice.service.GroupDeviceHandler INFO  [Thread-1] --> got groupDefinitionProvider 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCosGroupMemberProvider 
Apr 4 12:09:36 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init groupAdministrationService 
Apr 4 12:09:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init Virtual OS Device 
Apr 4 12:09:37 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init ESHLight Bridge 
Apr 4 12:09:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create RrdDatalogging 
Apr 4 12:09:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create MeasurementService 
Apr 4 12:09:38 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Init MeasurementService 
Apr 4 12:09:39 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create HTTP Server 
Apr 4 12:09:39 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create BidCos context and start handler 
Apr 4 12:09:39 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Create group context and start handler 
Apr 4 12:09:39 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] (un)registerCallback on LegacyServiceHandler called from url: http://127.0.0.1:39292/bidcos 
Apr 4 12:09:39 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [HmIP-RF_java_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 4 12:09:39 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-0] init finished 
Apr 4 12:09:39 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-2] Added InterfaceId: HmIP-RF_java 
Apr 4 12:09:39 de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil INFO  [vert.x-worker-thread-2] updateDevicesForClient HmIP-RF_java -> 464 device addresses will be added 
Apr 4 12:09:39 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Checking all devices on all accesspoints for updates 
Apr 4 12:09:39 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (RF) 
Apr 4 12:09:39 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: There are 0 APs queued with updatable devices (WIRED) 
Apr 4 12:09:40 de.eq3.ccu.server.BaseHMServer INFO  [Thread-1] Starting HMServer done 
Apr 4 12:09:54 org.apache.http.impl.client.DefaultHttpClient INFO  [HmIP-RF_java_WorkerPool-1] I/O exception (java.net.SocketException) caught when processing request to {}->http://127.0.0.1:39292: Broken pipe (Write failed) 
Apr 4 12:09:54 org.apache.http.impl.client.DefaultHttpClient INFO  [HmIP-RF_java_WorkerPool-1] Retrying request to {}->http://127.0.0.1:39292 
Apr 4 12:10:09 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-2] (un)registerCallback on VirtualDeviceHandlerRega called from url: xmlrpc_bin://127.0.0.1:31999 
Apr 4 12:10:09 de.eq3.ccu.virtualdevice.service.internal.rega.VirtualDeviceHandlerRega INFO  [vert.x-eventloop-thread-2] Added InterfaceId: 1008 
Apr 4 12:10:09 de.eq3.ccu.virtualdevice.service.internal.rega.BackendWorker INFO  [vert.x-worker-thread-16] Execute BackendCommand: de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand 
Apr 4 12:10:09 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] updateDevicesForClient -> 16 device addresses will be added 
Apr 4 12:10:19 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:31999 
Apr 4 12:10:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyBackendNotificationHandler INFO  [1009_WorkerPool-0] SYSTEM: LegacyBackendNotificationHandler Verticle or Worker started 
Apr 4 12:10:19 de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler INFO  [vert.x-worker-thread-1] init finished 
Apr 4 12:10:19 de.eq3.cbcs.legacy.bidcos.rpc.internal.InterfaceInitializer INFO  [vert.x-worker-thread-1] Added InterfaceId: 1009 
Apr 4 12:10:20 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] set ready config of INT0000001 
Apr 4 12:10:20 de.eq3.ccu.virtualdevice.service.internal.rega.BackendUpdateDevicesCommand INFO  [vert.x-worker-thread-16] set ready config of INT0000002 
Apr 4 12:14:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Apr 4 12:14:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Apr 4 12:14:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 
Apr 4 12:19:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: 0 Accesspoints in Queue 
Apr 4 12:19:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Permanent-/Burstlistener Handler utilization: 0/50 used 
Apr 4 12:19:24 de.eq3.cbcs.server.core.otau.DeviceBackgroundUpdateSubsystem INFO  [vert.x-eventloop-thread-2] SYSTEM: Eventlistener Handler utilization: 0/50 used 

Hütte
Beiträge: 702
Registriert: 08.02.2017, 11:08
Hat sich bedankt: 29 Mal
Danksagung erhalten: 70 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Hütte » 04.04.2021, 13:12

Welchen Level hast du beim Logging eingestellt?

Und wenn du diese Meldungen

Code: Alles auswählen

Apr  4 12:10:09 homematic-raspi local0.warn ReGaHss: WARNING: XMLRPC 'getValue': rpcClient.isFault() failed (url: xmlrpc://127.0.0.1:32010, params: {"000F18A98C9377:0","SENSOR_ERROR"}, result: [faultCode:-5,faultString:"Unknown Parameter value for value key: SENSOR_ERROR"]) [CallXmlrpcMethod():iseXmlRpc.cpp:2608]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: XMLRPC 'getValue' call failed (interface: 1009, params: {"000F18A98C9377:0","SENSOR_ERROR"}) [CallGetValue():iseXmlRpc.cpp:1435]
Apr  4 12:10:09 homematic-raspi local0.err ReGaHss: ERROR: CallGetValue failed; sVal = 0 [ReadValue():iseDOMdpHSS.cpp:124]
meinst, die habe ich nach einem Neustart ebenso. Aber nur nach einem Neustart. Die schlagen so für ziemlich jedes Gerät auf. Wenn dort z.B. "params: {"000F18A98C9377:0","SENSOR_ERROR"}" steht, handelt es sich um ein HmIP-Gerät. "000F18A98C9377" ist die Seriennummer des Gerätes.

Aber wie gesagt, die Meldungen kommen nur einmal, nämlich nach dem Neustart.

Wenn danach alles funktioniert, dann ist doch alles gut. Man sollte sich nicht zu sehr von den ganzen Log-Einträgen nach einem Neustart verwirren lassen.

Hütte
Beiträge: 702
Registriert: 08.02.2017, 11:08
Hat sich bedankt: 29 Mal
Danksagung erhalten: 70 Mal

Re: RegaHss , Watchdog Hilfe :(

Beitrag von Hütte » 04.04.2021, 14:09

Ich glaube, jetzt weiß ich, was du meinst, nachdem ich mir noch mal die beiden Schnipzel angeschaut habe.

Code: Alles auswählen

Apr 4 12:09:28 de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil ERROR [vert.x-worker-thread-2] Could not read link data 
com.fasterxml.jackson.databind.JsonMappingException: No content to map due to end-of-input
 at [Source: /etc/config/crRFD/data/linkData.conf; line: 1, column: 0]
	at com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:255)
	at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:3851)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3792)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2691)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.load(LinkUtil.java:123)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LinkUtil.getLinkInfo(LinkUtil.java:69)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.fillLinksOfChannel(DeviceUtil.java:2499)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getLinksOfChannel(DeviceUtil.java:2464)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.DeviceUtil.getAllLinks(DeviceUtil.java:2407)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.updateLinkCache(VirtualRemoteControl.java:808)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.VirtualRemoteControl.<init>(VirtualRemoteControl.java:132)
	at de.eq3.cbcs.legacy.bidcos.rpc.LegacyServiceHandler.<init>(LegacyServiceHandler.java:113)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.initializeService(LegacyAPIWorker.java:24)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.start(AbstractLegacyAPIWorker.java:63)
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker.start(LegacyAPIWorker.java:18)
	at io.vertx.core.AbstractVerticle.start(AbstractVerticle.java:111)
	at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$8(DeploymentManager.java:434)
	at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:337)
	at io.vertx.core.impl.TaskQueue.lambda$new$0(TaskQueue.java:60)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Hier will das System die Datei "/etc/config/crRFD/data/linkData.conf" auswerten. Diese Datei enthält bei mir die Direktverknüpfungen der HmIP Geräte. Meine Direktverknüpfungen zwischen den klassischen HM-Geräten tauchen hier nicht auf.

Vermutlich ist diese Datei bei dir korrupt geworden und hat kein valides json-Format. Denn der Inhalt fängt genau mit #{"linkData":# (ohne das #) an. Schau mal in ältere Backups (einfach in .gz umbenennen und entpacken), wie sie dort aussieht.
Das Problem ist, dass Anlernen von HmIP Geräten auch Verknüpfungen automatisch angelegt werden. Kann also kompliziert werden, diese Datei zu korrigieren.

Mehr Ideen habe ich dann auch nicht mehr.

Antworten

Zurück zu „RaspberryMatic“