LXCCU 2.9.12 - LXCCU: 1.7-2 Rasbian 7 Tage Phänomen

Fragen, Support etc.

Moderator: Co-Administratoren

Antworten
svenp
Beiträge: 630
Registriert: 11.12.2012, 14:24
Hat sich bedankt: 3 Mal
Danksagung erhalten: 4 Mal

LXCCU 2.9.12 - LXCCU: 1.7-2 Rasbian 7 Tage Phänomen

Beitrag von svenp » 30.08.2014, 07:44

Hallo, ich habe seit dem ich vor ein paar Wochen von der CCU1 auf Rasbian LXCCU umgestellt habe immer ziemlich genau nach 7 Tagen das Problem das LXCCU nicht mehr wie gewünscht funktioniert.

Vor genau 7 Tagen habe ich nun den Rasbian per apt-get update && apt-get upgrade auf den aktuellen Stand gebracht.
Gestern Abend fuhr dann der Terrassen Rolladen nicht mehr herunter da der Fensterkontakt nicht mehr zur Anlage funken konnte (Nach Betätigung ist die LED lange gelb (**Edit sollte natürlich gelb und nicht grün heißen) bis sie dann kurz Rot leuchtet).
Der Rolladen ist so eingestellt das er nur herunterfahren soll wenn die Terrassentür geschlossen ist.

Heute Morgen habe ich dann also die lxccu auf der Rasbian Console mit

lxc-stop --name lxccu
lxc-start --name lxccu

neu gestartet.

Nun habe ich bei vielen Geräten (Rauchmelder und Rolladen Aktoren) die Meldung Gerätekommunikation gestört.
Die Kontakte können nun wieder die Anlage erreichen.

Was ich merkwürdig finde ist das die Fehler ziemlich genau nach 7 Tagen auftauchen und ich das immer daran merke das die Kontake nicht mehr wie gewünscht funktionieren.

Vor dem Update zeigte mir Top immer einen sehr hohen Load an (über 1.0) normal ist bei mir 0.15 - 0.30.
Jetzt nach dem Update nach 7 Tagen war der Load normal aber die Kontakte waren trotzdem gestört.

Alle Programme die bei mir laufen, laufen entweder alle 5 Minuten oder Täglich. Egal an welchem Wochentag ich den Rasbian neu gestartet habe, fingen die Fehler nach ca. 7 Tagen an.

Nach einem kompletten Reboot des Raspi geht nun kein Kontakt mehr.

Ein Rückspielen der Konfig geht jetzt meines Wissens derzeit nicht. Wass soll ich nun machen?

svenp
Beiträge: 630
Registriert: 11.12.2012, 14:24
Hat sich bedankt: 3 Mal
Danksagung erhalten: 4 Mal

Re: LXCCU 2.9.12 - LXCCU: 1.7-2 Rasbian 7 Tage Phänomen

Beitrag von svenp » 30.08.2014, 10:49

Hier noch das Logfile auf lxccu.

Code: Alles auswählen

Aug 30 09:26:57 homematic-ccu2 syslog.info syslogd started: BusyBox v1.20.2
Aug 30 09:26:57 homematic-ccu2 user.notice kernel: klogd started: BusyBox v1.20.2 (2014-07-24 11:30:57 CEST)
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'dialout' unknown
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'kmem' unknown
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'video' unknown
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'lp' unknown
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'floppy' unknown
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'cdrom' unknown
Aug 30 07:26:57 homematic-ccu2 daemon.err udevd[48]: specified group 'tape' unknown
Aug 30 07:26:59 homematic-ccu2 daemon.err udevd[51]: inotify_add_watch(6, /dev/mmcblk0, 10) failed: No such file or directory
Aug 30 07:26:59 homematic-ccu2 daemon.err udevd[51]: inotify_add_watch(6, /dev/mmcblk0p2, 10) failed: No such file or directory
Aug 30 07:26:59 homematic-ccu2 daemon.err udevd[50]: inotify_add_watch(6, /dev/mmcblk0p1, 10) failed: No such file or directory
Aug 30 07:27:01 homematic-ccu2 daemon.info ifplugd(eth0)[127]: ifplugd 0.28 initializing.
Aug 30 07:27:01 homematic-ccu2 daemon.info ifplugd(eth0)[127]: Using interface eth0/4A:49:43:49:79:28 with driver <veth> (version: 1.0)
Aug 30 07:27:01 homematic-ccu2 daemon.info ifplugd(eth0)[127]: Using detection mode: SIOCETHTOOL
Aug 30 07:27:01 homematic-ccu2 daemon.info ifplugd(eth0)[127]: Initialization complete, link beat detected.
Aug 30 07:27:01 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: Beep failure, disabled.
Aug 30 07:27:01 homematic-ccu2 daemon.info ifplugd(eth0)[127]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.
Aug 30 07:27:01 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: udhcpc (v1.20.2) started
Aug 30 07:27:01 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: Sending discover...
Aug 30 07:27:01 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: Sending select for 192.168.1.90...
Aug 30 07:27:01 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: Lease of 192.168.1.90 obtained, lease time 86400
Aug 30 07:27:01 homematic-ccu2 user.err : Could not read serial number
Aug 30 09:27:01 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Aug 30 09:27:01 homematic-ccu2 user.debug setclock: Sat Aug 30 09:27:01 CEST 2014
Aug 30 07:27:02 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: rm: can't remove '/var/etc/resolv.conf': No such file or directory
Aug 30 07:27:02 homematic-ccu2 auth.info sshd[200]: Server listening on 0.0.0.0 port 22.
Aug 30 07:27:02 homematic-ccu2 auth.info sshd[200]: Server listening on :: port 22.
Aug 30 07:27:02 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: udhcpc (v1.20.2) started
Aug 30 07:27:02 homematic-ccu2 user.info logger: Updating RF Lan Gateway Coprocessor Firmware
Aug 30 07:27:02 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: Sending discover...
Aug 30 07:27:02 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: Sending select for 192.168.1.90...
Aug 30 07:27:02 homematic-ccu2 daemon.warn ifplugd(eth0)[127]: client: Lease of 192.168.1.90 obtained, lease time 86400
Aug 30 07:27:02 homematic-ccu2 user.debug update-coprocessor: firmware filename is: coprocessor_update.eq3
Aug 30 07:27:02 homematic-ccu2 user.info update-coprocessor: performGatewayCoproUpdate(): updating KEQ1066775
Aug 30 07:27:02 homematic-ccu2 daemon.info ifplugd(eth0)[127]: Program executed successfully.
Aug 30 07:27:04 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.4 Serial Number: KEQ1066775
Aug 30 07:27:04 homematic-ccu2 user.err update-coprocessor: LanConnection::perror(): recv error
Aug 30 07:27:04 homematic-ccu2 user.info update-coprocessor: Lan Device Information: Protocol-Version: 1 Product-ID: eQ3-HM-LGW Firmware-Version: 1.1.4 Serial Number: KEQ1066775
Aug 30 07:27:14 homematic-ccu2 user.err update-coprocessor: Could not connect to Lan Gateway ip: 192.168.1.91.
Aug 30 07:27:14 homematic-ccu2 user.info logger: Updating RF Lan Gateway Firmware
Aug 30 07:27:14 homematic-ccu2 user.info update-lgw-firmware: LAN Gateway Firmware Update...
Aug 30 07:27:14 homematic-ccu2 user.info update-lgw-firmware: Gateway KEQ1066775
Aug 30 07:27:16 homematic-ccu2 user.info update-lgw-firmware: Gateway type is eQ3-HM-LGW-App
Aug 30 07:27:16 homematic-ccu2 user.info update-lgw-firmware: Available Firmware Version:   1.1.4
Aug 30 07:27:16 homematic-ccu2 user.info update-lgw-firmware: Lan Gateway Firmware Version: 1.1.4
Aug 30 07:27:16 homematic-ccu2 user.info update-lgw-firmware: Firmware is up to date
Aug 30 07:27:16 homematic-ccu2 user.info logger: Updating Wired Lan Gateway Firmware
Aug 30 07:27:17 homematic-ccu2 user.info update-lgw-firmware: No gateway found in config file /etc/config/hs485d.conf
Aug 30 09:28:01 homematic-ccu2 user.debug setclock: Try to get time from ntp.homematic.com
Aug 30 09:28:02 homematic-ccu2 user.debug setclock: Sat Aug 30 09:28:02 CEST 2014
Aug 30 09:28:39 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:39 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Aug 30 09:28:40 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:40 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Aug 30 09:28:41 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:41 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Aug 30 09:28:44 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:44 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Aug 30 09:28:46 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:46 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Aug 30 09:28:47 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:47 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=DIRECTION failed getting physical value.
Aug 30 09:28:49 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:49 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:28:53 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:53 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:28:54 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:54 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:28:59 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:28:59 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:29:00 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:29:00 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:29:01 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:29:01 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:29:03 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:29:03 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 09:29:06 homematic-ccu2 user.err rfd: RFPhysicalDataInterfaceCommand::GetData SendFrame failed for LEVEL_GET
Aug 30 09:29:06 homematic-ccu2 user.err rfd: HSSParameter::GetValue() id=STATE failed getting physical value.
Aug 30 07:29:32 homematic-ccu2 daemon.info init: starting pid 358, tty '/dev/tty1': '/sbin/getty -L tty1 115200 linux'
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =getValue Params = {"System:1","U_SOURCE_FAIL"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1447)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =getValue Params = {"System:1","LOWBAT"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1447)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =getValue Params = {"System:1","U_USBD_OK"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1447)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =getValue Params = {"System:1","BAT_LEVEL"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallGetValue: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1447)]
Aug 30 09:29:38 homematic-ccu2 local0.err ReGaHss: Error: IseHssDP::ReadValue: CallGetValue failed; sVal = 0.000000 [../Platform/DOM/iseDOMdpHSS.cpp (130)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","1008"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1219)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=BidCos-Wired [../Platform/RT/iseRTHss.cpp (163)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","1009"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1219)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=System [../Platform/RT/iseRTHss.cpp (163)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: XmlRpc: Error in XmlRpcClient::writeRequest: write error (error 111). [../Platform/DOM/iseXmlRpc.h (281)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallXmlrpcMethod: execute failed; method =init Params = {"xmlrpc_bin://127.0.0.1:1999","7843"} result= nil [../Platform/DOM/iseXmlRpc.cpp (2621)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: IseXmlRpc::CallInit: CallXmlrpcMethod failed [../Platform/DOM/iseXmlRpc.cpp (1219)]
Aug 30 09:29:39 homematic-ccu2 local0.err ReGaHss: Error: XmlRpcClientThread::ThreadFunction(): failed call init for interface=CUxD [../Platform/RT/iseRTHss.cpp (163)]

Auffällig ist das der Load nach dem Reboot des Raspi sehr hoch ist und der Rega Prozess ständig aktiv.

Code: Alles auswählen

top - 08:48:31 up  3:41,  1 user,  load average: 0.92, 0.77, 0.81
Tasks:  78 total,   1 running,  77 sleeping,   0 stopped,   0 zombie
%Cpu(s): 18.8 us, 21.1 sy,  0.0 ni, 55.6 id,  4.3 wa,  0.0 hi,  0.3 si,  0.0 st
KiB Mem:    448748 total,   189524 used,   259224 free,    16748 buffers
KiB Swap:   102396 total,        0 used,   102396 free,    94860 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
 6935 root      20   0 18092 9732 2728 S   2.0  2.2   1:47.61 ReGaHss
28603 root      20   0  4672 1372 1036 R   1.0  0.3   0:00.10 top
    3 root      20   0     0    0    0 S   0.3  0.0   0:20.24 ksoftirqd/0
   36 root      20   0     0    0    0 S   0.3  0.0   0:00.54 jbd2/mmcblk0p2-
13659 root      20   0     0    0    0 S   0.3  0.0   0:00.92 kworker/u2:1
28143 root      20   0  9396 3056 2452 S   0.3  0.7   0:00.50 sshd
32635 root      20   0  4936 1724 1008 S   0.3  0.4   0:14.11 lighttpd
    1 root      20   0  2148  720  616 S   0.0  0.2   0:01.72 init
    2 root      20   0     0    0    0 S   0.0  0.0   0:00.00 kthreadd
    5 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 kworker/0:0H
    7 root      rt   0     0    0    0 S   0.0  0.0   0:00.21 watchdog/0

bullshit
Beiträge: 232
Registriert: 25.03.2014, 19:06

Re: LXCCU 2.9.12 - LXCCU: 1.7-2 Rasbian 7 Tage Phänomen

Beitrag von bullshit » 24.10.2014, 01:26

Bin gerade per zufall auf diesen Post gestoßen. Alles wieder in ordnung? Ich glaube du hast dich dann eh direkt im LXCCU Thread gemeldet?!

Lg
LXCCU Installationsanleitung
LXCCU Projekt Seite
News @LXCCUTeam

Ich übernehme für alle von mir gegebenen Hinweise, Tipps und Links keine Haftung! Das Befolgen meiner Tipps ist nur für Fachkundige gedacht und erfolgt auf eigene Gefahr!

Antworten

Zurück zu „Allgemeines zur OCCU“