CCU busy

Begonnen von tagedieb, 07 Januar 2018, 21:09:04

Vorheriges Thema - Nächstes Thema

tagedieb

Hallo und Guten Abend

mir ist aufgefallen, das nach dem heutigen update meine CCU stets busy ist, und sich im Menu auch nicht neu starten lässt
im Device CCU, unter set CCU finde ich nur CCU, HMCCU und busy
Ich habe die CCU bereits neu gestartet, jedoch keine Änderung
in der FHEM log ist folgendes zusehen: (auszug aus log)
18.01.07 20:27:29 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2018.01.07 20:27:29 0: HMCCU: Child process for server CB2001 started with PID 11719
2018.01.07 20:27:29 0: CCURPC: CB2001 Creating file queue /tmp/ccuqueue_2001_1
2018.01.07 20:27:29 2: HMCCU: Create child process with timeouts 0.01 and 0.25
2018.01.07 20:27:29 0: CCURPC: Initializing RPC server CB2001
2018.01.07 20:27:29 0: HMCCU: Child process for server CB2010 started with PID 11720
2018.01.07 20:27:29 0: CCURPC: CB2010 Creating file queue /tmp/ccuqueue_2010_1
2018.01.07 20:27:29 0: CCURPC: Initializing RPC server CB2010
2018.01.07 20:27:29 0: CCURPC: Callback server created listening on port 7420
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for events
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for new devices
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for deleted devices
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for modified devices
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for replaced devices
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for readded devices
2018.01.07 20:27:29 1: CCURPC: CB2010 Adding callback for list devices
2018.01.07 20:27:29 0: CCURPC: CB2010 Entering server loop
2018.01.07 20:27:29 0: CCURPC: Callback server created listening on port 7411
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for events
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for new devices
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for deleted devices
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for modified devices
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for replaced devices
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for readded devices
2018.01.07 20:27:29 1: CCURPC: CB2001 Adding callback for list devices
2018.01.07 20:27:29 0: CCURPC: CB2001 Entering server loop
2018.01.07 20:27:29 0: RPC server(s) starting
2018.01.07 20:27:31 1: HMLAN_Parse: HMLAN3 new condition ok
2018.01.07 20:27:34 3: CUL_HM set Thermometer getConfig
2018.01.07 20:27:37 3: FB7390 device opened
2018.01.07 20:27:37 1: HMLAN_Parse: HMLAN2 new condition ok
2018.01.07 20:27:40 3: FHEM2FHEM device opened (Cubeez)
2018.01.07 20:27:41 1: HMLAN_Parse: HMLAN1 new condition ok
2018.01.07 20:27:44 1: Timeout for WOL_Ping reached, terminated process 11674
2018.01.07 20:27:44 3: BlockingCall for Computer_B was aborted
2018.01.07 20:27:44 5: [Computer_B] WOL_SetNextTimer to 900
2018.01.07 20:27:44 5: [Computer_B] removing Timer: Computer_B_ping
2018.01.07 20:27:44 5: [Computer_B] setting  Timer: Computer_B_ping 2018-01-07 20:42:44
2018.01.07 20:27:44 1: Timeout for MilightBridge_DoPing reached, terminated process 11685
2018.01.07 20:27:44 3: BlockingCall for milight was aborted
2018.01.07 20:27:45 3: CUL_HM set CUL_HM_HM_LC_Bl1PBU_FM_20B38D statusRequest
2018.01.07 20:27:45 1: Timeout for WOL_Ping reached, terminated process 11696
2018.01.07 20:27:45 3: BlockingCall for Mediastation was aborted
2018.01.07 20:27:45 0: HMCCU: Received SL event. RPC server CB2001 enters server loop
2018.01.07 20:27:45 0: HMCCU: Received SL event. RPC server CB2010 enters server loop
2018.01.07 20:27:45 3: eq3: Read callback: Error: write to http://www.eq-3.de:80 timed out
2018.01.07 20:27:45 3: FritzBox7490: write to http://192.168.1.9:80 timed out
2018.01.07 20:27:48 3: CUL_1 IT_set: ITL230 on
2018.01.07 20:27:52 3: CUL_HM set CUL_HM_HM_LC_SW1_FM_21B07F statusRequest
2018.01.07 20:27:52 1: HMCCU: Registering callback http://192.168.1.85:7411/fh2001 with ID CB2001 at http://192.168.1.92:2001/
2018.01.07 20:27:52 1: CCURPC: CB2001 ListDevices. Sending init to HMCCU
2018.01.07 20:27:52 1: HMCCU: RPC callback with URL http://192.168.1.85:7411/fh2001 initialized
2018.01.07 20:27:52 1: HMCCU: Registering callback http://192.168.1.85:7420/fh2010 with ID CB2010 at http://192.168.1.92:2010/
2018.01.07 20:27:53 1: HMCCU: RPC callback with URL http://192.168.1.85:7420/fh2010 initialized
2018.01.07 20:27:53 2: CCURPC: CB2001 NewDevice received 125 device specifications
2018.01.07 20:27:56 3: FritzBox7580: http://192.168.1.10/webservices/homeautoswitch.lua?sid=38765c62dd2beb86&switchcmd=getdevicelistinfos: empty answer received
2018.01.07 20:27:56 3: CUL_HM set CUL_HM_HM_LC_Sw1PBU_FM_209C5D statusRequest
2018.01.07 20:27:57 0: HMCCU: Received IN event. RPC server CB2001 initialized.
2018.01.07 20:27:57 2: PRESENCE (Foscam4) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:01 3: CUL_HM set Containerrelais_Sw_01 statusRequest
2018.01.07 20:28:01 2: PRESENCE (Foscam5) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:03 2: PRESENCE (NAS_Dlink) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:03 2: PRESENCE (PanasonicBlueRay) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:03 2: PRESENCE (Powerswitch) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:03 2: PRESENCE (Whiskas) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:03 1: Timeout for MilightBridge_DoPing reached, terminated process 11727
2018.01.07 20:28:03 3: BlockingCall for milight was aborted
2018.01.07 20:28:03 3: CUL_HM set Containerrelais_Sw_02 statusRequest
2018.01.07 20:28:07 2: PRESENCE (Lenovo_PC) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:08 2: PRESENCE (MediaPC_lan) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:08 3: CUL_HM set Deckenlicht_Kueche statusRequest
2018.01.07 20:28:11 3: CUL_HM set Kellerlicht_Blumenkeller_Decke statusRequest
2018.01.07 20:28:12 2: PRESENCE (Medion_Fernseher) - device could not be checked (retrying in 10 seconds): Process died prematurely
2018.01.07 20:28:12 3: CUL_HM set Kellerlicht_Blumenkeller_Wand statusRequest
2018.01.07 20:28:14 3: CUL_HM set HM_3E8429 statusRequest
2018.01.07 20:28:15 3: CUL_HM set Kaffeeautomat02 statusRequest
2018.01.07 20:28:16 1: Timeout for MilightBridge_DoPing reached, terminated process 11800
2018.01.07 20:28:16 3: BlockingCall for milight was aborted
2018.01.07 20:28:17 3: CUL_HM set Katzenkellerneon statusRequest
2018.01.07 20:28:19 3: CUL_HM set Kellerlicht_Werkstatt statusRequest
2018.01.07 20:28:20 2: PRESENCE (PingCubie2) - check returned a valid result after 1 unsuccesful retry
2018.01.07 20:28:21 3: CUL_HM set LadestationS113 statusRequest
2018.01.07 20:28:22 3: Apothekerschrank set HSV 0, 100, 14 with ramp: 0, flags:
2018.01.07 20:28:23 3: CUL_HM set Kellerlicht_Heizungskeller statusRequest
2018.01.07 20:28:25 3: CUL_HM set Flurlicht statusRequest
2018.01.07 20:28:25 2: PRESENCE (Foscam5) - check returned a valid result after 1 unsuccesful retr


list CCU: als datei im Anhang

kann mir bitte jemand helfen, meinen Fehler zu finden?

Danke im voraus

gruss tagedieb
FHEM 5.6 auf Cubitruck
CUL und Cul 868 und 2 HM LAN an Zbox
Remoteserver auf 2.Zboxi
HM-CC-RT-DN,HM-LC-Bl1PBU-FM,HM-LC-SW1-FM,HM-LC-SW4-PCB,HM-LC-Sw1PBU-FM,HM-PB-2-WM55,HM-PB-6-WM55,HM-SCI-3-FM,HM-SEC-RHS,HM-SEC-SC,HM-SEC-SC-2,HM-SEC-TIS,HM-WDS10-TH-O u.viele mehr
diverse IT Empfänger und LW3

tagedieb

Hallo noch einmal

es muss etwas mit der Configdb.pm vom update des Vortages zu tun haben, denn nachdem ich die alte datei wieder eingespielt habe, funktioniert es wieder

Vielleicht wissen die Programmierer da mehr :-[

lg Tagedieb

FHEM 5.6 auf Cubitruck
CUL und Cul 868 und 2 HM LAN an Zbox
Remoteserver auf 2.Zboxi
HM-CC-RT-DN,HM-LC-Bl1PBU-FM,HM-LC-SW1-FM,HM-LC-SW4-PCB,HM-LC-Sw1PBU-FM,HM-PB-2-WM55,HM-PB-6-WM55,HM-SCI-3-FM,HM-SEC-RHS,HM-SEC-SC,HM-SEC-SC-2,HM-SEC-TIS,HM-WDS10-TH-O u.viele mehr
diverse IT Empfänger und LW3

zap

Dann ist das vermutlich das falsche Forum
2xCCU3 mit ca. 100 Aktoren, Sensoren
Entwicklung: FHEM auf Proxmox Debian VM
Produktiv inzwischen auf Home Assistant gewechselt.
Maintainer: HMCCU, (Fully, AndroidDB)