Hallo,
ich habe vor einigen Tagen ein Update von HMCCU durchgeführt und daraufhin, wie im Wiki beschrieben, die Device neu angelegt. Da sich teilweise die Readings geändert hatten, mussten auch einige DOIF etc. angepasst werden. Das lief dann alles wieder aber seit dem gestrigen Update habe ich 3 Fehlermeldungen im LOG beim Start von FHEM und FHEM ist deutlich langsamer, bis zum blockieren (z.B. wenn ein SVG-Plot definiert wird) geworden.
Das List (bis auf die Geräte, da es sonst extrem lang geworden wäre) des HMCCU:
Internals:
CCUNum 1
Clients :HMCCUDEV:HMCCUCHN:HMCCURPCPROC:
DEF 192.168.178.26 ccudelay=180
FUUID 5e19b1b9-f33f-6b6f-f198-30445ccf8e525693
NAME myHMCCU3
NOTIFYDEV global,TYPE=(HMCCU|HMCCUDEV|HMCCUCHN)
NR 1716
NTFY_ORDER 50-myHMCCU3
RPCState running
STATE running/OK
TYPE HMCCU
ccuaddr BidCoS-RF
ccuchannels 181
ccudevices 10
ccuif BidCos-RF
ccuinterfaces BidCos-RF,HmIP-RF,VirtualDevices
ccuip 192.168.178.26
ccuname HM-RCV-50 BidCoS-RF
ccustate active
ccutype CCU2/3
config 5.0
firmware 3.59.6
host 192.168.178.26
postInit 0
prot http
version 5.0 213141800
READINGS:
2021-11-12 12:01:55 count_channels 181
2021-11-12 12:01:55 count_devices 10
2021-11-12 12:01:55 count_groups 0
2021-11-12 12:01:55 count_interfaces 3
2021-11-12 12:01:55 count_programs 0
2021-11-12 12:02:31 rpcstate running
2021-11-12 12:02:32 state OK
hmccu:
ccuDevList "HM-RCV-50#BidCoS-RF","HmIP-RCV-50#HmIP-RCV-1",Alarm-KueOst-HmIP,Alarm-KueSued-HmIP,Heiz-AZ-HmIP,Heiz-BadOG-HmIP,Heiz-Bib-HmIP,Heiz-Kue-HmIP,Heiz-WZ-HmIP,Licht-BadOG-Spiegel-HmIP
ccuSuppDevList Alarm-KueOst-HmIP,Alarm-KueSued-HmIP,Heiz-AZ-HmIP,Heiz-BadOG-HmIP,Heiz-Bib-HmIP,Heiz-Kue-HmIP,Heiz-WZ-HmIP,Licht-BadOG-Spiegel-HmIP
defaults 0
evtime 0
evtimeout 0
rpccount 0
rpcports 9292,2010,2001
updatetime 0
adr:
Alarm-KueOst-HmIP:
address 00109BE989D89B
addtype dev
valid 1
.
.
.
.
Attributes:
ccuReqTimeout 6
ccudef-attributes 9.6.0_System
ccudef-substitute AES_KEY!(0|false):off,(1|true):on;;LOWBAT,LOW_BAT!(0|false):ok,(1|true):low;;UNREACH!(0|false):alive,(1|true):dead;;MOTION!(0|false):noMotion,(1|true):motion;;DIRECTION!0:stop,1:up,2:down,3:undefined;;WORKING!0:false,1:true;;INHIBIT!(0|false):unlocked,(1|true):locked
ccuflags procrpc,nonBlocking,reconnect
cmdIcon on:general_an off:general_aus
event-min-interval 60
room 9.6.0_System
rpcinterfaces BidCos-RF,HmIP-RF
rpcserver on
stateFormat rpcstate/state
verbose 3
und die Meldungen beim Start:
2021.11.12 12:02:17.490 1: HMCCU [myHMCCU3] Reading device config from CCU. This may take a couple of seconds ...
2021.11.12 12:02:17.491 2: HMCCU [myHMCCU3] Reading Device Descriptions for interface BidCos-RF
2021.11.12 12:02:17.754 2: HMCCU [myHMCCU3] Read 52 Device Descriptions for interface BidCos-RF
2021.11.12 12:02:17.754 2: HMCCU [myHMCCU3] Reading Paramset Descriptions for interface BidCos-RF
2021.11.12 12:02:19.960 2: HMCCU [myHMCCU3] Read 52 Paramset Descriptions for interface BidCos-RF
2021.11.12 12:02:19.961 2: HMCCU [myHMCCU3] Reading Peer Descriptions for interface BidCos-RF
2021.11.12 12:02:19.973 2: HMCCU [myHMCCU3] Read 0 Peer Descriptions for interface BidCos-RF
2021.11.12 12:02:19.973 2: HMCCU [myHMCCU3] Reading Device Descriptions for interface HmIP-RF
2021.11.12 12:02:20.618 2: HMCCU [myHMCCU3] Read 139 Device Descriptions for interface HmIP-RF
2021.11.12 12:02:20.619 2: HMCCU [myHMCCU3] Reading Paramset Descriptions for interface HmIP-RF
2021.11.12 12:02:29.960 2: HMCCU [myHMCCU3] Read 79 Paramset Descriptions for interface HmIP-RF
2021.11.12 12:02:29.961 2: HMCCU [myHMCCU3] Reading Peer Descriptions for interface HmIP-RF
2021.11.12 12:02:29.992 2: HMCCU [myHMCCU3] Read 7 Peer Descriptions for interface HmIP-RF
2021.11.12 12:02:30.006 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 8483.
2021.11.12 12:02:30.025 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 3660.
2021.11.12 12:02:30.028 1: PERL WARNING: Use of uninitialized value $cd in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 7969.
2021.11.12 12:02:30.169 2: HMCCU [myHMCCU3] Read device configuration: devices/channels=191 parametersets=131 links=7
2021.11.12 12:02:30.170 2: HMCCU [myHMCCU3] RPC device for interface BidCos-RF: d_rpc178026BidCos_RF
2021.11.12 12:02:30.170 2: HMCCU [myHMCCU3] RPC device for interface HmIP-RF: d_rpc178026HmIP_RF
2021.11.12 12:02:30.184 2: HMCCURPCPROC [d_rpc178026BidCos_RF] RPC server process started for interface BidCos-RF with PID=23131
2021.11.12 12:02:30.210 2: HMCCURPCPROC [d_rpc178026BidCos_RF] Initializing RPC server CB2001178092178026 for interface BidCos-RF
2021.11.12 12:02:30.318 2: HMCCURPCPROC [d_rpc178026BidCos_RF] Callback server CB2001178092178026 created. Listening on port 7411
2021.11.12 12:02:30.321 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CB2001178092178026 accepting connections. PID=23131
2021.11.12 12:02:30.399 1: HMCCURPCPROC [d_rpc178026BidCos_RF] RPC server starting
2021.11.12 12:02:30.596 2: HMCCURPCPROC [d_rpc178026HmIP_RF] RPC server process started for interface HmIP-RF with PID=23132
2021.11.12 12:02:30.619 2: HMCCURPCPROC [d_rpc178026HmIP_RF] Initializing RPC server CB2010178092178026 for interface HmIP-RF
2021.11.12 12:02:30.700 2: HMCCURPCPROC [d_rpc178026HmIP_RF] Callback server CB2010178092178026 created. Listening on port 7420
2021.11.12 12:02:30.703 2: HMCCURPCPROC [d_rpc178026HmIP_RF] CB2010178092178026 accepting connections. PID=23132
2021.11.12 12:02:30.809 1: HMCCURPCPROC [d_rpc178026HmIP_RF] RPC server starting
2021.11.12 12:02:30.918 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F09C:SSL routines:ssl3_get_record:http request (peer: 192.168.178.92)
2021.11.12 12:02:31.038 2: HMCCURPCPROC [d_rpc178026BidCos_RF] RPC server CB2001178092178026 enters server loop
2021.11.12 12:02:31.041 2: HMCCURPCPROC [d_rpc178026BidCos_RF] Registering callback http://192.168.178.92:7411/fh2001 of type A with ID CB2001178092178026 at http://192.168.178.26:2001
2021.11.12 12:02:31.212 1: HMCCURPCPROC [d_rpc178026BidCos_RF] RPC server CB2001178092178026 running
2021.11.12 12:02:31.235 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CB2001178092178026 NewDevice received 52 device and channel specifications
2021.11.12 12:02:31.308 1: HMCCURPCPROC [d_rpc178026BidCos_RF] Scheduled CCU ping every 300 seconds
2021.11.12 12:02:31.658 2: HMCCURPCPROC [d_rpc178026HmIP_RF] RPC server CB2010178092178026 enters server loop
2021.11.12 12:02:31.659 2: HMCCURPCPROC [d_rpc178026HmIP_RF] Registering callback http://192.168.178.92:7420/fh2010 of type A with ID CB2010178092178026 at http://192.168.178.26:2010
2021.11.12 12:02:31.819 1: HMCCURPCPROC [d_rpc178026HmIP_RF] RPC server CB2010178092178026 running
2021.11.12 12:02:31.919 1: HMCCU [myHMCCU3] All RPC servers running
2021.11.12 12:02:32.030 2: HMCCU [myHMCCU3] Updating 14 of 14 client devices matching devexp=.* filter=ccudevstate=active,ccuif=HmIP-RF|BidCos-RF
2021.11.12 12:02:32.438 2: HMCCURPCPROC [d_rpc178026HmIP_RF] CB2010178092178026 NewDevice received 139 device and channel specifications
Kann da einer der Experten bitte drüberschauen, ob durch die Umstellung auf Version 5 etwas an den Attributen nicht stimmt oder ansonsten ein Konfigurationsfehler vorliegt?
Hat sonst noch jemand diese Fehlermeldung oder das Verhalten beobachtet und wie kann das verbessert werden.
Grüße Jürgen
Ergänzung: Versionsstände
88_HMCCU.pm 25212 2021-11-10 17:51:58Z zap
88_HMCCUCHN.pm 25212 2021-11-10 17:51:58Z zap
88_HMCCUDEV.pm 25212 2021-11-10 17:51:58Z zap
88_HMCCURPCPROC.pm 25212 2021-11-10 17:51:58Z zap
Die Fehlermeldungen sollten natürlich nicht sein. Da muss ich mal schauen ...
Bitte prüfe mal, wie viele FHEM Prozesse laufen. Es sollte ein Hauptprozess laufen + je ein Prozess je CCU Schnittstelle. Also bei Dir vermutlich 3 (ggf. auch mehr, wenn andere Module verwendet werden, die ebenfalls Sub-Prozesse starten (z.B. SONOS).
Hoffe der Befehl den ich verwendet habe war richtig.
pi@Raspi043BPlus:~ $ ps -ef |grep fhem
fhem 25290 1 29 13:07 ? 00:18:45 /usr/bin/perl fhem.pl fhem.cfg
fhem 25326 25290 0 13:08 ? 00:00:17 /usr/bin/perl fhem.pl fhem.cfg
fhem 25327 25290 0 13:08 ? 00:00:03 /usr/bin/perl fhem.pl fhem.cfg
pi 27414 22877 0 14:11 pts/1 00:00:00 grep --color=auto fhem
Scheinen doch 3 Prozesse zu sein.
Ansonsten bringt ein ps ax:
pi@Raspi043BPlus:~ $ ps ax
PID TTY STAT TIME COMMAND
1 ? Ss 7:47 /sbin/init
2 ? S 0:16 [kthreadd]
3 ? I< 0:00 [rcu_gp]
4 ? I< 0:00 [rcu_par_gp]
8 ? I< 0:00 [mm_percpu_wq]
9 ? S 0:00 [rcu_tasks_rude_]
10 ? S 0:00 [rcu_tasks_trace]
11 ? S 15:24 [ksoftirqd/0]
12 ? I 44:06 [rcu_sched]
13 ? S 0:00 [migration/0]
14 ? S 0:00 [cpuhp/0]
15 ? S 0:00 [cpuhp/1]
16 ? S 0:00 [migration/1]
17 ? S 1:26 [ksoftirqd/1]
20 ? S 0:00 [cpuhp/2]
21 ? S 0:00 [migration/2]
22 ? S 4:35 [ksoftirqd/2]
25 ? S 0:00 [cpuhp/3]
26 ? S 0:00 [migration/3]
27 ? S 1:03 [ksoftirqd/3]
30 ? S 0:01 [kdevtmpfs]
31 ? I< 0:00 [netns]
35 ? S 0:00 [kauditd]
36 ? S 0:13 [khungtaskd]
37 ? S 0:00 [oom_reaper]
38 ? I< 0:00 [writeback]
39 ? S 13:06 [kcompactd0]
57 ? I< 0:00 [kblockd]
58 ? I< 0:00 [blkcg_punt_bio]
59 ? S 0:00 [watchdogd]
62 ? I< 0:00 [rpciod]
63 ? I< 0:00 [kworker/u9:0]
64 ? I< 0:00 [xprtiod]
65 ? S 29:29 [kswapd0]
66 ? I< 0:00 [nfsiod]
67 ? I< 0:00 [iscsi_eh]
68 ? I< 0:00 [iscsi_destroy]
69 ? I< 0:00 [dwc_otg]
70 ? I< 0:00 [DWC Notificatio]
72 ? S< 0:00 [vchiq-slot/0]
73 ? S< 0:00 [vchiq-recy/0]
74 ? S< 0:00 [vchiq-sync/0]
75 ? I< 0:00 [zswap-shrink]
77 ? I< 0:00 [mmc_complete]
82 ? S 5:55 [jbd2/mmcblk0p2-]
83 ? I< 0:00 [ext4-rsv-conver]
85 ? I< 0:00 [ipv6_addrconf]
137 ? S 0:00 [irq/199-usb-001]
149 ? Ss 97:59 /lib/systemd/systemd-udevd
174 ? S 0:00 [vchiq-keep/0]
175 ? S< 0:00 [SMIO]
182 ? I< 0:00 [mmal-vchiq]
183 ? I< 0:00 [mmal-vchiq]
185 ? I< 0:00 [mmal-vchiq]
186 ? I< 0:00 [mmal-vchiq]
237 ? I< 0:00 [cfg80211]
245 ? I< 0:00 [brcmf_wq/mmc1:0]
246 ? S 0:00 [brcmf_wdog/mmc1]
430 ? Ssl 0:29 /usr/sbin/rsyslogd -n -iNONE
435 ? SNs 0:03 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon
437 ? Ssl 0:00 /usr/bin/lxcfs /var/lib/lxcfs/
441 ? Ss 0:37 /lib/systemd/systemd-logind
444 ? Ss 0:23 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog
447 ? Ss 1:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
449 ? Ss 66:07 avahi-daemon: running [Raspi043BPlus-11.local]
454 ? SLsl 1:30 /usr/sbin/rngd -r /dev/hwrng
458 ? Ss 0:45 /usr/sbin/cron -f
462 ? Ss 0:20 /sbin/dhclient -4 -v -i -pf /run/dhclient.br0.pid -lf /var/lib/dhcp/dhclient.br0.leases -I -df /var
463 ? Ss 1:33 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --dev
482 ? S 0:00 avahi-daemon: chroot helper
562 ? Ssl 0:38 /lib/systemd/systemd-timesyncd
606 ? Ss 7:54 /usr/sbin/nmbd --foreground --no-process-group
614 tty1 Ss+ 0:00 /sbin/agetty -o -p -- \u --noclear tty1 linux
642 ? Ss 0:02 /usr/sbin/sshd -D
681 ? Ss 0:42 /usr/sbin/smbd --foreground --no-process-group
684 ? S 0:19 /usr/sbin/smbd --foreground --no-process-group
685 ? S 0:16 /usr/sbin/smbd --foreground --no-process-group
686 ? S 0:50 /usr/sbin/smbd --foreground --no-process-group
993 ? Ss 0:00 /usr/bin/lxc-start --lxcpath /var/lib/piVCCU3 --name lxc --pidfile /var/run/pivccu3.pid --daemon
1005 ? Ss 0:00 init
1105 ? S 70:29 /bin/hss_led -l 6
1149 ? Ss 0:00 dbus-daemon --system
1179 ? S 0:05 /sbin/syslogd -n -m 0
1182 ? S 0:06 /sbin/klogd -n
1202 ? Ss 0:00 /sbin/udhcpc -b -t 100 -T 3 -S -x hostname:ccu3-webui -i eth0 -F ccu3-webui -V eQ3-CCU3 -s /bin/dhc
1272 ? S 11:30 /usr/sbin/ifplugd -i eth0 -fI -u0 -d10
1283 ? Ss 21:07 /usr/sbin/ntpd -g 192.168.178.1:123
1305 ? S 0:00 /bin/eq3configd
1312 ? S 0:00 /usr/sbin/lighttpd-angel -f /etc/lighttpd/lighttpd.conf -D
1314 ? S 0:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf -D
1319 ? S 12:51 /bin/ssdpd
1348 ? S 15:00 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf -D
1349 ? S 15:06 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf -D
1350 ? S 15:01 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf -D
1351 ? S 14:59 /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf -D
1374 ? S<l 2010:28 /bin/multimacd -f /etc/multimacd.conf -l 5
1400 ? Sl 14:15 /bin/rfd -f /etc/config/rfd.conf -l 5
1415 ? Sl 2175:59 java -Xmx128m -Dos.arch=arm -Dlog4j.configuration=file:///etc/config/log4j.xml -Dfile.encoding=ISO
1539 ? S 0:00 /bin/eq3-uds-services
1545 ? Sl 98:31 /bin/ReGaHss.community -f /etc/rega.conf -l 2
1609 ? S 0:53 /usr/sbin/crond -f -l 9
8184 ? I 0:08 [kworker/u8:0-events_unbound]
8306 ? Ssl 0:01 npm
8317 ? S 0:00 sh -c node index.js
8318 ? Sl 14:31 node index.js
14695 ? I< 0:04 [kworker/1:1H-kblockd]
14696 ? I< 0:06 [kworker/2:1H-kblockd]
17033 ? S 0:02 /usr/sbin/smbd --foreground --no-process-group
20469 ? I 0:00 [kworker/3:2-mm_percpu_wq]
21707 ? I 0:00 [kworker/0:0-events]
21874 ? I< 0:01 [kworker/0:2H-mmc_complete]
22579 ? I< 0:00 [kworker/3:0H-kblockd]
22731 ? Ss 0:02 /lib/systemd/systemd-journald
22859 ? Ss 0:00 sshd: pi [priv]
22862 ? Ss 0:00 /lib/systemd/systemd --user
22863 ? S 0:00 (sd-pam)
22876 ? R 0:00 sshd: pi@pts/1
22877 pts/1 Ss 0:00 -bash
25290 ? S 19:12 /usr/bin/perl fhem.pl fhem.cfg
25326 ? S 0:18 /usr/bin/perl fhem.pl fhem.cfg
25327 ? S 0:03 /usr/bin/perl fhem.pl fhem.cfg
26336 ? I 0:00 [kworker/3:0-events]
26634 ? I 0:00 [kworker/1:0-events_power_efficient]
26670 ? I 0:00 [kworker/2:0-mm_percpu_wq]
26772 ? I< 0:00 [kworker/1:2H]
26774 ? I< 0:00 [kworker/3:1H]
26775 ? I< 0:00 [kworker/2:0H]
27173 ? I 0:00 [kworker/1:1-events_power_efficient]
27179 ? I< 0:00 [kworker/0:1H]
27208 ? I 0:00 [kworker/0:2-events]
27214 ? I 0:00 [kworker/u8:2-events_unbound]
27215 ? I 0:00 [kworker/2:2-mm_percpu_wq]
27343 ? I 0:00 [kworker/1:2-mm_percpu_wq]
27349 ? I 0:00 [kworker/0:1-events]
27383 ? I 0:00 [kworker/2:1-mm_percpu_wq]
27448 ? S 0:00 /usr/bin/perl fhem.pl fhem.cfg
27449 ? S 0:00 ping -c 4 192.168.178.91
27450 pts/1 R+ 0:00 ps ax
Ist das so ok?
Heute ist FHEM schon 2 mal "abgestürzt". Im Log sind Bootvorgänge zu sehen, aber keine Fehlermeldungen die (für mich) auf irgendetwas hindeuten. Beim 2.ten Mal (10:54) wollte ich über den Browser auf FHEM zugreifen aber es kam keine Anzeige. Im pi mit sudo service fhem status nachgeschaut.
pi@Raspi043BPlus:~ $ sudo service fhem status
● fhem.service - FHEM Home Automation
Loaded: loaded (/etc/systemd/system/fhem.service; enabled; vendor preset: ena
Active: active (running) since Sat 2021-11-13 10:54:09 CET; 1min 19s ago
Process: 19813 ExecStart=/usr/bin/perl fhem.pl fhem.cfg (code=exited, status=0
Main PID: 19823 (perl)
Tasks: 11 (limit: 2062)
CGroup: /system.slice/fhem.service
├─19823 /usr/bin/perl fhem.pl fhem.cfg
├─19981 /usr/bin/perl fhem.pl fhem.cfg
├─19982 /usr/bin/perl fhem.pl fhem.cfg
├─19983 /usr/bin/perl fhem.pl fhem.cfg
├─19984 /usr/bin/perl fhem.pl fhem.cfg
├─19985 /usr/bin/perl fhem.pl fhem.cfg
├─19986 /usr/bin/perl fhem.pl fhem.cfg
├─20019 /usr/bin/perl fhem.pl fhem.cfg
├─20107 /usr/bin/perl fhem.pl fhem.cfg
├─20115 /usr/bin/perl fhem.pl fhem.cfg
└─20156 /usr/bin/perl fhem.pl fhem.cfg
Nov 13 10:54:08 Raspi043BPlus systemd[1]: Starting FHEM Home Automation...
Nov 13 10:54:09 Raspi043BPlus systemd[1]: Started FHEM Home Automation.
Das Log:
2021.11.13 02:47:56.681 3: CUL_HM set de_Bad_OG_Licht_Spiegel statusRequest noArg
2021.11.13 02:49:09.666 3: UWZ Unwetterzentrale: UWZ.1811 Done fetching data
2021.11.13 03:10:09.568 2: PRESENCE (Handy_Petra_LP) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.11.13 03:32:39.459 1: Including fhem.cfg
2021.11.13 03:32:39.548 3: telnetPort: port 7072 opened
2021.11.13 03:32:40.122 3: WEB: port 8083 opened
2021.11.13 03:32:40.135 3: WEBS: port 8084 opened
2021.11.13 03:32:41.702 2: Registering GEOFANCY geofancy for URL /geo...
2021.11.13 03:32:41.762 3: WEBhook: port 8088 opened
2021.11.13 03:32:42.489 2: eventTypes: loaded 9935 lines from ./log/eventTypes.txt
2021.11.13 03:32:42.539 3: Opening CUL_0 device /dev/serial/by-id/usb-busware.de_CUL868-if00
2021.11.13 03:32:42.606 3: Setting CUL_0 serial parameters to 9600,8,N,1
2021.11.13 03:32:42.716 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2021.11.13 03:32:42.721 3: CUL_0 device opened
2021.11.13 03:32:42.740 2: Switched CUL_0 rfmode to HomeMatic
2021.11.13 03:32:43.512 3: additional HM config file loaded: ./FHEM/HMConfig_SenTHPL.pm
und
2021.11.13 08:46:46.148 3: CUL_HM set FL_UG_Rolladen on noArg
2021.11.13 08:51:18.118 3: UWZ Unwetterzentrale: UWZ.1811 Done fetching data
2021.11.13 10:52:38.964 1: PERL WARNING: Use of uninitialized value in int at ./FHEM/42_SYSMON.pm line 3516.
2021.11.13 10:54:09.197 1: Including fhem.cfg
2021.11.13 10:54:09.284 3: telnetPort: port 7072 opened
2021.11.13 10:54:09.816 3: WEB: port 8083 opened
2021.11.13 10:54:09.829 3: WEBS: port 8084 opened
2021.11.13 10:54:11.500 2: Registering GEOFANCY geofancy for URL /geo...
2021.11.13 10:54:11.559 3: WEBhook: port 8088 opened
2021.11.13 10:54:12.307 2: eventTypes: loaded 9935 lines from ./log/eventTypes.txt
2021.11.13 10:54:12.358 3: Opening CUL_0 device /dev/serial/by-id/usb-busware.de_CUL868-if00
Wie ist vorzugehen, um die Fehlerursache zu finden?
Grüße Jürgen
Wird Dein FHEM automatisch neu gestartet, wenn es abstürzt? Das kann problematisch sein, denn dann werden die Subprozesse nicht beendet und einfach neue gestartet.
In Deiner "ps" Ausgabe sind allerdings keine toten Prozesse zu sehen. Jedoch in der Ausgabe von "service fhem status". Das sind viel zu viele Prozesse.
In dem fhem log gibt es folgende kritische Meldungen:
2021.11.13 03:10:09.568 2: PRESENCE (Handy_Petra_LP) - device could not be checked (retrying in 10 seconds): Process died prematurely
2021.11.13 10:52:38.964 1: PERL WARNING: Use of uninitialized value in int at ./FHEM/42_SYSMON.pm line 3516.
2021.11.12 12:02:30.918 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F09C:SSL routines:ssl3_get_record:http request (peer: 192.168.178.92)
2021.11.12 12:02:30.006 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 8483.
2021.11.12 12:02:30.025 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 3660.
2021.11.12 12:02:30.028 1: PERL WARNING: Use of uninitialized value $cd in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 7969.
Eine dieser Meldungen / Module wird dann vermutlich die Ursache für den Absturz sein, wenn nicht noch andere Meldungen im Log stehen, die Du nicht gelistet hast.
Ticket: https://github.com/zapccu/HMCCU/issues/143
Danke für die Rückmeldung.
Automatischer Start deswegen, damit das System läuft wenn ich es nicht manuell wieder starten kann. Dachte das ist die beste Lösung, wenn ein Absturz erfolgt. Wie sollte man das System denn einrichten? Es gibt ja auch die Möglichkeit, über einen Cronjob FHEM nach einer gewissen Wartezeit neu zu starten. Ist diese Lösung besser?
Ticket: Das bedeutet, mit dem nächsten Update müßte das Problem behoben sein?
Kritische Meldungen: Die SSL-Warnung bekomme ich seit einiger Zeit, habe aber keinen Ansatz wie ich das behebe.
Die vielen Prozeße im status habe ich auch das erste Mal so gesehen.
Mein Tipp: Stelle erst einmal alles auf unverschlüsselte Kommunikation um.
Also außer dieser Meldung von FHEMWEB bzgl. ssl sind alles WARNINGS. ie WARNINGS sollten FHEM nicht zum Absturz bringen.
Guck mal, ob in der Zeit etwas im /var/log/kernlog steht.
Sieht mir nach einem OOM-Killer-problem aus, d.h. dem Pi ist der Speicher ausgegangen (Ist doch ein Pi?)
FHEM läuft auf einem pi 3B Plus mit einer 64GB Speicherkarte.
Obwohl ich solch ein Log das erste Mal sehe denke ich, dass es nicht gut aussieht.
Erster Absturz:
Nov 13 03:09:29 Raspi043BPlus kernel: [9218977.522217] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:09:29 Raspi043BPlus kernel: [9218977.522228] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:09:29 Raspi043BPlus kernel: [9218977.523566] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:09:29 Raspi043BPlus kernel: [9218977.523579] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:09:29 Raspi043BPlus kernel: [9218977.523590] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:09:29 Raspi043BPlus kernel: [9218977.523601] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:16:04 Raspi043BPlus kernel: [9219497.560725] eq3loop: eq3loop_write_master() retrun error:
Nov 13 03:16:07 Raspi043BPlus kernel: [9219870.353669] usb 1-1.2: USB disconnect, device number 59
Nov 13 03:16:07 Raspi043BPlus kernel: [9219874.621636] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 13 03:16:07 Raspi043BPlus kernel: [9219874.621661] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 03:16:07 Raspi043BPlus kernel: [9219874.621676] usb 1-1.2: Product: ConBee II
Nov 13 03:16:07 Raspi043BPlus kernel: [9219874.621690] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 13 03:16:07 Raspi043BPlus kernel: [9219874.621704] usb 1-1.2: SerialNumber: DE2439922
Nov 13 03:16:07 Raspi043BPlus kernel: [9219874.622930] cdc_acm 1-1.2:1.0: ttyACM2: USB ACM device
Nov 13 03:26:06 Raspi043BPlus kernel: [9220470.998619] usb 1-1.2: new full-speed USB device number 62 using dwc_otg
Nov 13 03:26:25 Raspi043BPlus kernel: [9220471.142981] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 13 03:26:58 Raspi043BPlus kernel: [9220471.142997] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 03:27:18 Raspi043BPlus kernel: [9220471.143007] usb 1-1.2: Product: ConBee II
Nov 13 03:27:38 Raspi043BPlus kernel: [9220471.143015] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 13 03:27:59 Raspi043BPlus kernel: [9220471.143023] usb 1-1.2: SerialNumber: DE2439922
Nov 13 03:28:14 Raspi043BPlus kernel: [9220471.143919] cdc_acm 1-1.2:1.0: ttyACM2: USB ACM device
Nov 13 03:28:39 Raspi043BPlus kernel: [9220474.519681] usb 1-1.2: USB disconnect, device number 62
Nov 13 03:28:54 Raspi043BPlus kernel: [9220474.838626] usb 1-1.2: new full-speed USB device number 63 using dwc_otg
Nov 13 03:29:21 Raspi043BPlus kernel: [9220474.992985] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 13 03:29:42 Raspi043BPlus kernel: [9220474.993002] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 03:30:10 Raspi043BPlus kernel: [9220474.993012] usb 1-1.2: Product: ConBee II
Nov 13 03:30:30 Raspi043BPlus kernel: [9220474.993020] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 13 03:30:48 Raspi043BPlus kernel: [9220474.993029] usb 1-1.2: SerialNumber: DE2439922
Nov 13 03:31:07 Raspi043BPlus kernel: [9220474.993946] cdc_acm 1-1.2:1.0: ttyACM2: USB ACM device
Nov 13 03:31:07 Raspi043BPlus kernel: [9220522.681978] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:31:07 Raspi043BPlus kernel: [9220522.681989] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 03:31:07 Raspi043BPlus kernel: [9220522.682001] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Den ConbeeII nutze ich seit mehreren Wochen für zigbee2mqtt ohne Probleme.
Die Zeile
Raspi043BPlus kernel: [9218977.522228] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
steht ununterbrochen seit
Nov 12 11:56:57 Raspi043BPlus kernel: [9164724.019925] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=perl,pid=22975,uid=999
Nov 12 11:56:57 Raspi043BPlus kernel: [9164724.019985] Out of memory: Killed process 22975 (perl) total-vm:367172kB, anon-rss:342720kB, file-rss:0kB, shmem-rss:0kB, UID:999 pgtables:368kB oom_score_adj:0
Nov 12 11:56:57 Raspi043BPlus kernel: [9164724.117113] oom_reaper: reaped process 22975 (perl), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Nov 12 21:26:05 Raspi043BPlus kernel: [9198871.780271] r7:80e083c0 r6:80e05008 r5:93b4be00 r4:822e5d50
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780284] [<802b2170>] (out_of_memory) from [<803018dc>] (__alloc_pages_nodemask+0x7ec/0x1184)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780291] r7:80f2d048 r6:00001000 r5:000013fe r4:00000000
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780301] [<803010f0>] (__alloc_pages_nodemask) from [<802abde0>] (pagecache_get_page+0x10c/0x34c)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780310] r10:80f316db r9:00000009 r8:80e059e4 r7:85ac51c0 r6:00100cca r5:00000044
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780314] r4:c5f80001
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780323] [<802abcd4>] (pagecache_get_page) from [<802add40>] (filemap_fault+0x638/0xb20)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780332] r10:80e05008 r9:822e5ec8 r8:00000040 r7:84f7e840 r6:822e5ec8 r5:84f7e840
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780336] r4:85ac50b0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780348] [<802ad708>] (filemap_fault) from [<80427a9c>] (ext4_filemap_fault+0x38/0x4c)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780357] r10:822e5fb0 r9:822e5ec8 r8:00000040 r7:00000000 r6:76e4c000 r5:822e5ec8
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780361] r4:85ac5098
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780374] [<80427a64>] (ext4_filemap_fault) from [<802e4f04>] (__do_fault+0x48/0x14c)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780379] r5:84f8f180 r4:822e5ec8
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780390] [<802e4ebc>] (__do_fault) from [<802e9fc0>] (handle_mm_fault+0xae8/0xe30)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780397] r7:00000000 r6:76e4c000 r5:80e05008 r4:00000254
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780407] [<802e94d8>] (handle_mm_fault) from [<809f4258>] (do_page_fault+0x144/0x314)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780415] r10:00000254 r9:00000000 r8:939da448 r7:939da400 r6:80000007 r5:76e4c4cc
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780420] r4:822e5fb0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780430] [<809f4114>] (do_page_fault) from [<80114080>] (do_PrefetchAbort+0x48/0x9c)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780439] r10:76a80090 r9:76b14f7c r8:822e5fb0 r7:76e4c4cc r6:809f4114 r5:00000007
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780443] r4:80e0adf8
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780454] [<80114038>] (do_PrefetchAbort) from [<80101024>] (ret_from_exception+0x0/0x1c)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780460] Exception stack(0x822e5fb0 to 0x822e5ff8)
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780467] 5fa0: 01d47f78 76ae9900 6b592300 00000000
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780476] 5fc0: 01d46ab8 01d487e8 76ae9900 01d48e00 76b16990 76b14f7c 76a80090 76f46968
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780483] 5fe0: 7ebcb600 7ebcc600 76e5eb04 76e4c4cc 20000010 ffffffff
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780491] r8:10c5387d r7:10c5383d r6:ffffffff r5:20000010 r4:76e4c4cc
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780496] Mem-Info:
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780512] active_anon:32486 inactive_anon:182230 isolated_anon:0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780512] active_file:56 inactive_file:567 isolated_file:0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780512] unevictable:4 dirty:0 writeback:0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780512] slab_reclaimable:3548 slab_unreclaimable:6378
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780512] mapped:451 shmem:4317 pagetables:3349 bounce:0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780512] free:4353 free_pcp:237 free_cma:56
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780528] Node 0 active_anon:129944kB inactive_anon:728920kB active_file:224kB inactive_file:2268kB unevictable:16kB isolated(anon):0kB isolated(file):0kB mapped:1804kB dirty:0kB writeback:0kB shmem:17268kB writeback_tmp:0kB kernel_stack:2168kB all_unreclaimable? no
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780544] DMA free:17412kB min:16384kB low:20480kB high:24576kB reserved_highatomic:4096KB active_anon:129944kB inactive_anon:728920kB active_file:204kB inactive_file:2872kB unevictable:16kB writepending:0kB present:970752kB managed:946392kB mlocked:16kB pagetables:13396kB bounce:0kB free_pcp:948kB local_pcp:580kB free_cma:224kB
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780550] lowmem_reserve[]: 0 0 0
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780576] DMA: 466*4kB (UMEHC) 292*8kB (UMEHC) 87*16kB (UMEH) 52*32kB (UMEH) 10*64kB (UME) 8*128kB (UMEH) 3*256kB (EH) 2*512kB (MH) 1*1024kB (U) 1*2048kB (M) 1*4096kB (M) = 17880kB
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780703] 5918 total pagecache pages
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780713] 911 pages in swap cache
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780720] Swap cache stats: add 140463, delete 139552, find 23715257/23743931
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780726] Free swap = 0kB
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780733] Total swap = 102396kB
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780739] 242688 pages RAM
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780745] 0 pages HighMem/MovableOnly
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780751] 6090 pages reserved
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780757] 16384 pages cma reserved
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780763] Tasks state (memory values in pages):
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780770] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780796] [ 149] 0 149 4531 57 22528 157 -1000 systemd-udevd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780810] [ 430] 0 430 6378 135 22528 193 0 rsyslogd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780820] [ 435] 0 435 923 9 10240 40 0 alsactl
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780831] [ 437] 0 437 5046 0 16384 56 0 lxcfs
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780842] [ 441] 0 441 3286 50 22528 128 0 systemd-logind
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780852] [ 444] 104 444 1637 76 16384 50 -900 dbus-daemon
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780863] [ 447] 0 447 2686 12 20480 89 0 wpa_supplicant
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780874] [ 449] 108 449 1475 65 12288 38 0 avahi-daemon
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780884] [ 454] 0 454 7170 22 18432 13 0 rngd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780894] [ 458] 0 458 1987 14 18432 31 0 cron
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780906] [ 462] 0 462 1979 44 14336 176 0 dhclient
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780916] [ 463] 65534 463 1080 5 14336 39 0 thd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780927] [ 482] 108 482 1442 13 12288 50 0 avahi-daemon
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780938] [ 562] 100 562 5495 19 24576 132 0 systemd-timesyn
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780949] [ 606] 0 606 8041 61 38912 303 0 nmbd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780960] [ 614] 0 614 1077 0 12288 25 0 agetty
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780970] [ 642] 0 642 2682 16 18432 129 -1000 sshd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780981] [ 681] 0 681 12091 160 57344 332 0 smbd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.780992] [ 684] 0 684 11357 131 51200 339 0 smbd-notifyd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781002] [ 685] 0 685 11358 137 49152 336 0 cleanupd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781012] [ 686] 0 686 12088 142 51200 345 0 lpqd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781023] [ 993] 0 993 2501 0 18432 132 0 lxc-start
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781034] [ 1005] 0 1005 779 0 10240 20 0 init
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781044] [ 1105] 0 1105 1098 29 14336 16 0 hss_led
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781054] [ 1149] 1001 1149 723 1 12288 38 0 dbus-daemon
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781066] [ 1179] 0 1179 779 9 12288 10 0 syslogd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781076] [ 1182] 0 1182 779 11 10240 14 0 klogd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781086] [ 1202] 0 1202 779 6 10240 18 0 udhcpc
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781098] [ 1272] 0 1272 456 6 8192 16 0 ifplugd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781108] [ 1283] 0 1283 1798 38 16384 76 0 ntpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781119] [ 1305] 0 1305 1022 0 12288 37 0 eq3configd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781129] [ 1312] 0 1312 395 0 10240 11 0 lighttpd-angel
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781140] [ 1314] 0 1314 1648 33 14336 227 0 lighttpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781150] [ 1319] 0 1319 977 23 14336 13 0 ssdpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781161] [ 1348] 0 1348 2089 248 16384 466 0 lighttpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781171] [ 1349] 0 1349 2087 243 16384 469 0 lighttpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781181] [ 1350] 0 1350 2050 241 16384 458 0 lighttpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781191] [ 1351] 0 1351 2102 200 16384 527 0 lighttpd
Nov 12 21:26:06 Raspi043BPlus kernel: [9198871.781201] [ 1374] 0 1374 2993 53 18432 24 0 multimacd
Nov 12 21:30:00 Raspi043BPlus kernel: [9199107.453590] usb 1-1.2: USB disconnect, device number 49
Nov 12 21:30:05 Raspi043BPlus kernel: [9199111.589658] usb 1-1.2: new full-speed USB device number 51 using dwc_otg
Nov 12 21:35:41 Raspi043BPlus kernel: [9199445.846467] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 12 21:35:56 Raspi043BPlus kernel: [9199445.846478] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 12 21:36:13 Raspi043BPlus kernel: [9199445.846490] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
im Log. Zu der Uhrzeit hatte ich versucht, meine DOIF etc. auf das geänderte Modul HMCCU anzupassen.
Um 10:52, bei der Meldung von sysmon, hat es wieder mit der Zeile angefangen
Nov 13 10:49:43 Raspi043BPlus kernel: [9244009.230096] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:50:26 Raspi043BPlus kernel: [9244009.230107] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:51:20 Raspi043BPlus kernel: [9244009.230118] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:51:42 Raspi043BPlus kernel: [9244009.230129] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:14 Raspi043BPlus kernel: [9244009.230140] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9244009.230151] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9244009.230162] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9244009.230173] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9244009.230184] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9244009.230267] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9246974.699572] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
und führte dann dazu
Nov 13 10:52:37 Raspi043BPlus kernel: [9247258.203526] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247258.203537] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247258.681869] usb 1-1.2: USB disconnect, device number 103
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.003571] usb 1-1.2: new full-speed USB device number 104 using dwc_otg
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.147935] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.147952] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.147961] usb 1-1.2: Product: ConBee II
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.147969] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.147977] usb 1-1.2: SerialNumber: DE2439922
Nov 13 10:52:37 Raspi043BPlus kernel: [9247259.148881] cdc_acm 1-1.2:1.0: ttyACM2: USB ACM device
Nov 13 10:52:37 Raspi043BPlus kernel: [9247262.523962] usb 1-1.2: USB disconnect, device number 104
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058351] [<809e477c>] (dump_backtrace) from [<809e4b0c>] (show_stack+0x20/0x24)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058359] r7:ffffffff r6:00000000 r5:60000193 r4:80ee5d54
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058369] [<809e4aec>] (show_stack) from [<809e8cb8>] (dump_stack+0xcc/0xf8)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058381] [<809e8bec>] (dump_stack) from [<80301060>] (warn_alloc+0xd4/0x164)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058390] r10:00040800 r9:80e05008 r8:ffffe000 r7:80c170f8 r6:00000000 r5:00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058395] r4:80e05008 r3:b5d307d2
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058406] [<80300f8c>] (warn_alloc) from [<803021b0>] (__alloc_pages_nodemask+0x10c0/0x1184)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058411] r3:00000000 r2:80c170f8
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058419] r8:00000000 r7:00000000 r6:00000004 r5:00000001 r4:00000800
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058431] [<803010f0>] (__alloc_pages_nodemask) from [<80313518>] (allocate_slab+0x2c4/0x360)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058439] r10:ffffffff r9:00000002 r8:00000000 r7:00000000 r6:00000004 r5:81401a80
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058444] r4:00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058454] [<80313254>] (allocate_slab) from [<80316954>] (___slab_alloc.constprop.27+0x3a8/0x56c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058462] r10:81401a80 r9:00000254 r8:b6b2e680 r7:b6b2e680 r6:00000900 r5:81400e80
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058468] r4:00000000 r3:003beee0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058476] [<803165ac>] (___slab_alloc.constprop.27) from [<80316b88>] (__slab_alloc.constprop.26+0x70/0x80)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058485] r10:0683b5c2 r9:00000254 r8:b6b2e680 r7:806b2698 r6:00000900 r5:81401a80
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058490] r4:60000113
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058498] [<80316b18>] (__slab_alloc.constprop.26) from [<803176dc>] (__kmalloc+0x57c/0x5c8)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058505] r8:00000900 r7:80e057c8 r6:00000000 r5:00000000 r4:81401a80
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058516] [<80317160>] (__kmalloc) from [<806b2698>] (bcm2835_dma_create_cb_chain+0x64/0x308)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058525] r10:000d0418 r9:00000000 r8:7e202040 r7:00000002 r6:00000040 r5:81762640
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058529] r4:00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058539] [<806b2634>] (bcm2835_dma_create_cb_chain) from [<806b2e94>] (bcm2835_dma_prep_slave_sg+0x140/0x318)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058547] r10:40000000 r9:00000000 r8:823b7000 r7:00000002 r6:00000040 r5:00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058552] r4:81762640
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058564] [<806b2d54>] (bcm2835_dma_prep_slave_sg) from [<8081c8cc>] (bcm2835_sdhost_request+0x4a4/0x70c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058572] r10:806b2d54 r9:8238af7c r8:82271b40 r7:80ff1eb0 r6:80e05008 r5:8238aea8
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058576] r4:82271800
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058589] [<8081c428>] (bcm2835_sdhost_request) from [<807fbb18>] (__mmc_start_request+0x88/0x198)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058597] r10:8238ae00 r9:823320e0 r8:82271800 r7:00000000 r6:8238aea8 r5:8238aea8
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058602] r4:82271800
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058610] [<807fba90>] (__mmc_start_request) from [<807fbcbc>] (mmc_start_request+0x94/0xbc)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058618] r7:00000000 r6:00000000 r5:8238aea8 r4:82271800
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058629] [<807fbc28>] (mmc_start_request) from [<8080fd54>] (mmc_blk_mq_issue_rq+0x350/0x93c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058636] r7:00000000 r6:82332008 r5:8238aea8 r4:80e05008
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058646] [<8080fa04>] (mmc_blk_mq_issue_rq) from [<80810754>] (mmc_mq_queue_rq+0x158/0x2a0)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058654] r10:00000002 r9:823320e0 r8:82271800 r7:82272800 r6:82332010 r5:8238ae00
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058659] r4:82332008
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058670] [<808105fc>] (mmc_mq_queue_rq) from [<805ef920>] (blk_mq_dispatch_rq_list+0x128/0x7ec)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058679] r10:8238ae00 r9:82368000 r8:8227b000 r7:00000004 r6:8227b000 r5:855d9e3c
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058683] r4:8238ae30
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058694] [<805ef7f8>] (blk_mq_dispatch_rq_list) from [<805f50fc>] (__blk_mq_do_dispatch_sched+0x174/0x2b4)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058702] r10:8227b004 r9:82333200 r8:00000000 r7:80e05008 r6:8227b000 r5:855d9e3c
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058707] r4:0000001c
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058716] [<805f4f88>] (__blk_mq_do_dispatch_sched) from [<805f54a0>] (__blk_mq_sched_dispatch_requests+0x108/0x1b0)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058725] r10:00000000 r9:00000000 r8:8227b004 r7:80e05008 r6:855d9e84 r5:00000001
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058729] r4:8227b000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058738] [<805f5398>] (__blk_mq_sched_dispatch_requests) from [<805f57e4>] (blk_mq_sched_dispatch_requests+0x54/0x6c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058746] r8:00000020 r7:b6b30700 r6:b6b2b840 r5:00000001 r4:8227b000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058756] [<805f5790>] (blk_mq_sched_dispatch_requests) from [<805ecd0c>] (__blk_mq_run_hw_queue+0xb0/0x14c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058762] r5:00000001 r4:8227b000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058771] [<805ecc5c>] (__blk_mq_run_hw_queue) from [<805ecdd0>] (blk_mq_run_work_fn+0x28/0x2c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058777] r5:83632180 r4:8227b040
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058789] [<805ecda8>] (blk_mq_run_work_fn) from [<8013b980>] (process_one_work+0x250/0x5a0)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058798] [<8013b730>] (process_one_work) from [<8013bd30>] (worker_thread+0x60/0x5c4)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058806] r10:b6b2b840 r9:80e03d00 r8:b6b2b858 r7:00000008 r6:b6b2b840 r5:83632194
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058811] r4:83632180
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058821] [<8013bcd0>] (worker_thread) from [<801437b8>] (kthread+0x170/0x174)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058830] r10:82a59e74 r9:83632180 r8:8013bcd0 r7:855d8000 r6:00000000 r5:83553080
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058834] r4:841fe980
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058843] [<80143648>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058848] Exception stack(0x855d9fb0 to 0x855d9ff8)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058855] 9fa0: 00000000 00000000 00000000 00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058863] 9fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058870] 9fe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058878] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143648
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058883] r4:83553080
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058887] Mem-Info:
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058900] active_anon:106134 inactive_anon:106215 isolated_anon:0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058900] active_file:91 inactive_file:475 isolated_file:0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058900] unevictable:4 dirty:0 writeback:0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058900] slab_reclaimable:3608 slab_unreclaimable:9751
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058900] mapped:405 shmem:1853 pagetables:2782 bounce:0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058900] free:4096 free_pcp:62 free_cma:56
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058911] Node 0 active_anon:424536kB inactive_anon:424860kB active_file:396kB inactive_file:1828kB unevictable:16kB isolated(anon):0kB isolated(file):128kB mapped:1672kB dirty:0kB writeback:0kB shmem:7412kB writeback_tmp:0kB kernel_stack:2168kB all_unreclaimable? no
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058924] DMA free:16404kB min:16384kB low:20480kB high:24576kB reserved_highatomic:0KB active_anon:424536kB inactive_anon:424860kB active_file:24kB inactive_file:2056kB unevictable:16kB writepending:0kB present:970752kB managed:946392kB mlocked:16kB pagetables:11128kB bounce:0kB free_pcp:248kB local_pcp:248kB free_cma:224kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058928] lowmem_reserve[]: 0 0 0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.058941] DMA: 1013*4kB (UMEC) 266*8kB (UMEC) 150*16kB (UME) 56*32kB (UME) 32*64kB (UME) 17*128kB (ME) 5*256kB (UME) 0*512kB 1*1024kB (M) 0*2048kB 0*4096kB = 16900kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059001] 3211 total pagecache pages
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059008] 757 pages in swap cache
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059013] Swap cache stats: add 167819, delete 167062, find 23810870/23845887
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059017] Free swap = 0kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059020] Total swap = 102396kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059024] 242688 pages RAM
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059028] 0 pages HighMem/MovableOnly
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059032] 6090 pages reserved
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059036] 16384 pages cma reserved
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059043] SLUB: Unable to allocate memory on node -1, gfp=0x900(GFP_NOWAIT|__GFP_ZERO)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059049] cache: kmalloc-1k, object size: 1024, buffer size: 1024, default order: 2, min order: 0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.059055] node 0: slabs: 62, objs: 860, free: 0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.083370] SLUB: Unable to allocate memory on node -1, gfp=0x900(GFP_NOWAIT|__GFP_ZERO)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.083383] cache: kmalloc-1k, object size: 1024, buffer size: 1024, default order: 2, min order: 0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.083390] node 0: slabs: 62, objs: 860, free: 0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185925] lpqd invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185945] CPU: 2 PID: 19282 Comm: lpqd Tainted: G C O 5.10.17-v7+ #1421
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185950] Hardware name: BCM2835
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185954] Backtrace:
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185978] [<809e477c>] (dump_backtrace) from [<809e4b0c>] (show_stack+0x20/0x24)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185987] r7:ffffffff r6:00000000 r5:60000113 r4:80ee5d54
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.185997] [<809e4aec>] (show_stack) from [<809e8cb8>] (dump_stack+0xcc/0xf8)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186006] [<809e8bec>] (dump_stack) from [<809e6fa8>] (dump_header+0x64/0x208)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186015] r10:80e05144 r9:00100cca r8:00000000 r7:80c13384 r6:8d6ae400 r5:8d6b0000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186020] r4:82ab3d50 r3:b5d307d2
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186033] [<809e6f44>] (dump_header) from [<802b18b0>] (oom_kill_process+0x1b4/0x1c0)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186041] r7:80c13384 r6:82ab3d50 r5:8d6b0580 r4:8d6b0000
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186050] [<802b16fc>] (oom_kill_process) from [<802b2428>] (out_of_memory+0x2b8/0x390)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186057] r7:80e083c0 r6:80e05008 r5:8d6b0000 r4:82ab3d50
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186069] [<802b2170>] (out_of_memory) from [<803018dc>] (__alloc_pages_nodemask+0x7ec/0x1184)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186076] r7:80e05784 r6:00000000 r5:ffffe000 r4:00400040
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186087] [<803010f0>] (__alloc_pages_nodemask) from [<802abde0>] (pagecache_get_page+0x10c/0x34c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186095] r10:80f316db r9:00000007 r8:80e059e4 r7:85a74848 r6:00100cca r5:00000044
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186100] r4:44980001
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186109] [<802abcd4>] (pagecache_get_page) from [<802add40>] (filemap_fault+0x638/0xb20)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186117] r10:80e05008 r9:82ab3ec8 r8:00000040 r7:8d4f6600 r6:82ab3ec8 r5:8d4f6600
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186122] r4:85a74738
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186133] [<802ad708>] (filemap_fault) from [<80427a9c>] (ext4_filemap_fault+0x38/0x4c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186142] r10:82ab3fb0 r9:82ab3ec8 r8:00000040 r7:00000000 r6:74068000 r5:82ab3ec8
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186147] r4:85a74720
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186158] [<80427a64>] (ext4_filemap_fault) from [<802e4f04>] (__do_fault+0x48/0x14c)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186163] r5:93814ea0 r4:82ab3ec8
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186173] [<802e4ebc>] (__do_fault) from [<802e9fc0>] (handle_mm_fault+0xae8/0xe30)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186180] r7:00000000 r6:74068000 r5:80e05008 r4:00000254
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186190] [<802e94d8>] (handle_mm_fault) from [<809f4258>] (do_page_fault+0x144/0x314)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186199] r10:00000254 r9:00000000 r8:939db048 r7:939db000 r6:00000017 r5:74068a5c
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186203] r4:82ab3fb0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186213] [<809f4114>] (do_page_fault) from [<80113fb8>] (do_DataAbort+0x4c/0xcc)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186221] r10:00000275 r9:01d105a0 r8:82ab3fb0 r7:74068a5c r6:809f4114 r5:00000017
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186226] r4:80e0abf8
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186235] [<80113f6c>] (do_DataAbort) from [<80100da4>] (__dabt_usr+0x44/0x60)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186240] Exception stack(0x82ab3fb0 to 0x82ab3ff8)
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186247] 3fa0: 00000278 7630c778 00000000 950412de
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186255] 3fc0: 00000000 00000001 00000003 950412de 74061000 01d105a0 00000275 74068a64
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186322] DMA free:16544kB min:16384kB low:20480kB high:24576kB reserved_highatomic:0KB active_anon:424536kB inactive_anon:424860kB active_file:0kB inactive_file:2340kB unevictable:16kB writepending:0kB present:970752kB managed:946392kB mlocked:16kB pagetables:11128kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:224kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186328] lowmem_reserve[]: 0 0 0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186354] DMA: 1022*4kB (UMEC) 266*8kB (UMEC) 150*16kB (UME) 56*32kB (UME) 32*64kB (UME) 17*128kB (ME) 5*256kB (UME) 0*512kB 1*1024kB (M) 0*2048kB 0*4096kB = 16936kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186465] 3272 total pagecache pages
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186474] 757 pages in swap cache
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186482] Swap cache stats: add 167819, delete 167062, find 23810870/23845887
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186488] Free swap = 0kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186494] Total swap = 102396kB
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186500] 242688 pages RAM
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186506] 0 pages HighMem/MovableOnly
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186512] 6090 pages reserved
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186518] 16384 pages cma reserved
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186525] Tasks state (memory values in pages):
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186532] [ pid ] uid tgid total_vm rss pgtables_bytes swapents oom_score_adj name
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186557] [ 149] 0 149 4531 96 22528 118 -1000 systemd-udevd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186570] [ 430] 0 430 6378 199 22528 136 0 rsyslogd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186580] [ 435] 0 435 923 9 10240 40 0 alsactl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186591] [ 437] 0 437 5046 0 16384 56 0 lxcfs
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186602] [ 441] 0 441 3286 39 22528 139 0 systemd-logind
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186612] [ 444] 104 444 1637 71 16384 53 -900 dbus-daemon
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186623] [ 447] 0 447 2686 12 20480 89 0 wpa_supplicant
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186634] [ 449] 108 449 1475 59 12288 44 0 avahi-daemon
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186645] [ 454] 0 454 7170 25 18432 13 0 rngd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186655] [ 458] 0 458 1987 14 18432 31 0 cron
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186665] [ 462] 0 462 1979 36 14336 184 0 dhclient
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186676] [ 463] 65534 463 1080 5 14336 39 0 thd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186687] [ 482] 108 482 1442 7 12288 56 0 avahi-daemon
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186697] [ 562] 100 562 5495 19 24576 132 0 systemd-timesyn
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186708] [ 606] 0 606 8041 62 38912 302 0 nmbd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186718] [ 614] 0 614 1077 0 12288 25 0 agetty
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186729] [ 642] 0 642 2682 29 18432 116 -1000 sshd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186739] [ 681] 0 681 12091 131 57344 356 0 smbd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186750] [ 684] 0 684 11357 110 51200 360 0 smbd-notifyd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186761] [ 685] 0 685 11358 115 49152 355 0 cleanupd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186771] [ 686] 0 686 12088 124 51200 363 0 lpqd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186783] [ 993] 0 993 2501 0 18432 132 0 lxc-start
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186793] [ 1005] 0 1005 779 0 10240 20 0 init
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186804] [ 1105] 0 1105 1098 29 14336 16 0 hss_led
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186815] [ 1149] 1001 1149 723 1 12288 38 0 dbus-daemon
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186825] [ 1179] 0 1179 779 11 12288 8 0 syslogd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186836] [ 1182] 0 1182 779 18 10240 9 0 klogd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186847] [ 1202] 0 1202 779 0 10240 26 0 udhcpc
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186857] [ 1272] 0 1272 456 6 8192 16 0 ifplugd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186868] [ 1283] 0 1283 1798 37 16384 77 0 ntpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186879] [ 1305] 0 1305 1022 0 12288 37 0 eq3configd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186890] [ 1312] 0 1312 395 0 10240 11 0 lighttpd-angel
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186900] [ 1314] 0 1314 1648 32 14336 228 0 lighttpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186910] [ 1319] 0 1319 977 24 14336 13 0 ssdpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186920] [ 1348] 0 1348 2089 180 16384 534 0 lighttpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186931] [ 1349] 0 1349 2087 238 16384 474 0 lighttpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186942] [ 1350] 0 1350 2050 207 16384 492 0 lighttpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186952] [ 1351] 0 1351 2102 266 16384 461 0 lighttpd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186963] [ 1374] 0 1374 2993 52 18432 27 0 multimacd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186974] [ 1400] 0 1400 5611 1515 30720 981 0 rfd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186985] [ 1415] 0 1415 68333 21733 159744 2744 0 java
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.186995] [ 1539] 0 1539 1017 0 10240 36 0 eq3-uds-service
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187006] [ 1545] 0 1545 7788 1380 40960 1618 0 ReGaHss.communi
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187017] [ 1609] 0 1609 811 17 12288 8 0 crond
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187028] [ 29446] 0 29446 4722 503 43008 18 0 systemd-journal
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187039] [ 29856] 999 29856 146142 141123 593920 315 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187050] [ 30105] 999 30105 38525 28404 161792 5464 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187060] [ 30107] 999 30107 38636 29483 161792 4496 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187070] [ 30744] 1000 30744 38718 1920 174080 0 0 npm
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187081] [ 30758] 1000 30758 486 15 10240 0 0 sh
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187092] [ 30759] 1000 30759 44180 7732 305152 7 0 node
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187106] [ 19192] 999 19192 146142 141102 593920 317 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187116] [ 19193] 999 19193 146142 141108 593920 317 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187127] [ 19197] 999 19197 146142 141109 593920 316 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187137] [ 19198] 999 19198 146142 141109 593920 316 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187148] [ 19199] 999 19199 146142 141109 593920 316 0 perl
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187159] [ 19235] 0 19235 2289 61 16384 9 0 cron
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187172] [ 19271] 0 19271 779 18 10240 0 0 watchdog
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187182] [ 19276] 0 19276 779 19 12288 0 0 sh
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187193] [ 19280] 0 19280 746 16 8192 0 0 sh
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187203] [ 19282] 0 19282 12126 159 51200 333 0 lpqd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187213] [ 19283] 0 19283 8041 96 38912 269 0 nmbd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187225] [ 19287] 0 19287 1987 26 14336 19 0 cron
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187235] [ 19298] 0 19298 12091 161 45056 326 0 smbd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187246] [ 19300] 0 19300 746 14 10240 0 0 sh
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187258] [ 19309] 0 19309 2682 25 18432 120 0 sshd
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187266] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=perl,pid=29856,uid=999
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.187337] Out of memory: Killed process 29856 (perl) total-vm:584568kB, anon-rss:564492kB, file-rss:0kB, shmem-rss:0kB, UID:999 pgtables:580kB oom_score_adj:0
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572532] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572542] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572550] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572558] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572566] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572574] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572582] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572590] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572598] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572606] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572614] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572622] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572630] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572638] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572646] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572654] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572662] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572779] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572787] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572795] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.572803] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.574159] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.574173] raw-uart raw-uart1: generic_raw_uart_handle_rx_char(): rx fifo full.
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.977144] eq3loop: eq3loop_write_master() mmd_hmip: not enought space in the buffers. free space = 41, required space = 46
Nov 13 10:52:37 Raspi043BPlus kernel: [9247263.977162] eq3loop: eq3loop_write_master() retrun error:
Nov 13 10:52:37 Raspi043BPlus kernel: [9247264.047271] eq3loop: eq3loop_write_master() mmd_hmip: not enought space in the buffers. free space = 2, required space = 46
Nov 13 10:52:37 Raspi043BPlus kernel: [9247264.047290] eq3loop: eq3loop_write_master() retrun error:
Nov 13 10:52:37 Raspi043BPlus kernel: [9247264.047380] eq3loop: eq3loop_write_master() mmd_hmip: not enought space in the buffers. free space = 2, required space = 39
Nov 13 10:52:37 Raspi043BPlus kernel: [9247264.047392] eq3loop: eq3loop_write_master() retrun error:
Nov 13 10:52:37 Raspi043BPlus kernel: [9247264.047466] eq3loop: eq3loop_write_master() mmd_hmip: not enought space in the buffers. free space = 2, required space = 10
Nov 13 10:59:59 Raspi043BPlus kernel: [9247707.294657] usb 1-1.2: new full-speed USB device number 106 using dwc_otg
Nov 13 11:00:00 Raspi043BPlus kernel: [9247707.429075] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 13 11:00:00 Raspi043BPlus kernel: [9247707.429092] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 11:00:00 Raspi043BPlus kernel: [9247707.429110] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 13 11:00:00 Raspi043BPlus kernel: [9247707.431555] cdc_acm 1-1.2:1.0: ttyACM1: USB ACM device
Nov 13 11:00:03 Raspi043BPlus kernel: [9247711.329235] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 13 11:00:03 Raspi043BPlus kernel: [9247711.329275] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 13 11:00:03 Raspi043BPlus kernel: [9247711.331967] cdc_acm 1-1.2:1.0: ttyACM1: USB ACM device
Bei der Interpretation muss ich leider passen. Kann daraus gelesen werden, was denn eigentlich die Ursache für die plötzlichen Abstürze ist?
Grüße Jürgen
Nov 12 11:56:57 Raspi043BPlus kernel: [9164724.019925] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=perl,pid=22975,uid=999
Nov 12 11:56:57 Raspi043BPlus kernel: [9164724.019985] Out of memory: Killed process 22975 (perl) total-vm:367172kB, anon-rss:342720kB, file-rss:0kB, shmem-rss:0kB, UID:999 pgtables:368kB oom_score_adj:0
Wenn der Speicher vollläuft, guckt das System nach Prozessen welche
- Viel Speicher brauchen
- selten verwendet werden
und entscheidet, welche Prozesse er kill und damit Speicher freischaufelt damit das System nicht stirbt. Hier war es "perl" und damit bestimmt ein Teil von FHEM.
Kurz gesagt: Du hast (hattest) zu wenig RAM. Gebe uns bitte mal (als root oder mit sudo)
ps aux | grep fhem
free
Wie angefordert :)
pi@Raspi043BPlus:~ $ ps aux | grep fhem
fhem 19823 35.9 26.1 259500 247848 ? S 10:54 255:19 /usr/bin/perl fhem.pl fhem.cfg
fhem 20107 0.3 14.3 163184 135720 ? S 10:55 2:45 /usr/bin/perl fhem.pl fhem.cfg
fhem 20115 0.0 14.1 162500 134132 ? S 10:55 0:34 /usr/bin/perl fhem.pl fhem.cfg
pi 22922 0.0 0.0 7360 532 pts/1 S+ 22:44 0:00 grep --color=auto fhem
pi@Raspi043BPlus:~ $ free
total used free shared buff/cache available
Mem: 946392 550884 174464 10536 221044 333228
Swap: 102396 90340 12056
Er hat also schon geswapt. Spitzenmäßig also schon mal mehr als 60% Speichernutzung gehabt. Du pings doch mit fhem gewisse Geräte? In dem Modul kann man die Menge der Folks einschränken (Frag mich nicht wie)
Geswapt? Bedeutet das, dass der RAM-Speicher zu voll geworden ist und Teile auf die SD-Karte ausgelagert wurden?
Wie kann man herausfinden, was für den vollen Speicher verantwortlich ist?
Die pings:
5 Handys werden über das PRESENCE-Modul bei einer Fritzbox über
function {checkAllFritzMACpresent("XX:XX:XX:XX:XX:XX")} 60 60alle 60 Sekunden abgefragt. 2 der Handys haben Android und die werden zusätzlich noch über einen Lan-Ping
lan-ping 192.168.178.38 60auch alle 60-Sekunden abgefragt da ich gelesen habe, dass die Abfrage über die Fritzbox bei Android-Handys nicht zuverlässig funktioniert. Das ist schon seit mehreren Jahren so und ich hatte bisher keine Probleme bemerkt.
Was kann ich noch tun, damit das Problem nicht noch einmal auftritt?
Zum automatischen Start: Wie habt ihr denn euer System eingerichtet?
ZitatAutomatischer Start deswegen, damit das System läuft wenn ich es nicht manuell wieder starten kann. Dachte das ist die beste Lösung, wenn ein Absturz erfolgt. Wie sollte man das System denn einrichten? Es gibt ja auch die Möglichkeit, über einen Cronjob FHEM nach einer gewissen Wartezeit neu zu starten. Ist diese Lösung besser?
Grüße Jürgen
ZitatIn dem Modul kann man die Menge der Folks einschränken (Frag mich nicht wie)
Zitat von: Wernieman am 14 November 2021, 23:28:12
In dem Modul kann man die Menge der Folks einschränken (Frag mich nicht wie)
ZitatblockingCallMax
Begrenzt die Anzahl der parallel laufenden Prozesse, die von der BlockingCall FHEM Hilfsroutine gestartet wurden. Sinnvoll auf weniger leistungsfaehigen Hardware, die Voreinstellung ist 32. Nach erreichen dieser Grenze werden weitere Aufrufe verzögert.
findest unter global
Zitat von: bmwfan am 14 November 2021, 10:36:18
Geswapt? Bedeutet das, dass der RAM-Speicher zu voll geworden ist und Teile auf die SD-Karte ausgelagert wurden?
Wie kann man herausfinden, was für den vollen Speicher verantwortlich ist?
Die pings:
5 Handys werden über das PRESENCE-Modul bei einer Fritzbox über
function {checkAllFritzMACpresent("XX:XX:XX:XX:XX:XX")} 60 60
alle 60 Sekunden abgefragt. 2 der Handys haben Android und die werden zusätzlich noch über einen Lan-Ping
lan-ping 192.168.178.38 60
auch alle 60-Sekunden abgefragt da ich gelesen habe, dass die Abfrage über die Fritzbox bei Android-Handys nicht zuverlässig funktioniert. Das ist schon seit mehreren Jahren so und ich hatte bisher keine Probleme bemerkt.
Was kann ich noch tun, damit das Problem nicht noch einmal auftritt?
Zum automatischen Start: Wie habt ihr denn euer System eingerichtet?
Grüße Jürgen
EDIT:
Zitat
CGroup: /system.slice/fhem.service
├─19823 /usr/bin/perl fhem.pl fhem.cfg
├─19981 /usr/bin/perl fhem.pl fhem.cfg
├─19982 /usr/bin/perl fhem.pl fhem.cfg
├─19983 /usr/bin/perl fhem.pl fhem.cfg
├─19984 /usr/bin/perl fhem.pl fhem.cfg
├─19985 /usr/bin/perl fhem.pl fhem.cfg
├─19986 /usr/bin/perl fhem.pl fhem.cfg
├─20019 /usr/bin/perl fhem.pl fhem.cfg
├─20107 /usr/bin/perl fhem.pl fhem.cfg
├─20115 /usr/bin/perl fhem.pl fhem.cfg
└─20156 /usr/bin/perl fhem.pl fhem.cfg
sieht nach sehr vielen Forks aus...
...jeder Fork "zieht" sich den kompletten fhem-Speicher noch mal "rein"...
Wenn es wirklich forking ist und auch das Einschränken nicht hilft, dann ist evtl. das einen Blick wert: https://forum.fhem.de/index.php/topic,117007.msg1113644.html#msg1113644
Martin "bemängelt" dort gerade das Blocking, was ja schon mal gut ist das zu nutzen und fhem nicht zu blockieren aber halt für jeden Presence-Ping einen Fork macht...
..."seine Abwandlung" macht das besser...
Habe ich aber selbst noch nicht getestet (steht noch auf der Liste ;) )...
Was läuft sonst noch auf dem PI?
Ich habe was von Conbee
(und deCONZ) zigbee2mqtt gelesen...
Evtl. da auch mal abspecken und auf eine andere HW auslagern...
Gruß, Joachim
Jetzt hatte sich nicht nur FHEM sondern der ganze Pi aufgehängt. Musste den Stecker ziehen, zum wiederbeleben. Diese Meldung im Log:
2021.11.15 13:08:49.771 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 13:09:39.118 1: 192.168.178.47:1000 disconnected, waiting to reappear (HM485_LAN)
2021.11.15 13:09:39.277 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 13:09:42.127 3: HM485_LAN: connected to device 192.168.178.47:1000
2021.11.15 13:09:42.128 1: 192.168.178.47:1000 reappeared (HM485_LAN)
2021.11.15 13:09:45.081 3: HM485_LAN: Lan Device Information
2021.11.15 13:09:45.081 3: HM485_LAN: Protocol-Version: 01
2021.11.15 13:09:45.081 3: HM485_LAN: Interface-Type: eQ3-HMW-LGW
2021.11.15 13:09:45.081 3: HM485_LAN: Firmware-Version: 1.0.4
2021.11.15 13:09:45.081 3: HM485_LAN: Serial-Number: LEQ0636394
2021.11.15 13:09:45.082 3: HM485_LAN: Initialize the interface
2021.11.15 13:17:38.467 1: Timeout for SYSMON_blockingCall reached, terminated process 27302
2021.11.15 13:17:44.765 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 13:17:45.022 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 13:18:44.445 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 13:34:53.504 1: Including fhem.cfg
2021.11.15 13:34:53.576 3: telnetPort: port 7072 opened
Im pi:
pi@Raspi043BPlus:~ $ ps aux | grep fhem
fhem 665 72.8 17.7 178512 168440 ? R 13:34 6:03 /usr/bin/perl fhem.pl fhem.cfg
fhem 2018 1.0 16.3 169424 154752 ? S 13:39 0:02 /usr/bin/perl fhem.pl fhem.cfg
fhem 2020 0.4 16.3 169424 154688 ? S 13:39 0:01 /usr/bin/perl fhem.pl fhem.cfg
fhem 2021 0.1 16.3 169424 154688 ? S 13:39 0:00 /usr/bin/perl fhem.pl fhem.cfg
pi 2492 0.0 0.0 7360 496 pts/1 S+ 13:43 0:00 grep --color=auto fhem
pi@Raspi043BPlus:~ $ free
total used free shared buff/cache available
Mem: 946392 480116 169620 7480 296656 411552
Swap: 102396 0 102396
@MadMax-FHEM:
Was läuft alles:
System Info
ConfigType: configFile
SVN rev: 25227
OS: linux
Perl: 5.28.1
uniqueId: 032...
Modules Model Count
BOSEST 1
CUL
CUL 1
CUL_HM
HM-SEN-MDIR-WM55 1
HM-MOD-RE-8 1
HM-ES-PMSW1-PL 1
HM-MOD-EM-8 1
HM-LC-SW2-FM 1
HM-RC-8 1
DOIF
Perl 3
FHEM 74
DOIFtools 1
ENIGMA2
DUO2 1
FB_CALLLIST 1
FB_CALLMONITOR 1
FHEMWEB 3
FRITZBOX 2
FRITZ!Repeater 3000 1
FRITZ!Box 7530 1
FileLog 84
GEOFANCY 1
HM485 8
HM485_LAN 1
HMCCU 1
HMCCUCHN 3
HMCCUDEV 7
HMCCURPCPROC 3
HMUARTLGW
HM-MOD-UART 1
HMinfo 1
HOMEMODE 1
HTTPMOD 3
pharmacy_emergency_service_germany 1
HTTPSRV 1
IPCAM 3
Jalousie 7
JeeLink
LaCrosseITPlusReader.10.1q 1
LaCrosse 2
MQTT2_DEVICE 11
shelly2rgbw_4w_split 8
owntracks_device 1
SHSW-1 3
SHSW-25 10
shellydimmer 1
zigbee2mqtt_human_body_movement_illuminance 1
ebus_analyzeReadingList 1
tasmota_basic_state_power1 1
zigbee2mqtt_bridge 1
eBus_daemon_splitter 1
tasmota_POW 3
zigbee2mqtt_human_body_movement 2
MQTT2_SERVER 1
MQTT_GENERIC_BRIDGE 1
PRESENCE
function 4
lan-ping 2
daemon 1
PROPLANTA 1
Pushover 2
RESIDENTS 1
ROOMMATE 5
Robonect 1
SVG 21
SYSMON 1
SamsungAV 1
Shelly
shellydimmer 1
TRAFFIC 2
UWZ 1
allowed 2
at 8
autocreate 1
dummy 52
eventTypes 1
expandJSON 1
freezemon 1
holiday 2
livetracking 1
logProxy 1
monitoring 2
msgConfig 1
notify 13
rain 1
readingsGroup 15
statistics 1
structure 2
telnet 1
weblink 9
ConbeeII ist für zigbeemqtt
CUL für Homematic
Kann mir jemand weiterhelfen?
Grüße Jürgen
Mal in eine ganz andere Richtung: schon mal eine andere SD-Karte probiert?
Die ist gerade einmal etwa 6 Monate drin. Da es mit der letzten Karte (16GB) nach ca. 1,5 Jahren seltsame Ausfälle gab, habe ich eine deutlich größere Karte (64GB) gekauft und eingebaut. Ich kann mir nicht vorstellen, dass die auch schon defekt sein kann aber möglich ist alles.
Steht im /var/log/kern.log (und/oder syslog) etwas zu der Absturzzeit?
Mich würde oom und i/o Fehler/Warnungen interessieren
Ich verstehe beide logs nicht. Die Einträge sind nicht cronologisch???. Siehe Dateien im Anhang.
Und schon wieder hat sich der Raspi aufgehängt:
FHEM-Log:
2021.11.15 20:16:42.496 1: 192.168.178.47:1000 disconnected, waiting to reappear (HM485_LAN)
2021.11.15 20:16:47.034 3: MQTT2_DEVICE set MQTT2_shellyswitch25_C45BBE75D1CC off
2021.11.15 20:16:47.268 3: PRESENCE (PsnceDaemon) - skip scan due to running job
2021.11.15 20:16:49.461 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 20:16:49.555 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 20:16:49.581 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.15 20:16:49.883 3: HM485_LAN: connected to device 192.168.178.47:1000
2021.11.15 20:16:49.884 1: 192.168.178.47:1000 reappeared (HM485_LAN)
2021.11.15 20:31:39.072 1: Including fhem.cfg
2021.11.15 20:31:39.144 3: telnetPort: port 7072 opened
2021.11.15 20:31:39.842 3: WEB: port 8083 opened
2021.11.15 20:31:39.852 3: WEBS: port 8084 opened
2021.11.15 20:31:41.080 2: Registering GEOFANCY geofancy for URL /geo...
2021.11.15 20:31:41.127 3: WEBhook: port 8088 opened
2021.11.15 20:31:41.716 2: eventTypes: loaded 10038 lines from ./log/eventTypes.txt
2021.11.15 20:31:41.757 3: Opening CUL_0 device /dev/serial/by-id/usb-busware.de_CUL868-if00
2021.11.15 20:31:41.809 3: Setting CUL_0 serial parameters to 9600,8,N,1
2021.11.15 20:31:41.918 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2021.11.15 20:31:41.923 3: CUL_0 device opened
2021.11.15 20:31:41.930 2: Switched CUL_0 rfmode to HomeMatic
2021.11.15 20:31:42.532 3: additional HM config file loaded: ./FHEM/HMConfig_SenTHPL.pm
2021.11.15 20:31:42.716 3: Opening myJeeLink1 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL014JZA-if00-port0
2021.11.15 20:31:42.719 3: Setting myJeeLink1 serial parameters to 57600,8,N,1
2021.11.15 20:31:43.727 3: myJeeLink1 device opened
2021.11.15 20:31:44.856 3: TABLETUI: new ext defined infix:ftui/: dir:./www/tablet/:
2021.11.15 20:31:44.856 3: Registering HTTPSRV TABLETUI for URL /ftui and assigned link ftui/ ...
2021.11.15 20:31:45.217 3: HM485: HM485: Converting device files
2021.11.15 20:31:45.218 3: HM485: ==============================
2021.11.15 20:31:45.219 3: HM485: hmw_central.xml up to date
2021.11.15 20:31:45.220 3: HM485: hmw_generic.xml up to date
2021.11.15 20:31:45.220 3: HM485: hmw_io12_sw14_dr.xml up to date
2021.11.15 20:31:45.220 3: HM485: hmw_io12_sw7_dr.xml up to date
2021.11.15 20:31:45.220 3: HM485: hmw_io12_sw7_dr_V3_02.xml up to date
2021.11.15 20:31:45.221 3: HM485: hmw_io_12_fm.xml up to date
2021.11.15 20:31:45.221 3: HM485: hmw_io_4_fm.xml up to date
2021.11.15 20:31:45.221 3: HM485: hmw_io_4_fm_V3_02.xml up to date
2021.11.15 20:31:45.221 3: HM485: hmw_io_sr_fm.xml up to date
2021.11.15 20:31:45.221 3: HM485: hmw_lc_bl1_dr.xml up to date
2021.11.15 20:31:45.221 3: HM485: hmw_lc_bl1_dr_V3_02.xml up to date
2021.11.15 20:31:45.222 3: HM485: hmw_lc_dim1l_dr.xml up to date
2021.11.15 20:31:45.222 3: HM485: hmw_lc_sw2_dr.xml up to date
2021.11.15 20:31:45.222 3: HM485: hmw_lc_sw2_dr_V3_02.xml up to date
2021.11.15 20:31:45.222 3: HM485: hmw_sen_sc_12_dr.xml up to date
2021.11.15 20:31:45.222 3: HM485: Loading available device files
2021.11.15 20:31:45.223 3: HM485: ==============================
2021.11.15 20:31:45.223 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_central.pm
2021.11.15 20:31:45.226 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_generic.pm
2021.11.15 20:31:45.228 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw14_dr.pm
2021.11.15 20:31:45.241 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr.pm
2021.11.15 20:31:45.256 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_V3_02.pm
2021.11.15 20:31:45.270 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_12_fm.pm
2021.11.15 20:31:45.285 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm.pm
2021.11.15 20:31:45.300 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_V3_02.pm
2021.11.15 20:31:45.314 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_sr_fm.pm
2021.11.15 20:31:45.329 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr.pm
2021.11.15 20:31:45.349 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_V3_02.pm
2021.11.15 20:31:45.369 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_dim1l_dr.pm
2021.11.15 20:31:45.389 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr.pm
2021.11.15 20:31:45.405 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_V3_02.pm
2021.11.15 20:31:45.420 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_sen_sc_12_dr.pm
2021.11.15 20:31:46.775 3: UPDATE_FTUI: Defined with URL https://raw.githubusercontent.com/knowthelist/fhem-tablet-ui/master/controls_fhemtabletui.txt and interval 86400 featurelevel 6.1
2021.11.15 20:31:47.648 3: Pollenflug: Defined with URL http://www.donnerwetter.de/pollenflug/region.hts?plz=88483&PTag=0 and interval 3600 featurelevel 6.1
2021.11.15 20:31:49.283 3: Opening my_callmonitor device 192.168.178.1:1012
2021.11.15 20:31:49.291 3: FB_CALLMONITOR (my_callmonitor) - loading cache file ./log/my_callmonitor.txt
2021.11.15 20:31:49.293 2: FB_CALLMONITOR (my_callmonitor) - read 35 contacts from Cache
2021.11.15 20:31:54.077 3: ArduinoNano_Zisterne: Defined with URL http://192.168.178.45/ and interval 61 featurelevel 6.1
2021.11.15 20:31:54.377 3: LaCrosse_Kueche: I/O device is myJeeLink1
2021.11.15 20:31:54.394 3: LaCrosse_Bad_EG: I/O device is myJeeLink1
2021.11.15 20:31:54.658 3: MQTT2_FHEM_Server: port 1883 opened
2021.11.15 20:31:58.333 1: HMCCU [myHMCCU3] CCU port 8181 is not reachable
2021.11.15 20:31:58.335 1: HMCCU [myHMCCU3] Initialized version 5.0 213171649
2021.11.15 20:31:58.335 1: HMCCU [myHMCCU3] Scheduling delayed initialization in 180 seconds
2021.11.15 20:31:58.342 3: myHMCCU3: unknown attribute rpcinterfaces. Type 'attr myHMCCU3 ?' for a detailed list.
2021.11.15 20:31:58.578 3: HMCCUDEV [Licht_BadOG_Spiegel] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:31:59.237 3: freezemon defined myFreezemon freezemon
2021.11.15 20:31:59.239 0: [Freezemon] myFreezemon: Unwrapping CallFn
2021.11.15 20:31:59.240 0: [Freezemon] myFreezemon: Unwrapping AnalyzeCommand
2021.11.15 20:31:59.240 0: [Freezemon] myFreezemon: Unwrapping HttpUtils_NonblockingGet
2021.11.15 20:31:59.240 0: [Freezemon] myFreezemon: Unwrapping Log3
2021.11.15 20:31:59.241 3: [Freezemon] myFreezemon: Wrapping Log3
2021.11.15 20:31:59.398 3: [SamsungAV] SamsungQ85 defined with host: 192.168.178.37 port: 8001
2021.11.15 20:31:59.616 3: NotdienstApotheke: interval is 0, no periodic updates will done.
2021.11.15 20:31:59.616 3: NotdienstApotheke: Defined with URL https://apothekenfinder.mobi/interface/json.php?device=web&source=not&search=88483 featurelevel 6.1
2021.11.15 20:32:01.145 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CCU not ready. Trying later ...
2021.11.15 20:32:01.151 2: HMCCURPCPROC [d_rpc178026HmIP_RF] CCU not ready. Trying later ...
2021.11.15 20:32:01.224 3: Modul 90_Jalousie.pm: Init Done with Version V 0.00.09 von gevoo - 18.12.2015 modifiziert JG
2021.11.15 20:32:01.225 3: Name = Jal_KU_Fenster, Parameter = Jalousie Jal_KU_Fenster_03 39 2
2021.11.15 20:32:01.225 1: Jalousie mit Rolloaktor Jal_KU_Fenster_03 verbunden
2021.11.15 20:32:01.227 3: Name = Jal_KU_Sued, Parameter = Jalousie Jal_KU_Sued_03 64 2
2021.11.15 20:32:01.228 1: Jalousie mit Rolloaktor Jal_KU_Sued_03 verbunden
2021.11.15 20:32:01.230 3: Name = Jal_WZ_Fest_Ost, Parameter = Jalousie Jal_WZ_Fest_Ost_03 64 2
2021.11.15 20:32:01.230 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Ost_03 verbunden
2021.11.15 20:32:01.232 3: Name = Jal_WZ_Fest_Sued, Parameter = Jalousie Jal_WZ_Fest_Sued_03 64 2
2021.11.15 20:32:01.232 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Sued_03 verbunden
2021.11.15 20:32:01.234 3: Name = Jal_WZ_Schiebetuer, Parameter = Jalousie Jal_WZ_Schiebetuer_03 64 2
2021.11.15 20:32:01.234 1: Jalousie mit Rolloaktor Jal_WZ_Schiebetuer_03 verbunden
2021.11.15 20:32:01.236 3: Name = Jal_WZ_SuedWest, Parameter = Jalousie Jal_WZ_Fest_SuedWest_03 64 2
2021.11.15 20:32:01.236 1: Jalousie mit Rolloaktor Jal_WZ_Fest_SuedWest_03 verbunden
2021.11.15 20:32:01.238 3: Name = Jal_WZ_West, Parameter = Jalousie Jal_WZ_Fest_West_03 64 2
2021.11.15 20:32:01.238 1: Jalousie mit Rolloaktor Jal_WZ_Fest_West_03 verbunden
2021.11.15 20:32:02.180 3: HMCCUCHN [Alarm_KueOst_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.229 3: HMCCUCHN [Alarm_KueOst_HmIP] Invalid value STATE for attribute statedatapoint
2021.11.15 20:32:02.245 3: HMCCUCHN [Alarm_KueSued_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.278 3: HMCCUCHN [Alarm_KueSued_HmIP] Invalid value STATE for attribute statedatapoint
2021.11.15 20:32:02.288 3: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.324 3: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.360 3: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.400 3: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.440 3: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.479 3: HMCCUDEV [HmIP_BDT_0008DA49929255_3] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.554 3: HMCCUCHN [Heiz_BadOG_Handtuch_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.15 20:32:02.614 2: HMCCURPCPROC [d_rpc178026VirtualDevices] CCU not ready. Trying later ...
2021.11.15 20:32:02.618 1: Including ./log/fhem.save
2021.11.15 20:32:04.497 3: Opening myHMUARTGPIO device 192.168.178.53:4001
2021.11.15 20:32:04.499 1: CUL_HM start inital cleanup
2021.11.15 20:32:06.582 1: CUL_HM finished initial cleanupkern.log:
[code]Nov 15 13:35:44 Raspi043BPlus kernel: [ 65.265759] eq3loop: eq3loop_open_slave() mmd_hmip
Nov 15 20:20:08 Raspi043BPlus kernel: [24328.212056] INFO: task kworker/1:2:19649 blocked for more than 122 seconds.
Nov 15 20:20:09 Raspi043BPlus kernel: [24328.212081] Tainted: G C O 5.10.17-v7+ #1421
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212094] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212107] task:kworker/1:2 state:D stack: 0 pid:19649 ppid: 2 flags:0x00000000
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212173] Backtrace:
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212207] [<809ed8f0>] (__schedule) from [<809ee2c8>] (schedule+0x68/0xe4)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212232] r10:82249800 r9:ffffe000 r8:00000000 r7:00000000 r6:60000113 r5:a3b84d80
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212244] r4:ffffe000
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212263] [<809ee260>] (schedule) from [<807fabd0>] (__mmc_claim_host+0xe0/0x238)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212277] r5:82249a18 r4:00000002
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212295] [<807faaf0>] (__mmc_claim_host) from [<807fad60>] (mmc_get_card+0x38/0x3c)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212313] r10:00000000 r9:00000000 r8:00000040 r7:b6b42c00 r6:82249a18 r5:00000000
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212324] r4:8224a800
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212344] [<807fad28>] (mmc_get_card) from [<8080499c>] (mmc_sd_detect+0x24/0x7c)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212357] r5:82249800 r4:82249800
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212377] [<80804978>] (mmc_sd_detect) from [<807fd5bc>] (mmc_rescan+0xdc/0x3b0)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212390] r5:82249800 r4:82249a7c
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212413] [<807fd4e0>] (mmc_rescan) from [<8013b980>] (process_one_work+0x250/0x5a0)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212431] r9:00000000 r8:00000040 r7:b6b42c00 r6:b6b3f640 r5:a3ad1880 r4:82249a7c
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212450] [<8013b730>] (process_one_work) from [<8013bd30>] (worker_thread+0x60/0x5c4)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212469] r10:b6b3f640 r9:80e03d00 r8:b6b3f658 r7:00000008 r6:b6b3f640 r5:a3ad1894
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212482] r4:a3ad1880
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212504] [<8013bcd0>] (worker_thread) from [<801437b8>] (kthread+0x170/0x174)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212532] r10:8465be74 r9:a3ad1880 r8:8013bcd0 r7:85e5c000 r6:00000000 r5:b0c55b00
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212545] r4:847fde80
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212564] [<80143648>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212577] Exception stack(0x85e5dfb0 to 0x85e5dff8)
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212593] dfa0: 00000000 00000000 00000000 00000000
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212613] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212628] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212646] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143648
Nov 15 20:20:10 Raspi043BPlus kernel: [24328.212658] r4:b0c55b00
Nov 15 20:22:10 Raspi043BPlus kernel: [24451.092319] Tainted: G C O 5.10.17-v7+ #1421
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092331] task:kworker/1:2 state:D stack: 0 pid:19649 ppid: 2 flags:0x00000000
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092374] Backtrace:
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092403] r10:82249800 r9:ffffe000 r8:00000000 r7:00000000 r6:60000113 r5:a3b84d80
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092419] [<809ee260>] (schedule) from [<807fabd0>] (__mmc_claim_host+0xe0/0x238)
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092436] [<807faaf0>] (__mmc_claim_host) from [<807fad60>] (mmc_get_card+0x38/0x3c)
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092451] r4:8224a800
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092469] r5:82249800 r4:82249800
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092487] r5:82249800 r4:82249a7c
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092510] r9:00000000 r8:00000040 r7:b6b42c00 r6:b6b3f640 r5:a3ad1880 r4:82249a7c
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092531] r10:b6b3f640 r9:80e03d00 r8:b6b3f658 r7:00000008 r6:b6b3f640 r5:a3ad1894
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092548] [<8013bcd0>] (worker_thread) from [<801437b8>] (kthread+0x170/0x174)
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092563] r4:847fde80
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092573] [<80143648>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28)
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092579] Exception stack(0x85e5dfb0 to 0x85e5dff8)
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092588] dfa0: 00000000 00000000 00000000 00000000
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092597] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092606] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092615] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143648
Nov 15 20:22:11 Raspi043BPlus kernel: [24451.092621] r4:b0c55b00
Nov 15 20:24:14 Raspi043BPlus kernel: [24573.972638] INFO: task kworker/1:2:19649 blocked for more than 368 seconds.
Nov 15 20:24:19 Raspi043BPlus kernel: [24573.972669] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 15 20:24:22 Raspi043BPlus kernel: [24573.972724] Workqueue: events_freezable mmc_rescan
Nov 15 20:24:23 Raspi043BPlus kernel: [24573.972773] [<809ed8f0>] (__schedule) from [<809ee2c8>] (schedule+0x68/0xe4)
Nov 15 20:24:25 Raspi043BPlus kernel: [24573.972801] r4:ffffe000
Nov 15 20:24:27 Raspi043BPlus kernel: [24573.972830] r5:82249a18 r4:00000002
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.972866] r10:00000000 r9:00000000 r8:00000040 r7:b6b42c00 r6:82249a18 r5:00000000
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.972893] [<807fad28>] (mmc_get_card) from [<8080499c>] (mmc_sd_detect+0x24/0x7c)
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.972932] [<80804978>] (mmc_sd_detect) from [<807fd5bc>] (mmc_rescan+0xdc/0x3b0)
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.972966] [<807fd4e0>] (mmc_rescan) from [<8013b980>] (process_one_work+0x250/0x5a0)
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973000] [<8013b730>] (process_one_work) from [<8013bd30>] (worker_thread+0x60/0x5c4)
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973026] r4:a3ad1880
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973060] r10:8465be74 r9:a3ad1880 r8:8013bcd0 r7:85e5c000 r6:00000000 r5:b0c55b00
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973086] [<80143648>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28)
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973113] dfa0: 00000000 00000000 00000000 00000000
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973128] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973143] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973158] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143648
Nov 15 20:24:28 Raspi043BPlus kernel: [24573.973168] r4:b0c55b00
Nov 15 20:26:17 Raspi043BPlus kernel: [24696.852917] INFO: task kworker/1:2:19649 blocked for more than 491 seconds.
Nov 15 20:26:21 Raspi043BPlus kernel: [24696.852943] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 15 20:26:25 Raspi043BPlus kernel: [24696.852995] Workqueue: events_freezable mmc_rescan
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853039] [<809ed8f0>] (__schedule) from [<809ee2c8>] (schedule+0x68/0xe4)
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853064] r4:ffffe000
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853091] r5:82249a18 r4:00000002
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853121] r10:00000000 r9:00000000 r8:00000040 r7:b6b42c00 r6:82249a18 r5:00000000
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853147] [<807fad28>] (mmc_get_card) from [<8080499c>] (mmc_sd_detect+0x24/0x7c)
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853171] [<80804978>] (mmc_sd_detect) from [<807fd5bc>] (mmc_rescan+0xdc/0x3b0)
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853199] [<807fd4e0>] (mmc_rescan) from [<8013b980>] (process_one_work+0x250/0x5a0)
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853233] [<8013b730>] (process_one_work) from [<8013bd30>] (worker_thread+0x60/0x5c4)
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853256] r4:a3ad1880
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853287] r10:8465be74 r9:a3ad1880 r8:8013bcd0 r7:85e5c000 r6:00000000 r5:b0c55b00
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853312] [<80143648>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28)
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853333] dfa0: 00000000 00000000 00000000 00000000
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853348] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853361] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853375] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143648
Nov 15 20:26:26 Raspi043BPlus kernel: [24696.853384] r4:b0c55b00
Nov 15 20:28:19 Raspi043BPlus kernel: [24819.733199] Tainted: G C O 5.10.17-v7+ #1421
Nov 15 20:28:21 Raspi043BPlus kernel: [24819.733212] task:kworker/1:2 state:D stack: 0 pid:19649 ppid: 2 flags:0x00000000
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733253] Backtrace:
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733283] r10:82249800 r9:ffffe000 r8:00000000 r7:00000000 r6:60000113 r5:a3b84d80
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733299] [<809ee260>] (schedule) from [<807fabd0>] (__mmc_claim_host+0xe0/0x238)
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733315] [<807faaf0>] (__mmc_claim_host) from [<807fad60>] (mmc_get_card+0x38/0x3c)
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733330] r4:8224a800
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733348] r5:82249800 r4:82249800
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733366] r5:82249800 r4:82249a7c
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733388] r9:00000000 r8:00000040 r7:b6b42c00 r6:b6b3f640 r5:a3ad1880 r4:82249a7c
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733408] r10:b6b3f640 r9:80e03d00 r8:b6b3f658 r7:00000008 r6:b6b3f640 r5:a3ad1894
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733424] [<8013bcd0>] (worker_thread) from [<801437b8>] (kthread+0x170/0x174)
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733439] r4:847fde80
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733450] [<80143648>] (kthread) from [<801000ec>] (ret_from_fork+0x14/0x28)
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733457] Exception stack(0x85e5dfb0 to 0x85e5dff8)
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733465] dfa0: 00000000 00000000 00000000 00000000
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733474] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733482] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733491] r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:80143648
Nov 15 20:28:22 Raspi043BPlus kernel: [24819.733497] r4:b0c55b00
Nov 15 20:30:22 Raspi043BPlus kernel: [24942.613495] INFO: task kworker/1:2:19649 blocked for more than 737 seconds.
Nov 15 20:30:28 Raspi043BPlus kernel: [24942.613506] Tainted: G C O 5.10.17-v7+ #1421
Nov 15 20:30:32 Raspi043BPlus kernel: [24942.613511] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 15 20:30:33 Raspi043BPlus kernel: [24942.613546] Workqueue: events_freezable mmc_rescan
Nov 15 20:30:34 Raspi043BPlus kernel: [24942.613575] [<809ed8f0>] (__schedule) from [<809ee2c8>] (schedule+0x68/0xe4)
Nov 15 20:30:39 Raspi043BPlus kernel: [24942.613593] r4:ffffe000
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Booting Linux on physical CPU 0x0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Linux version 5.10.17-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1421 SMP Thu May 27 13:59:01 BST 2021
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] CPU: div instructions available: patching division code
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Memory policy: Data cache writealloc
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Reserved memory: created CMA memory pool at 0x37400000, size 64 MiB
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Zone ranges:
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] DMA [mem 0x0000000000000000-0x000000003b3fffff]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Normal empty
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Movable zone start for each node
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Early memory node ranges
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] node 0: [mem 0x0000000000000000-0x000000003b3fffff]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000003b3fffff]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] On node 0 totalpages: 242688
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] DMA zone: 2133 pages used for memmap
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] DMA zone: 0 pages reserved
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] DMA zone: 242688 pages, LIFO batch:63
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] percpu: Embedded 20 pages/cpu s50700 r8192 d23028 u81920
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] pcpu-alloc: s50700 r8192 d23028 u81920 alloc=20*4096
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] pcpu-alloc:
- 0
- 1
- 2
- 3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 240555
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=tty1 root=PARTUUID=3de6e9d9-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Kernel parameter elevator= does not have any effect anymore.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Please use sysfs to set IO scheduler for individual devices.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Memory: 879832K/970752K available (9216K kernel code, 1311K rwdata, 2940K rodata, 1024K init, 860K bss, 25384K reserved, 65536K cma-reserved)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] ftrace: allocating 31910 entries in 63 pages
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] ftrace: allocated 63 pages with 6 groups
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] rcu: Hierarchical RCU implementation.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Rude variant of Tasks RCU enabled.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] Tracing variant of Tasks RCU enabled.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000008] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000025] Switching to timer-based delay loop, resolution 52ns
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.000314] Console: colour dummy device 80x30
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.001172] printk: console [tty1] enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.001244] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.001304] pid_max: default: 32768 minimum: 301
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.001536] LSM: Security Framework initializing
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.001794] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.001845] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.003467] Disabling memory control group subsystem
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.003605] CPU: Testing write buffer coherency: ok
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.004122] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.005376] Setting up static identity map for 0x100000 - 0x10003c
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.005585] rcu: Hierarchical SRCU implementation.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.006524] smp: Bringing up secondary CPUs ...
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.007735] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.009045] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.010411] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.010571] smp: Brought up 1 node, 4 CPUs
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.010627] SMP: Total of 4 processors activated (153.60 BogoMIPS).
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.010658] CPU: All CPU(s) started in HYP mode.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.010686] CPU: Virtualization extensions available.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.011700] devtmpfs: initialized
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.029236] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.029529] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.029590] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.032840] pinctrl core: initialized pinctrl subsystem
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.034054] NET: Registered protocol family 16
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.038335] DMA: preallocated 1024 KiB pool for atomic coherent allocations
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.044107] audit: initializing netlink subsys (disabled)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.044429] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.045032] thermal_sys: Registered thermal governor 'step_wise'
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.046001] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.046065] hw-breakpoint: maximum watchpoint size is 8 bytes.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.046363] Serial: AMBA PL011 UART driver
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.064912] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.080154] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-05-27T14:04:13, variant start
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.090165] raspberrypi-firmware soc:firmware: Firmware hash is 7d9a298cda813f747b51fe17e1e417e7bf5ca94d
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.138753] bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.141320] SCSI subsystem initialized
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.141592] usbcore: registered new interface driver usbfs
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.141692] usbcore: registered new interface driver hub
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.141795] usbcore: registered new device driver usb
Nov 15 19:17:05 Raspi043BPlus kernel: [ 0.143756] clocksource: Switched to clocksource arch_sys_counter
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.918362] VFS: Disk quotas dquot_6.6.0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.918512] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.918739] FS-Cache: Loaded
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.918996] CacheFiles: Loaded
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.929529] NET: Registered protocol family 2
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.930582] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.930771] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.930919] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.931134] TCP: Hash tables configured (established 8192 bind 8192)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.931332] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.931412] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.931888] NET: Registered protocol family 1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.932709] RPC: Registered named UNIX socket transport module.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.932744] RPC: Registered udp transport module.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.932774] RPC: Registered tcp transport module.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.932804] RPC: Registered tcp NFSv4.1 backchannel transport module.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.934617] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.938434] Initialise system trusted keyrings
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.938727] workingset: timestamp_bits=14 max_order=18 bucket_order=4
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.948378] zbud: loaded
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.950490] FS-Cache: Netfs 'nfs' registered for caching
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.951369] NFS: Registering the id_resolver key type
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.951440] Key type id_resolver registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.951471] Key type id_legacy registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.951647] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.952867] Key type asymmetric registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.952900] Asymmetric key parser 'x509' registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.952977] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.953018] io scheduler mq-deadline registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.953049] io scheduler kyber registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.956741] bcm2708_fb soc:fb: FB found 1 display(s)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.969058] Console: switching to colour frame buffer device 82x26
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.976260] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 656x416
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.985174] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.990076] bcm2835-rng 3f104000.rng: hwrng registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.993055] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 1.999136] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.016842] brd: module loaded
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.031621] loop: module loaded
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.035940] Loading iSCSI transport class v2.0-870.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.040262] libphy: Fixed MDIO Bus: probed
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.043181] usbcore: registered new interface driver lan78xx
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.045958] usbcore: registered new interface driver smsc95xx
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.048561] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.779369] Core Release: 2.80a
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.781837] Setting default values for core params
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.784367] Finished setting default values for core params
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.987283] Using Buffer DMA mode
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.989802] Periodic Transfer Interrupt Enhancement - disabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.992369] Multiprocessor Interrupt Enhancement - disabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.994927] OTG VER PARAM: 0, OTG VER FLAG: 0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 2.997388] Dedicated Tx FIFOs mode
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.000301]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.000322] WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = b7514000 dma = 0xf7514000 len=9024
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.007281] FIQ FSM acceleration enabled for :
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.007281] Non-periodic Split Transactions
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.007281] Periodic Split Transactions
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.007281] High-Speed Isochronous Endpoints
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.007281] Interrupt/Control Split Transaction hack enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.018176] dwc_otg: Microframe scheduler enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.018240]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.018250] WARN::hcd_init_fiq:457: FIQ on core 1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.022555]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.022564] WARN::hcd_init_fiq:458: FIQ ASM at 807be568 length 36
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.026994]
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.027003] WARN::hcd_init_fiq:497: MPHI regs_base at bb810000
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.031485] dwc_otg 3f980000.usb: DWC OTG Controller
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.033894] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.036279] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.038611] Init: Port Power? op_state=1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.040848] Init: Power Port (0)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.043374] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.048003] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.050467] usb usb1: Product: DWC OTG Controller
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.052829] usb usb1: Manufacturer: Linux 5.10.17-v7+ dwc_otg_hcd
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.055241] usb usb1: SerialNumber: 3f980000.usb
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.058357] hub 1-0:1.0: USB hub found
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.060792] hub 1-0:1.0: 1 port detected
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.064246] dwc_otg: FIQ enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.064259] dwc_otg: NAK holdoff enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.064271] dwc_otg: FIQ split-transaction FSM enabled
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.064289] Module dwc_common_port init
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.064618] usbcore: registered new interface driver usb-storage
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.067283] mousedev: PS/2 mouse device common for all mice
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.070880] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.076366] sdhci: Secure Digital Host Controller Interface driver
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.078910] sdhci: Copyright(c) Pierre Ossman
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.081989] mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.085324] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.088135] sdhci-pltfm: SDHCI platform and OF driver helper
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.092602] ledtrig-cpu: registered to indicate activity on CPUs
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.095659] hid: raw HID events driver (C) Jiri Kosina
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.098405] usbcore: registered new interface driver usbhid
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.101007] usbhid: USB HID core driver
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.108759] Initializing XFRM netlink socket
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.111373] NET: Registered protocol family 17
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.114045] Key type dns_resolver registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.117040] Registering SWP/SWPB emulation handler
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.119557] registered taskstats version 1
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.121894] Loading compiled-in X.509 certificates
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.125151] Key type ._fscrypt registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.127477] Key type .fscrypt registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.129801] Key type fscrypt-provisioning registered
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.144925] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.149118] mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.151514] mmc-bcm2835 3f300000.mmcnr: DMA channel allocated
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.180526] sdhost: log_buf @ (ptrval) (f7513000)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.221156] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.225137] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.228947] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.232600] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.237631] of_cfs_init
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.239844] of_cfs_init: OK
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.242688] Waiting for root device PARTUUID=3de6e9d9-02...
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.256625] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.273954] Indeed it is in host mode hprt0 = 00021501
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.344688] random: fast init done
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.385536] mmc0: host does not support reading read-only switch, assuming write-enable
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.394400] mmc0: new high speed SDXC card at address aaaa
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.397663] mmcblk0: mmc0:aaaa SD64G 59.5 GiB
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.404510] mmc1: new high speed SDIO card at address 0001
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.409381] mmcblk0: p1 p2
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.427795] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.430142] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.483844] usb 1-1: new high-speed USB device number 2 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.486411] Indeed it is in host mode hprt0 = 00001101
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.521135] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.543987] EXT4-fs (mmcblk0p2): 6 orphan inodes deleted
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.546381] EXT4-fs (mmcblk0p2): recovery complete
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.564979] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.569929] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.580676] devtmpfs: mounted
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.590721] Freeing unused kernel memory: 1024K
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.594254] Run /sbin/init as init process
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.596840] with arguments:
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.596852] /sbin/init
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.596863] with environment:
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.596874] HOME=/
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.596885] TERM=linux
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.724230] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.729589] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.733145] hub 1-1:1.0: USB hub found
Nov 15 19:17:05 Raspi043BPlus kernel: [ 3.736043] hub 1-1:1.0: 4 ports detected
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.053822] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.184161] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.189552] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.193237] hub 1-1.1:1.0: USB hub found
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.196173] hub 1-1.1:1.0: 3 ports detected
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.303916] usb 1-1.2: new full-speed USB device number 4 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.360838] NET: Registered protocol family 10
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.365124] Segment Routing with IPv6
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.438281] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.443894] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.446771] usb 1-1.2: Product: ConBee II
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.449631] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.449644] usb 1-1.2: SerialNumber: DE2439922
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.553835] usb 1-1.1.2: new full-speed USB device number 5 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.714669] usb 1-1.1.2: New USB device found, idVendor=0403, idProduct=6f70, bcdDevice= 6.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.720582] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.727033] usb 1-1.1.2: Product: HB-RF-USB
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.730477] usb 1-1.1.2: Manufacturer: Alexander Reinert
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.733580] usb 1-1.1.2: SerialNumber: A93C9AVJ
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.783846] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.941045] usb 1-1.3: New USB device found, idVendor=03eb, idProduct=204b, bcdDevice= 0.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.946706] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.949663] usb 1-1.3: Product: CUL868
Nov 15 19:17:05 Raspi043BPlus kernel: [ 4.952492] usb 1-1.3: Manufacturer: busware.de
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.023838] usb 1-1.1.3: new full-speed USB device number 7 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.191423] usb 1-1.1.3: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.196844] usb 1-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.202451] usb 1-1.1.3: Product: FT232R USB UART
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.205329] usb 1-1.1.3: Manufacturer: FTDI
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.208101] usb 1-1.1.3: SerialNumber: AL014JZA
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.442459] random: systemd: uninitialized urandom read (16 bytes read)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.459418] random: systemd: uninitialized urandom read (16 bytes read)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.470427] random: systemd: uninitialized urandom read (16 bytes read)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.514006] usb 1-1.1.1: new high-speed USB device number 8 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.644579] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.649267] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.920823] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.923140] libphy: lan78xx-mdiobus: probed
Nov 15 19:17:05 Raspi043BPlus kernel: [ 5.951563] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
Nov 15 19:17:05 Raspi043BPlus kernel: [ 6.463300] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.594971] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.598239] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.598268] [vc_sm_connected_init]: start
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.601141] [vc_sm_connected_init]: installed successfully
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.606665] generic_raw_uart: loading out-of-tree module taints kernel.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.608847] mc: Linux media interface: v0.10
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.625749] pl011_raw_uart 3f201000.serial: there is not valid maps for state default
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.625960] pl011_raw_uart 3f201000.serial: I2C adapter of configured RTC device is not yet initialized
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.625976] pl011_raw_uart 3f201000.serial: failed to initialize generic_raw_uart module
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.679721] videodev: Linux video capture interface: v2.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.712122] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.714429] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.718976] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.726510] bcm2835_audio bcm2835_audio: card created with 8 channels
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.727046] pl011_raw_uart 3f201000.serial: there is not valid maps for state default
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.727278] pl011_raw_uart 3f201000.serial: I2C adapter of configured RTC device is not yet initialized
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.727296] pl011_raw_uart 3f201000.serial: failed to initialize generic_raw_uart module
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.729234] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.751160] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.758972] pl011_raw_uart 3f201000.serial: there is not valid maps for state default
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.759164] pl011_raw_uart 3f201000.serial: Missing I2C driver of rtc device, trying to load
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.759183] pl011_raw_uart 3f201000.serial: Requesting module i2c:rx8130-legacy
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.771103] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.771758] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.773101] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.773509] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.773543] bcm2835-isp bcm2835-isp: Register output node 0 with media controller
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.773569] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.773606] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.773628] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.777043] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.777416] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.793062] rtc-rx8130 1-0032: Unable to read registers #28..#30
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.793088] i2c i2c-1: probing for rx8130 failed
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.793124] rtc-rx8130: probe of 1-0032 failed with error -121
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.795551] usb 1-1.2: USB disconnect, device number 4
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.795901] rtc-rx8130 1-0032: Unable to read registers #28..#30
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.795919] i2c i2c-1: probing for rx8130 failed
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.795955] rtc-rx8130: probe of 1-0032 failed with error -121
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.825754] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.825939] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.863082] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.863155] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.871518] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.871572] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
Nov 15 19:17:05 Raspi043BPlus kernel: [ 7.998531] cfg80211: Loading compiled-in X.509 certificates for regulatory database
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.003976] pl011_raw_uart 3f201000.serial: Initialized pl011 device; mapbase=0x3f201000; irq=114; clockrate=47999625
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.093851] usb 1-1.2: new full-speed USB device number 9 using dwc_otg
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.135319] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.214869] brcmfmac: F1 signature read @0x18000000=0x15264345
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.228698] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.230620] usbcore: registered new interface driver brcmfmac
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.232539] usb 1-1.2: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.232566] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.232583] usb 1-1.2: Product: ConBee II
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.232598] usb 1-1.2: Manufacturer: dresden elektronik ingenieurtechnik GmbH
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.232613] usb 1-1.2: SerialNumber: DE2439922
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.277301] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.419396] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.430582] cdc_acm 1-1.2:1.0: ttyACM1: USB ACM device
Nov 15 19:17:05 Raspi043BPlus kernel: [ 8.436526] usbcore: registered
Hast Du vorher ein Reboot gemacht? Das kern.log ist deutlich kürzer (hört nach ~7 Sekunden auf) als das Vorheriere.
Keinen Reboot, aber nicht alles kopiert. Fehler?
Heute Nacht wieder Absturz. Anbei die kompletten Logs. Vieleicht kannst Du was erkennen, ich leider nicht.
Das FHEM-Log. Scheint so, als ob die Probleme irgendwann um 05:21 angefangen haben.
2021.11.16 05:15:00.858 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:15:02.795 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:15:03.937 3: UWZ Unwetterzentrale: UWZ.1811 Done fetching data
2021.11.16 05:15:04.156 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:16:27.504 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:16:27.574 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:16:28.953 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:17:07.420 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:18:51.216 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:18:52.720 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:18:53.261 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:18:53.277 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:18:54.855 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:20:05.749 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:20:28.051 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:20:29.499 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:04.076 3: UWZ Unwetterzentrale: UWZ.1811 Done fetching data
2021.11.16 05:21:11.561 1: FRITZBOX FritzBox7530: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
2021.11.16 05:21:27.326 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:27.625 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:28.688 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:32.613 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:34.072 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:52.441 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:21:54.018 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:22:01.006 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:22:01.469 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:22:02.206 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:22:23.251 3: CUL_HM set HM_572922_Sw_02 statusRequest noArg
2021.11.16 05:22:26.002 3: CUL_HM set de_Bad_OG_Licht_Spiegel statusRequest noArg
2021.11.16 05:22:49.647 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:23:22.237 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:23:22.446 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:23:23.700 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:24:55.504 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:24:56.942 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:24:57.248 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:38:34.393 2: autocreate: define MQTT2_rpi02 MQTT2_DEVICE rpi02 MQTT2_FHEM_Server
2021.11.16 05:38:34.514 2: autocreate: define FileLog_MQTT2_rpi02 FileLog ./log/MQTT2_rpi02-%Y.log MQTT2_rpi02
2021.11.16 05:39:10.871 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:39:11.118 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 05:39:11.365 2: HMCCURPCPROC [d_rpc178026BidCos_RF] Received no events from interface CB2001178092178026 for 614.167011976242 seconds
2021.11.16 05:39:11.366 2: HMCCU [myHMCCU3] Reconnecting to CCU
2021.11.16 05:39:11.413 2: HMCCURPCPROC [d_rpc178026BidCos_RF] Registering callback http://192.168.178.92:7411/fh2001 of type A with ID CB2001178092178026 at http://192.168.178.26:2001
2021.11.16 05:39:12.403 2: HMCCURPCPROC [d_rpc178026HmIP_RF] Registering callback http://192.168.178.92:7420/fh2010 of type A with ID CB2010178092178026 at http://192.168.178.26:2010
2021.11.16 05:39:12.525 2: HMCCURPCPROC [d_rpc178026VirtualDevices] Registering callback http://192.168.178.92:14702/fh9292 of type A with ID CB9292178092178026 at http://192.168.178.26:9292/groups
2021.11.16 05:39:12.581 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CB2001178092178026 NewDevice received 52 device and channel specifications
2021.11.16 05:39:13.731 2: HMCCURPCPROC [d_rpc178026VirtualDevices] CB9292178092178026 NewDevice received 16 device and channel specifications
2021.11.16 05:39:22.902 1: 192.168.178.47:1000 disconnected, waiting to reappear (HM485_LAN)
2021.11.16 05:39:23.272 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed (peer: 192.168.178.52)
2021.11.16 06:35:39.536 2: PRESENCE (HASH(0x7149730)) - scan aboart
2021.11.16 06:35:40.191 1: ERROR: empty name in readingsBeginUpdate
2021.11.16 06:35:40.191 1: stacktrace:
2021.11.16 06:35:40.274 1: main::readingsBeginUpdate called by fhem.pl (5091)
2021.11.16 06:35:40.329 1: main::readingsSingleUpdate called by ./FHEM/73_PRESENCE.pm (861)
2021.11.16 06:35:40.330 1: main::PRESENCE_daemonAbortedScan called by FHEM/Blocking.pm (144)
2021.11.16 06:35:40.330 1: main::BlockingStart called by FHEM/Blocking.pm (107)
2021.11.16 06:35:40.331 1: main::BlockingCall called by ./FHEM/42_SYSMON.pm (916)
2021.11.16 06:35:40.331 1: main::SYSMON_Update called by fhem.pl (3427)
2021.11.16 06:35:40.331 1: main::HandleTimeout called by fhem.pl (695)
2021.11.16 06:35:40.487 1: PERL WARNING: Use of uninitialized value $name in concatenation (.) or string at fhem.pl line 4945.
2021.11.16 06:35:40.627 1: readingsUpdate(,daemonAboartCnt,1) missed to call readingsBeginUpdate first.
2021.11.16 06:35:40.627 1: stacktrace:
2021.11.16 06:35:40.628 1: main::readingsBulkUpdate called by fhem.pl (5092)
2021.11.16 06:35:40.628 1: main::readingsSingleUpdate called by ./FHEM/73_PRESENCE.pm (861)
2021.11.16 06:35:40.628 1: main::PRESENCE_daemonAbortedScan called by FHEM/Blocking.pm (144)
2021.11.16 06:35:40.628 1: main::BlockingStart called by FHEM/Blocking.pm (107)
2021.11.16 06:35:40.629 1: main::BlockingCall called by ./FHEM/42_SYSMON.pm (916)
2021.11.16 06:35:40.629 1: main::SYSMON_Update called by fhem.pl (3427)
2021.11.16 06:35:40.629 1: main::HandleTimeout called by fhem.pl (695)
2021.11.16 06:35:40.630 1: PERL WARNING: Use of uninitialized value $d in hash element at fhem.pl line 4681.
2021.11.16 06:35:40.630 1: PERL WARNING: Use of uninitialized value $dev in hash element at fhem.pl line 3764.
2021.11.16 06:55:57.551 1: Error: >HASH(0x7149730)< has no TYPE, but following keys: >READINGS,helper<
2021.11.16 07:06:35.833 1: Including fhem.cfg
2021.11.16 07:06:35.903 3: telnetPort: port 7072 opened
2021.11.16 07:06:36.649 3: WEB: port 8083 opened
2021.11.16 07:06:36.660 3: WEBS: port 8084 opened
2021.11.16 07:06:37.998 2: Registering GEOFANCY geofancy for URL /geo...
2021.11.16 07:06:38.048 3: WEBhook: port 8088 opened
2021.11.16 07:06:38.661 2: eventTypes: loaded 10047 lines from ./log/eventTypes.txt
2021.11.16 07:06:38.704 3: Opening CUL_0 device /dev/serial/by-id/usb-busware.de_CUL868-if00
2021.11.16 07:06:38.756 3: Setting CUL_0 serial parameters to 9600,8,N,1
2021.11.16 07:06:38.865 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2021.11.16 07:06:38.870 3: CUL_0 device opened
2021.11.16 07:06:38.879 2: Switched CUL_0 rfmode to HomeMatic
2021.11.16 07:06:39.513 3: additional HM config file loaded: ./FHEM/HMConfig_SenTHPL.pm
2021.11.16 07:06:39.704 3: Opening myJeeLink1 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL014JZA-if00-port0
2021.11.16 07:06:39.707 3: Setting myJeeLink1 serial parameters to 57600,8,N,1
2021.11.16 07:06:40.716 3: myJeeLink1 device opened
2021.11.16 07:06:41.987 3: TABLETUI: new ext defined infix:ftui/: dir:./www/tablet/:
2021.11.16 07:06:41.987 3: Registering HTTPSRV TABLETUI for URL /ftui and assigned link ftui/ ...
2021.11.16 07:06:42.402 3: HM485: HM485: Converting device files
2021.11.16 07:06:42.403 3: HM485: ==============================
2021.11.16 07:06:42.404 3: HM485: hmw_central.xml up to date
2021.11.16 07:06:42.405 3: HM485: hmw_generic.xml up to date
2021.11.16 07:06:42.405 3: HM485: hmw_io12_sw14_dr.xml up to date
2021.11.16 07:06:42.405 3: HM485: hmw_io12_sw7_dr.xml up to date
2021.11.16 07:06:42.406 3: HM485: hmw_io12_sw7_dr_V3_02.xml up to date
2021.11.16 07:06:42.406 3: HM485: hmw_io_12_fm.xml up to date
2021.11.16 07:06:42.406 3: HM485: hmw_io_4_fm.xml up to date
2021.11.16 07:06:42.406 3: HM485: hmw_io_4_fm_V3_02.xml up to date
2021.11.16 07:06:42.406 3: HM485: hmw_io_sr_fm.xml up to date
2021.11.16 07:06:42.407 3: HM485: hmw_lc_bl1_dr.xml up to date
2021.11.16 07:06:42.407 3: HM485: hmw_lc_bl1_dr_V3_02.xml up to date
2021.11.16 07:06:42.407 3: HM485: hmw_lc_dim1l_dr.xml up to date
2021.11.16 07:06:42.407 3: HM485: hmw_lc_sw2_dr.xml up to date
2021.11.16 07:06:42.408 3: HM485: hmw_lc_sw2_dr_V3_02.xml up to date
2021.11.16 07:06:42.408 3: HM485: hmw_sen_sc_12_dr.xml up to date
2021.11.16 07:06:42.408 3: HM485: Loading available device files
2021.11.16 07:06:42.408 3: HM485: ==============================
2021.11.16 07:06:42.408 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_central.pm
2021.11.16 07:06:42.412 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_generic.pm
2021.11.16 07:06:42.414 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw14_dr.pm
2021.11.16 07:06:42.429 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr.pm
2021.11.16 07:06:42.445 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_V3_02.pm
2021.11.16 07:06:42.463 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_12_fm.pm
2021.11.16 07:06:42.480 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm.pm
2021.11.16 07:06:42.496 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_V3_02.pm
2021.11.16 07:06:42.511 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_sr_fm.pm
2021.11.16 07:06:42.527 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr.pm
2021.11.16 07:06:42.551 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_V3_02.pm
2021.11.16 07:06:42.572 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_dim1l_dr.pm
2021.11.16 07:06:42.594 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr.pm
2021.11.16 07:06:42.612 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_V3_02.pm
2021.11.16 07:06:42.627 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_sen_sc_12_dr.pm
2021.11.16 07:06:44.122 3: UPDATE_FTUI: Defined with URL https://raw.githubusercontent.com/knowthelist/fhem-tablet-ui/master/controls_fhemtabletui.txt and interval 86400 featurelevel 6.1
2021.11.16 07:06:45.093 3: Pollenflug: Defined with URL http://www.donnerwetter.de/pollenflug/region.hts?plz=88483&PTag=0 and interval 3600 featurelevel 6.1
2021.11.16 07:06:46.814 3: Opening my_callmonitor device 192.168.178.1:1012
2021.11.16 07:06:46.824 3: FB_CALLMONITOR (my_callmonitor) - loading cache file ./log/my_callmonitor.txt
2021.11.16 07:06:46.826 2: FB_CALLMONITOR (my_callmonitor) - read 35 contacts from Cache
2021.11.16 07:06:51.706 3: ArduinoNano_Zisterne: Defined with URL http://192.168.178.45/ and interval 61 featurelevel 6.1
2021.11.16 07:06:52.019 3: LaCrosse_Kueche: I/O device is myJeeLink1
2021.11.16 07:06:52.038 3: LaCrosse_Bad_EG: I/O device is myJeeLink1
2021.11.16 07:06:52.319 3: MQTT2_FHEM_Server: port 1883 opened
2021.11.16 07:06:56.005 1: HMCCU [myHMCCU3] CCU port 8181 is not reachable
2021.11.16 07:06:56.007 1: HMCCU [myHMCCU3] Initialized version 5.0 213171649
2021.11.16 07:06:56.007 1: HMCCU [myHMCCU3] Scheduling delayed initialization in 180 seconds
2021.11.16 07:06:56.014 3: myHMCCU3: unknown attribute rpcinterfaces. Type 'attr myHMCCU3 ?' for a detailed list.
2021.11.16 07:06:56.212 3: HMCCUDEV [Licht_BadOG_Spiegel] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:56.815 3: freezemon defined myFreezemon freezemon
2021.11.16 07:06:56.817 0: [Freezemon] myFreezemon: Unwrapping CallFn
2021.11.16 07:06:56.817 0: [Freezemon] myFreezemon: Unwrapping AnalyzeCommand
2021.11.16 07:06:56.818 0: [Freezemon] myFreezemon: Unwrapping HttpUtils_NonblockingGet
2021.11.16 07:06:56.818 0: [Freezemon] myFreezemon: Unwrapping Log3
2021.11.16 07:06:56.819 3: [Freezemon] myFreezemon: Wrapping Log3
2021.11.16 07:06:56.954 3: [SamsungAV] SamsungQ85 defined with host: 192.168.178.37 port: 8001
2021.11.16 07:06:57.203 3: NotdienstApotheke: interval is 0, no periodic updates will done.
2021.11.16 07:06:57.204 3: NotdienstApotheke: Defined with URL https://apothekenfinder.mobi/interface/json.php?device=web&source=not&search=88483 featurelevel 6.1
2021.11.16 07:06:58.677 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CCU not ready. Trying later ...
2021.11.16 07:06:58.684 2: HMCCURPCPROC [d_rpc178026HmIP_RF] CCU not ready. Trying later ...
2021.11.16 07:06:58.775 3: Modul 90_Jalousie.pm: Init Done with Version V 0.00.09 von gevoo - 18.12.2015 modifiziert JG
2021.11.16 07:06:58.776 3: Name = Jal_KU_Fenster, Parameter = Jalousie Jal_KU_Fenster_03 39 2
2021.11.16 07:06:58.776 1: Jalousie mit Rolloaktor Jal_KU_Fenster_03 verbunden
2021.11.16 07:06:58.779 3: Name = Jal_KU_Sued, Parameter = Jalousie Jal_KU_Sued_03 64 2
2021.11.16 07:06:58.779 1: Jalousie mit Rolloaktor Jal_KU_Sued_03 verbunden
2021.11.16 07:06:58.782 3: Name = Jal_WZ_Fest_Ost, Parameter = Jalousie Jal_WZ_Fest_Ost_03 64 2
2021.11.16 07:06:58.783 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Ost_03 verbunden
2021.11.16 07:06:58.785 3: Name = Jal_WZ_Fest_Sued, Parameter = Jalousie Jal_WZ_Fest_Sued_03 64 2
2021.11.16 07:06:58.786 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Sued_03 verbunden
2021.11.16 07:06:58.789 3: Name = Jal_WZ_Schiebetuer, Parameter = Jalousie Jal_WZ_Schiebetuer_03 64 2
2021.11.16 07:06:58.789 1: Jalousie mit Rolloaktor Jal_WZ_Schiebetuer_03 verbunden
2021.11.16 07:06:58.792 3: Name = Jal_WZ_SuedWest, Parameter = Jalousie Jal_WZ_Fest_SuedWest_03 64 2
2021.11.16 07:06:58.793 1: Jalousie mit Rolloaktor Jal_WZ_Fest_SuedWest_03 verbunden
2021.11.16 07:06:58.795 3: Name = Jal_WZ_West, Parameter = Jalousie Jal_WZ_Fest_West_03 64 2
2021.11.16 07:06:58.796 1: Jalousie mit Rolloaktor Jal_WZ_Fest_West_03 verbunden
2021.11.16 07:06:59.583 3: HMCCUCHN [Alarm_KueOst_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.628 3: HMCCUCHN [Alarm_KueSued_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.662 3: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.697 3: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.732 3: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.767 3: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.802 3: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.837 3: HMCCUDEV [HmIP_BDT_0008DA49929255_3] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.913 3: HMCCUCHN [Heiz_BadOG_Handtuch_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 07:06:59.974 2: HMCCURPCPROC [d_rpc178026VirtualDevices] CCU not ready. Trying later ...
2021.11.16 07:06:59.977 1: Including ./log/fhem.save
2021.11.16 07:07:01.896 3: Opening myHMUARTGPIO device 192.168.178.53:4001
2021.11.16 07:07:01.898 1: CUL_HM start inital cleanup
2021.11.16 07:07:03.839 1: CUL_HM finished initial cleanup
2021.11.16 07:07:03.913 3: monitoring (Activity_monitoring) set Activity_monitoring active
2021.11.16 07:07:04.095 3: monitoring (Batterie_monitoring) set Batterie_monitoring active
2021.11.16 07:07:04.183 3: [SamsungAV] device SamsungQ85 initialising....
Das sieht doch eher nach einem hardwareproblem aus, oder?
Die letzte Zeit habe ich doch einiges geändert (HMCCU hatte ein Update, das einige Änderungen erforderte), PRESENCE habe ich eine Version von martinp876 eingespielt, die weniger Wartezeiten verursachen soll...
Hoffe wir finden die Ursache.
Gruß Jürgen
Ich sehe viel zu häufig den oom (OutOfMemory) Killer und auch sonstige Speichermangel Meldungen.
Wie schon mal gesagt:
- hast Du die Anzahl von Forks in FHEM begrenzt?
- Was läuft (abgesehen von FHEM) noch auf dem Rechner?
Insofern Hardwareproblem, das Du mit dem System einfach an die Speichergrenze des PIs kommst
Ich sehe da auch Netzwerkprobleme:
[myHMCCU3] CCU port 8181 is not reachable
2021.11.16 05:21:11.561 1: FRITZBOX FritzBox7530: Readout_Aborted.1931 Error: Timeout when reading Fritz!Box data.
Ich nehme an, die Fritzbox ist Dein Router. Das würde mir schon zu denken geben ...
Hatte gestern die Forks mit global BlockingCallMax auf 16 gestellt, aber heute Nacht war wieder ein Absturz. Was ist denn ein empfehlenswerter Wertt dafür?
Was läuft zu FHEM sonst noch?
Jeelink
zigbee2mqtt mit einem ConbeeII-Stick
Tablet-UI für Anzeige auf einem Tablet
HM485 wired für Ansteuerung Jalousien mit Interface eQ3-HMW-LGW
HmIP mit einer Hardware von Alexander Reiner
piVCCU
VCCU
MQTT2-Server für Shellys, Datenübertragung zu anderem RPI
Datenübertragung über MQTT2 von einem anderen Pi (ebusd, 1wire...)
Homemode-Modul
Residents-Modul, Roommate-Modul
@zap: Am Netzwerk wurde nichts verändert. Kann das nicht daher kommen, dass FHEM zu lange blockiert war und deswegen in einen TimeOut beid er Abfrage von Router und HMCCU gelaufen ist?
Nach einem reboot sieht es so aus:
pi@Raspi043BPlus:~ $ free
total used free shared buff/cache available
Mem: 945364 335348 251656 13388 358360 544184
Swap: 102396 0 102396
vorher waren nur 65 GB frei angezeigt.
Noch eine Ergänzung. Nach dem Neustart von FHEM scheint HMCCU nicht schnell genug zu starten und es kommen Fehlermeldungen.
2021.11.16 10:14:23.612 1: Including fhem.cfg
2021.11.16 10:14:23.697 3: telnetPort: port 7072 opened
2021.11.16 10:14:24.528 3: WEB: port 8083 opened
2021.11.16 10:14:24.540 3: WEBS: port 8084 opened
2021.11.16 10:14:26.158 2: Registering GEOFANCY geofancy for URL /geo...
2021.11.16 10:14:26.219 3: WEBhook: port 8088 opened
2021.11.16 10:14:26.887 2: eventTypes: loaded 10047 lines from ./log/eventTypes.txt
2021.11.16 10:14:27.029 3: Opening CUL_0 device /dev/serial/by-id/usb-busware.de_CUL868-if00
2021.11.16 10:14:27.097 3: Setting CUL_0 serial parameters to 9600,8,N,1
2021.11.16 10:14:27.207 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2021.11.16 10:14:27.212 3: CUL_0 device opened
2021.11.16 10:14:27.222 2: Switched CUL_0 rfmode to HomeMatic
2021.11.16 10:14:28.033 3: additional HM config file loaded: ./FHEM/HMConfig_SenTHPL.pm
2021.11.16 10:14:32.564 1: HMCCU [myHMCCU3] CCU port 8181 is not reachable
2021.11.16 10:14:32.565 1: HMCCU [myHMCCU3] Initialized version 5.0 213171649
2021.11.16 10:14:32.566 1: HMCCU [myHMCCU3] Scheduling delayed initialization in 180 seconds
2021.11.16 10:14:32.580 3: myHMCCU3: unknown attribute rpcinterfaces. Type 'attr myHMCCU3 ?' for a detailed list.
2021.11.16 10:14:32.930 3: Opening myJeeLink1 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL014JZA-if00-port0
2021.11.16 10:14:32.935 3: Setting myJeeLink1 serial parameters to 57600,8,N,1
2021.11.16 10:14:33.957 3: myJeeLink1 device opened
2021.11.16 10:14:35.746 3: TABLETUI: new ext defined infix:ftui/: dir:./www/tablet/:
2021.11.16 10:14:35.747 3: Registering HTTPSRV TABLETUI for URL /ftui and assigned link ftui/ ...
2021.11.16 10:14:36.372 3: HM485: HM485: Converting device files
2021.11.16 10:14:36.373 3: HM485: ==============================
2021.11.16 10:14:36.376 3: HM485: hmw_central.xml up to date
2021.11.16 10:14:36.376 3: HM485: hmw_generic.xml up to date
2021.11.16 10:14:36.377 3: HM485: hmw_io12_sw14_dr.xml up to date
2021.11.16 10:14:36.378 3: HM485: hmw_io12_sw7_dr.xml up to date
2021.11.16 10:14:36.379 3: HM485: hmw_io12_sw7_dr_V3_02.xml up to date
2021.11.16 10:14:36.379 3: HM485: hmw_io_12_fm.xml up to date
2021.11.16 10:14:36.380 3: HM485: hmw_io_4_fm.xml up to date
2021.11.16 10:14:36.381 3: HM485: hmw_io_4_fm_V3_02.xml up to date
2021.11.16 10:14:36.382 3: HM485: hmw_io_sr_fm.xml up to date
2021.11.16 10:14:36.382 3: HM485: hmw_lc_bl1_dr.xml up to date
2021.11.16 10:14:36.382 3: HM485: hmw_lc_bl1_dr_V3_02.xml up to date
2021.11.16 10:14:36.383 3: HM485: hmw_lc_dim1l_dr.xml up to date
2021.11.16 10:14:36.383 3: HM485: hmw_lc_sw2_dr.xml up to date
2021.11.16 10:14:36.384 3: HM485: hmw_lc_sw2_dr_V3_02.xml up to date
2021.11.16 10:14:36.385 3: HM485: hmw_sen_sc_12_dr.xml up to date
2021.11.16 10:14:36.385 3: HM485: Loading available device files
2021.11.16 10:14:36.386 3: HM485: ==============================
2021.11.16 10:14:36.386 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_central.pm
2021.11.16 10:14:36.391 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_generic.pm
2021.11.16 10:14:36.394 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw14_dr.pm
2021.11.16 10:14:36.406 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr.pm
2021.11.16 10:14:36.428 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_V3_02.pm
2021.11.16 10:14:36.452 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_12_fm.pm
2021.11.16 10:14:36.475 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm.pm
2021.11.16 10:14:36.499 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_V3_02.pm
2021.11.16 10:14:36.521 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_sr_fm.pm
2021.11.16 10:14:36.543 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr.pm
2021.11.16 10:14:36.573 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_V3_02.pm
2021.11.16 10:14:36.603 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_dim1l_dr.pm
2021.11.16 10:14:36.636 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr.pm
2021.11.16 10:14:36.660 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_V3_02.pm
2021.11.16 10:14:36.687 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_sen_sc_12_dr.pm
2021.11.16 10:14:39.246 3: UPDATE_FTUI: Defined with URL https://raw.githubusercontent.com/knowthelist/fhem-tablet-ui/master/controls_fhemtabletui.txt and interval 86400 featurelevel 6.1
2021.11.16 10:14:40.605 3: Pollenflug: Defined with URL http://www.donnerwetter.de/pollenflug/region.hts?plz=88483&PTag=0 and interval 3600 featurelevel 6.1
2021.11.16 10:14:42.962 3: Opening my_callmonitor device 192.168.178.1:1012
2021.11.16 10:14:42.979 3: FB_CALLMONITOR (my_callmonitor) - loading cache file ./log/my_callmonitor.txt
2021.11.16 10:14:42.981 2: FB_CALLMONITOR (my_callmonitor) - read 35 contacts from Cache
2021.11.16 10:14:48.657 3: ArduinoNano_Zisterne: Defined with URL http://192.168.178.45/ and interval 61 featurelevel 6.1
2021.11.16 10:14:49.065 3: LaCrosse_Kueche: I/O device is myJeeLink1
2021.11.16 10:14:49.102 3: LaCrosse_Bad_EG: I/O device is myJeeLink1
2021.11.16 10:14:49.552 3: MQTT2_FHEM_Server: port 1883 opened
2021.11.16 10:14:50.220 3: HMCCUDEV [Licht_BadOG_Spiegel] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:51.161 3: freezemon defined myFreezemon freezemon
2021.11.16 10:14:51.165 0: [Freezemon] myFreezemon: Unwrapping CallFn
2021.11.16 10:14:51.165 0: [Freezemon] myFreezemon: Unwrapping AnalyzeCommand
2021.11.16 10:14:51.166 0: [Freezemon] myFreezemon: Unwrapping HttpUtils_NonblockingGet
2021.11.16 10:14:51.166 0: [Freezemon] myFreezemon: Unwrapping Log3
2021.11.16 10:14:51.168 3: [Freezemon] myFreezemon: Wrapping Log3
2021.11.16 10:14:51.410 3: [SamsungAV] SamsungQ85 defined with host: 192.168.178.37 port: 8001
2021.11.16 10:14:51.854 3: NotdienstApotheke: interval is 0, no periodic updates will done.
2021.11.16 10:14:51.854 3: NotdienstApotheke: Defined with URL https://apothekenfinder.mobi/interface/json.php?device=web&source=not&search=88483 featurelevel 6.1
2021.11.16 10:14:54.071 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CCU not ready. Trying later ...
2021.11.16 10:14:54.080 2: HMCCURPCPROC [d_rpc178026HmIP_RF] CCU not ready. Trying later ...
2021.11.16 10:14:54.195 3: Modul 90_Jalousie.pm: Init Done with Version V 0.00.09 von gevoo - 18.12.2015 modifiziert JG
2021.11.16 10:14:54.196 3: Name = Jal_KU_Fenster, Parameter = Jalousie Jal_KU_Fenster_03 39 2
2021.11.16 10:14:54.196 1: Jalousie mit Rolloaktor Jal_KU_Fenster_03 verbunden
2021.11.16 10:14:54.199 3: Name = Jal_KU_Sued, Parameter = Jalousie Jal_KU_Sued_03 64 2
2021.11.16 10:14:54.199 1: Jalousie mit Rolloaktor Jal_KU_Sued_03 verbunden
2021.11.16 10:14:54.202 3: Name = Jal_WZ_Fest_Ost, Parameter = Jalousie Jal_WZ_Fest_Ost_03 64 2
2021.11.16 10:14:54.202 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Ost_03 verbunden
2021.11.16 10:14:54.204 3: Name = Jal_WZ_Fest_Sued, Parameter = Jalousie Jal_WZ_Fest_Sued_03 64 2
2021.11.16 10:14:54.204 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Sued_03 verbunden
2021.11.16 10:14:54.206 3: Name = Jal_WZ_Schiebetuer, Parameter = Jalousie Jal_WZ_Schiebetuer_03 64 2
2021.11.16 10:14:54.206 1: Jalousie mit Rolloaktor Jal_WZ_Schiebetuer_03 verbunden
2021.11.16 10:14:54.208 3: Name = Jal_WZ_SuedWest, Parameter = Jalousie Jal_WZ_Fest_SuedWest_03 64 2
2021.11.16 10:14:54.208 1: Jalousie mit Rolloaktor Jal_WZ_Fest_SuedWest_03 verbunden
2021.11.16 10:14:54.210 3: Name = Jal_WZ_West, Parameter = Jalousie Jal_WZ_Fest_West_03 64 2
2021.11.16 10:14:54.211 1: Jalousie mit Rolloaktor Jal_WZ_Fest_West_03 verbunden
2021.11.16 10:14:55.243 3: HMCCUCHN [Alarm_KueOst_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.301 3: HMCCUCHN [Alarm_KueSued_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.351 3: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.402 3: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.452 3: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.504 3: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.556 3: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.612 3: HMCCUDEV [HmIP_BDT_0008DA49929255_3] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.725 3: HMCCUCHN [Heiz_BadOG_Handtuch_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 10:14:55.812 2: HMCCURPCPROC [d_rpc178026VirtualDevices] CCU not ready. Trying later ...
2021.11.16 10:14:55.816 1: Including ./log/fhem.save
2021.11.16 10:14:58.301 3: Opening myHMUARTGPIO device 192.168.178.53:4001
2021.11.16 10:14:58.304 1: CUL_HM start inital cleanup
2021.11.16 10:15:00.719 1: CUL_HM finished initial cleanup
2021.11.16 10:15:00.815 3: monitoring (Activity_monitoring) set Activity_monitoring active
2021.11.16 10:15:00.974 3: monitoring (Batterie_monitoring) set Batterie_monitoring active
2021.11.16 10:15:01.082 3: [SamsungAV] device SamsungQ85 initialising....
2021.11.16 10:15:01.154 3: telnetForBlockingFn_1637054101: port 33695 opened
2021.11.16 10:15:01.197 2: di_Bad_OG_Licht_Spiegel: set HmIP_BDT_0008DA49929255_3 off: Device state doesn't allow set commands
2021.11.16 10:15:01.198 3: di_Bad_OG_Licht_Spiegel: error in startup: set HmIP_BDT_0008DA49929255_3 off: Device state doesn't allow set commands
2021.11.16 10:15:01.472 1: PERL WARNING: Use of uninitialized value $4 in string at (eval 663) line 1.
2021.11.16 10:15:01.472 3: eval: {ReadingsTimestamp($name,"timer_02_c02","") =~ /^(\d+)-(\d+)-(\d+)\s(\d+:\d+):(\d+)$/;return "$4";}
2021.11.16 10:15:03.687 1: PERL WARNING: Use of uninitialized value in pattern match (m//) at ./FHEM/36_JeeLink.pm line 363.
2021.11.16 10:15:05.504 2: MQTT_GENERIC_BRIDGE: evalValue: user value ('{"$base/$roomname/$device/$sensor/$reading"}'') eval error: Global symbol "$roomname" requires explicit package name (did you forget to declare "my $roomname"?) at (eval 726) line 1.
Global symbol "$sensor" requires explicit package name (did you forget to declare "my $sensor"?) at (eval 726) line 1.
2021.11.16 10:15:05.857 0: Featurelevel: 6.1
2021.11.16 10:15:05.857 0: Server started with 505 defined entities (fhem.pl:25197/2021-11-07 perl:5.028001 os:linux user:fhem pid:674)
2021.11.16 10:15:06.974 1: PERL WARNING: Use of uninitialized value $hybernate in concatenation (.) or string at ./FHEM/86_Robonect.pm line 592.
2021.11.16 10:15:06.974 3: eval: sunset_abs()
2021.11.16 10:15:07.932 3: CUL_HM set AZ_Rolladen statusRequest noArg
2021.11.16 10:15:08.949 3: myHMUARTGPIO device opened
2021.11.16 10:15:09.350 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed (peer: 192.168.178.52)
2021.11.16 10:15:10.669 3: Opening HM485_LAN device 192.168.178.47:1000
2021.11.16 10:15:10.673 3: HM485_LAN: connected to device 192.168.178.47:1000
2021.11.16 10:15:10.673 3: HM485_LAN device opened
2021.11.16 10:15:10.855 3: CUL_HM set FL_UG_Rolladen statusRequest noArg
2021.11.16 10:15:11.697 3: HM485_LAN: Lan Device Information
2021.11.16 10:15:11.697 3: HM485_LAN: Protocol-Version: 01
2021.11.16 10:15:11.697 3: HM485_LAN: Interface-Type: eQ3-HMW-LGW
2021.11.16 10:15:11.698 3: HM485_LAN: Firmware-Version: 1.0.4
2021.11.16 10:15:11.698 3: HM485_LAN: Serial-Number: LEQ0636394
2021.11.16 10:15:11.698 3: HM485_LAN: Initialize the interface
2021.11.16 10:15:12.615 3: UWZ Unwetterzentrale: UWZ.1811 Done fetching data
2021.11.16 10:15:12.963 3: CUL_HM set Gara_Re8_Sw01_TorAuf statusRequest noArg
2021.11.16 10:15:16.291 1: PERL WARNING: Use of uninitialized value $value in string eq at fhem.pl line 4926.
2021.11.16 10:15:16.649 3: HM485_LAN: Initialisierung von Modul 00010854
2021.11.16 10:15:16.814 3: CUL_HM set Gara_Re8_Sw02_TorLueften statusRequest noArg
2021.11.16 10:15:16.822 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F09C:SSL routines:ssl3_get_record:http request (peer: 192.168.178.92)
2021.11.16 10:15:17.414 3: HM485_LAN: Initialisierung von Modul 000107E1
2021.11.16 10:15:18.165 3: HM485_LAN: Initialisierung von Modul 0001076C
2021.11.16 10:15:18.326 3: CUL_HM set Gara_Re8_Sw03_TorZu statusRequest noArg
2021.11.16 10:15:18.334 3: Jal_WZ_Fest_SuedWest: Request config for device 00010854
2021.11.16 10:15:18.341 3: Jal_WZ_Fest_SuedWest: Lese Eeprom 00010854
2021.11.16 10:15:19.412 1: FHEMWEB SSL/HTTPS error: SSL accept attempt failed error:1408F09C:SSL routines:ssl3_get_record:http request (peer: 192.168.178.92)
2021.11.16 10:15:19.416 3: HM485_LAN: Initialisierung von Modul 00010A77
2021.11.16 10:15:19.450 3: CUL_HM set Gara_Re8_Sw04_TorLicht statusRequest noArg
2021.11.16 10:15:21.460 3: CUL_HM set Gara_Re_8_Sw_05 statusRequest noArg
2021.11.16 10:15:21.618 3: HM485_LAN: Initialisierung von Modul 00010B2C
2021.11.16 10:15:21.748 3: Jal_WZ_Fest_West: Request config for device 000107E1
2021.11.16 10:15:21.755 3: Jal_WZ_Fest_West: Lese Eeprom 000107E1
2021.11.16 10:15:21.966 3: HM485_LAN: Initialisierung von Modul 00010AA7
2021.11.16 10:15:22.180 3: HM485_LAN: Initialisierung von Modul 00010A88
2021.11.16 10:15:23.272 3: HM485_LAN: Initialisierung von Modul 00010A70
2021.11.16 10:15:23.433 3: CUL_HM set Gara_Re_8_Sw_06 statusRequest noArg
2021.11.16 10:15:23.451 3: Jal_KU_Ost_00: Request config for device 0001076C
2021.11.16 10:15:23.458 3: Jal_KU_Ost_00: Lese Eeprom 0001076C
2021.11.16 10:15:25.032 3: CUL_HM set Gara_Re_8_Sw_07 statusRequest noArg
2021.11.16 10:15:25.826 2: AttrTemplates: got 259 entries
2021.11.16 10:15:26.772 3: CUL_HM set Gara_Re_8_Sw_08 statusRequest noArg
2021.11.16 10:15:30.176 3: CUL_HM set Licht_Gart_Hof statusRequest noArg
2021.11.16 10:15:33.439 3: CUL_HM set HM_572922_Sw_02 statusRequest noArg
2021.11.16 10:15:36.807 3: CUL_HM set Mar_Gar_Ost statusRequest noArg
2021.11.16 10:15:41.490 3: CUL_HM set Mar_Gar_West statusRequest noArg
2021.11.16 10:15:43.808 3: CUL_HM set WK_Steckdose_Waschen_Sw statusRequest noArg
2021.11.16 10:15:50.524 3: CUL_HM set de_Bad_OG_Licht_Spiegel statusRequest noArg
2021.11.16 10:15:57.626 3: Jal_KU_Fenster_00: Request config for device 00010A77
2021.11.16 10:15:57.632 3: Jal_KU_Fenster_00: Lese Eeprom 00010A77
2021.11.16 10:15:57.782 3: CUL_HM set HM_572922 getConfig noArg
2021.11.16 10:16:01.494 3: Jal_KU_Sued_00: Request config for device 00010B2C
2021.11.16 10:16:01.500 3: Jal_KU_Sued_00: Lese Eeprom 00010B2C
2021.11.16 10:16:08.900 3: Jal_WZ_Fest_Ost_00: Request config for device 00010AA7
2021.11.16 10:16:08.908 3: Jal_WZ_Fest_Ost_00: Lese Eeprom 00010AA7
2021.11.16 10:16:09.427 3: Jal_WZ_Fest_Sued_00: Request config for device 00010A88
2021.11.16 10:16:09.435 3: Jal_WZ_Fest_Sued_00: Lese Eeprom 00010A88
2021.11.16 10:16:09.953 3: Jal_WZ_Schiebetuer_00: Request config for device 00010A70
2021.11.16 10:16:09.963 3: Jal_WZ_Schiebetuer_00: Lese Eeprom 00010A70
2021.11.16 10:16:33.313 3: CUL_HM set de_Bad_OG_Licht_Spiegel getConfig noArg
2021.11.16 10:17:32.568 1: HMCCU [myHMCCU3] Initializing devices
2021.11.16 10:17:32.725 2: HMCCU [myHMCCU3] Deleting old groups
2021.11.16 10:17:32.731 2: HMCCU [myHMCCU3] Updating device table
2021.11.16 10:17:32.744 2: HMCCU [myHMCCU3] Initializing 13 client devices in state 'pending'
2021.11.16 10:17:32.745 2: HMCCU [myHMCCU3] Can't get device description for 00109BE989D89B:1 HMCCU_DetectDevice:187 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:32.746 2: HMCCU [myHMCCU3] Can't get device description for 00109BE989D89B:1 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:190 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:32.746 2: HMCCUCHN [Alarm_KueOst_HmIP] Can't get device description for 00109BE989D89B:1 HMCCU_UpdateDeviceRoles:193 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:32.754 1: HMCCURPCPROC [d_rpc178026HmIP_RF] Initialized version 5.0 213171649 for interface HmIP-RF with I/O device myHMCCU3
2021.11.16 10:17:33.156 1: HMCCURPCPROC [d_rpc178026VirtualDevices] Initialized version 5.0 213171649 for interface VirtualDevices with I/O device myHMCCU3
2021.11.16 10:17:33.389 2: HMCCU [myHMCCU3] Can't get device description for 000C9A4999F2BC HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.390 2: HMCCU [myHMCCU3] Can't get device description for 000C9A4999F2BC HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.390 2: HMCCUDEV [HmIP_BWTH_000C9A4999F2BC_9] Can't get device description for 000C9A4999F2BC HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.394 2: HMCCU [myHMCCU3] Can't get device description for 000C9A499EE32F HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.395 2: HMCCU [myHMCCU3] Can't get device description for 000C9A499EE32F HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.395 2: HMCCUDEV [HmIP_BWTH_000C9A499EE32F_9] Can't get device description for 000C9A499EE32F HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.399 2: HMCCU [myHMCCU3] Can't get device description for 000C9BE98E7AB8 HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.400 2: HMCCU [myHMCCU3] Can't get device description for 000C9BE98E7AB8 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.400 2: HMCCUDEV [HmIP_BWTH_000C9BE98E7AB8_9] Can't get device description for 000C9BE98E7AB8 HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.408 1: HMCCURPCPROC [d_rpc178026BidCos_RF] Initialized version 5.0 213171649 for interface BidCos-RF with I/O device myHMCCU3
2021.11.16 10:17:33.638 2: HMCCU [myHMCCU3] Can't get device description for 00109BE989D6EC:1 HMCCU_DetectDevice:187 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.639 2: HMCCU [myHMCCU3] Can't get device description for 00109BE989D6EC:1 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:190 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.640 2: HMCCUCHN [Alarm_KueSued_HmIP] Can't get device description for 00109BE989D6EC:1 HMCCU_UpdateDeviceRoles:193 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.643 2: HMCCU [myHMCCU3] Can't get device description for 000A1D8991DD5F:1 HMCCU_DetectDevice:187 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.644 2: HMCCU [myHMCCU3] Can't get device description for 000A1D8991DD5F:1 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:190 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.645 2: HMCCUCHN [Heiz_BadOG_Handtuch_HmIP] Can't get device description for 000A1D8991DD5F:1 HMCCU_UpdateDeviceRoles:193 HMCCUCHN_InitDevice:3129 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.648 2: HMCCU [myHMCCU3] Can't get device description for 000C9A49A7E499 HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.649 2: HMCCU [myHMCCU3] Can't get device description for 000C9A49A7E499 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.650 2: HMCCUDEV [HmIP_BWTH_000C9A49A7E499_9] Can't get device description for 000C9A49A7E499 HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.653 2: HMCCU [myHMCCU3] Can't get device description for 0008DA49929255 HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.654 2: HMCCU [myHMCCU3] Can't get device description for 0008DA49929255 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.654 2: HMCCUDEV [Licht_BadOG_Spiegel] Can't get device description for 0008DA49929255 HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.655 2: HMCCU [myHMCCU3] Can't get device description for 000C9BE99C66F8 HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.656 2: HMCCU [myHMCCU3] Can't get device description for 000C9BE99C66F8 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.656 2: HMCCUDEV [HmIP_BWTH_000C9BE99C66F8_9] Can't get device description for 000C9BE99C66F8 HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.661 2: HMCCU [myHMCCU3] Can't get device description for 0008DA49929255 HMCCU_DetectDevice:212 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.661 2: HMCCU [myHMCCU3] Can't get device description for 0008DA49929255 HMCCU_DetectDevice:3642 HMCCU_SetSCAttributes:217 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.662 2: HMCCUDEV [HmIP_BDT_0008DA49929255_3] Can't get device description for 0008DA49929255 HMCCU_UpdateDeviceRoles:220 HMCCUDEV_InitDevice:3128 HMCCU_UpdateDeviceTable:5635 HMCCU_GetDeviceList:536 HMCCU_InitDevice:3427 HandleTimeout:695
2021.11.16 10:17:33.887 1: HMCCU [myHMCCU3] Read 13 devices with 203 channels from CCU 192.168.178.26
2021.11.16 10:17:33.887 1: HMCCU [myHMCCU3] Read 0 programs from CCU 192.168.178.26
2021.11.16 10:17:33.887 1: HMCCU [myHMCCU3] Read 2 virtual groups from CCU 192.168.178.26
2021.11.16 10:17:33.887 1: HMCCU [myHMCCU3] Reading device config from CCU. This may take a couple of seconds ...
2021.11.16 10:17:33.888 2: HMCCU [myHMCCU3] Reading Device Descriptions for interface HmIP-RF
2021.11.16 10:17:34.750 2: HMCCU [myHMCCU3] Read 148 Device Descriptions for interface HmIP-RF
2021.11.16 10:17:34.751 2: HMCCU [myHMCCU3] Reading Paramset Descriptions for interface HmIP-RF
2021.11.16 10:17:48.354 2: HMCCU [myHMCCU3] Read 88 Paramset Descriptions for interface HmIP-RF
2021.11.16 10:17:48.355 2: HMCCU [myHMCCU3] Reading Peer Descriptions for interface HmIP-RF
2021.11.16 10:17:48.407 2: HMCCU [myHMCCU3] Read 12 Peer Descriptions for interface HmIP-RF
2021.11.16 10:17:48.407 2: HMCCU [myHMCCU3] Reading Device Descriptions for interface VirtualDevices
2021.11.16 10:17:48.521 2: HMCCU [myHMCCU3] Read 16 Device Descriptions for interface VirtualDevices
2021.11.16 10:17:48.522 2: HMCCU [myHMCCU3] Reading Paramset Descriptions for interface VirtualDevices
2021.11.16 10:17:51.619 2: HMCCU [myHMCCU3] Read 9 Paramset Descriptions for interface VirtualDevices
2021.11.16 10:17:51.620 2: HMCCU [myHMCCU3] Reading Peer Descriptions for interface VirtualDevices
2021.11.16 10:17:51.640 2: HMCCU [myHMCCU3] Read 0 Peer Descriptions for interface VirtualDevices
2021.11.16 10:17:51.641 2: HMCCU [myHMCCU3] Reading Device Descriptions for interface BidCos-RF
2021.11.16 10:17:51.800 2: HMCCU [myHMCCU3] Read 52 Device Descriptions for interface BidCos-RF
2021.11.16 10:17:51.801 2: HMCCU [myHMCCU3] Reading Paramset Descriptions for interface BidCos-RF
2021.11.16 10:17:54.304 2: HMCCU [myHMCCU3] Read 52 Paramset Descriptions for interface BidCos-RF
2021.11.16 10:17:54.305 2: HMCCU [myHMCCU3] Reading Peer Descriptions for interface BidCos-RF
2021.11.16 10:17:54.318 2: HMCCU [myHMCCU3] Read 0 Peer Descriptions for interface BidCos-RF
2021.11.16 10:17:54.335 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.337 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.339 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.341 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.342 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.361 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.362 1: PERL WARNING: Use of uninitialized value in concatenation (.) or string at ./FHEM/88_HMCCU.pm line 3660.
2021.11.16 10:17:54.365 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.374 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.377 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.386 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.390 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.406 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.409 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.434 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.438 2: HMCCU [myHMCCU3] Control datapoint not defined for channel 10, role
2021.11.16 10:17:54.454 2: HMCCU [myHMCCU3] Read RPC device configuration: devices/channels=216 parametersets=149 links=12
ich meinte eigentlich, was läuft außerhalb von FHEM noch auf dem PI.
z.B. piVCCU ist so etwas.
bei dem PI würde ich 16 schon als deutlich zu hoch ansehen, eher bei 4-8 ..
Gib uns bitte mal bei einem frisch gestarteten System (nach c.a. 10 Minuten und als root (oder sudo)):
ps aux | grep fhem ; echo ; free
Gerade frisch gestartet:
pi@Raspi043BPlus:~ $ ps aux | grep fhem ; echo ; free
fhem 3984 78.9 15.8 160348 150272 ? S 10:21 2:18 /usr/bin/perl fhem.pl fhem.cfg
fhem 4119 1.5 14.3 149780 135212 ? S 10:22 0:01 /usr/bin/perl fhem.pl fhem.cfg
fhem 4122 0.4 14.2 149656 134980 ? S 10:22 0:00 /usr/bin/perl fhem.pl fhem.cfg
fhem 4123 0.2 14.2 149668 135008 ? S 10:22 0:00 /usr/bin/perl fhem.pl fhem.cfg
pi 4351 0.0 0.0 7360 492 pts/1 S+ 10:24 0:00 grep --color=auto fhem
total used free shared buff/cache available
Mem: 945364 436880 144896 13508 363588 441980
Swap: 102396 0 102396
Seltsam. Bevor ich Fhem neu gestartet hatte waren es
pi@Raspi043BPlus:~ $ free
total used free shared buff/cache available
Mem: 945364 329668 252872 13508 362824 553652
Swap: 102396 0 102396
Kann es sein, dass bei einem restart von FHEM Reste zurückbleiben und den Speicher belegen?
Zitat von: bmwfan am 16 November 2021, 09:57:33
Hatte gestern die Forks mit global BlockingCallMax auf 16 gestellt, aber heute Nacht war wieder ein Absturz. Was ist denn ein empfehlenswerter Wertt dafür?
16? Wirklich?
Noch mal: ein Fork für Blocking bedeutet, dass das KOMPLETTE laufende fhem geclont wird! Ich glaube nicht, dass 16 da viel hilft, weil du hattest ja weiter vorne einen "Baum" gepostet und der war ja schon groß aber (deutlich) kleiner als 16 (waren 11 bzw. dann wohl ohne "Original" 10) und auch da hattest du ja Probleme...
Bei mir steht der auf 5...
Zitat von: bmwfan am 16 November 2021, 09:57:33
Was läuft zu FHEM sonst noch?
zigbee2mqtt mit einem ConbeeII-Stick
Tablet-UI für Anzeige auf einem Tablet
piVCCU
Also mal das was NICHT "in" fhem läuft ausgeklammert läuft bei dir auf einem PI3B(+) (wenn ich das recht im Kopf habe):
fhem
eine CCU (piVCCU)
zigbee2mqtt (zigbee Bridge)
Bei Tablet-UI bin ich raus, keine Ahnung was das für das System auf dem das läuft zusätzlich bedeutet...
...aber alleine schon fhem, CCU und zigbee2mqtt auf dem armen "kleinen" PI...
Also ich habe das verteilt auf andere PI, also deCONZ (Zigbee-Bridge) auf einem extra PI (CCU nutze ich nicht), d.h. bei mir läuft NUR fhem auf einem PI3B+ und das ganz geschmeidig...
Und um solche Probleme nicht zu bekommen, kommt da auch nichts anderes drauf (auch, wenn es sicher geht)...
Protokollierst du deinen Speicherverbrauch?
Also generell?
Weil es ja neben dem Blocking/Forking auch generell einen Speicheranstieg (bei fhem) geben kann (gibt Threads dazu im Forum und ich war vor Umstieg auf Buster auch betroffen / aber es soll wohl je nach "Konstellation" und verwendeter Module auch damit noch Probleme geben)...
...nur als weitere Idee...
Zitat von: bmwfan am 16 November 2021, 09:57:33
Nach einem reboot sieht es so aus:
pi@Raspi043BPlus:~ $ free
total used free shared buff/cache available
Mem: 945364 335348 251656 13388 358360 544184
Swap: 102396 0 102396
vorher waren nur 65 GB frei angezeigt.
Der PI hat doch insgesamt nur 1GB, da können ja keine 64GB frei sein ;)
Gruß, Joachim
es ist doch völlig egal, was free anzeigt.
wenn das os "oom" sagt, war es zu wenig. ;)
nimm für deine ccu ein eigenen pi.
@MadMax-FHEM
Hörte das mit Forks das erste Mal und konnte mir nicht viel vorstellen. Habe keine Empfehlungen gefunden und dachte, ich halbiere mal den Standardwert zum Testen. Dann muss ich aber noch deutlich weiter herunter.
Hardware ist PI3b(+) mit 64 GB Speicherkarte.
Es läuft fhem, CCU (piVCCU), zigbee2mqtt auf dem ConbeeII aber nicht deConz, ebusd (Abfrage Vaillant-Heizung)
Ich habe schon einen 2.ten Raspi im Technikraum und über MQTT2 angebunden. War aber doch ein Aufwand, das zum Laufen zu bringen. Wie hast Du Deine PI dann miteinander für den Datenaustausch verbunden?
Speicherverbrauch protokollieren:
Bisher nicht, aber ich suche mal im Forum wie das geht und richte es ein.
1GB: Ich denke inzwischen halt auch in PC-Dimensionen. Sind natürlich 64 MB. ;)
@frank: Werde ich machen. Habe noch einen herumliegen. Muss nur erst recherchieren, wie ich dann die Daten zwischen den PI's austauschen kann. Ist mir noch nicht klar wie das geht, wenn ein PI die CCU ansteuert und der andere ihn mit Daten versorgen und welche abholen muss.
Danke für die Hilfe an alle.
ZitatSpeicherverbrauch protokollieren:
Bisher nicht, aber ich suche mal im Forum wie das geht und richte es ein.
alles, was du zusätzlich definierst, braucht doch noch mehr speicher.
schaffe erst mal platz, damit du "atmen" kannst.
Zitat von: bmwfan am 16 November 2021, 10:50:37
Hardware ist PI3b(+) mit 64 GB Speicherkarte.
Es läuft fhem, CCU (piVCCU), zigbee2mqtt auf dem ConbeeII aber nicht deConz, ebusd (Abfrage Vaillant-Heizung)
Naja, die SD bzw. der Speicher darauf ist (erst mal) uninteressant, es geht um RAM! ;)
Ja klar: du zigbee2mqtt ich deCONZ (beides eine "externe" Zigbee-Bridge 8) ) wollte nur sagen, dass das eine weitere Komponente/Server-Dienst außerhalb fhem ist...
Zitat von: bmwfan am 16 November 2021, 10:50:37
@frank: Werde ich machen. Habe noch einen herumliegen. Muss nur erst recherchieren, wie ich dann die Daten zwischen den PI's austauschen kann. Ist mir noch nicht klar wie das geht, wenn ein PI die CCU ansteuert und der andere ihn mit Daten versorgen und welche abholen muss.
Naja eine CCU von einem externen PI einbinden geht doch GENAUSO wie lokal...
...gut andere IP nat. ;)
EDIT: es gibt ja bestimmt auch bei piVCCU sowas wie eine Konfiguration, die man bestimmt auf das neue System/PI übertragen kann / also offen: wie bekommst du die piVCCU auf einen anderen Rechner/PI ohne, dass sich "da(bei)" was ändert... (nutze [noch] keine CCU)...
Gleiches gilt für zigbee2mqtt, einfach dort (also bei zigbee2mqtt) die IP des fhem mit dem laufenden MQTT2-Server angeben (falls dort noch "localhost" eingetragen ist / wenn da jetzt schon die fhem-IP drin steht, dann brauchst du gar nix ändern, außer zigbee2mqtt auf einen anderen PI o.ä. installieren und Stick und Config übertragen)...
Gruß, Joachim
Habe jetzt einige Plots, die ich nicht mehr brauche, gelöscht. RAM wurde schon geloggt, aber nicht angezeigt. Mache ich jetzt, um zu sehen wie die max. Belastung ist.
Filelogs, was nicht unbedingt benötigt wird, habe ich ausgeschalten.
Mal sehen, ob der PI jetzt stabiler läuft. Parallel schaue ich, dass ich für piVCCU einen eigenen PI spendiere. Dann kann ich auch mein FHEM auf einen PI legen, der durch die Nähe zur CCU-Hardware nicht im Schaltscharnk (schwer zugänglich) montiert ist.
@MadMax-FHEM: Danke für die Tipps der Enbindung. Werde ich so angehen.
Habe noch einen PI2 Model B herumliegen. Denkst Du, der packt CCU + zigbee2mqtt oder ist der dann auch überlastet?
Zitat von: bmwfan am 16 November 2021, 11:31:16
Habe jetzt einige Plots, die ich nicht mehr brauche, gelöscht. RAM wurde schon geloggt, aber nicht angezeigt. Mache ich jetzt, um zu sehen wie die max. Belastung ist.
Filelogs, was nicht unbedingt benötigt wird, habe ich ausgeschalten.
Naja, das wird nicht die Welt retten ;)
Hast du maxBlockingCall schon deutlich runter gesetzt?
Zitat von: bmwfan am 16 November 2021, 11:31:16
@MadMax-FHEM: Danke für die Tipps der Enbindung. Werde ich so angehen.
Habe noch einen PI2 Model B herumliegen. Denkst Du, der packt CCU + zigbee2mqtt oder ist der dann auch überlastet?
Gerne.
Äh, da eher mal auf eine Antwort von zap warten oder im Forum suchen...
...oder einen neuen Thread mit genau der Frage aufmachen...
Aber (soweit ich das überblicke/im Kopf habe):
CCU2 (also "Original" von ELV) war Plattform (vergleichbar) PI2 -> langsam, bzw. kommt drauf an wieviele Geräte
CCU3 (also "Original" von ELV) bzw. Bausatz "Charly" ist Basis PI3 -> aktuell
Vielleicht beantwortet das schon die Frage...
...und zeigt u.U. auch, dass es evtl. (jetzt schon) nicht "schlau" ist eine CCU (und ein Zigbee-Gateway) zusammen mit fhem auf einem PI3 zu haben ;)
Gruß, Joachim
blockingCallMax ist auf 4 gestellt.
CCU: Ich benutze als Hardware eine HB-RF-USB Platine von Alexander Reinert für die piVCCU. Diese läuft als CCU3 => also besser gleich auf einen PI3 gehen. Mal suchen. Vielleicht liegt noch einer herum.
Überlastung: Ich habe mir immer die CPU-Belastung angeschaut um abzuschätzen, ob ich noch was draufpacken kann, nicht aber das RAM. Bin halt vom PC gewohnt, dass RAM kein Problem mehr darstellt. Muss doch noch einiges umdenken bei den kleinen Kerlchen.
Da Du laut ps aktuell schon 4 FHEM-Prozesse hast, würde ich eher auf 5 Stellen, d.h. 1 für ping in "reserve".
Sonst auch die Empfehlung: Nimm die pivccu auf einen anderen PI, das ist das einfachste. Ob Du jetzt "lokal" per netzwerk oder übe echtes Netwerk gehst ...
Nachfrage: Sie sind doch per Kabel verbunden? Nicht per WLAN??
Logfiles reduzieren, ist gut für die SDCard, aber macht den Speicher auch nicht voll. Dein free sieht eigentlich gut aus, gehe deshalb wirklich von Problemen bezüglich "noch-blocking-ping" aus.
Wie man zigbe2mqtt auf einen anderen Pi schmeißen könnte, müssen Dir die Experten von "dort" erzählen. Weiß ja nicht mal, wie es in FHEM eingebunden wird.
Ist gerade wieder abgestürzt. Setze Blocking mal auf 5.
Eigener Pi (3B+ noch gefunden) für die piVCCU gerade am Aufsetzen.
Raspis sind über LAN verbunden und das Modul für die piVCCU über USB.
Danke für eure Hilfe.
@zap: Wenn der Pi aus dem stromlosen Zustand bootet ist HMCCU immer inaktiv. Vermute, dass dieser Prozeß nicht schnell genug hochfährt. FHEM muss dann immer manuell "restartet" werden, damit HMCCU läuft.
2021.11.16 17:01:29.595 1: Including fhem.cfg
2021.11.16 17:01:29.670 3: telnetPort: port 7072 opened
2021.11.16 17:01:30.231 3: WEB: port 8083 opened
2021.11.16 17:01:30.241 3: WEBS: port 8084 opened
2021.11.16 17:01:31.526 2: Registering GEOFANCY geofancy for URL /geo...
2021.11.16 17:01:31.572 3: WEBhook: port 8088 opened
2021.11.16 17:01:32.179 2: eventTypes: loaded 10047 lines from ./log/eventTypes.txt
2021.11.16 17:01:32.294 3: Opening CUL_0 device /dev/serial/by-id/usb-busware.de_CUL868-if00
2021.11.16 17:01:32.347 3: Setting CUL_0 serial parameters to 9600,8,N,1
2021.11.16 17:01:32.456 3: CUL_0: Possible commands: BbCFiAZNkGMKUYRTVWXefmLltux
2021.11.16 17:01:32.461 3: CUL_0 device opened
2021.11.16 17:01:32.469 2: Switched CUL_0 rfmode to HomeMatic
2021.11.16 17:01:33.075 3: additional HM config file loaded: ./FHEM/HMConfig_SenTHPL.pm
2021.11.16 17:01:36.956 1: HMCCU [myHMCCU3] CCU port 8181 is not reachable
2021.11.16 17:01:36.956 1: HMCCU [myHMCCU3] Initialized version 5.0 213171649
2021.11.16 17:01:36.957 1: HMCCU [myHMCCU3] Scheduling delayed initialization in 180 seconds
2021.11.16 17:01:36.962 3: myHMCCU3: unknown attribute rpcinterfaces. Type 'attr myHMCCU3 ?' for a detailed list.
2021.11.16 17:01:37.138 3: Opening myJeeLink1 device /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AL014JZA-if00-port0
2021.11.16 17:01:37.141 3: Setting myJeeLink1 serial parameters to 57600,8,N,1
2021.11.16 17:01:38.150 3: myJeeLink1 device opened
2021.11.16 17:01:39.233 3: TABLETUI: new ext defined infix:ftui/: dir:./www/tablet/:
2021.11.16 17:01:39.233 3: Registering HTTPSRV TABLETUI for URL /ftui and assigned link ftui/ ...
2021.11.16 17:01:39.614 3: HM485: HM485: Converting device files
2021.11.16 17:01:39.614 3: HM485: ==============================
2021.11.16 17:01:39.616 3: HM485: hmw_central.xml up to date
2021.11.16 17:01:39.616 3: HM485: hmw_generic.xml up to date
2021.11.16 17:01:39.617 3: HM485: hmw_io12_sw14_dr.xml up to date
2021.11.16 17:01:39.617 3: HM485: hmw_io12_sw7_dr.xml up to date
2021.11.16 17:01:39.617 3: HM485: hmw_io12_sw7_dr_V3_02.xml up to date
2021.11.16 17:01:39.617 3: HM485: hmw_io_12_fm.xml up to date
2021.11.16 17:01:39.617 3: HM485: hmw_io_4_fm.xml up to date
2021.11.16 17:01:39.618 3: HM485: hmw_io_4_fm_V3_02.xml up to date
2021.11.16 17:01:39.618 3: HM485: hmw_io_sr_fm.xml up to date
2021.11.16 17:01:39.618 3: HM485: hmw_lc_bl1_dr.xml up to date
2021.11.16 17:01:39.618 3: HM485: hmw_lc_bl1_dr_V3_02.xml up to date
2021.11.16 17:01:39.618 3: HM485: hmw_lc_dim1l_dr.xml up to date
2021.11.16 17:01:39.618 3: HM485: hmw_lc_sw2_dr.xml up to date
2021.11.16 17:01:39.619 3: HM485: hmw_lc_sw2_dr_V3_02.xml up to date
2021.11.16 17:01:39.619 3: HM485: hmw_sen_sc_12_dr.xml up to date
2021.11.16 17:01:39.619 3: HM485: Loading available device files
2021.11.16 17:01:39.619 3: HM485: ==============================
2021.11.16 17:01:39.619 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_central.pm
2021.11.16 17:01:39.622 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_generic.pm
2021.11.16 17:01:39.625 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw14_dr.pm
2021.11.16 17:01:39.633 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr.pm
2021.11.16 17:01:39.647 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io12_sw7_dr_V3_02.pm
2021.11.16 17:01:39.663 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_12_fm.pm
2021.11.16 17:01:39.677 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm.pm
2021.11.16 17:01:39.692 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_4_fm_V3_02.pm
2021.11.16 17:01:39.706 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_io_sr_fm.pm
2021.11.16 17:01:39.721 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr.pm
2021.11.16 17:01:39.741 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_bl1_dr_V3_02.pm
2021.11.16 17:01:39.761 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_dim1l_dr.pm
2021.11.16 17:01:39.782 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr.pm
2021.11.16 17:01:39.797 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_lc_sw2_dr_V3_02.pm
2021.11.16 17:01:39.811 3: HM485: Loading device file: ./FHEM/lib/HM485/Devices/hmw_sen_sc_12_dr.pm
2021.11.16 17:01:41.268 3: UPDATE_FTUI: Defined with URL https://raw.githubusercontent.com/knowthelist/fhem-tablet-ui/master/controls_fhemtabletui.txt and interval 86400 featurelevel 6.1
2021.11.16 17:01:42.150 3: Pollenflug: Defined with URL http://www.donnerwetter.de/pollenflug/region.hts?plz=88483&PTag=0 and interval 3600 featurelevel 6.1
2021.11.16 17:01:43.547 3: Opening my_callmonitor device 192.168.178.1:1012
2021.11.16 17:01:43.554 3: FB_CALLMONITOR (my_callmonitor) - loading cache file ./log/my_callmonitor.txt
2021.11.16 17:01:43.556 2: FB_CALLMONITOR (my_callmonitor) - read 36 contacts from Cache
2021.11.16 17:01:48.066 3: ArduinoNano_Zisterne: Defined with URL http://192.168.178.45/ and interval 61 featurelevel 6.1
2021.11.16 17:01:48.361 3: LaCrosse_Kueche: I/O device is myJeeLink1
2021.11.16 17:01:48.378 3: LaCrosse_Bad_EG: I/O device is myJeeLink1
2021.11.16 17:01:48.666 3: MQTT2_FHEM_Server: port 1883 opened
2021.11.16 17:01:49.152 3: HMCCUDEV [Licht_BadOG_Spiegel] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:49.828 3: freezemon defined myFreezemon freezemon
2021.11.16 17:01:49.831 0: [Freezemon] myFreezemon: Unwrapping CallFn
2021.11.16 17:01:49.831 0: [Freezemon] myFreezemon: Unwrapping AnalyzeCommand
2021.11.16 17:01:49.831 0: [Freezemon] myFreezemon: Unwrapping HttpUtils_NonblockingGet
2021.11.16 17:01:49.831 0: [Freezemon] myFreezemon: Unwrapping Log3
2021.11.16 17:01:49.832 3: [Freezemon] myFreezemon: Wrapping Log3
2021.11.16 17:01:51.696 2: HMCCURPCPROC [d_rpc178026BidCos_RF] CCU not ready. Trying later ...
2021.11.16 17:01:51.703 2: HMCCURPCPROC [d_rpc178026HmIP_RF] CCU not ready. Trying later ...
2021.11.16 17:01:51.795 3: Modul 90_Jalousie.pm: Init Done with Version V 0.00.09 von gevoo - 18.12.2015 modifiziert JG
2021.11.16 17:01:51.795 3: Name = Jal_KU_Fenster, Parameter = Jalousie Jal_KU_Fenster_03 39 2
2021.11.16 17:01:51.796 1: Jalousie mit Rolloaktor Jal_KU_Fenster_03 verbunden
2021.11.16 17:01:51.798 3: Name = Jal_KU_Sued, Parameter = Jalousie Jal_KU_Sued_03 64 2
2021.11.16 17:01:51.799 1: Jalousie mit Rolloaktor Jal_KU_Sued_03 verbunden
2021.11.16 17:01:51.801 3: Name = Jal_WZ_Fest_Ost, Parameter = Jalousie Jal_WZ_Fest_Ost_03 64 2
2021.11.16 17:01:51.802 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Ost_03 verbunden
2021.11.16 17:01:51.804 3: Name = Jal_WZ_Fest_Sued, Parameter = Jalousie Jal_WZ_Fest_Sued_03 64 2
2021.11.16 17:01:51.805 1: Jalousie mit Rolloaktor Jal_WZ_Fest_Sued_03 verbunden
2021.11.16 17:01:51.807 3: Name = Jal_WZ_Schiebetuer, Parameter = Jalousie Jal_WZ_Schiebetuer_03 64 2
2021.11.16 17:01:51.807 1: Jalousie mit Rolloaktor Jal_WZ_Schiebetuer_03 verbunden
2021.11.16 17:01:51.810 3: Name = Jal_WZ_SuedWest, Parameter = Jalousie Jal_WZ_Fest_SuedWest_03 64 2
2021.11.16 17:01:51.810 1: Jalousie mit Rolloaktor Jal_WZ_Fest_SuedWest_03 verbunden
2021.11.16 17:01:51.812 3: Name = Jal_WZ_West, Parameter = Jalousie Jal_WZ_Fest_West_03 64 2
2021.11.16 17:01:51.813 1: Jalousie mit Rolloaktor Jal_WZ_Fest_West_03 verbunden
2021.11.16 17:01:52.711 3: HMCCUCHN [Alarm_KueOst_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:52.760 3: HMCCUCHN [Alarm_KueSued_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:52.797 3: HMCCUDEV [HmIP_BDT_0008DA49929255_3] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:52.875 3: HMCCUCHN [Heiz_BadOG_Handtuch_HmIP] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:52.937 2: HMCCURPCPROC [d_rpc178026VirtualDevices] CCU not ready. Trying later ...
2021.11.16 17:01:52.952 3: HMCCUDEV [Thermostat_AZ] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:52.996 3: HMCCUDEV [Thermostat_BadOG] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:53.037 3: HMCCUDEV [Thermostat_BibOG] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:53.075 3: HMCCUDEV [Thermostat_Kue] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:53.109 3: HMCCUDEV [Thermostat_WZ] Cannot detect IO device, maybe CCU not ready or device doesn't exist on CCU
2021.11.16 17:01:53.135 1: Including ./log/fhem.save
2021.11.16 17:01:55.010 3: Opening myHMUARTGPIO device 192.168.178.53:4001
2021.11.16 17:01:55.013 1: CUL_HM start inital cleanup
2021.11.16 17:01:57.219 1: CUL_HM finished initial cleanup
2021.11.16 17:01:57.302 3: monitoring (Activity_monitoring) set Activity_monitoring active
HMCCU braucht immer lange zum booten. FHEM ist schneller. Habe hier hier mit einer CCU2 die gleichen Probleme, wenn nach einem Stromausfall die Systeme hochfahren. Eigentlich sollte das HMCCU-Modul das abkönnen, hatte aber bisher (noch) keine Zeit/Lust dazu, es zu analysieren, zu optimieren. Wahrscheinlich würde in reopen auf HMCCU-Connecktor ausreichen.
Wenn mit "blocking" ist es schon abschmiert, bringt Dir die 5 wenig. kannst ja mal gucken, ob der oom wieder zugeschlagen hat (wieder als root oder sudo):
grep -i -e "oom" -e "i/o" /var/log/kern.log
Es gibt übrigens eine andere alternative: Ein System mit mehr Speicher (Hardware) ..... allerdings bin ich (persöhnlich) ein Freund von separieren. Auf meinem hauptsystem per docker, aber z.B. das externe "gateway" ist auch ein Pi. Und für gewisse Hardware (sispm-Dosen) gibt es auch noch einen 2. Pi. Wenn der Probleme auf dem USB-Bus bekommt, interessiert es mein Hauptrechner dadurch überhaupt nicht.
Wenn die CCU als Software auf dem gleichen Rechner läuft wie FHEM, ist bei einem Neustart FHEM immer viel schneller wieder da.
Ich würde das auf 2 System verteilen, das macht vieles einfacher
Je nach Menge der Devices und der genutzten Schnittstellen hatte ich bei der CCU schon Startzeiten von >1 Minute
Hallo,
habe jetzt einen Raspi 3B mit piVCCU aufgesetzt. Läuft auch.
Habe einen Main-Raspi mit FHEM neu aufgesetzt, da das Backup des Haupt-Raspi nicht sicher gelaufen ist. Sporadisch wieder die Abstürze, sodaß ich mich entschlossen habe, FHEM komplett neu aufzusetzen. Dabei stoße ich natürlich immer wieder auf Probleme (HM485 erkennt nicht alle Aktoren, Shellys gehen noch gar nicht....) aber ich kämpfe mich durch.
Danke an alle, die mir geholfen haben.