@chrissh Und ob das jemandem hilft Vielen lieben Dank für die Vorlage! Wo hast du denn die richtigen Mappings für die Homekit Funktionen gefunden?
NEWS
Latest posts made by TronLand
-
RE: Einstellungen für Klimaanlage Daikin mit YAHKA
-
RE: Proxmox VM friert ein
Jetzt ist es wieder passiert... ;-(
In keinen Logs auch nur der geringste Hinweis. Alle Logs sehen normal aus, dann plötzlich kein Eintrag mehr bis zu meinem Reboot. Bin echt am Verzweifeln.
Ich bin echt für jeden Hinweis dankbar.Gruß
Michael -
RE: Proxmox VM friert ein
@dr-bakterius
Hatte alle Skripte deaktiviert.
Das mit den 50% (+-5) ist so ein Proxmox Ding. Wenn eine VM mal z.B. einen Kernal Panic wirft und nicht mehr erreichbar ist, dann zeigt Proxmox genau die gleiche Auslastung. Warum, weiß ich nicht.
A -
RE: Proxmox VM friert ein
Nach was genau? Die Datenbank ist auf einem anderen Rechner.
Meinst du in der Konfiguration des ioBroker Adapters?
Was könnte denn dort nicht stimmen? Sieht für mich so aus, als würde der Adapter genau das machen, was er soll. Nach 20 (oder mehr) neuen Daten einmal zur Datenbank schreiben.Gruß
Michael
-
RE: Proxmox VM friert ein
Hallo,
nun ist es wieder passiert.
Habe eine neue (64bit) VM aufgesetzt und ioBroker restored.
Punkt 22:18 ging die Prozessorlast auf ca. 50% und ioBroker war nicht mehr erreichbar.Linux ioBroker 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Jul 10 15:45:11 2022 from 192.168.10.111 tech@ioBroker:~$ cd /opt/iobroker tech@ioBroker:/opt/iobroker$ npm ls | grep -E 'github.com|ERR' [sudo] password for tech: ├── iobroker.life360@0.2.17 (git+ssh://git@github.com/migoller/iobroker.life360.git#fb48e5d206f904abaf7a464acb79eb0dfbab52ea) tech@ioBroker:/opt/iobroker$ iobroker update -i Used repository: stable Adapter "admin" : 5.3.8 , installed 5.3.8 Adapter "backitup" : 2.4.9 , installed 2.4.9 Adapter "discovery" : 3.0.3 , installed 3.0.3 Adapter "hm-rega" : 3.0.40 , installed 3.0.40 Adapter "hm-rpc" : 1.15.12 , installed 1.15.12 Adapter "influxdb" : 2.6.3 , installed 2.6.3 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.11.4 , installed 1.11.4 Adapter "javascript" : 5.7.0 , installed 5.7.0 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "mqtt" : 3.0.6 , installed 3.0.6 Adapter "node-red" : 3.3.1 , installed 3.3.1 Adapter "nut" : 1.5.1 , installed 1.5.1 Adapter "pi-hole" : 1.3.4 , installed 1.3.4 Adapter "smartmeter" : 3.3.4 , installed 3.3.4 Adapter "wireguard" : 1.3.1 , installed 1.3.1 Adapter "withings" : 0.0.9 , installed 0.0.7 [Updatable] Adapter "yahka" : 0.13.1 , installed 0.13.1 Adapter "zigbee" : 1.7.5 , installed 1.7.5 tech@ioBroker:/opt/iobroker$ sudo ln -s /usr/bin/node /usr/bin/nodejs ln: failed to create symbolic link '/usr/bin/nodejs': File exists tech@ioBroker:/opt/iobroker$ uname -m && which nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs x86_64 /usr/bin/nodejs /usr/bin/node /usr/bin/npm v16.16.0 v16.16.0 8.11.0 tech /opt/iobroker Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 https://deb.nodesource.com/node_16.x bullseye InRelease Hit:3 http://ftp.tu-chemnitz.de/debian bullseye InRelease Hit:4 http://ftp.tu-chemnitz.de/debian bullseye-updates InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. nodejs: Installed: 16.16.0-deb-1nodesource1 Candidate: 16.16.0-deb-1nodesource1 Version table: *** 16.16.0-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u1 500 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages 12.22.5~dfsg-2~11u1 500 500 http://ftp.tu-chemnitz.de/debian bullseye/main amd64 Packages tech@ioBroker:/opt/iobroker$
syslog.log:
Jul 12 21:27:21 ioBroker qemu-ga: info: guest-ping called Jul 12 21:27:33 ioBroker qemu-ga: info: guest-ping called Jul 12 21:27:44 ioBroker qemu-ga: info: guest-ping called Jul 12 21:27:54 ioBroker qemu-ga: info: guest-ping called Jul 12 21:28:05 ioBroker qemu-ga: info: guest-ping called Jul 12 21:28:17 ioBroker qemu-ga: info: guest-ping called Jul 12 21:28:28 ioBroker qemu-ga: info: guest-ping called Jul 12 21:28:39 ioBroker qemu-ga: info: guest-ping called Jul 12 21:28:52 ioBroker qemu-ga: info: guest-ping called Jul 12 21:29:03 ioBroker qemu-ga: info: guest-ping called Jul 12 21:29:13 ioBroker qemu-ga: info: guest-ping called Jul 12 21:29:25 ioBroker qemu-ga: info: guest-ping called Jul 12 21:29:36 ioBroker qemu-ga: info: guest-ping called Jul 12 22:05:34 ioBroker dhclient[341]: DHCPREQUEST for 192.168.1.101 on ens18 to 192.168.1.200 port 67 Jul 12 22:05:34 ioBroker dhclient[341]: DHCPACK of 192.168.1.101 from 192.168.1.200 Jul 12 22:05:34 ioBroker dhclient[341]: bound to 192.168.1.101 -- renewal in 2767 seconds. Jul 12 22:17:01 ioBroker CRON[4503]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jul 12 22:36:27 ioBroker kernel: [ 0.000000] Linux version 5.10.0-16-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.127-1 (2022-06-30) Jul 12 22:36:27 ioBroker kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-16-amd64 root=UUID=d362ca41-a039-4c29-a1ee-8b143035a2a2 ro quiet Jul 12 22:36:27 ioBroker kernel: [ 0.000000] x86/fpu: x87 FPU will use FXSAVE Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffd9fff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bffda000-0x00000000bfffffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001bfffffff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000000] NX (Execute Disable) protection: active Jul 12 22:36:27 ioBroker kernel: [ 0.000000] SMBIOS 2.8 present. Jul 12 22:36:27 ioBroker kernel: [ 0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 Jul 12 22:36:27 ioBroker kernel: [ 0.000000] Hypervisor detected: KVM Jul 12 22:36:27 ioBroker kernel: [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 Jul 12 22:36:27 ioBroker kernel: [ 0.000000] kvm-clock: cpu 0, msr 1bacb8001, primary cpu clock Jul 12 22:36:27 ioBroker kernel: [ 0.000000] kvm-clock: using sched offset of 10540014338 cycles Jul 12 22:36:27 ioBroker kernel: [ 0.000002] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns Jul 12 22:36:27 ioBroker kernel: [ 0.000005] tsc: Detected 1996.800 MHz processor Jul 12 22:36:27 ioBroker kernel: [ 0.000745] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000748] e820: remove [mem 0x000a0000-0x000fffff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000752] last_pfn = 0x1c0000 max_arch_pfn = 0x400000000 Jul 12 22:36:27 ioBroker kernel: [ 0.000784] MTRR default type: write-back Jul 12 22:36:27 ioBroker kernel: [ 0.000785] MTRR fixed ranges enabled:
kern.log:
Jul 11 09:04:36 ioBroker kernel: [ 3.059065] audit: type=1400 audit(1657523076.524:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=301 comm="apparmor_parser" Jul 11 09:04:36 ioBroker kernel: [ 3.059067] audit: type=1400 audit(1657523076.524:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=301 comm="apparmor_parser" Jul 11 09:04:37 ioBroker kernel: [ 3.569939] random: crng init done Jul 11 09:04:37 ioBroker kernel: [ 3.569942] random: 167 urandom warning(s) missed due to ratelimiting Jul 12 22:36:27 ioBroker kernel: [ 0.000000] Linux version 5.10.0-16-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.127-1 (2022-06-30) Jul 12 22:36:27 ioBroker kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-16-amd64 root=UUID=d362ca41-a039-4c29-a1ee-8b143035a2a2 ro quiet Jul 12 22:36:27 ioBroker kernel: [ 0.000000] x86/fpu: x87 FPU will use FXSAVE Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-provided physical RAM map: Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffd9fff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bffda000-0x00000000bfffffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001bfffffff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000000] NX (Execute Disable) protection: active Jul 12 22:36:27 ioBroker kernel: [ 0.000000] SMBIOS 2.8 present. Jul 12 22:36:27 ioBroker kernel: [ 0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 Jul 12 22:36:27 ioBroker kernel: [ 0.000000] Hypervisor detected: KVM Jul 12 22:36:27 ioBroker kernel: [ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 Jul 12 22:36:27 ioBroker kernel: [ 0.000000] kvm-clock: cpu 0, msr 1bacb8001, primary cpu clock Jul 12 22:36:27 ioBroker kernel: [ 0.000000] kvm-clock: using sched offset of 10540014338 cycles Jul 12 22:36:27 ioBroker kernel: [ 0.000002] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns Jul 12 22:36:27 ioBroker kernel: [ 0.000005] tsc: Detected 1996.800 MHz processor Jul 12 22:36:27 ioBroker kernel: [ 0.000745] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved Jul 12 22:36:27 ioBroker kernel: [ 0.000748] e820: remove [mem 0x000a0000-0x000fffff] usable Jul 12 22:36:27 ioBroker kernel: [ 0.000752] last_pfn = 0x1c0000 max_arch_pfn = 0x400000000 Jul 12 22:36:27 ioBroker kernel: [ 0.000784] MTRR default type: write-back
ioBroker Log:
2022-07-12 22:15:56.862 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:16:03.863 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:16:04.000 - [33mwarn[39m: hm-rpc.0 (1333) State value to set for "hm-rpc.0.0009170993369E.0.RSSI_DEVICE" has value "128" greater than max "127" 2022-07-12 22:16:14.113 - [32minfo[39m: influxdb.0 (510) Store 22 buffered influxDB history points 2022-07-12 22:16:24.121 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:16:34.132 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:16:43.715 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:16:51.725 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:17:00.157 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:17:10.168 - [32minfo[39m: influxdb.0 (510) Store 22 buffered influxDB history points 2022-07-12 22:17:19.849 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:17:28.332 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:17:37.693 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:17:46.204 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:17:56.215 - [32minfo[39m: influxdb.0 (510) Store 22 buffered influxDB history points 2022-07-12 22:18:05.754 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:18:16.018 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:18:22.833 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:18:30.412 - [32minfo[39m: influxdb.0 (510) Store 21 buffered influxDB history points 2022-07-12 22:36:29.107 - [32minfo[39m: host.iobVM iobroker.js-controller version 4.0.23 js-controller starting 2022-07-12 22:36:29.109 - [32minfo[39m: host.iobVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2022-07-12 22:36:29.110 - [32minfo[39m: host.iobVM hostname: iobVM, node: v16.16.0 2022-07-12 22:36:29.111 - [32minfo[39m: host.iobVM ip addresses: 192.168.1.101 fe80::fc7b:28ff:fe6b:cc51 2022-07-12 22:36:29.216 - [32minfo[39m: host.iobVM Sets unsupported 2022-07-12 22:36:29.217 - [32minfo[39m: host.iobVM Sets unsupported 2022-07-12 22:36:29.922 - [32minfo[39m: host.iobVM connected to Objects and States 2022-07-12 22:36:29.937 - [32minfo[39m: host.iobVM added notifications configuration of host 2022-07-12 22:36:30.394 - [32minfo[39m: host.iobVM 28 instances found 2022-07-12 22:36:30.416 - [32minfo[39m: host.iobVM starting 11 instances 2022-07-12 22:36:30.569 - [32minfo[39m: host.iobVM instance system.adapter.admin.0 started with pid 446 2022-07-12 22:36:31.354 - [32minfo[39m: admin.0 (446) Sets unsupported 2022-07-12 22:36:31.356 - [32minfo[39m: admin.0 (446) Sets unsupported 2022-07-12 22:36:31.626 - [32minfo[39m: admin.0 (446) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v16.16.0, js-controller: 4.0.23 2022-07-12 22:36:31.650 - [32minfo[39m: admin.0 (446) requesting all states 2022-07-12 22:36:31.650 - [32minfo[39m: admin.0 (446) requesting all objects 2022-07-12 22:36:31.784 - [32minfo[39m: admin.0 (446) Request actual repository... 2022-07-12 22:36:32.253 - [32minfo[39m: admin.0 (446) received all objects 2022-07-12 22:36:32.343 - [32minfo[39m: host.iobVM Updating repository "stable" under "http://repo.iobroker.live/sources-dist.json" 2022-07-12 22:36:32.375 - [32minfo[39m: admin.0 (446) http server listening on port 8081 2022-07-12 22:36:32.376 - [32minfo[39m: admin.0 (446) Use link "http://localhost:8081" to configure. 2022-07-12 22:36:33.239 - [32minfo[39m: admin.0 (446) Repository received successfully. 2022-07-12 22:36:34.558 - [32minfo[39m: host.iobVM instance system.adapter.javascript.0 started with pid 461 2022-07-12 22:36:35.959 - [32minfo[39m: javascript.0 (461) Sets unsupported 2022-07-12 22:36:35.961 - [32minfo[39m: javascript.0 (461) Sets unsupported 2022-07-12 22:36:36.295 - [32minfo[39m: javascript.0 (461) starting. Version 5.7.0 in /opt/iobroker/node_modules/iobroker.javascript, node: v16.16.0, js-controller: 4.0.23 2022-07-12 22:36:37.399 - [32minfo[39m: javascript.0 (461) requesting all states 2022-07-12 22:36:37.399 - [32minfo[39m: javascript.0 (461) requesting all objects 2022-07-12 22:36:38.074 - [32minfo[39m: javascript.0 (461) received all states 2022-07-12 22:36:38.338 - [32minfo[39m: javascript.0 (461) received all objects 2022-07-12 22:36:38.597 - [32minfo[39m: javascript.0 (461) Start javascript script.js.common.Speedy
-
RE: Proxmox VM friert ein
@glasfaser Ja, weiss ich jetzt auch. Nochmals sorry dafür.
-
RE: Proxmox VM friert ein
@glasfaser Eigentlich nicht. Das sind beides Raspberry Pi's. Hab' mit denen eigentlich keine Probleme.
Aber auf denen läuft nicht nicht die 64bit Version. -
RE: Proxmox VM friert ein
@thomas-braun Oh Mist. Wie komm' ich denn auf die 32bit Version? Muss wohl verrutscht sein, als ich das Image ausgewählt habe.
Ich Idiot.
Okay, ihr habt mir superschnell geholfen! Vielen vielen Dank!!!!!
Ich denke, ich verbringe den Abend mit dem Aufsetzen einer neuen VM und dem Einspielen meiner BackupsIch kann mich echt nicht erinnern, dass ich npm installiert habe. Aber ist ja so.
Nochmals vielen vielen Dank für Eure Hilfe!!!
Viele Grüße aus Heidelberg!
Michael -
RE: Proxmox VM friert ein
@glasfaser: Hmm... Ich hatte vor langer Zeit mal das Problem, dass sich nodejs nicht aktualisieren ließ. Es kam immer, dass die neueste Version schon installiert wurde. Dann ein paar mal iob stop, iob update self , usw.
Manuell hab' ich nichts gemacht.