Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Probleme bei Updates

    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

    Probleme bei Updates

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      toki1973 @shellyrulestheworld last edited by toki1973

      Konnte das Node.js auch über den Terminal Zugriff durchführen. Über die iob GUI ging das nicht. Es hat sehr lange gedauert bis die GUI wieder erreichbar war.

      Ein Diag zeigt Fehler bei redis - habe ich aber gar nicht aktiviert. Allerdings habe ich schonmanchal eine langsame Event Durcheichung.

      ```bash
      ======================= SUMMARY =======================
                              v.2025-02-02
      
      
       Static hostname: iobroker
             Icon name: computer-vm
               Chassis: vm 🖴
        Virtualization: kvm
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.1.0-28-amd64
          Architecture: x86-64
       Hardware Vendor: QEMU
        Hardware Model: Standard PC _i440FX + PIIX, 1996_
      Firmware Version: rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org
      
      Installation:           kvm
      Kernel:                 x86_64
      Userland:               64 bit
      Timezone:               Europe/Berlin (CET, +0100)
      User-ID:                1000
      Display-Server:         false
      Boot Target:            multi-user.target
      
      Pending OS-Updates:     1
      Pending iob updates:    0
      
      Nodejs-Installation:
      /usr/bin/nodejs         v20.18.2
      /usr/bin/node           v20.18.2
      /usr/bin/npm            10.8.2
      /usr/bin/npx            10.8.2
      /usr/bin/corepack       0.29.4
      
      Recommended versions are nodejs  Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker"]
      No connection to databases possible ... and npm  Connection is closed.
      nodeJS installation is correct
      
      MEMORY:
                     total        used        free      shared  buff/cache   available
      Mem:            6.3G        4.1G        1.2G        610K        1.4G        2.3G
      Swap:           1.0G          0B        1.0G
      Total:          7.4G        4.1G        2.2G
      
      Active iob-Instances:   0
      /opt/iobroker/node_modules/standard-as-callback/built/index.js:6
              throw e;
              ^
      
      Error: Connection is closed.
          at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
          at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
          at Object.onceWrapper (node:events:633:26)
          at Socket.emit (node:events:518:28)
          at TCP.<anonymous> (node:net:343:12)
      Emitted 'error' event on ScanStream instance at:
          at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
          at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
          at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
          at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      Node.js v20.18.2
      
      ioBroker Core:          js-controller           7.0.6
                              admin                   7.0.23
      
      ioBroker Status:        iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Status admin and web instance:
      
      Objects:                126111
      States:                 97783
      
      Size of iob-Database:
      
      93M     /opt/iobroker/iobroker-data/objects.jsonl
      25M     /opt/iobroker/iobroker-data/states.jsonl
      
      
      Operating System is the current Debian stable version codenamed 'bookworm'!
      
      =================== END OF SUMMARY ====================
      
      Jedesmal nach dem Update habe ich Probleme.
      T Homoran 2 Replies Last reply Reply Quote 0
      • T
        toki1973 @toki1973 last edited by toki1973

           Checking autostart (5/5)
        ==========================================================================
        
        ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ====
        Legitimierung ist zum Stoppen von »iobroker.service« notwendig.
        Authenticating as: toki,,, (toki)
        Password: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
        Enabling autostart...
        Autostart enabled!
        
        ==========================================================================
        
            Your installation was fixed successfully
            Run iobroker start to start ioBroker again!
        
        ==========================================================================
        
        
        toki@iobroker:~$ iob status
        /opt/iobroker/node_modules/standard-as-callback/built/index.js:6
                throw e;
                ^
        
        Error: Connection is closed.
            at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
            at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
            at Object.onceWrapper (node:events:633:26)
            at Socket.emit (node:events:518:28)
            at TCP.<anonymous> (node:net:343:12)
        Emitted 'error' event on ScanStream instance at:
            at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
            at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
            at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
            at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        
        Node.js v20.18.2
        
        
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @toki1973 last edited by

          @toki1973

          Das ist aber was für einen eigenen Thread. Dein nodejs ist ja richtig installiert.
          Da dann die Ausgabe von

          iob diag
          

          in der Langfassung rein.

          Homoran 1 Reply Last reply Reply Quote 0
          • Homoran
            Homoran Global Moderator Administrators @Thomas Braun last edited by

            @thomas-braun Hab 7ch mal gemacht, mir fiel aber kein passender Threadtitel ein.

            @toki1973 bitte provisorischen Threadtitel anpassen

            1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @toki1973 last edited by

              @toki1973 sagte in Probleme bei Updates:

              Konnte das Node.js auch über den Terminal Zugriff durchführen. Über die iob GUI ging das nicht.

              Wo soll man da nodejs upgraden können? 🤔

              @toki1973 sagte in Probleme bei Updates:

              Jedesmal nach dem Update habe ich Probleme.

              Welcher Art?

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

              Support us

              ioBroker
              Community Adapters
              Donate
              FAQ Cloud / IOT
              HowTo: Node.js-Update
              HowTo: Backup/Restore
              Downloads
              BLOG

              423
              Online

              31.9k
              Users

              80.3k
              Topics

              1.3m
              Posts

              3
              5
              201
              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