NEWS
UNSOLVED (gelöst) Raspi rebootet, dann fkt. Zigbee nicht mehr
-
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 Raspi rebootet (warum, kA), dann zeigt der Zigbee Adapter das alles OK ist aber es kommen keine Daten mehr.
-
@Humidor nodejs sauber installiert?
node -v und nodejs -v müssen die gleiche Version zurückgeben.
Schau hier mal rein:https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian/13
-
@Thomas-Braun sagte in Raspi rebootet, dann fkt. Zigbee nicht mehr:
nodejs -v
Hi Thomas
ja, beide sind identische VersionenEs hat sich auch gerade was getan, nach 1 Stunde kam ein neuer Wert ??
Stellt sich die Frage warum der Pi restartet. -
@Humidor Und warum gibst du dann oben im Kasten was anderes an?
Zeig die Ausgabe von
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
-
das sind Standard-Einträge, ich kenne keinen Unterschied von Node und Nodejs, Nodejs habe ich unter Info gefunden und eingetragen..... hab es geändert.
/usr/bin/nodejs v12.18.2 /usr/bin/node v12.18.2 /usr/bin/npm 6.14.5 nodejs: Installiert: 12.18.2-1nodesource1 Installationskandidat: 12.18.2-1nodesource1 Versionstabelle: *** 12.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.21.0~dfsg-1~deb10u1+rpi1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
-
-
pi@humidor:~ $ less /var/log/messages Jul 17 17:37:09 humidor kernel: [ 5.056266] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Jul 17 17:37:09 humidor kernel: [ 5.098671] logitech-djreceiver 0003:046D:C52B.0003: hiddev96,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-3f980000.usb-1.1.3/input2 Jul 17 17:37:09 humidor kernel: [ 5.134672] usbcore: registered new interface driver brcmfmac Jul 17 17:37:09 humidor kernel: [ 5.243499] input: Logitech Unifying Device. Wireless PID:4024 Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input0 Jul 17 17:37:09 humidor kernel: [ 5.244888] input: Logitech Unifying Device. Wireless PID:4024 Mouse as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input1 Jul 17 17:37:09 humidor kernel: [ 5.245577] input: Logitech Unifying Device. Wireless PID:4024 Consumer Control as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input2 Jul 17 17:37:09 humidor kernel: [ 5.245935] hid-generic 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:4024] on usb-3f980000.usb-1.1.3:1 Jul 17 17:37:09 humidor kernel: [ 5.391271] random: crng init done Jul 17 17:37:09 humidor kernel: [ 5.391285] random: 7 urandom warning(s) missed due to ratelimiting Jul 17 17:37:09 humidor kernel: [ 5.499809] sd 0:0:0:0: Attached scsi generic sg0 type 0 Jul 17 17:37:09 humidor kernel: [ 6.093532] input: Logitech K400 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.3/1-1.1.3:1.2/0003:046D:C52B.0003/0003:046D:4024.0004/input/input6 Jul 17 17:37:09 humidor kernel: [ 6.094646] logitech-hidpp-device 0003:046D:4024.0004: input,hidraw1: USB HID v1.11 Keyboard [Logitech K400] on usb-3f980000.usb-1.1.3:1 Jul 17 17:37:09 humidor mtp-probe: bus: 1, device: 7 was not an MTP device Jul 17 17:37:09 humidor usbmount[234]: /dev/sda does not contain a filesystem or disklabel Jul 17 17:37:09 humidor rsyslogd: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.1901.0] Jul 17 17:37:09 humidor rsyslogd: [origin software="rsyslogd" swVersion="8.1901.0" x-pid="350" x-info="https://www.rsyslog.com"] start Jul 17 17:37:10 humidor kernel: [ 7.332531] uart-pl011 3f201000.serial: no DMA platform data Jul 17 17:37:10 humidor kernel: [ 7.407180] 8021q: 802.1Q VLAN Support v1.8 Jul 17 17:37:10 humidor kernel: [ 7.586757] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS Jul 17 17:37:10 humidor kernel: [ 7.683263] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Jul 17 17:37:10 humidor kernel: [ 8.015640] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Jul 17 17:37:10 humidor kernel: [ 8.015658] 8021q: adding VLAN 0 to HW filter on device eth0 Jul 17 17:37:10 humidor kernel: [ 8.030859] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Jul 17 17:37:16 humidor kernel: [ 14.110257] Bluetooth: Core ver 2.22 Jul 17 17:37:16 humidor kernel: [ 14.110314] NET: Registered protocol family 31 Jul 17 17:37:16 humidor kernel: [ 14.110318] Bluetooth: HCI device and connection manager initialized Jul 17 17:37:16 humidor kernel: [ 14.110332] Bluetooth: HCI socket layer initialized Jul 17 17:37:16 humidor kernel: [ 14.110339] Bluetooth: L2CAP socket layer initialized Jul 17 17:37:16 humidor kernel: [ 14.110359] Bluetooth: SCO socket layer initialized Jul 17 17:37:16 humidor kernel: [ 14.141987] Bluetooth: HCI UART driver ver 2.3 Jul 17 17:37:16 humidor kernel: [ 14.142001] Bluetooth: HCI UART protocol H4 registered Jul 17 17:37:16 humidor kernel: [ 14.142085] Bluetooth: HCI UART protocol Three-wire (H5) registered Jul 17 17:37:16 humidor kernel: [ 14.142292] Bluetooth: HCI UART protocol Broadcom registered Jul 17 17:37:17 humidor kernel: [ 14.605120] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Jul 17 17:37:17 humidor kernel: [ 14.605128] Bluetooth: BNEP filters: protocol multicast Jul 17 17:37:17 humidor kernel: [ 14.605140] Bluetooth: BNEP socket layer initialized Jul 17 18:02:22 humidor kernel: [ 1511.033942] usb 1-1.1.2: USB disconnect, device number 5 Jul 17 18:02:26 humidor kernel: [ 1514.409614] usb 1-1.1.3: USB disconnect, device number 6 Jul 17 18:15:55 humidor kernel: [ 2323.365861] usb 1-1.1.2: new high-speed USB device number 8 using dwc_otg Jul 17 18:15:55 humidor kernel: [ 2323.501989] usb 1-1.1.2: New USB device found, idVendor=0951, idProduct=1665, bcdDevice= 1.00 Jul 17 18:15:55 humidor kernel: [ 2323.502005] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 17 18:15:55 humidor kernel: [ 2323.502014] usb 1-1.1.2: Product: DataTraveler 2.0 Jul 17 18:15:55 humidor kernel: [ 2323.502023] usb 1-1.1.2: Manufacturer: Kingston Jul 17 18:15:55 humidor kernel: [ 2323.502032] usb 1-1.1.2: SerialNumber: 001BFC31A1C7BF8159AD3830 Jul 17 18:15:55 humidor kernel: [ 2323.505779] usb-storage 1-1.1.2:1.0: USB Mass Storage device detected Jul 17 18:15:55 humidor kernel: [ 2323.507718] scsi host0: usb-storage 1-1.1.2:1.0 Jul 17 18:15:55 humidor mtp-probe: checking bus 1, device 8: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2" Jul 17 18:15:55 humidor mtp-probe: bus: 1, device: 8 was not an MTP device Jul 17 18:15:55 humidor mtp-probe: checking bus 1, device 8: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2" Jul 17 18:15:55 humidor mtp-probe: bus: 1, device: 8 was not an MTP device Jul 17 18:15:56 humidor kernel: [ 2324.569059] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 4 Jul 17 18:15:56 humidor kernel: [ 2324.572531] sd 0:0:0:0: Attached scsi generic sg0 type 0 Jul 17 18:15:57 humidor kernel: [ 2325.952473] sd 0:0:0:0: [sda] 30728832 512-byte logical blocks: (15.7 GB/14.7 GiB) Jul 17 18:15:57 humidor kernel: [ 2325.952756] sd 0:0:0:0: [sda] Write Protect is off Jul 17 18:15:57 humidor kernel: [ 2325.979106] sda: sda1 Jul 17 18:15:57 humidor kernel: [ 2325.982043] sd 0:0:0:0: [sda] Attached SCSI removable disk Jul 17 18:15:57 humidor usbmount[2670]: /dev/sda does not contain a filesystem or disklabel Jul 17 18:15:58 humidor usbmount[2689]: executing command: mount -tvfat -osync,noexec,nodev,noatime,nodiratime,gid=users,dmask=0007,fmask=0117 /dev/sda1 /media/usb0 Jul 17 18:15:58 humidor usbmount[2689]: executing command: run-parts /etc/usbmount/mount.d (END)
ich kann das ganze irgendwie hier nicht posten, was soll ich den suchen / finden ?
zeigt das etwas interessantes?
Jul 15 13:02:29 humidor kernel: [ 1171.005835] usb 1-1.3: new full-speed USB device number 7 using dwc_otg Jul 15 13:02:29 humidor kernel: [ 1171.153607] usb 1-1.3: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09 Jul 15 13:02:29 humidor kernel: [ 1171.153618] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 15 13:02:29 humidor kernel: [ 1171.153623] usb 1-1.3: Product: TI CC2531 USB CDC Jul 15 13:02:29 humidor kernel: [ 1171.153627] usb 1-1.3: Manufacturer: Texas Instruments Jul 15 13:02:29 humidor kernel: [ 1171.153631] usb 1-1.3: SerialNumber: __0X00124B00016C09A3 Jul 15 13:02:29 humidor mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3" Jul 15 13:02:29 humidor mtp-probe: bus: 1, device: 7 was not an MTP device Jul 15 13:02:29 humidor kernel: [ 1171.432576] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device Jul 15 13:02:29 humidor kernel: [ 1171.433277] usbcore: registered new interface driver cdc_acm Jul 15 13:02:29 humidor kernel: [ 1171.433284] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters Jul 15 13:02:29 humidor mtp-probe: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3" Jul 15 13:02:29 humidor mtp-probe: bus: 1, device: 7 was not an MTP device Jul 15 16:42:03 humidor kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Jul 15 16:42:03 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 15 16:42:03 humidor kernel: [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d Jul 15 16:42:03 humidor kernel: [ 0.000000] CPU: div instructions available: patching division code Jul 15 16:42:03 humidor kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Jul 15 16:42:03 humidor kernel: [ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 Jul 15 16:42:03 humidor kernel: [ 0.000000] Memory policy: Data cache writealloc Jul 15 16:42:03 humidor kernel: [ 0.000000] cma: Reserved 8 MiB at 0x3ac00000 Jul 15 16:42:03 humidor kernel: [ 0.000000] random: get_random_bytes called from start_kernel+0xac/0x4b4 with crng_init=0 Jul 15 16:42:03 humidor kernel: [ 0.000000] percpu: Embedded 16 pages/cpu s36864 r8192 d20480 u65536 Jul 15 16:42:03 humidor kernel: [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 240555 Jul 15 16:42:03 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=1824 bcm2708_fb.fbheight=984 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
-
@Humidor Nix ungewöhnliches zu sehen. Nur dein Speichermedium hat kein disklabel.
-
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?
-
@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
-
das log in der iobroker oberfläche?
dort sehe ich nicht alles? nur ständig diese Einträgeweb.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
-
-
@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 ....
-
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...
-
@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 ???
-
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
-
Nee ... die Log´s zeigen nichts .
Beobachte es und dann kannst du dich ja wieder melden .......
-
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 nachvollziehen2020-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