Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Aktualisierungen der Adapter funktionieren nicht

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Aktualisierungen der Adapter funktionieren nicht

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

      @Guido-Spoltmann

      iobroker list instances
      
      Guido Spoltmann 1 Reply Last reply Reply Quote 0
      • Guido Spoltmann
        Guido Spoltmann @Thomas Braun last edited by

        @Thomas-Braun sagte in Aktualisierungen der Adapter funktionieren nicht:

        iobroker list instances

        pi@raspberrypi:~ $ iobroker list instances
        internal/modules/cjs/loader.js:818
          throw err;
          ^
        
        Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
            at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
            at Function.Module._load (internal/modules/cjs/loader.js:667:27)
            at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
            at internal/main/run_main_module.js:17:47 {
          code: 'MODULE_NOT_FOUND',
          requireStack: []
        }
        
        
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @Guido Spoltmann last edited by

          @Guido-Spoltmann
          Das ist nicht gut...

          iobroker -v
          iobroker status
          
          cd /opt/iobroker
          npm i iobroker.js-controller@3.1.6 --production
          
          Guido Spoltmann wendy2702 2 Replies Last reply Reply Quote 0
          • Guido Spoltmann
            Guido Spoltmann @Thomas Braun last edited by

            @Thomas-Braun sagte in Aktualisierungen der Adapter funktionieren nicht:

            npm i iobroker.js-controller@3.1.6 --production

            Hab ich mir schon fast gedacht....

            pi@raspberrypi:~ $ iobroker -v
            internal/modules/cjs/loader.js:818
              throw err;
              ^
            
            Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
                at Function.Module._load (internal/modules/cjs/loader.js:667:27)
                at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
                at internal/main/run_main_module.js:17:47 {
              code: 'MODULE_NOT_FOUND',
              requireStack: []
            }
            pi@raspberrypi:~ $ iobroker status
            internal/modules/cjs/loader.js:818
              throw err;
              ^
            
            Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
                at Function.Module._load (internal/modules/cjs/loader.js:667:27)
                at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
                at internal/main/run_main_module.js:17:47 {
              code: 'MODULE_NOT_FOUND',
              requireStack: []
            }
            pi@raspberrypi:~ $ cd /opt/iobroker
            pi@raspberrypi:/opt/iobroker $ npm i iobroker.js-controller@3.1.6 --production
            npm ERR! code EAI_AGAIN
            npm ERR! errno EAI_AGAIN
            npm ERR! request to https://registry.npmjs.org/iobroker.js-controller failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org
            
            npm ERR! A complete log of this run can be found in:
            npm ERR!     /home/iobroker/.npm/_logs/2020-12-27T12_42_34_286Z-debug.log
            pi@raspberrypi:/opt/iobroker $
            
            
            Thomas Braun 2 Replies Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @Guido Spoltmann last edited by

              @Guido-Spoltmann Immer noch ein Knoten in deinem lokalen Netz, würde ich sagen.

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

                @Guido-Spoltmann

                ping npmjs.org
                traceroute npmjs.org
                
                Guido Spoltmann 1 Reply Last reply Reply Quote 0
                • Guido Spoltmann
                  Guido Spoltmann @Thomas Braun last edited by

                  @Thomas-Braun sagte in Aktualisierungen der Adapter funktionieren nicht:

                  traceroute npmjs.org

                  pi@raspberrypi:/opt/iobroker $ ping npmjs.org
                  ping: npmjs.org: Temporary failure in name resolution
                  pi@raspberrypi:/opt/iobroker $ traceroute npmjs.org
                  npmjs.org: Temporary failure in name resolution
                  Cannot handle "host" cmdline arg `npmjs.org' on position 1 (argc 1)
                  pi@raspberrypi:/opt/iobroker $
                  
                  
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Guido Spoltmann last edited by Thomas Braun

                    @Guido-Spoltmann
                    Tjoar...
                    Ohne DNS auch keine Namensauflösung. Hast du da irgendwas in der Fritzbox umgefummelt?

                    cat /etc/resolv.conf
                    
                    Guido Spoltmann 1 Reply Last reply Reply Quote 0
                    • Guido Spoltmann
                      Guido Spoltmann @Thomas Braun last edited by Guido Spoltmann

                      @Thomas-Braun
                      Hi nein es läuft hie auch alles, habe 4 Teenies die mich sofort informiert hätten das das Internet nicht geht.

                      pi@raspberrypi:/opt/iobroker $ cat /etc/resolv.conf
                      # Generated by resolvconf
                      domain fritz.box
                      nameserver 192.168.178.1
                      nameserver fd00::464e:6dff:fe26:9597
                      
                      
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Guido Spoltmann last edited by

                        @Guido-Spoltmann

                        ping 104.16.22.35
                        
                        Guido Spoltmann 1 Reply Last reply Reply Quote 0
                        • Guido Spoltmann
                          Guido Spoltmann @Thomas Braun last edited by

                          @Thomas-Braun sagte in Aktualisierungen der Adapter funktionieren nicht:

                          ping 104.16.22.35

                          pi@raspberrypi:/opt/iobroker $ ping 104.16.22.35
                          PING 104.16.22.35 (104.16.22.35) 56(84) bytes of data.
                          64 bytes from 104.16.22.35: icmp_seq=1 ttl=58 time=10.4 ms
                          64 bytes from 104.16.22.35: icmp_seq=2 ttl=58 time=9.59 ms
                          64 bytes from 104.16.22.35: icmp_seq=3 ttl=58 time=9.53 ms
                          64 bytes from 104.16.22.35: icmp_seq=4 ttl=58 time=9.33 ms
                          64 bytes from 104.16.22.35: icmp_seq=5 ttl=58 time=8.94 ms
                          64 bytes from 104.16.22.35: icmp_seq=6 ttl=58 time=9.68 ms
                          64 bytes from 104.16.22.35: icmp_seq=7 ttl=58 time=9.41 ms
                          64 bytes from 104.16.22.35: icmp_seq=8 ttl=58 time=9.49 ms
                          64 bytes from 104.16.22.35: icmp_seq=9 ttl=58 time=9.28 ms
                          64 bytes from 104.16.22.35: icmp_seq=10 ttl=58 time=9.39 ms
                          64 bytes from 104.16.22.35: icmp_seq=11 ttl=58 time=23.2 ms
                          64 bytes from 104.16.22.35: icmp_seq=12 ttl=58 time=22.3 ms
                          64 bytes from 104.16.22.35: icmp_seq=13 ttl=58 time=9.21 ms
                          64 bytes from 104.16.22.35: icmp_seq=14 ttl=58 time=9.29 ms
                          64 bytes from 104.16.22.35: icmp_seq=15 ttl=58 time=9.27 ms
                          64 bytes from 104.16.22.35: icmp_seq=16 ttl=58 time=9.45 ms
                          64 bytes from 104.16.22.35: icmp_seq=17 ttl=58 time=30.4 ms
                          64 bytes from 104.16.22.35: icmp_seq=18 ttl=58 time=9.33 ms
                          64 bytes from 104.16.22.35: icmp_seq=19 ttl=58 time=25.3 ms
                          64 bytes from 104.16.22.35: icmp_seq=20 ttl=58 time=8.86 ms
                          64 bytes from 104.16.22.35: icmp_seq=21 ttl=58 time=9.44 ms
                          64 bytes from 104.16.22.35: icmp_seq=22 ttl=58 time=9.70 ms
                          ^C
                          --- 104.16.22.35 ping statistics ---
                          22 packets transmitted, 22 received, 0% packet loss, time 54ms
                          rtt min/avg/max/mdev = 8.855/12.307/30.355/6.268 ms
                          
                          
                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Guido Spoltmann last edited by

                            @Guido-Spoltmann Gut, also raus kommst du. Nur die Namensauflösung tickt nicht sauber.
                            Ich vermute ja immer noch eine Einstellung in der Fritzbox.

                            Kannst du die mal durchstarten?

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

                              @Thomas-Braun
                              So Neustart ist erledigt...
                              Habe jetzt nochmal die letzten Befehle in Putty eingetragen:

                              pi@raspberrypi:/opt/iobroker $ ping npmjs.org
                              PING npmjs.org(2606:4700::6810:1a23 (2606:4700::6810:1a23)) 56 data bytes
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=1 ttl=57 tim                                                                                                                                                             e=9.73 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=2 ttl=57 tim                                                                                                                                                             e=9.47 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=3 ttl=57 tim                                                                                                                                                             e=9.08 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=4 ttl=57 tim                                                                                                                                                             e=9.29 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=5 ttl=57 tim                                                                                                                                                             e=9.33 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=6 ttl=57 time=32.2 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=7 ttl=57 time=39.2 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=8 ttl=57 time=9.58 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=9 ttl=57 time=9.51 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=10 ttl=57 time=9.27 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=11 ttl=57 time=9.20 ms
                              64 bytes from 2606:4700::6810:1a23 (2606:4700::6810:1a23): icmp_seq=12 ttl=57 time=36.5 ms
                              ^C
                              --- npmjs.org ping statistics ---
                              12 packets transmitted, 12 received, 0% packet loss, time 25ms
                              rtt min/avg/max/mdev = 9.079/16.029/39.242/11.600 ms
                              pi@raspberrypi:/opt/iobroker $ traceroute npmjs.org
                              traceroute to npmjs.org (104.16.20.35), 30 hops max, 60 byte packets
                               1  fritz.box (192.168.178.1)  0.392 ms  0.350 ms  0.295 ms
                               2  185.113.144.6 (185.113.144.6)  4.897 ms  4.829 ms  4.719 ms
                               3  185.113.144.2 (185.113.144.2)  4.658 ms  4.552 ms  4.622 ms
                               4  185.113.144.1 (185.113.144.1)  4.555 ms  4.445 ms  4.381 ms
                               5  ae0-408.dus10.core-backbone.com (81.95.15.37)  9.165 ms  9.097 ms  9.078 ms
                               6  ae15-2029.fra30.core-backbone.com (81.95.15.70)  12.090 ms  10.177 ms  9.994 ms
                               7  core-backbone.cloudflare.com (80.255.9.34)  10.854 ms  10.597 ms  10.815 ms
                               8  104.16.20.35 (104.16.20.35)  10.522 ms  10.632 ms  10.632 ms
                              pi@raspberrypi:/opt/iobroker $
                              

                              Sieht besser aus oder?

                              1 Reply Last reply Reply Quote 0
                              • wendy2702
                                wendy2702 last edited by

                                @Guido-Spoltmann sagte in Aktualisierungen der Adapter funktionieren nicht:

                                https://registry.npmjs.org/iobroker.js-controller

                                Kannst das auch mal an einem PC in einem Browser eingeben und schauen ob die Seite erreichbar ist.

                                Klappt das liegt es wohl am PI.

                                Klappt es nicht: Netzwerk bzw. Fritzbox

                                Guido Spoltmann 1 Reply Last reply Reply Quote 0
                                • Guido Spoltmann
                                  Guido Spoltmann @wendy2702 last edited by

                                  @wendy2702 sagte in Aktualisierungen der Adapter funktionieren nicht:

                                  https://registry.npmjs.org/iobroker.js-controller

                                  Ja klappt...27-12-_2020_14-39-31.png

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

                                    @Guido-Spoltmann Dann sollte es ja jetzt funktionieren.

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

                                      @Thomas-Braun sagte in Aktualisierungen der Adapter funktionieren nicht:

                                      @Guido-Spoltmann
                                      Das ist nicht gut...

                                      iobroker -v
                                      iobroker status
                                      
                                      cd /opt/iobroker
                                      npm i iobroker.js-controller@3.1.6 --production
                                      

                                      Dann das erneut ausführen

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

                                        @wendy2702 Aber nicht die Zeile mit npm i..., wenn es schon läuft.

                                        Guido Spoltmann wendy2702 2 Replies Last reply Reply Quote 1
                                        • Guido Spoltmann
                                          Guido Spoltmann @Thomas Braun last edited by

                                          @Thomas-Braun
                                          Bin im Admin Bereich angekommen, vielen Dank für die Unterstützung. Hab ja nebenbei wieder was dazu gelernt.
                                          LG
                                          Guido

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

                                            @Thomas-Braun sagte in Aktualisierungen der Adapter funktionieren nicht:

                                            @wendy2702 Aber nicht die Zeile mit npm i..., wenn es schon läuft.

                                            Das stimmt, allerdings konnte ich kein logfile sehen in dem die Installation bzw. Der Start als erfolgreich zu erkennen war.

                                            Gucke aber auch nur am Handy und habe es vielleicht übersehen oder überlesen.

                                            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

                                            470
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter update error
                                            5
                                            44
                                            2480
                                            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