Navigation

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

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    iobroker zeschossen

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

      @krisiun
      Dann sollte bei

      sudo apt update
      

      nur noch der fehlende Schlüssel für nodesource angemeckert werden.

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

        @thomas-braun

        Kann aber trotzdem den iob nicht starten. Gleiche Fehler.

        krisiun@Marek2:/root$ iobroker start
        /usr/bin/node: 1: cannot create : Permission denied
        /usr/bin/node: 2: : not found
        /usr/bin/node: 4: Syntax error: Unterminated quoted string
        
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Krisiun last edited by Thomas Braun

          @krisiun

          NICHT SO SCHNELL!
          Du bist ja auch noch nicht fertig...

          sudo apt update
          cd
          

          sagt?

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

            @thomas-braun

            krisiun@Marek2:/root$ sudo apt update
            Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
            Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
            Hit:3 http://security.ubuntu.com/ubuntu jammy-security InRelease
            Get:4 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]
            Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
            Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease
            Err:4 https://dl.yarnpkg.com/debian stable InRelease
              The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
            Err:6 https://deb.nodesource.com/node_18.x nodistro InRelease
              The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
            Fetched 17.1 kB in 4s (4719 B/s)
            Reading package lists... Done
            Building dependency tree... Done
            Reading state information... Done
            1 package can be upgraded. Run 'apt list --upgradable' to see it.
            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_18.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
            W: Failed to fetch https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
            W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>
            W: Some index files failed to download. They have been ignored, or old ones used instead.
            
            Thomas Braun 2 Replies Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Krisiun last edited by

              @krisiun

              Du solltest doch yarn löschen...

              sudo rm /etc/apt/sources.list.d/yar*
              
              Krisiun 1 Reply Last reply Reply Quote 0
              • Krisiun
                Krisiun @Thomas Braun last edited by

                @thomas-braun
                Dann sag mir bitte, bitte wie? Sorry aber das ist mir auch schon unangenehm dass ich das nicht schnalle

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

                  @krisiun

                  Dann

                  sudo rm `sudo find / -name nodesource.gpg`
                  sudo rm `sudo find / -name nodesource.key`
                  sudo apt install -y ca-certificates curl gnupg
                  sudo mkdir -p /etc/apt/keyrings
                  curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
                  sudo apt update
                  
                  1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Krisiun last edited by

                    @krisiun sagte in iobroker zeschossen:

                    Dann sag mir bitte, bitte wie?

                    Steht doch da.

                    sudo rm /etc/apt/sources.list.d/yar*
                    
                    Krisiun 1 Reply Last reply Reply Quote 0
                    • Krisiun
                      Krisiun @Thomas Braun last edited by

                      @thomas-braun
                      Ich bin dabei aber ich kanns nicht finden

                      Thomas Braun bahnuhr 2 Replies Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Krisiun last edited by

                        @krisiun sagte in iobroker zeschossen:

                        ich kanns nicht finden

                        Was? Dein Terminal?

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

                          @thomas-braun
                          wo ich das löschen kann

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • bahnuhr
                            bahnuhr Forum Testing Most Active @Krisiun last edited by

                            @krisiun sagte in iobroker zeschossen:

                            Ich bin dabei aber ich kanns nicht finden

                            Du sollst da nichts finden.
                            Sondern dich per putty (oder was du auch immer nimmst) einloggen.
                            Und dann in der konsole den Befehl eingeben.

                            Mehr nicht.

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

                              @krisiun

                              MIT DEM BEFEHL:

                              sudo rm /etc/apt/sources.list.d/yar*
                              

                              Klickst du da mit einem Filebrowser wild durch die Gegend? Lass das!

                              Krisiun 2 Replies Last reply Reply Quote 0
                              • Krisiun
                                Krisiun @Thomas Braun last edited by

                                @thomas-braun

                                krisiun@Marek2:/root$ sudo rm /etc/apt/sources.list.d/yar*
                                rm: cannot remove '/etc/apt/sources.list.d/yar*': No such file or directory
                                krisiun@Marek2:/root$
                                
                                
                                Thomas Braun 1 Reply Last reply Reply Quote 0
                                • Krisiun
                                  Krisiun @Thomas Braun last edited by

                                  @thomas-braun
                                  Ist wohl wieder falsch?

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

                                    @krisiun

                                    cd
                                    ls -lAh /etc/apt/sources.list.d/
                                    
                                    Krisiun 1 Reply Last reply Reply Quote 0
                                    • Krisiun
                                      Krisiun @Thomas Braun last edited by

                                      @thomas-braun

                                      krisiun@Marek2:/root$ ls -lAh /etc/apt/sources.list.d/
                                      total 0
                                      -rw-r--r-- 1 root root 100 Oct  8 21:12 nodesource.list
                                      -rw-r--r-- 1 root root 202 Nov 22  2022 nodesource.list.distUpgrade
                                      -rw-r--r-- 1 root root 109 Oct  8 21:11 nodesource.list.save
                                      
                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Krisiun last edited by

                                        @krisiun

                                        cd
                                        sudo rm /etc/apt/sources.list.d/nodesource.list.*
                                        sudo apt update
                                        
                                        Krisiun 1 Reply Last reply Reply Quote 0
                                        • Homoran
                                          Homoran Global Moderator Administrators @Krisiun last edited by

                                          @krisiun sagte in iobroker zeschossen:

                                          Hab alles gemacht

                                          zeigen!
                                          incl. Eingabe

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

                                            @thomas-braun

                                            krisiun@Marek2:/root$ cd
                                            krisiun@Marek2:~$ sudo rm /etc/apt/sources.list.d/nodesource.list.*
                                            krisiun@Marek2:~$ sudo apt update
                                            Hit:1 https://deb.nodesource.com/node_18.x nodistro InRelease
                                            Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
                                            Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease
                                            Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
                                            Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
                                            Err:1 https://deb.nodesource.com/node_18.x nodistro InRelease
                                              The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
                                            Reading package lists... Done
                                            Building dependency tree... Done
                                            Reading state information... Done
                                            1 package can be upgraded. Run 'apt list --upgradable' to see it.
                                            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_18.x nodistro InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
                                            W: Failed to fetch https://deb.nodesource.com/node_18.x/dists/nodistro/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2F59B5F99B1BE0B4
                                            W: Some index files failed to download. They have been ignored, or old ones used instead.
                                            
                                            Thomas Braun 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

                                            722
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            9
                                            175
                                            15408
                                            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