Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Off Topic
    4. Proxmox
    5. Proxmox VM friert ein

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Proxmox VM friert ein

    This topic has been deleted. Only users with topic management privileges can see it.
    • Glasfaser
      Glasfaser @TronLand last edited by

      @tronland sagte in Proxmox VM friert ein:

      Okay, ihr habt mir superschnell geholfen!

      Das wäre auch noch schneller gelaufen ... wenn du schon oben im Start-Thread mehr Infos gehabt hättest .

      https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge

      T Thomas Braun 2 Replies Last reply Reply Quote 0
      • T
        TronLand @Glasfaser last edited by

        @glasfaser Ja, weiss ich jetzt auch. Nochmals sorry dafür.

        1 Reply Last reply Reply Quote 0
        • Glasfaser
          Glasfaser @TronLand last edited by

          @tronland sagte in Proxmox VM friert ein:

          Hab' mit denen eigentlich keine Probleme.

          würde es aber trotzdem mal prüfen mit der Anfrage die ich oben gestellt habe !

          T 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @TronLand last edited by

            @tronland sagte in Proxmox VM friert ein:

            Aber auf denen läuft nicht nicht die 64bit Version.

            Bei den arm-basierten Geräten ist das (noch) nicht weiter wild, da wird noch das allermeiste auch für 32bit gebacken. i386 wird dahingegen schon geraume Zeit nicht mehr voll bedient.

            1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Glasfaser last edited by

              @glasfaser

              Im dritten Posting stand es drin:

              Debian VM Linux iobVM 5.10.0-14-686-pae
              Habs aber auch überlesen.

              Glasfaser 1 Reply Last reply Reply Quote 1
              • Glasfaser
                Glasfaser @Thomas Braun last edited by

                @TT-Tom

                Warum bewertest du @crunchip Negativ !

                Ist doch erstmal eine Logisch vorgehensweise , wenn wir hier was benötigen !?
                .

                e3a08552-62d7-47f2-8814-2d258fbbabfe-grafik.png

                T crunchip 2 Replies Last reply Reply Quote 1
                • T
                  TT-Tom @Glasfaser last edited by

                  @glasfaser
                  War nicht mit Absicht, muss beim blättern passiert sein. Nehme ich gleich wieder zurück. Sorry

                  1 Reply Last reply Reply Quote 1
                  • crunchip
                    crunchip Forum Testing Most Active @Glasfaser last edited by

                    @glasfaser was dir so alles auffällt😁

                    1 Reply Last reply Reply Quote 0
                    • T
                      TronLand @Glasfaser last edited by TronLand

                      @glasfaser

                      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.

                      Screenshot 2022-07-12 224807.png image_2022-07-12_230551097.png

                      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  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:16:03.863  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:16:04.000  - warn: 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  - info: influxdb.0 (510) Store 22 buffered influxDB history points
                      2022-07-12 22:16:24.121  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:16:34.132  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:16:43.715  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:16:51.725  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:17:00.157  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:17:10.168  - info: influxdb.0 (510) Store 22 buffered influxDB history points
                      2022-07-12 22:17:19.849  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:17:28.332  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:17:37.693  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:17:46.204  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:17:56.215  - info: influxdb.0 (510) Store 22 buffered influxDB history points
                      2022-07-12 22:18:05.754  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:18:16.018  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:18:22.833  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:18:30.412  - info: influxdb.0 (510) Store 21 buffered influxDB history points
                      2022-07-12 22:36:29.107  - info: host.iobVM iobroker.js-controller version 4.0.23 js-controller starting
                      2022-07-12 22:36:29.109  - info: host.iobVM Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                      2022-07-12 22:36:29.110  - info: host.iobVM hostname: iobVM, node: v16.16.0
                      2022-07-12 22:36:29.111  - info: host.iobVM ip addresses: 192.168.1.101 fe80::fc7b:28ff:fe6b:cc51
                      2022-07-12 22:36:29.216  - info: host.iobVM Sets unsupported
                      2022-07-12 22:36:29.217  - info: host.iobVM Sets unsupported
                      2022-07-12 22:36:29.922  - info: host.iobVM connected to Objects and States
                      2022-07-12 22:36:29.937  - info: host.iobVM added notifications configuration of host
                      2022-07-12 22:36:30.394  - info: host.iobVM 28 instances found
                      2022-07-12 22:36:30.416  - info: host.iobVM starting 11 instances
                      2022-07-12 22:36:30.569  - info: host.iobVM instance system.adapter.admin.0 started with pid 446
                      2022-07-12 22:36:31.354  - info: admin.0 (446) Sets unsupported
                      2022-07-12 22:36:31.356  - info: admin.0 (446) Sets unsupported
                      2022-07-12 22:36:31.626  - info: 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  - info: admin.0 (446) requesting all states
                      2022-07-12 22:36:31.650  - info: admin.0 (446) requesting all objects
                      2022-07-12 22:36:31.784  - info: admin.0 (446) Request actual repository...
                      2022-07-12 22:36:32.253  - info: admin.0 (446) received all objects
                      2022-07-12 22:36:32.343  - info: host.iobVM Updating repository "stable" under "http://repo.iobroker.live/sources-dist.json"
                      2022-07-12 22:36:32.375  - info: admin.0 (446) http server listening on port 8081
                      2022-07-12 22:36:32.376  - info: admin.0 (446) Use link "http://localhost:8081" to configure.
                      2022-07-12 22:36:33.239  - info: admin.0 (446) Repository received successfully.
                      2022-07-12 22:36:34.558  - info: host.iobVM instance system.adapter.javascript.0 started with pid 461
                      2022-07-12 22:36:35.959  - info: javascript.0 (461) Sets unsupported
                      2022-07-12 22:36:35.961  - info: javascript.0 (461) Sets unsupported
                      2022-07-12 22:36:36.295  - info: 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  - info: javascript.0 (461) requesting all states
                      2022-07-12 22:36:37.399  - info: javascript.0 (461) requesting all objects
                      2022-07-12 22:36:38.074  - info: javascript.0 (461) received all states
                      2022-07-12 22:36:38.338  - info: javascript.0 (461) received all objects
                      2022-07-12 22:36:38.597  - info: javascript.0 (461) Start javascript script.js.common.Speedy
                      
                      Thomas Braun Dr. Bakterius 2 Replies Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @TronLand last edited by

                        @tronland

                        Da würde ich mal in der Konfiguration von influxdb herumschauen.

                        T 1 Reply Last reply Reply Quote 0
                        • T
                          TronLand @Thomas Braun last edited by TronLand

                          @thomas-braun

                          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

                          Screenshot 2022-07-13 062550.png
                          Screenshot 2022-07-13 062609.png

                          1 Reply Last reply Reply Quote 0
                          • Dr. Bakterius
                            Dr. Bakterius Most Active @TronLand last edited by

                            @tronland sagte in Proxmox VM friert ein:

                            Punkt 22:18 ging die Prozessorlast auf ca. 50% und ioBroker war nicht mehr erreichbar.

                            Kann es sich um ein Skript handeln das amokläuft? Also irgendeine Endlosschleife.

                            T 1 Reply Last reply Reply Quote 0
                            • T
                              TronLand @Dr. Bakterius last edited by

                              @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

                              1 Reply Last reply Reply Quote 0
                              • T
                                TronLand last edited by

                                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

                                isi07 1 Reply Last reply Reply Quote 0
                                • isi07
                                  isi07 @TronLand last edited by

                                  @tronland
                                  Hallo
                                  hast Du das Problem lösen können? Ich bin mit meinem IObroker auch auf Proxmox umgezogen und habe genau das gleiche Problem. Nach ein paar Tagen friert die IObroker-VM mit den beschriebenen Symptomen ein. Auch ich kann in den logs keine Fehler feststellen.
                                  Viele Grüße

                                  1 Reply Last reply Reply Quote 0
                                  • crunchip
                                    crunchip Forum Testing Most Active last edited by

                                    @isi07 sagte in Proxmox VM friert ein:

                                    genau das gleiche Problem.

                                    hast du genau die selbe Hardware, das selbe installiert?

                                    Ein paar mehr Info`s bräuchte man schon dazu

                                    isi07 1 Reply Last reply Reply Quote 0
                                    • isi07
                                      isi07 @crunchip last edited by

                                      @crunchip
                                      sorry, hier mehr Details

                                      ich habe in folgender Diskussion ein ähnliches Problem gefunden und heute schon den Kernel des Host Systems aktualisiert
                                      Es scheint wohl ein Problem mit dem Celeron N5105 zu existieren
                                      https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/

                                      Als Host habe ich
                                      Intel NUC 11 NUC11ATKC4
                                      mit Celeron N5105

                                      224d979a-aa8c-49b2-9469-6829ce03fd1b-grafik.png

                                      Ich habe mehrere VMs und einen LXC Container. Das Problem tritt bei mir nur in der VM mit iobroker auf.

                                      Die VM für iobroker ist jetzt so eingestellt:
                                      a485a321-0b3c-447c-98de-49f946b8bd8c-grafik.png

                                      iobroker@iobroker:/opt/iobroker$ npm ls | grep -E 'github.com|ERR'
                                      ├── iobroker.accuweather@1.2.4 (git+ssh://git@github.com/isi07/ioBroker.accuweather.git#f161fbf1c577e752bd24c1761ce4c6c1f60549b3)
                                      
                                      iobroker@iobroker:/opt/iobroker$ iobroker update -i
                                      Used repository: Beta (latest)
                                      Adapter    "accuweather"  : 1.2.4    , installed 1.2.4
                                      Adapter    "admin"        : 6.2.23   , installed 6.2.23
                                      Adapter    "alarm"        : 3.1.1    , installed 3.1.1
                                      Adapter    "alias-manager": 1.2.6    , installed 1.2.6
                                      Adapter    "backitup"     : 2.5.2    , installed 2.5.2
                                      Adapter    "cloud"        : 4.3.0    , installed 4.3.0
                                      Adapter    "coronavirus-statistics": 0.8.7, installed 0.8.7
                                      Adapter    "cul"          : 2.0.2    , installed 2.0.2
                                      Adapter    "daswetter"    : 3.1.4    , installed 3.1.4
                                      Adapter    "deconz"       : 1.3.21   , installed 1.3.21
                                      Adapter    "devices"      : 1.1.0    , installed 1.1.0
                                      Adapter    "discovery"    : 3.1.0    , installed 3.1.0
                                      Adapter    "dwd"          : 2.8.3    , installed 2.8.3
                                      Adapter    "echarts"      : 1.0.12   , installed 1.0.12
                                      Adapter    "email"        : 1.1.4    , installed 1.1.4
                                      Adapter    "eusec"        : 0.9.4    , installed 0.9.4
                                      Adapter    "feiertage"    : 1.1.0    , installed 1.1.0
                                      Adapter    "followthesun" : 0.4.0-alpha.1, installed 0.4.0-alpha.1
                                      Adapter    "fritzdect"    : 2.2.6    , installed 2.2.6
                                      Adapter    "history"      : 2.2.4    , installed 2.2.4
                                      Adapter    "hm-rega"      : 3.0.43   , installed 3.0.43
                                      Adapter    "hm-rpc"       : 1.15.15  , installed 1.15.15
                                      Adapter    "ical"         : 1.13.2   , installed 1.13.2
                                      Adapter    "influxdb"     : 3.2.0    , installed 3.2.0
                                      Adapter    "info"         : 1.9.21   , installed 1.9.21
                                      Adapter    "jarvis"       : 3.0.15   , installed 3.0.15
                                      Adapter    "javascript"   : 6.0.3    , installed 6.0.3
                                      Controller "js-controller": 4.0.23   , installed 4.0.23
                                      Adapter    "logparser"    : 1.1.0    , installed 1.1.0
                                      Adapter    "mihome-vacuum": 3.6.0    , installed 3.6.0
                                      Adapter    "mobile"       : 1.0.1    , installed 1.0.1
                                      Adapter    "modbus"       : 5.0.8    , installed 5.0.8
                                      Adapter    "net-tools"    : 0.2.0    , installed 0.2.0
                                      Adapter    "parcel"       : 0.0.23   , installed 0.0.23
                                      Adapter    "plex"         : 0.9.1    , installed 0.9.1
                                      Adapter    "proxmox"      : 1.3.5    , installed 1.3.5
                                      Adapter    "pushover"     : 3.0.3    , installed 3.0.3
                                      Adapter    "pvforecast"   : 2.3.0    , installed 2.3.0
                                      Adapter    "scenes"       : 2.3.9    , installed 2.3.9
                                      Adapter    "scheduler"    : 0.1.2    , installed 0.1.2
                                      Adapter    "schoolfree"   : 1.0.1    , installed 1.0.1
                                      Adapter    "shelly"       : 6.2.4    , installed 6.2.4
                                      Adapter    "shuttercontrol": 1.4.18  , installed 1.4.18
                                      Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
                                      Adapter    "smartcontrol" : 1.3.1    , installed 1.3.1
                                      Adapter    "socketio"     : 6.1.10   , installed 6.1.10
                                      Adapter    "sonos"        : 2.2.3    , installed 2.2.3
                                      Adapter    "spotify-premium": 1.2.2  , installed 1.2.2
                                      Adapter    "stiebel-isg"  : 1.7.5    , installed 1.7.5
                                      Adapter    "time-switch"  : 2.2.2    , installed 2.2.2
                                      Adapter    "tr-064"       : 4.2.17   , installed 4.2.17
                                      Adapter    "trashschedule": 2.0.3    , installed 2.0.3
                                      Adapter    "tvprogram"    : 1.1.2    , installed 1.1.2
                                      Adapter    "uv-protect"   : 0.3.6    , installed 0.3.6
                                      Adapter    "vis"          : 1.4.15   , installed 1.4.15
                                      Adapter    "web"          : 5.2.10   , installed 5.2.10
                                      Adapter    "withings"     : 0.0.13   , installed 0.0.13
                                      Adapter    "ws"           : 2.1.5    , installed 2.1.5
                                      Adapter    "yahka"        : 0.17.0   , installed 0.17.0
                                      
                                      iobroker@iobroker:/opt/iobroker$ sudo ln -s /usr/bin/node /usr/bin/nodejs
                                      [sudo] Passwort für iobroker:
                                      ln: die symbolische Verknüpfung '/usr/bin/nodejs' konnte nicht angelegt werden: Die Datei existiert bereits
                                      
                                      iobroker@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.18.0
                                      v16.18.0
                                      8.19.2
                                      iobroker
                                      /opt/iobroker
                                      OK:1 http://security.debian.org/debian-security bullseye-security InRelease
                                      OK:2 http://deb.debian.org/debian bullseye InRelease
                                      OK:3 http://deb.debian.org/debian bullseye-updates InRelease
                                      OK:4 https://deb.nodesource.com/node_16.x bullseye InRelease
                                      OK:5 https://repos.influxdata.com/debian bullseye InRelease
                                      Paketlisten werden gelesen… Fertig
                                      Abhängigkeitsbaum wird aufgebaut… Fertig
                                      Statusinformationen werden eingelesen… Fertig
                                      Aktualisierung für 2 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
                                      nodejs:
                                        Installiert:           16.18.0-deb-1nodesource1
                                        Installationskandidat: 16.18.0-deb-1nodesource1
                                        Versionstabelle:
                                       *** 16.18.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://deb.debian.org/debian bullseye/main amd64 Packages
                                      

                                      Der letzte Absturz war gestern.
                                      Es äußert sich so, dass die VM nicht mehr reagiert. Der CPU Load wird bei ca 50% angezeigt.
                                      Es hilft nur ein Reset.

                                      Log vom ioBroker

                                      2022-10-29 17:43:58.854 - info: influxdb.0 (12858) Store 101 buffered influxDB history points
                                      2022-10-29 17:44:43.174 - info: influxdb.0 (12858) Store 102 buffered influxDB history points
                                      2022-10-29 17:45:00.038 - info: host.iobroker instance system.adapter.daswetter.0 started with pid 50040
                                      2022-10-29 17:45:01.067 - info: influxdb.0 (12858) Store 101 buffered influxDB history points
                                      2022-10-29 17:45:01.366 - info: daswetter.0 (50040) starting. Version 3.1.4 in /opt/iobroker/node_modules/iobroker.daswetter, node: v16.18.0, js-controller: 4.0.23
                                      2022-10-29 17:45:09.410 - info: daswetter.0 (50040) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment
                                      2022-10-29 17:45:09.918 - info: daswetter.0 (50040) cleaned everything up...
                                      2022-10-29 17:45:09.927 - info: host.iobroker instance system.adapter.daswetter.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
                                      2022-10-29 17:45:31.109 - info: influxdb.0 (12858) Store 101 buffered influxDB history points
                                      2022-10-29 17:45:56.788 - info: javascript.0 (12873) script.js.control.lueften: Lüften!
                                      2022-10-29 17:46:03.596 - info: influxdb.0 (12858) Store 101 buffered influxDB history points
                                      2022-10-29 17:46:47.535 - info: influxdb.0 (12858) Store 101 buffered influxDB history points
                                      2022-10-29 17:47:23.746 - info: influxdb.0 (12858) Store 102 buffered influxDB history points
                                      2022-10-29 19:15:43.634 - info: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
                                      2022-10-29 19:15:43.636 - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
                                      2022-10-29 19:15:43.637 - info: host.iobroker hostname: iobroker, node: v16.18.0
                                      2022-10-29 19:15:43.637 - info: host.iobroker ip addresses: 192.168.1.95 fe80::42:afff:fe31:dbb1
                                      2022-10-29 19:15:45.234 - info: host.iobroker connected to Objects and States
                                      2022-10-29 19:15:45.266 - info: host.iobroker added notifications configuration of host
                                      2022-10-29 19:15:45.713 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeCurrent"
                                      2022-10-29 19:15:45.714 - info: host.iobroker 61 instances found
                                      2022-10-29 19:15:45.755 - info: host.iobroker starting 42 instances
                                      2022-10-29 19:15:45.846 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewest"
                                      2022-10-29 19:15:45.904 - info: host.iobroker instance system.adapter.admin.0 started with pid 472
                                      2022-10-29 19:15:45.912 - info: host.iobroker Delete state "system.host.iobroker.versions.nodeNewestNext"
                                      2022-10-29 19:15:45.969 - info: host.iobroker Delete state "system.host.iobroker.versions.npmCurrent"
                                      2022-10-29 19:15:46.022 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewest"
                                      2022-10-29 19:15:46.071 - info: host.iobroker Delete state "system.host.iobroker.versions.npmNewestNext"
                                      2022-10-29 19:15:46.120 - info: host.iobroker Some obsolete host states deleted.
                                      

                                      Der kern.log ist zu dem Zeitpunkt des Absturzes irgendwie unvollständig, da ist nichts drin.
                                      Es bricht schon am Vortag ab und steigt dann erst mit dem Neustart nach dem Absturz wieder ein.

                                      Oct 28 23:17:28 iobroker kernel: [10857.468256] device-mapper: uevent: version 1.0.3
                                      Oct 28 23:17:28 iobroker kernel: [10857.468351] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
                                      Oct 28 23:17:29 iobroker kernel: [10858.826570] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
                                      Oct 28 23:17:29 iobroker kernel: [10858.841567] JFS: nTxBlock = 8192, nTxLock = 65536
                                      Oct 28 23:17:29 iobroker kernel: [10858.891689] QNX4 filesystem 0.2.3 registered.
                                      Oct 28 23:17:29 iobroker kernel: [10859.009341] raid6: sse2x4   gen() 10934 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.077314] raid6: sse2x4   xor()  6947 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.145333] raid6: sse2x2   gen() 13516 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.213314] raid6: sse2x2   xor()  7560 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.281333] raid6: sse2x1   gen() 11930 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.349334] raid6: sse2x1   xor()  7237 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.349337] raid6: using algorithm sse2x2 gen() 13516 MB/s
                                      Oct 28 23:17:29 iobroker kernel: [10859.349337] raid6: .... xor() 7560 MB/s, rmw enabled
                                      Oct 28 23:17:29 iobroker kernel: [10859.349353] raid6: using intx1 recovery algorithm
                                      Oct 28 23:17:29 iobroker kernel: [10859.352633] xor: measuring software checksum speed
                                      Oct 28 23:17:29 iobroker kernel: [10859.353189]    prefetch64-sse  : 17804 MB/sec
                                      Oct 28 23:17:29 iobroker kernel: [10859.353848]    generic_sse     : 15363 MB/sec
                                      Oct 28 23:17:29 iobroker kernel: [10859.353849] xor: using function: prefetch64-sse (17804 MB/sec)
                                      Oct 28 23:17:30 iobroker kernel: [10859.437634] Btrfs loaded, crc32c=crc32c-generic
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] Linux version 5.10.0-19-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.149-2 (2022-10-21)
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 root=UUID=a0f69eef-29ae-429e-b2c8-fb1cb9ac7915 ro quiet
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] x86/fpu: x87 FPU will use FXSAVE
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-provided physical RAM map:
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bffd9fff] usable
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x00000000bffda000-0x00000000bfffffff] reserved
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000023fffffff] usable
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] NX (Execute Disable) protection: active
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] SMBIOS 2.8 present.
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] DMI: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] Hypervisor detected: KVM
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
                                      Oct 29 19:15:42 iobroker kernel: [    0.000000] kvm-clock: cpu 0, msr 1cb4f3001, primary cpu clock
                                      Oct 29 19:15:42 iobroker kernel: [    0.000001] kvm-clock: using sched offset of 82759752833378 cycles
                                      Oct 29 19:15:42 iobroker kernel: [    0.000003] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
                                      Oct 29 19:15:42 iobroker kernel: [    0.000006] tsc: Detected 1996.800 MHz processor
                                      

                                      Im Syslog sehe ich auch nichts Auffälliges vor dem Absturz.

                                      Oct 29 16:46:49 iobroker qemu-ga: info: guest-ping called
                                      Oct 29 17:17:01 iobroker CRON[49159]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
                                      Oct 29 19:15:42 iobroker systemd-random-seed[214]: Kernel entropy pool is not initialized yet, waiting until it is.
                                      Oct 29 19:15:42 iobroker systemd[1]: Starting Flush Journal to Persistent Storage...
                                      Oct 29 19:15:42 iobroker systemd[1]: Started Rule-based Manager for Device Events and Files.
                                      Oct 29 19:15:42 iobroker systemd[1]: Finished Coldplug All udev Devices.
                                      Oct 29 19:15:42 iobroker systemd[1]: Starting Helper to synchronize boot up for ifupdown...
                                      Oct 29 19:15:42 iobroker systemd[1]: Finished Flush Journal to Persistent Storage.
                                      Oct 29 19:15:42 iobroker systemd[1]: Finished Helper to synchronize boot up for ifupdown.
                                      Oct 29 19:15:42 iobroker systemd-udevd[249]: Using default interface naming scheme 'v247'.
                                      Oct 29 19:15:42 iobroker systemd-udevd[249]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
                                      

                                      Schon mal vielen Dank für Eure Hilfe und weitere Ideen zur Lösung des Problems.
                                      Viele Grüße
                                      Christian

                                      crunchip 1 Reply Last reply Reply Quote 0
                                      • crunchip
                                        crunchip Forum Testing Most Active @isi07 last edited by

                                        @isi07 sagte in Proxmox VM friert ein:

                                        schon den Kernel des Host Systems aktualisiert

                                        also keine Änderung und auch jetzt das Problem?

                                        @isi07 sagte in Proxmox VM friert ein:

                                        mehrere VMs

                                        und was laufen da für ein Systeme?

                                        isi07 1 Reply Last reply Reply Quote 0
                                        • isi07
                                          isi07 @crunchip last edited by

                                          @crunchip
                                          heute noch keinen weiteren Absturz. Die Abstürze waren auch vorher unregelmäßig ... so nach ein paar Tagen Laufzeit.
                                          werde berichten, ob es mit dem neuen Kernel eventuell schon gelöst ist

                                          Auf den anderen Systemen läuft:
                                          VM mit deCONZ
                                          VM mit Raspberrymatic
                                          LXC mit InfluxDB und Grafana

                                          1 Reply Last reply Reply Quote 0
                                          • crunchip
                                            crunchip Forum Testing Most Active last edited by

                                            @isi07 sagte in Proxmox VM friert ein:

                                            Auf den anderen Systemen läuft

                                            eher die Frage nach Debian , Ubuntu....Kernel? denn warum sollte es in einer VM zu Problemen führen, wenn die anderen funktionieren.
                                            vllt liegt es dann eher an iobroker, das da etwas nicht rund läuft und zu deinem Problem führt

                                            isi07 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            783
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            20
                                            186
                                            18116
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo