HMCCU Update failed

[Rewe2000]

Hallo,

ich bin mit Fhem von Raspi 3 (Buster) auf Raspi 4 (Bullseye) umgezogen, Linux und Fhem sind aktuell.

Ich beobachte nach einen "shutdown restart" folgende Meldung von der HMCCU im LOG:
2022.02.20 16:03:15 2: HMCCU [CCU2] Update success=81 failed=1


Das einzige was ich bewusst geändert habe, ich verwende bei den RPC-Servern unter ccuflags nicht mehr das "noInitialUpdate".
Dieses war in der Vergangenheit notwendig, damit Fhem mit meiner CCU3 (Raspberrymatic) ohne größere Hänger gestartet ist.
Genau seit dieser Zeit fällt mir auch die Meldung auf.

Code Auswählen Erweitern

2022.02.20 16:02:31 0: Featurelevel: 6.1
2022.02.20 16:02:31 0: Server started with 487 defined entities (fhem.pl:25704/2022-02-18 perl:5.032001 os:linux user:fhem pid:4377)
2022.02.20 16:02:31 1: Perfmon: possible freeze starting at 16:02:23, delay is 8.991
2022.02.20 16:02:31 1: CUL_HM start inital cleanup
2022.02.20 16:02:32 1: CUL_HM finished initial cleanup
2022.02.20 16:02:32 2: ModbusTCPServer_Parse: except (code 2)
2022.02.20 16:02:32 2: AttrTemplates: got 255 entries
2022.02.20 16:02:43 1: HMCCU [CCU2] Reading device config from CCU. This may take a couple of seconds ...
2022.02.20 16:02:43 2: HMCCU [CCU2] Reading Device Descriptions for interface HmIP-RF
2022.02.20 16:02:44 2: HMCCU [CCU2] Read 430 Device Descriptions for interface HmIP-RF
2022.02.20 16:02:44 2: HMCCU [CCU2] Reading Paramset Descriptions for interface HmIP-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Read 494 Paramset Descriptions for interface HmIP-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Reading Peer Descriptions for interface HmIP-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Read 49 Peer Descriptions for interface HmIP-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Reading Device Descriptions for interface BidCos-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Read 88 Device Descriptions for interface BidCos-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Reading Paramset Descriptions for interface BidCos-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Read 217 Paramset Descriptions for interface BidCos-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Reading Peer Descriptions for interface BidCos-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Read 0 Peer Descriptions for interface BidCos-RF
2022.02.20 16:02:56 2: HMCCU [CCU2] Reading Device Descriptions for interface VirtualDevices
2022.02.20 16:02:56 2: HMCCU [CCU2] Read 48 Device Descriptions for interface VirtualDevices
2022.02.20 16:02:56 2: HMCCU [CCU2] Reading Paramset Descriptions for interface VirtualDevices
2022.02.20 16:02:58 2: HMCCU [CCU2] Read 17 Paramset Descriptions for interface VirtualDevices
2022.02.20 16:02:58 2: HMCCU [CCU2] Reading Peer Descriptions for interface VirtualDevices
2022.02.20 16:02:58 2: HMCCU [CCU2] Read 0 Peer Descriptions for interface VirtualDevices
2022.02.20 16:02:58 2: HMCCU [CCU2] Read device configuration in 15 seconds: devices/channels=566 parametersets=728 links=49
2022.02.20 16:02:58 2: HMCCU [CCU2] RPC device for interface HmIP-RF: d_rpc050032HmIP_RF
2022.02.20 16:02:58 2: HMCCU [CCU2] RPC device for interface BidCos-RF: d_rpc050032BidCos_RF
2022.02.20 16:02:58 2: HMCCU [CCU2] RPC device for interface VirtualDevices: d_rpc050032VirtualDevices
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032HmIP_RF] RPC server process started for interface HmIP-RF with PID=4755
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032HmIP_RF] Initializing RPC server CB2010050033050032 for interface HmIP-RF
2022.02.20 16:02:58 1: HMCCURPCPROC [d_rpc050032HmIP_RF] RPC server starting
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] RPC server process started for interface BidCos-RF with PID=4756
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] Initializing RPC server CB2001050033050032 for interface BidCos-RF
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032HmIP_RF] Callback server CB2010050033050032 created. Listening on port 7420
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032HmIP_RF] CB2010050033050032 accepting connections. PID=4755
2022.02.20 16:02:58 1: HMCCURPCPROC [d_rpc050032BidCos_RF] RPC server starting
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] RPC server process started for interface VirtualDevices with PID=4757
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] Initializing RPC server CB9292050033050032 for interface VirtualDevices
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] Callback server CB2001050033050032 created. Listening on port 7411
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] CB2001050033050032 accepting connections. PID=4756
2022.02.20 16:02:58 1: HMCCURPCPROC [d_rpc050032VirtualDevices] RPC server starting
2022.02.20 16:02:58 2: HMCCU [CCU2] RPC server start: 3 started, 0 already running, 0 failed to start
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032HmIP_RF] RPC server CB2010050033050032 enters server loop
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032HmIP_RF] Registering callback http://192.168.50.33:7420/fh2010 of type A with ID CB2010050033050032 at http://192.168.50.32:2010
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] Callback server CB9292050033050032 created. Listening on port 14702
2022.02.20 16:02:58 1: HMCCURPCPROC [d_rpc050032HmIP_RF] RPC server CB2010050033050032 running
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] CB9292050033050032 accepting connections. PID=4757
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] RPC server CB2001050033050032 enters server loop
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] Registering callback http://192.168.50.33:7411/fh2001 of type A with ID CB2001050033050032 at http://192.168.50.32:2001
2022.02.20 16:02:58 1: HMCCURPCPROC [d_rpc050032BidCos_RF] RPC server CB2001050033050032 running
2022.02.20 16:02:58 1: HMCCURPCPROC [d_rpc050032BidCos_RF] Scheduled CCU ping every 300 seconds
2022.02.20 16:02:58 1: Perfmon: possible freeze starting at 16:02:44, delay is 14.678
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032BidCos_RF] CB2001050033050032 NewDevice received 88 device and channel specifications
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] RPC server CB9292050033050032 enters server loop
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] Registering callback http://192.168.50.33:14702/fh9292 of type A with ID CB9292050033050032 at http://192.168.50.32:9292/groups
2022.02.20 16:02:58 2: HMCCURPCPROC [d_rpc050032VirtualDevices] CB9292050033050032 NewDevice received 48 device and channel specifications
2022.02.20 16:02:59 2: HMCCURPCPROC [d_rpc050032HmIP_RF] CB2010050033050032 NewDevice received 430 device and channel specifications
2022.02.20 16:03:08 1: HMCCURPCPROC [d_rpc050032VirtualDevices] RPC server CB9292050033050032 running
2022.02.20 16:03:08 1: HMCCU [CCU2] All RPC servers running
2022.02.20 16:03:08 2: HMCCU [CCU2] Updating 82 of 82 client devices matching devexp=.* filter=ccudevstate=active,ccuif=VirtualDevices|HmIP-RF|BidCos-RF
2022.02.20 16:03:09 1: Perfmon: possible freeze starting at 16:02:59, delay is 10.017
2022.02.20 16:03:15 2: HMCCU [CCU2] Update success=81 failed=1
2022.02.20 16:03:15 1: Perfmon: possible freeze starting at 16:03:10, delay is 5.145
2022.02.20 16:07:22 1: PERL WARNING: Use of uninitialized value in subroutine entry at ./FHEM/93_DbRep.pm line 4839.

Ich stelle aktuell keinerlei Fehler oder Abweichungen fest, mich irritiert nur die Meldung beim Start.
Irgendein Device scheint da Probleme beim Update mit der Raspberrymatic zu haben.

Habt ihr eine Idee/Tipp woher die kommen könnte.

Gruß Reinhard

[zap]

Ich werde das Logging eerweitern, damit das Gerät in so einem Fall identifziert werden kann.