Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Fehlermeldungen beim Biobroker Update

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Fehlermeldungen beim Biobroker Update

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @Volleyhomer last edited by

      @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

      Ist das Problem denn jetzt die alte debian oder die alte npm, node, etc. Version?

      Alles zusammen. Da ist ja gar nix aktuell bei dir.

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

        @volleyhomer
        Versuch:

        NODE_MAJOR=16
        sudo apt update
        sudo apt install -y ca-certificates curl gnupg
        sudo mkdir -p /etc/apt/keyrings
        curl -kL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
        echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_${NODE_MAJOR}.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list
        echo -e "Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001" | sudo tee /etc/apt/preferences.d/nodejs.pref
        sudo apt update
        sudo apt install nodejs
        
        V 1 Reply Last reply Reply Quote 1
        • V
          Volleyhomer @Thomas Braun last edited by

          @thomas-braun said in Fehlermeldungen beim Biobroker Update:

          NODE_MAJOR=16

          Hagelt Fehlermeldungen. Ich glaube ich muss mir dann mal ein Wochenende frei nehmen, die Kinder ausquartieren und in Ruhe mich einlesen und alles neu aufsetzen.

          NodeJS Update scheint aber geklappt zu haben.

          pi@rock64:~$ NODE_MAJOR=16
          pi@rock64:~$ sudo apt update
          [sudo] password for pi: 
          Ign:1 http://httpredir.debian.org/debian stretch InRelease
          Ign:2 http://security.debian.org stretch/updates InRelease               
          Err:3 http://security.debian.org stretch/updates Release                 
            404  Not Found [IP: 146.75.122.132 80]
          Ign:4 http://httpredir.debian.org/debian stretch-updates InRelease       
          Ign:5 http://httpredir.debian.org/debian stretch-backports InRelease     
          Err:6 http://httpredir.debian.org/debian stretch Release
            404  Not Found [IP: 146.75.122.132 80]
          Err:7 http://httpredir.debian.org/debian stretch-updates Release
            404  Not Found [IP: 146.75.122.132 80]
          Err:8 http://httpredir.debian.org/debian stretch-backports Release
            404  Not Found [IP: 146.75.122.132 80]
          Hit:10 https://deb.nodesource.com/node_14.x stretch InRelease
          Hit:9 http://mirrors.dotsrc.org/armbian-apt stretch InRelease
          Reading package lists... Done
          E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          pi@rock64:~$ sudo apt install -y ca-certificates curl gnupg
          Reading package lists... Done
          Building dependency tree       
          Reading state information... Done
          gnupg is already the newest version (2.1.18-8~deb9u4).
          The following packages will be upgraded:
            ca-certificates curl libcurl3
          3 upgraded, 0 newly installed, 0 to remove and 132 not upgraded.
          Need to get 652 kB of archives.
          After this operation, 35.8 kB of additional disk space will be used.
          Ign:1 http://security.debian.org stretch/updates/main arm64 ca-certificates all 20200601~deb9u2
          Err:2 http://security.debian.org stretch/updates/main arm64 curl arm64 7.52.1-5+deb9u16
            404  Not Found [IP: 146.75.122.132 80]
          Err:3 http://security.debian.org stretch/updates/main arm64 libcurl3 arm64 7.52.1-5+deb9u16
            404  Not Found [IP: 146.75.122.132 80]
          Err:1 http://security.debian.org stretch/updates/main armhf ca-certificates all 20200601~deb9u2
            404  Not Found [IP: 146.75.122.132 80]
          E: Failed to fetch http://security.debian.org/pool/updates/main/c/ca-certificates/ca-certificates_20200601~deb9u2_all.deb  404  Not Found [IP: 146.75.122.132 80]
          E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/curl_7.52.1-5+deb9u16_arm64.deb  404  Not Found [IP: 146.75.122.132 80]
          E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/libcurl3_7.52.1-5+deb9u16_arm64.deb  404  Not Found [IP: 146.75.122.132 80]
          E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
          pi@rock64:~$ sudo mkdir -p /etc/apt/keyrings
          pi@rock64:~$ 
          pi@rock64:~$ curl -kL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
            % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                           Dload  Upload   Total   Spent    Left  Speed
          100  1684  100  1684    0     0   7395      0 --:--:-- --:--:-- --:--:--  7385
          pi@rock64:~$ echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_${NODE_MAJOR}.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list
          deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x nodistro main
          pi@rock64:~$ echo -e "Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001" | sudo tee /etc/apt/preferences.d/nodejs.pref
          Package: nodejs
          Pin: origin deb.nodesource.com
          Pin-Priority: 1001
          pi@rock64:~$ sudo apt update
          Ign:1 http://security.debian.org stretch/updates InRelease
          Ign:2 http://httpredir.debian.org/debian stretch InRelease               
          Ign:3 http://httpredir.debian.org/debian stretch-updates InRelease       
          Err:4 http://security.debian.org stretch/updates Release                 
            404  Not Found [IP: 146.75.122.132 80]
          Ign:5 http://httpredir.debian.org/debian stretch-backports InRelease     
          Err:6 http://httpredir.debian.org/debian stretch Release
            404  Not Found [IP: 146.75.122.132 80]
          Err:7 http://httpredir.debian.org/debian stretch-updates Release
            404  Not Found [IP: 146.75.122.132 80]
          Err:8 http://httpredir.debian.org/debian stretch-backports Release
            404  Not Found [IP: 146.75.122.132 80]
          Get:10 https://deb.nodesource.com/node_16.x nodistro InRelease [12.1 kB]
          Hit:9 http://mirrors.dotsrc.org/armbian-apt stretch InRelease                        
          Get:11 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages [7469 B]
          Get:12 https://deb.nodesource.com/node_16.x nodistro/main arm64 Packages [7485 B]
          Get:13 https://deb.nodesource.com/node_16.x nodistro/main arm64 Contents (deb) [19.5 kB]
          Get:14 https://deb.nodesource.com/node_16.x nodistro/main armhf Contents (deb) [19.5 kB]
          Reading package lists... Done   
          E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.
          pi@rock64:~$ sudo apt install nodejs
          Reading package lists... Done
          Building dependency tree       
          Reading state information... Done
          The following packages will be upgraded:
            nodejs
          1 upgraded, 0 newly installed, 0 to remove and 135 not upgraded.
          Need to get 27.2 MB of archives.
          After this operation, 7285 kB of additional disk space will be used.
          Get:1 https://deb.nodesource.com/node_16.x nodistro/main arm64 nodejs arm64 16.20.2-1nodesource1 [27.2 MB]
          Fetched 27.2 MB in 6s (3939 kB/s)                                                                                                                                                                                                                
          (Reading database ... 38255 files and directories currently installed.)
          Preparing to unpack .../nodejs_16.20.2-1nodesource1_arm64.deb ...
          Detected old npm client, removing...
          Unpacking nodejs (16.20.2-1nodesource1) over (14.21.3-1nodesource1) ...
          Setting up nodejs (16.20.2-1nodesource1) ...
          Processing triggers for man-db (2.7.6.1-2) ...
          pi@rock64:~$ 
          
          
          V 1 Reply Last reply Reply Quote 0
          • V
            Volleyhomer @Volleyhomer last edited by

            @volleyhomer said in Fehlermeldungen beim Biobroker Update:

            @thomas-braun said in Fehlermeldungen beim Biobroker Update:

            NODE_MAJOR=16

            Hagelt Fehlermeldungen. Ich glaube ich muss mir dann mal ein Wochenende frei nehmen, die Kinder ausquartieren und in Ruhe mich einlesen und alles neu aufsetzen.

            NodeJS Update scheint aber geklappt zu haben.

            pi@rock64:~$ NODE_MAJOR=16
            pi@rock64:~$ sudo apt update
            [sudo] password for pi: 
            Ign:1 http://httpredir.debian.org/debian stretch InRelease
            Ign:2 http://security.debian.org stretch/updates InRelease               
            Err:3 http://security.debian.org stretch/updates Release                 
              404  Not Found [IP: 146.75.122.132 80]
            Ign:4 http://httpredir.debian.org/debian stretch-updates InRelease       
            Ign:5 http://httpredir.debian.org/debian stretch-backports InRelease     
            Err:6 http://httpredir.debian.org/debian stretch Release
              404  Not Found [IP: 146.75.122.132 80]
            Err:7 http://httpredir.debian.org/debian stretch-updates Release
              404  Not Found [IP: 146.75.122.132 80]
            Err:8 http://httpredir.debian.org/debian stretch-backports Release
              404  Not Found [IP: 146.75.122.132 80]
            Hit:10 https://deb.nodesource.com/node_14.x stretch InRelease
            Hit:9 http://mirrors.dotsrc.org/armbian-apt stretch InRelease
            Reading package lists... Done
            E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            pi@rock64:~$ sudo apt install -y ca-certificates curl gnupg
            Reading package lists... Done
            Building dependency tree       
            Reading state information... Done
            gnupg is already the newest version (2.1.18-8~deb9u4).
            The following packages will be upgraded:
              ca-certificates curl libcurl3
            3 upgraded, 0 newly installed, 0 to remove and 132 not upgraded.
            Need to get 652 kB of archives.
            After this operation, 35.8 kB of additional disk space will be used.
            Ign:1 http://security.debian.org stretch/updates/main arm64 ca-certificates all 20200601~deb9u2
            Err:2 http://security.debian.org stretch/updates/main arm64 curl arm64 7.52.1-5+deb9u16
              404  Not Found [IP: 146.75.122.132 80]
            Err:3 http://security.debian.org stretch/updates/main arm64 libcurl3 arm64 7.52.1-5+deb9u16
              404  Not Found [IP: 146.75.122.132 80]
            Err:1 http://security.debian.org stretch/updates/main armhf ca-certificates all 20200601~deb9u2
              404  Not Found [IP: 146.75.122.132 80]
            E: Failed to fetch http://security.debian.org/pool/updates/main/c/ca-certificates/ca-certificates_20200601~deb9u2_all.deb  404  Not Found [IP: 146.75.122.132 80]
            E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/curl_7.52.1-5+deb9u16_arm64.deb  404  Not Found [IP: 146.75.122.132 80]
            E: Failed to fetch http://security.debian.org/pool/updates/main/c/curl/libcurl3_7.52.1-5+deb9u16_arm64.deb  404  Not Found [IP: 146.75.122.132 80]
            E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
            pi@rock64:~$ sudo mkdir -p /etc/apt/keyrings
            pi@rock64:~$ 
            pi@rock64:~$ curl -kL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
              % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                             Dload  Upload   Total   Spent    Left  Speed
            100  1684  100  1684    0     0   7395      0 --:--:-- --:--:-- --:--:--  7385
            pi@rock64:~$ echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_${NODE_MAJOR}.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list
            deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_16.x nodistro main
            pi@rock64:~$ echo -e "Package: nodejs\nPin: origin deb.nodesource.com\nPin-Priority: 1001" | sudo tee /etc/apt/preferences.d/nodejs.pref
            Package: nodejs
            Pin: origin deb.nodesource.com
            Pin-Priority: 1001
            pi@rock64:~$ sudo apt update
            Ign:1 http://security.debian.org stretch/updates InRelease
            Ign:2 http://httpredir.debian.org/debian stretch InRelease               
            Ign:3 http://httpredir.debian.org/debian stretch-updates InRelease       
            Err:4 http://security.debian.org stretch/updates Release                 
              404  Not Found [IP: 146.75.122.132 80]
            Ign:5 http://httpredir.debian.org/debian stretch-backports InRelease     
            Err:6 http://httpredir.debian.org/debian stretch Release
              404  Not Found [IP: 146.75.122.132 80]
            Err:7 http://httpredir.debian.org/debian stretch-updates Release
              404  Not Found [IP: 146.75.122.132 80]
            Err:8 http://httpredir.debian.org/debian stretch-backports Release
              404  Not Found [IP: 146.75.122.132 80]
            Get:10 https://deb.nodesource.com/node_16.x nodistro InRelease [12.1 kB]
            Hit:9 http://mirrors.dotsrc.org/armbian-apt stretch InRelease                        
            Get:11 https://deb.nodesource.com/node_16.x nodistro/main armhf Packages [7469 B]
            Get:12 https://deb.nodesource.com/node_16.x nodistro/main arm64 Packages [7485 B]
            Get:13 https://deb.nodesource.com/node_16.x nodistro/main arm64 Contents (deb) [19.5 kB]
            Get:14 https://deb.nodesource.com/node_16.x nodistro/main armhf Contents (deb) [19.5 kB]
            Reading package lists... Done   
            E: The repository 'http://security.debian.org stretch/updates Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            E: The repository 'http://httpredir.debian.org/debian stretch Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            E: The repository 'http://httpredir.debian.org/debian stretch-updates Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            E: The repository 'http://httpredir.debian.org/debian stretch-backports Release' does no longer have a Release file.
            N: Updating from such a repository can't be done securely, and is therefore disabled by default.
            N: See apt-secure(8) manpage for repository creation and user configuration details.
            pi@rock64:~$ sudo apt install nodejs
            Reading package lists... Done
            Building dependency tree       
            Reading state information... Done
            The following packages will be upgraded:
              nodejs
            1 upgraded, 0 newly installed, 0 to remove and 135 not upgraded.
            Need to get 27.2 MB of archives.
            After this operation, 7285 kB of additional disk space will be used.
            Get:1 https://deb.nodesource.com/node_16.x nodistro/main arm64 nodejs arm64 16.20.2-1nodesource1 [27.2 MB]
            Fetched 27.2 MB in 6s (3939 kB/s)                                                                                                                                                                                                                
            (Reading database ... 38255 files and directories currently installed.)
            Preparing to unpack .../nodejs_16.20.2-1nodesource1_arm64.deb ...
            Detected old npm client, removing...
            Unpacking nodejs (16.20.2-1nodesource1) over (14.21.3-1nodesource1) ...
            Setting up nodejs (16.20.2-1nodesource1) ...
            Processing triggers for man-db (2.7.6.1-2) ...
            pi@rock64:~$ 
            
            

            Obwohl...

            pi@rock64:~$ type -P nodejs node npm npx && nodejs -v && node -v && npm -v && npx -v
            /usr/bin/nodejs
            /usr/bin/node
            /usr/bin/npm
            /usr/bin/npx
            v16.20.2
            v16.20.2
            8.19.4
            8.19.4
            pi@rock64:~$ 
            
            Homoran Thomas Braun 2 Replies Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @Volleyhomer last edited by Homoran

              @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

              Obwohl

              dann besteht Hoffnung die wichtigsten Komponenten von iobroker relativ aktuell zu bekommen.
              dann backup
              Neuinstallation
              Restore

              am besten jetzt das erste backup starten und an sicherer Stelle extern speichern

              geht denn jetzt iob diag?

              V 1 Reply Last reply Reply Quote 1
              • Thomas Braun
                Thomas Braun Most Active @Volleyhomer last edited by

                @volleyhomer

                Hagelt Fehlermeldungen.

                Natürlich...
                Aber nodejs@16 ist jetzt drauf, das ist die höchste Version die du da drauf bekommst. Alles andere braucht auch ein aktuelleres Betriebssystem.

                iob stop
                iob update
                iob upgrade self
                
                V 1 Reply Last reply Reply Quote 0
                • V
                  Volleyhomer @Homoran last edited by

                  @homoran said in Fehlermeldungen beim Biobroker Update:

                  @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

                  Obwohl

                  dann besteht Hoffnung die wichtigsten Komponenten von iobroker relativ aktuell zu bekommen.
                  dann backup
                  Neuinstallation
                  Restore

                  am besten jetzt das erste backup starten und an sicherer Stelle extern speichern

                  geht denn jetzt iob diag?

                  Nein, geht nicht.

                  pi@rock64:~$ iob diag
                  pi@rock64:~$ 
                  

                  Backups kopiere ich nach dem erstellen immer direkt via filezilla in die icloud. Normalerweise via backitup auch auf das NAS.

                  1 Reply Last reply Reply Quote 0
                  • V
                    Volleyhomer @Thomas Braun last edited by

                    @thomas-braun said in Fehlermeldungen beim Biobroker Update:

                    @volleyhomer

                    Hagelt Fehlermeldungen.

                    Natürlich...
                    Aber nodejs@16 ist jetzt drauf, das ist die höchste Version die du da drauf bekommst. Alles andere braucht auch ein aktuelleres Betriebssystem.

                    iob stop
                    iob update
                    iob upgrade self
                    

                    Ich hab gerade kurz bzgl. debian Update gegoogelt. Habe ich keine Ahnung von, scheint ja aber nicht wild zu sein. Geht sowas "am offenen Herzen"? Ich bekomme nächste Woche eine neue eMMC für den ROCK64 und werde damit dann alles nochmal neu aufsetzen.

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

                      @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

                      Habe ich keine Ahnung von, scheint ja aber nicht wild zu sein.

                      Aber nicht über drei Releases aus einer Ruine heraus.
                      Bring den iobroker jetzt auf den höchstmöglichen Stand, zieh ein Backup und dann spielst du das sauber in ein frisch installiertes Debian 12 'Bookworm' wieder ein.

                      V 1 Reply Last reply Reply Quote 0
                      • V
                        Volleyhomer @Thomas Braun last edited by

                        @thomas-braun said in Fehlermeldungen beim Biobroker Update:

                        @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

                        Habe ich keine Ahnung von, scheint ja aber nicht wild zu sein.

                        Aber nicht über drei Releases aus einer Ruine heraus.
                        Bring den iobroker jetzt auf den höchstmöglichen Stand, zieh ein Backup und dann spielst du das sauber in ein frisch installiertes Debian 12 'Bookworm' wieder ein.

                        Okay. Das werde ich dann irgendwann die nächsten Tage angehen. Vielen Dank für deine Mühe, Zeit und Hilfe!

                        1 Reply Last reply Reply Quote 0
                        • V
                          Volleyhomer last edited by Volleyhomer

                          @Thomas-Braun :

                          Ein Problem habe ich jetzt noch. Wenn ich Adapter updaten will (u.a. auch Admin) dann wird mir in der iobroker UI folgendes angezeigt.


                          Dependencies
                          js-controller (>=3.3.0): 4.0.24
                          admin (>=5.1.28): 6.3.5
                          node (>=16): 14.21.3


                          angezeigt. Version ist laut Kommando Zeile aber:

                          pi@rock64:~$ node -v
                          v16.20.2
                          pi@rock64:~$ 
                          

                          Muss man da noch irgendwas reseten? Neu starten? Oder ähnliches?

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

                            @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

                            Neu starten?

                            Würde ich machen.
                            Und dann nochmal

                            iob diag
                            
                            V 1 Reply Last reply Reply Quote 0
                            • V
                              Volleyhomer @Thomas Braun last edited by

                              @thomas-braun said in Fehlermeldungen beim Biobroker Update:

                              @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

                              Neu starten?

                              Würde ich machen.
                              Und dann nochmal

                              iob diag
                              

                              Okay, nochmals danke dir.
                              Ein harter Reboot hat geholfen. Jetzt wird im UI auch die korrekten Versionen erkannt.

                              Dann hoffe ich, dass ich beim neuen Aufsetzen so klar komme; Sonst melde ich mich wieder 🙂

                              Schönen Sonntagabend noch!

                              W 1 Reply Last reply Reply Quote 0
                              • W
                                Wildbill @Volleyhomer last edited by Wildbill

                                @volleyhomer sagte in Fehlermeldungen beim Biobroker Update:

                                Ein harter Reboot hat geholfen. Jetzt wird im UI auch die korrekten Versionen erkannt.

                                Was ist ein „harter“ Reboot? Strom weg und gut? Das solltest Du tunlichst vermeiden. Die Chancen stehen gut, Dir dabei mindestens das Dateisystem zu zerstören (geöffnete Dateien und welche, die gerade beschrieben werden sind danach in unbrauchbarem Zustand), beim Raspi kannst Du so auch relativ einfach die SD-Karte zerstören, so dass Du eine neue kaufen musst.
                                Reboot immer sauber mittels

                                sudo reboot
                                

                                oder zum Abschalten

                                sudo shutdown -h now
                                
                                

                                Gruss, Jürgen

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

                                Support us

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

                                812
                                Online

                                31.6k
                                Users

                                79.6k
                                Topics

                                1.3m
                                Posts

                                4
                                37
                                1525
                                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