(gelöst) Raspi rebootet, dann fkt. Zigbee nicht mehr

Humidor

hier vielleicht?

Jul 16 20:17:12 humidor kernel: [   14.612125] Bluetooth: BNEP filters: protocol multicast
Jul 16 20:17:12 humidor kernel: [   14.612157] Bluetooth: BNEP socket layer initialized
Jul 17 00:00:32 humidor rsyslogd:  [origin software="rsyslogd" swVersion="8.1901.0" x-pid="306" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Jul 17 17:37:09 humidor mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Jul 17 17:37:09 humidor mtp-probe: bus: 1, device: 7 was not an MTP device
Jul 17 17:37:09 humidor mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Jul 17 17:37:09 humidor mtp-probe: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2"
Jul 17 17:37:09 humidor mtp-probe: bus: 1, device: 5 was not an MTP device
Jul 17 17:37:09 humidor mtp-probe: checking bus 1, device 6: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3"
Jul 17 17:37:09 humidor mtp-probe: bus: 1, device: 6 was not an MTP device
Jul 17 17:37:09 humidor mtp-probe: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Jul 17 17:37:09 humidor mtp-probe: bus: 1, device: 4 was not an MTP device
Jul 17 17:37:09 humidor mtp-probe: bus: 1, device: 7 was not an MTP device
Jul 17 17:37:09 humidor mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1"
Jul 17 17:37:09 humidor kernel: [    0.000000] Booting Linux on physical CPU 0x0
Jul 17 17:37:09 humidor kernel: [    0.000000] Linux version 4.19.118-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1311 SMP Mon Apr 27 14:21:24 BST 2020
Jul 17 17:37:09 humidor kernel: [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
Jul 17 17:37:09 humidor kernel: [    0.000000] CPU: div instructions available: patching division code
Jul 17 17:37:09 humidor kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Jul 17 17:37:09 humidor kernel: [    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
Jul 17 17:37:09 humidor kernel: [    0.000000] Memory policy: Data cache writealloc
Jul 17 17:37:09 humidor kernel: [    0.000000] cma: Reserved 8 MiB at 0x3ac00000
Jul 17 17:37:09 humidor kernel: [    0.000000] random: get_random_bytes called from start_kernel+0xac/0x4b4 with crng_init=0
Jul 17 17:37:09 humidor kernel: [    0.000000] percpu: Embedded 16 pages/cpu s36864 r8192 d20480 u65536
Jul 17 17:37:09 humidor kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 240555
Jul 17 17:37:09 humidor kernel: [    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.f
bwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 elevator=deadline 
fsck.repair=yes rootwait
Jul 17 17:37:09 humidor kernel: [    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Jul 17 17:37:09 humidor kernel: [    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Jul 17 17:37:09 humidor kernel: [    0.000000] Memory: 939064K/970752K available (8192K kernel code, 656K rwdata, 2232K rodata, 1024K init, 831K bss, 23496K reserved, 8192K cma-reserved)
Jul 17 17:37:09 humidor kernel: [    0.000000] Virtual kernel memory layout:

ist 0.00000 dort wo er neu gestartet hat?

Glasfaser

@Humidor sagte in Raspi rebootet, dann fkt. Zigbee nicht mehr:

Raspi rebootet (warum, kA),

Du meinst ioBroker hat rebootet !?

dann schau im ioBroker Log , was dort die letzten Meldungen sind

Humidor

das log in der iobroker oberfläche?
dort sehe ich nicht alles? nur ständig diese Einträge


web.0	2020-07-17 19:12:35.199	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flot
web.0	2020-07-17 19:12:34.475	info	(615) ==>Connected system.user.admin from 192.168.0.170
web.0	2020-07-17 19:12:34.340	info	(615) <==Disconnect system.user.admin from 192.168.0.170 vis.0
web.0	2020-07-17 19:12:33.814	info	(615) ==>Connected system.user.admin from 192.168.0.170
web.0	2020-07-17 19:12:33.812	info	(615) ==>Connected system.user.admin from 192.168.0.170
web.0	2020-07-17 19:10:33.959	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flot
web.0	2020-07-17 19:10:33.952	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flotEdit
web.0	2020-07-17 19:10:24.728	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flot
web.0	2020-07-17 19:10:24.726	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flot
web.0	2020-07-17 19:10:24.712	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flot
web.0	2020-07-17 19:10:23.729	info	(615) <==Disconnect system.user.admin from 192.168.0.170 flot

Glasfaser

@Humidor

Nee ... das sind die aktuellen Log´s

hier :

.

Glasfaser

@Humidor sagte in Raspi rebootet, dann fkt. Zigbee nicht mehr:

web.0 2020-07-17 19:10:33.959

Deine Uhrzeit ist auch nicht richtig ... !!!
oder ist das ein Auszug ...

vor dem Absturz / Reboot den Log ....

Humidor

um 17:37 hat er einen restart gemacht, ob pi oder iobroker kann ich echt nicht sagen

2020-07-17 17:37:01.970 - info: host.humidor received SIGTERM
2020-07-17 17:37:02.118 - info: javascript.0 (1117) Stop script script.js.common.Humidor_#1
2020-07-17 17:37:02.021 - info: fritzdect.0 (1245) cleaned everything up...
2020-07-17 17:37:02.004 - info: harmony.0 (1038) [END] Terminating
2020-07-17 17:37:02.185 - info: telegram.0 (17023) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.231 - info: fritzdect.0 (1245) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.241 - info: javascript.0 (1117) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.123 - info: host.humidor stopInstance system.adapter.admin.0 (force=false, process=true)
2020-07-17 17:37:02.124 - info: host.humidor stopInstance system.adapter.info.0 (force=false, process=true)
2020-07-17 17:37:02.126 - info: host.humidor stopInstance system.adapter.zigbee.0 (force=false, process=true)
2020-07-17 17:37:02.136 - info: host.humidor stopInstance system.adapter.web.0 (force=false, process=true)
2020-07-17 17:37:02.138 - info: host.humidor stopInstance system.adapter.harmony.0 (force=false, process=true)
2020-07-17 17:37:02.139 - info: host.humidor stopInstance system.adapter.telegram.0 (force=false, process=true)
2020-07-17 17:37:02.140 - info: host.humidor stopInstance system.adapter.javascript.0 (force=false, process=true)
2020-07-17 17:37:02.142 - info: host.humidor stopInstance system.adapter.cloud.0 (force=false, process=true)
2020-07-17 17:37:02.143 - info: host.humidor stopInstance system.adapter.iot.0 (force=false, process=true)
2020-07-17 17:37:02.144 - info: host.humidor stopInstance system.adapter.hue.0 (force=false, process=true)
2020-07-17 17:37:02.145 - info: host.humidor stopInstance system.adapter.rpi2.0 (force=false, process=true)
2020-07-17 17:37:02.147 - info: host.humidor stopInstance system.adapter.vis.0 (force=false, process=false)
2020-07-17 17:37:02.149 - info: host.humidor stopInstance system.adapter.fritzdect.0 (force=false, process=true)
2020-07-17 17:37:02.150 - info: host.humidor stopInstance system.adapter.history.0 (force=false, process=true)
2020-07-17 17:37:02.155 - info: host.humidor stopInstance system.adapter.admin.0 send kill signal
2020-07-17 17:37:02.159 - info: host.humidor stopInstance system.adapter.info.0 send kill signal
2020-07-17 17:37:02.162 - info: host.humidor stopInstance system.adapter.zigbee.0 send kill signal
2020-07-17 17:37:02.167 - info: host.humidor stopInstance system.adapter.web.0 send kill signal
2020-07-17 17:37:02.176 - info: host.humidor stopInstance system.adapter.harmony.0 send kill signal
2020-07-17 17:37:02.179 - info: host.humidor stopInstance system.adapter.telegram.0 send kill signal
2020-07-17 17:37:02.197 - info: host.humidor stopInstance system.adapter.javascript.0 send kill signal
2020-07-17 17:37:02.201 - info: host.humidor stopInstance system.adapter.cloud.0 send kill signal
2020-07-17 17:37:02.205 - info: host.humidor stopInstance system.adapter.iot.0 send kill signal
2020-07-17 17:37:02.215 - info: host.humidor stopInstance system.adapter.hue.0 send kill signal
2020-07-17 17:37:02.219 - info: host.humidor stopInstance system.adapter.rpi2.0 send kill signal
2020-07-17 17:37:02.222 - info: host.humidor stopInstance system.adapter.fritzdect.0 send kill signal
2020-07-17 17:37:02.182 - info: cloud.0 (1134) Connection changed: io client disconnect
2020-07-17 17:37:02.230 - info: cloud.0 (1134) Connection lost
2020-07-17 17:37:02.268 - info: cloud.0 (1134) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.210 - info: harmony.0 (1038) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.141 - info: web.0 (567) terminated http server on port 8082
2020-07-17 17:37:01.972 - info: info.0 (533) cleaned everything up...
2020-07-17 17:37:02.161 - info: iot.0 (1151) Connection changed: disconnect
2020-07-17 17:37:02.311 - info: info.0 (533) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.313 - info: web.0 (567) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.223 - info: rpi2.0 (1185) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.022 - info: hue.0 (1166) cleaned everything up...
2020-07-17 17:37:02.214 - info: iot.0 (1151) Connection lost
2020-07-17 17:37:02.328 - info: iot.0 (1151) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.332 - info: hue.0 (1166) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:01.979 - info: admin.0 (522) terminating http server on port 8081
2020-07-17 17:37:02.403 - info: harmony.0 (1038) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.410 - info: fritzdect.0 (1245) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.419 - info: rpi2.0 (1185) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.424 - info: info.0 (533) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.436 - info: hue.0 (1166) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.438 - info: cloud.0 (1134) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.443 - info: iot.0 (1151) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.437 - info: web.0 (567) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.458 - info: javascript.0 (1117) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.413 - info: history.0 (1260) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.027 - info: zigbee.0 (556) cleaned everything up...
2020-07-17 17:37:02.369 - info: zigbee.0 (556) Zigbee: disabling joining new devices.
2020-07-17 17:37:02.483 - info: zigbee.0 (556) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.372 - info: admin.0 (522) Got terminate signal TERMINATE_YOURSELF
2020-07-17 17:37:02.536 - info: telegram.0 (17023) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.548 - info: admin.0 (522) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:02.722 - info: zigbee.0 (556) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-17 17:37:03.082 - info: host.humidor instance system.adapter.harmony.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.107 - info: host.humidor instance system.adapter.rpi2.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.119 - info: host.humidor instance system.adapter.fritzdect.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.136 - info: host.humidor instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.151 - info: host.humidor instance system.adapter.cloud.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.170 - info: host.humidor instance system.adapter.iot.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.180 - info: host.humidor instance system.adapter.hue.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.182 - info: host.humidor stopInstance system.adapter.admin.0 killing pid 522
2020-07-17 17:37:03.183 - info: host.humidor stopInstance system.adapter.zigbee.0 killing pid 556
2020-07-17 17:37:03.184 - info: host.humidor stopInstance system.adapter.web.0 killing pid 567
2020-07-17 17:37:03.185 - info: host.humidor stopInstance system.adapter.telegram.0 killing pid 17023
2020-07-17 17:37:03.229 - info: host.humidor instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.231 - warn: host.humidor instance system.adapter.zigbee.0 terminated due to SIGTERM
2020-07-17 17:37:03.232 - info: host.humidor instance system.adapter.zigbee.0 terminated with code null ()
2020-07-17 17:37:03.233 - info: host.humidor instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.238 - info: host.humidor instance system.adapter.javascript.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.240 - info: host.humidor instance system.adapter.history.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.240 - info: host.humidor All instances are stopped.
2020-07-17 17:37:03.242 - info: host.humidor instance system.adapter.telegram.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-07-17 17:37:03.243 - info: host.humidor All instances are stopped.
2020-07-17 17:37:03.384 - info: host.humidor terminated
2020-07-17 17:37:20.059 - info: host.humidor iobroker.js-controller version 3.1.6 js-controller starting
2020-07-17 17:37:20.067 - info: host.humidor Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-07-17 17:37:20.068 - info: host.humidor hostname: humidor, node: v12.18.2
2020-07-17 17:37:20.071 - info: host.humidor ip addresses: 192.168.0.153 fe80::212e:9e36:4462:6d29
2020-07-17 17:37:20.628 - info: host.humidor connected to Objects and States
2020-07-17 17:37:21.161 - info: host.humidor 15 instances found
2020-07-17 17:37:21.245 - info: host.humidor starting 14 instances
2020-07-17 17:37:21.302 - info: host.humidor instance system.adapter.admin.0 started with pid 568
2020-07-17 17:37:25.272 - info: host.humidor instance system.adapter.info.0 started with pid 579
2020-07-17 17:37:26.104 - info: admin.0 (568) starting. Version 4.1.1 in /opt/iobroker/node_modules/iobroker.admin, node: v12.18.2, js-controller: 3.1.6
2020-07-17 17:37:26.235 - info: admin.0 (568) requesting all states
2020-07-17 17:37:26.237 - info: admin.0 (568) requesting all objects
2020-07-17 17:37:27.388 - info: admin.0 (568) received all objects
2020-07-17 17:37:27.747 - info: admin.0 (568) http server listening on port 8081
2020-07-17 17:37:27.748 - info: admin.0 (568) Use link "http://localhost:8081" to configure.
2020-07-17 17:37:29.265 - info: host.humidor instance system.adapter.zigbee.0 started with pid 602
2020-07-17 17:37:33.288 - info: host.humidor instance system.adapter.web.0 started with pid 615
2020-07-17 17:37:33.312 - info: zigbee.0 (602) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.zigbee, node: v12.18.2, js-controller: 3.1.6
2020-07-17 17:37:33.385 - info: zigbee.0 (602) Starting Zigbee...

Glasfaser

@Humidor sagte in Raspi rebootet, dann fkt. Zigbee nicht mehr:

um 17:37 hat er einen restart gemacht,

und vor dieser Zeit ... was steht im Log

Error / Warn ???

Humidor

2020-07-17 17:27:27.191 - info: web.0 (567) <==Disconnect system.user.admin from 192.168.0.170 flot
2020-07-17 17:27:27.281 - info: web.0 (567) ==>Connected system.user.admin from 192.168.0.170
2020-07-17 17:27:31.128 - info: web.0 (567) <==Disconnect system.user.admin from 192.168.0.170 flot
2020-07-17 17:27:31.133 - info: web.0 (567) <==Disconnect system.user.admin from 192.168.0.170 flot
2020-07-17 17:27:31.137 - info: web.0 (567) <==Disconnect system.user.admin from 192.168.0.170 vis.0
2020-07-17 17:27:31.387 - info: web.0 (567) ==>Connected system.user.admin from 192.168.0.170
2020-07-17 17:27:31.749 - info: web.0 (567) ==>Connected system.user.admin from 192.168.0.170
2020-07-17 17:27:31.894 - info: web.0 (567) ==>Connected system.user.admin from 192.168.0.170
2020-07-17 17:30:21.444 - info: javascript.0 (1117) script.js.common.Humidor_#1: Temperatur OK
2020-07-17 17:31:27.035 - info: javascript.0 (1117) Stop script script.js.common.Humidor_#1
2020-07-17 17:31:27.148 - info: javascript.0 (1117) Start javascript script.js.common.Humidor_#1
2020-07-17 17:31:27.170 - info: javascript.0 (1117) script.js.common.Humidor_#1: registered 2 subscriptions and 1 schedule

Glasfaser

@Humidor

Nee ... die Log´s zeigen nichts .

Beobachte es und dann kannst du dich ja wieder melden .......

Humidor

ich denke jetzt nicht, dass der Pi oder iobroker neu startet, nur die Instanz Telegram ??
sheduled restart.... nicht von mir wo definiert, weder in der Instanz noch im Telegram kann ich solch eine Einstellung nachvollziehen

2020-07-18 04:44:09.034 - info: web.0 (615) <==Disconnect system.user.admin from 192.168.0.170 flotEdit
2020-07-18 04:44:09.906 - info: web.0 (615) <==Disconnect system.user.admin from 192.168.0.170 flot
2020-07-18 04:44:11.719 - info: web.0 (615) <==Disconnect system.user.admin from 192.168.0.170 vis.0
2020-07-18 04:44:11.731 - info: web.0 (615) <==Disconnect system.user.admin from 192.168.0.170 vis.0
2020-07-18 04:44:11.983 - info: web.0 (615) <==Disconnect system.user.admin from 192.168.0.170
2020-07-18 05:04:00.070 - info: telegram.0 (1147) Scheduled restart.
2020-07-18 05:04:00.621 - info: telegram.0 (1147) terminating
2020-07-18 05:04:00.623 - info: telegram.0 (1147) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-07-18 05:04:01.200 - info: host.humidor instance system.adapter.telegram.0 scheduled normal terminated and will be restarted on schedule.
2020-07-18 05:04:01.230 - info: host.humidor Restart adapter system.adapter.telegram.0 because enabled
2020-07-18 05:04:02.287 - info: host.humidor instance system.adapter.telegram.0 started with pid 24331
2020-07-18 05:04:06.273 - info: telegram.0 (24331) starting. Version 1.5.9 in /opt/iobroker/node_modules/iobroker.telegram, node: v12.18.2, js-controller: 3.1.6
2020-07-18 05:22:12.811 - info: javascript.0 (1163) script.js.common.Humidor_#1: Temperatur OK
2020-07-18 05:22:12.815 - info: javascript.0 (1163) script.js.common.Humidor_#1: Feuchte OK
2020-07-18 06:13:38.841 - info: web.0 (615) ==>Connected system.user.admin from 192.168.0.170
2020-07-18 06:13:39.481 - info: web.0 (615) ==>Connected system.user.admin from 192.168.0.170

#OK gefunden, ein Cron Job (im Experten Modus sichtbar) macht einen Restart

Systemdata	Bitte Ausfüllen
Hardwaresystem:	Pi3b+
Arbeitsspeicher:	1GB
Festplattenart:	SD-Karte
Betriebssystem:	Ubuntu
Node-Version:	12.18.2
Nodejs-Version:	12.18.2
NPM-Version:	6.14.5
Installationsart:	Skript
Image genutzt:	Ja
Ort/Name der Imagedatei:	https://www.iobroker.net/#de/download

Community Forum

NEWS

(gelöst) Raspi rebootet, dann fkt. Zigbee nicht mehr

Support us

801

32.4k

81.6k

1.3m