Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Error/Bug
  4. Adapter-Installationen schlagen fehl

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.8k

  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    883

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Adapter-Installationen schlagen fehl

Geplant Angeheftet Gesperrt Verschoben Error/Bug
5 Beiträge 2 Kommentatoren 1.5k Aufrufe
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • M Offline
    M Offline
    mimquadrat
    schrieb am zuletzt editiert von
    #1

    Hallo Leute,

    im Moment kann ich leider keine Updates mehr machen. Egal welchen Adapter ich installieren möchte nach dem "System Call" geht nichts mehr.

    Neustarts gemacht

    npm intall iobroker gemacht

    JS-Controller 0.8.4

    Was mir noch aufgefallen ist: Bei jeder Adapterinstallation wird sayit mitinstalliert.

    aber selbst das geht nicht
    > iobroker 2016-01-23 17:15:20 error host.raspberrypi Cannot install iobroker.sayit: 254

    Beim Wolf Adapter kam das hier ` > $ ./iobroker add wolf

    npm install iobroker.wolf –production --prefix "/opt/iobroker" (System call)

    npm

    WARN

    enoent ENOENT, open '/opt/iobroker/package.json'

    npm

    WARN

    mongodb-core@1.2.28 requires a peer of kerberos@~0.0 but none was installed.

    npm WARN

    iobroker No description

    npm

    WARN iobroker No repository field.

    npm

    WARN

    iobroker No README data

    npm

    WARN

    iobroker No license field.

    host.raspberrypi install adapter wolf

    npm install --production --prefix "/opt/iobroker/node_modules/iobroker.wolf" (System call)

    npm

    ERR!

    Linux 4.1.7-v7+

    npm ERR! argv "node" "/usr/local/bin/npm" "install" "--production" "--prefix" "/opt/iobroker/node_modules/iobroker.wolf"

    npm ERR! node v0.12.6npm

    ERR! npm v3.5.2

    npm ERR!

    Cannot read property 'target' of nullnpm ERR!

    npm ERR! If you need help, you may report this error at:

    npm

    ERR! <https://github.com/npm/npm/issues>

    npm ERR! Please include the following file with any support request:

    npm ERR! /opt/npm-debug.log

    Cannot install iobroker.wolf: 1

    ERROR: process exited with code 25 `

    könnt ihr mir helfen?

    1 Antwort Letzte Antwort
    0
    • N Offline
      N Offline
      nobody
      schrieb am zuletzt editiert von
      #2

      hi,

      scheint leider nun ein Standard-Problem mit den Jessie-Image zu werden.

      Einmal vorher folgendes ausführen:

      sudo apt-get install libkrb5-dev
      
      

      Die Begründung steht hier:

      http://forum.iobroker.net/viewtopic.php?t=1962

      1 Antwort Letzte Antwort
      0
      • M Offline
        M Offline
        mimquadrat
        schrieb am zuletzt editiert von
        #3

        Hi Nobody,

        vielen Dank für Deinen Tipp, leider bringt es keiner Besserung.

        Nicht mal Updates gehen mehr

        Hier Beispiel von Node-Red Update:

        $ ./iobroker upgrade node-red
        npm install iobroker.node-red --production --prefix "/opt/iobroker" (System call)
        npm
        
        ERR! Linux 4.1.7-v7+
        npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6npm ERR! npm  v3.5.2
        
        npm ERR! code ECONNRESETnpm ERR! errno ECONNRESET
        npm 
        ERR! syscall read
        
        npm ERR! network read ECONNRESETnpm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        npm ERR! Linux 4.1.7-v7+
        npm ERR! 
        argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6
        
        npm ERR!
        
        npm  v3.5.2npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        npm ERR! syscall read
        
        npm ERR! network read ECONNRESET
        npm 
        ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm
         ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        npm ERR! syscall read
        
        npm ERR! network read ECONNRESET
        npm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        npm ERR! Linux 4.1.7-v7+
        npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        npm 
        ERR! syscall read
        
        npm ERR! network read ECONNRESET
        npm ERR! network This is most likely not a problem with npm itselfnpm ERR! network and is related to network connectivity.
        npm ERR! network
         In most cases you are behind a proxy or have bad network settings.npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm
         ERR! Linux 4.1.7-v7+npm ERR! argv
         "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        npm ERR! 
        syscall read
        npm ERR! network read ECONNRESET
        npm ERR! network This is most likely not a problem with npm itself
        npm ERR!
         network and is related to network connectivity.npm 
        ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm 
        ERR! errno ECONNRESETnpm ERR! syscall read
        
        npm ERR! network read ECONNRESET
        npm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        
        npm ERR! network In most cases you are behind a proxy or have bad network settings.npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm ERR! Linux 4.1.7-v7+npm
         ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        npm ERR! syscall read
        
        npm
         ERR! network read ECONNRESETnpm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm ERR! network 
        
        npm ERR! network If you are behind a proxy, please make sure that thenpm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        
        npm ERR! code ECONNRESETnpm ERR! errno ECONNRESET
        npm ERR! syscall read
        
        npm ERR! network read ECONNRESET
        npm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm ERR! network 
        npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        npm
         ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        npm ERR! syscall read
        
        npm ERR! network read ECONNRESET
        
        npm ERR! network This is most likely not a problem with npm itselfnpm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm 
        ERR! network npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm ERR! Linux 4.1.7-v7+npm ERR! argv
         "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        npm ERR! code ECONNRESET
        npm ERR! errno ECONNRESET
        
        npm ERR! 
        syscall read
        npm ERR! network read ECONNRESET
        npm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm ERR!
         network npm ERR! network If you are behind a proxy, please make sure that the
        
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        npm
         ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm  v3.5.2
        
        npm ERR! code ECONNRESETnpm ERR! errno ECONNRESET
        npm ERR! syscall read
        
        npm ERR! 
        network read ECONNRESETnpm ERR! network This is most likely not a problem with npm itself
        npm ERR! network and is related to network connectivity.
        npm ERR! network In most cases you are behind a proxy or have bad network settings.
        npm 
        ERR! network npm ERR! network If you are behind a proxy, please make sure that the
        npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
        
        npm
         ERR! Linux 4.1.7-v7+npm ERR! argv "node" "/usr/local/bin/npm" "install" "iobroker.node-red" "--production" "--prefix" "/opt/iobroker"
        npm ERR! node v0.12.6
        npm ERR! npm 
         v3.5.2
        npm
         ERR! shasum check failed for /tmp/npm-2687-e3746185/registry.npmjs.org/when/-/when-3.7.7.tgznpm ERR! Expected: aba03fc3bb736d6c88b091d013d8a8e590d84718
        npm ERR! Actual:   e70ad1d480b0a11ef0f7d0e7542269a06a693a85
        npm ERR! From:     https://registry.npmjs.org/when/-/when-3.7.7.tgz
        npm ERR! 
        npm ERR! If you need help, you may report this error at:
        npm ERR!     <https: github.com/npm/issues="">
        
        npm
         ERR! Please include the following file with any support request:
        npm ERR!     /opt/npm-debug.log
        ERROR: host.raspberrypi Cannot install iobroker.node-red: 1
        ERROR: process exited with code 25</https:>
        
        1 Antwort Letzte Antwort
        0
        • N Offline
          N Offline
          nobody
          schrieb am zuletzt editiert von
          #4

          ok, das ist jetzt aber ein anderer Fehler und auch kein spezifischer Fehler für die Installation mit ioBroker sondern entweder ein Netzproblem oder ein Problem mit npm selbst.

          Klappt der Zugang zum Internet vom System aus?

          Falls der Zugriff auf das Internet und auf die npm-Server geht, versuche mal den npm Cache komplett zu löschen und es dann erneut zu versuchen.

          sudo rm -rf ~/.npm
          
          

          Was mir noch aufgefallen ist:
          ` > npm ERR! node v0.12.6npm

          ERR! npm v3.5.2 `

          Die npm Version passt nicht richtig zu node.js Version.

          Wenn ich mich richtig erinnere sollte alles unter node.js 4.x eigentlich nur npm Versionen 2.x verwenden.

          1 Antwort Letzte Antwort
          0
          • M Offline
            M Offline
            mimquadrat
            schrieb am zuletzt editiert von
            #5

            du bist spitze! ich hatte da mal ein Update auf NPM 3.x gemacht blöderweise…

            hab mit````
            npm install npm@2 -g

            
            danke!!!!
            1 Antwort Letzte Antwort
            0
            Antworten
            • In einem neuen Thema antworten
            Anmelden zum Antworten
            • Älteste zuerst
            • Neuste zuerst
            • Meiste Stimmen


            Support us

            ioBroker
            Community Adapters
            Donate

            745

            Online

            32.6k

            Benutzer

            82.1k

            Themen

            1.3m

            Beiträge
            Community
            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
            ioBroker Community 2014-2025
            logo
            • Anmelden

            • Du hast noch kein Konto? Registrieren

            • Anmelden oder registrieren, um zu suchen
            • Erster Beitrag
              Letzter Beitrag
            0
            • Home
            • Aktuell
            • Tags
            • Ungelesen 0
            • Kategorien
            • Unreplied
            • Beliebt
            • GitHub
            • Docu
            • Hilfe