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. ioBroker Allgemein
  4. Raspberrypi install iobroker - node.js 8.12

NEWS

  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    22
    1
    1.2k

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    9.2k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    14
    1
    2.5k

Raspberrypi install iobroker - node.js 8.12

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
27 Beiträge 6 Kommentatoren 5.7k 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.
  • A Offline
    A Offline
    Arnulf
    schrieb am zuletzt editiert von
    #16

    ah thx.

    the zigbee adapter still had problems. So I decided to deinstall this adapter and reinstall it

    Now it wprks

    thank you

    Before I make any othe changes I will do a full backup tomorrow… :lol:

    1 Antwort Letzte Antwort
    0
    • A Offline
      A Offline
      Arnulf
      schrieb am zuletzt editiert von
      #17

      @AlCalzone:

      > Error: EACCES: permission denied, scandir '/root/.npm/_logs'
      Run

      sudo chown -R $(whoami) ~/.npm
      

      and try again.

      And try npm rebuild without sudo before resorting to sudo npm rebuild. sudo is known to cause problems. `

      hm…

      just to clarity first...

      sudo chown -R $(whoami) ~/.npm
      

      means that the ohnership of all files and subdirectories are transferred to user "pi"?

      and I have to set this commad at /opt/iobroker ?

      and what is with iobroker? do I have to stop it first?

      1 Antwort Letzte Antwort
      0
      • AlCalzoneA Offline
        AlCalzoneA Offline
        AlCalzone
        Developer
        schrieb am zuletzt editiert von
        #18

        @Arnulf:

        just to clarity first…

        sudo chown -R $(whoami) ~/.npm
        

        means that the ohnership of all files and subdirectories are transferred to user "pi"? `

        Newer npm versions have the tendency to change the ownership of the .npm folder in the current user's homedir (~). So when you execute npm install with sudo and later without, it won't be able to access ~/.npm (e.g. /home/pi/.npm) because it now belongs to root.

        The above command changes the ownership back to whomever it belonged in the first place.

        And no, you don't need to do anything with iobroker or change folder to execute that command.

        Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

        1 Antwort Letzte Antwort
        0
        • A Offline
          A Offline
          Arnulf
          schrieb am zuletzt editiert von
          #19

          I tryed n

          sudo chown -R $(whoami) ~/.npm

          ==> no output, cursor prompt returns within miliseconds

          then

          npm rebuild

          from the root directory shows this

          ! pi@ioBroker-Pi:~ $ npm rebuild
          ! ajv@6.5.5 /home/pi/node_modules/ajv
          ! fast-deep-equal@2.0.1 /home/pi/node_modules/fast-deep-equal
          ! fast-json-stable-stringify@2.0.0 /home/pi/node_modules/fast-json-stable-stringify
          ! json-schema-traverse@0.4.1 /home/pi/node_modules/json-schema-traverse
          ! uri-js@4.2.2 /home/pi/node_modules/uri-js
          ! punycode@2.1.1 /home/pi/node_modules/punycode
          ! asap@2.0.6 /home/pi/node_modules/asap
          ! asn1@0.2.4 /home/pi/node_modules/asn1
          ! safer-buffer@2.1.2 /home/pi/node_modules/safer-buffer
          ! assert-plus@1.0.0 /home/pi/node_modules/assert-plus
          ! asynckit@0.4.0 /home/pi/node_modules/asynckit
          ! aws-sign2@0.7.0 /home/pi/node_modules/aws-sign2
          ! aws4@1.8.0 /home/pi/node_modules/aws4
          ! bcrypt-pbkdf@1.0.2 /home/pi/node_modules/bcrypt-pbkdf
          ! tweetnacl@0.14.5 /home/pi/node_modules/tweetnacl
          ! caseless@0.12.0 /home/pi/node_modules/caseless
          ! combined-stream@1.0.7 /home/pi/node_modules/combined-stream
          ! delayed-stream@1.0.0 /home/pi/node_modules/delayed-stream
          ! core-util-is@1.0.2 /home/pi/node_modules/core-util-is
          ! dashdash@1.14.1 /home/pi/node_modules/dashdash
          ! debug@2.6.9 /home/pi/node_modules/debug
          ! ms@2.0.0 /home/pi/node_modules/ms
          ! ecc-jsbn@0.1.2 /home/pi/node_modules/ecc-jsbn
          ! jsbn@0.1.1 /home/pi/node_modules/jsbn
          ! extend@3.0.2 /home/pi/node_modules/extend
          ! extsprintf@1.3.0 /home/pi/node_modules/extsprintf
          ! forever-agent@0.6.1 /home/pi/node_modules/forever-agent
          ! form-data@2.3.3 /home/pi/node_modules/form-data
          ! mime-types@2.1.21 /home/pi/node_modules/mime-types
          ! mime-db@1.37.0 /home/pi/node_modules/mime-db
          ! getpass@0.1.7 /home/pi/node_modules/getpass
          ! har-schema@2.0.0 /home/pi/node_modules/har-schema
          ! har-validator@5.1.3 /home/pi/node_modules/har-validator
          ! http-signature@1.2.0 /home/pi/node_modules/http-signature
          ! jsprim@1.4.1 /home/pi/node_modules/jsprim
          ! json-schema@0.2.3 /home/pi/node_modules/json-schema
          ! verror@1.10.0 /home/pi/node_modules/verror
          ! sshpk@1.15.2 /home/pi/node_modules/sshpk
          ! ip@1.1.5 /home/pi/node_modules/ip
          ! is-absolute@0.2.6 /home/pi/node_modules/is-absolute
          ! is-relative@0.2.1 /home/pi/node_modules/is-relative
          ! is-unc-path@0.1.2 /home/pi/node_modules/is-unc-path
          ! unc-path-regex@0.1.2 /home/pi/node_modules/unc-path-regex
          ! is-windows@0.2.0 /home/pi/node_modules/is-windows
          ! is-typedarray@1.0.0 /home/pi/node_modules/is-typedarray
          ! isstream@0.1.2 /home/pi/node_modules/isstream
          ! json-stringify-safe@5.0.1 /home/pi/node_modules/json-stringify-safe
          ! lodash@4.17.11 /home/pi/node_modules/lodash
          ! minimist@0.0.8 /home/pi/node_modules/minimist
          ! mkdirp@0.5.1 /home/pi/node_modules/mkdirp
          ! node-persist@2.1.0 /home/pi/node_modules/node-persist
          ! q@1.1.2 /home/pi/node_modules/q
          ! node-red-contrib-alexa-local@0.3.12 /home/pi/node_modules/node-red-contrib-alexa-local
          ! peer-ssdp@0.0.5 /home/pi/node_modules/peer-ssdp
          ! stoppable@1.0.5 /home/pi/node_modules/stoppable
          ! node-red-contrib-bool-gate@1.0.2 /home/pi/node_modules/node-red-contrib-bool-gate
          ! node-red-contrib-wemo-emulator@0.6.0 /home/pi/node_modules/node-red-contrib-wemo-emulator
          ! wemore@0.6.0 /home/pi/node_modules/wemore
          ! node-ssdp@2.9.1 /home/pi/node_modules/node-ssdp
          ! q@2.0.3 /home/pi/node_modules/wemore/node_modules/q
          ! pop-iterate@1.0.1 /home/pi/node_modules/pop-iterate
          ! weak-map@1.0.5 /home/pi/node_modules/weak-map
          ! request@2.88.0 /home/pi/node_modules/request
          ! oauth-sign@0.9.0 /home/pi/node_modules/oauth-sign
          ! performance-now@2.1.0 /home/pi/node_modules/performance-now
          ! qs@6.5.2 /home/pi/node_modules/qs
          ! safe-buffer@5.1.2 /home/pi/node_modules/safe-buffer
          ! tough-cookie@2.4.3 /home/pi/node_modules/tough-cookie
          ! psl@1.1.29 /home/pi/node_modules/psl
          ! punycode@1.4.1 /home/pi/node_modules/tough-cookie/node_modules/punycode
          ! tunnel-agent@0.6.0 /home/pi/node_modules/tunnel-agent
          ! uuid@3.3.2 /home/pi/node_modules/uuid
          ! xml2js@0.4.19 /home/pi/node_modules/xml2js
          ! sax@1.2.4 /home/pi/node_modules/sax
          ! xmlbuilder@9.0.7 /home/pi/node_modules/xmlbuilder

          but with starting point /opt/iobroker all the same sh… again

          1 Antwort Letzte Antwort
          0
          • AlCalzoneA Offline
            AlCalzoneA Offline
            AlCalzone
            Developer
            schrieb am zuletzt editiert von
            #20

            You have to execute "npm rebuild" in /opt/iobroker.

            Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

            1 Antwort Letzte Antwort
            0
            • A Offline
              A Offline
              Arnulf
              schrieb am zuletzt editiert von Jey Cee
              #21

              @AlCalzone:

              You have to execute "npm rebuild" in /opt/iobroker.

              This is what I've done.

              And I receive same error messages as shown in my former post

              [Update]

              nice

              now, after one reboot iobroker is dead

              pi@ioBroker-Pi:/opt/iobroker $ sudo iobroker start
              module.js:550
                  throw err;
                  ^
              
              Error: Cannot find module '/usr/local/www/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                  at Function.Module._resolveFilename (module.js:548:15)
                  at Function.Module._load (module.js:475:25)
                  at Function.Module.runMain (module.js:694:10)
                  at startup (bootstrap_node.js:204:16)
                  at bootstrap_node.js:625:3
              
              

              now (after iobroker is definately not running I tryed again npm rebuild

              log.txt

              so my try was to do chmod 777 /var/lib/dpkg because of the first messages

              E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: Keine Berechtigung)
              E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, sind Sie root?
              

              but no change. Same errors
              next try:

               sudo apt-get install build-essential
              

              result:

                Paketlisten werden gelesen… Fertig
               Abhängigkeitsbaum wird aufgebaut.
               Statusinformationen werden eingelesen.... Fertig
               build-essential ist schon die neueste Version (12.3).
               Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
               gyp javascript-common libc-ares2 libhttp-parser2.8 libjs-inherits libjs-jquery
               libjs-node-uuid libjs-underscore libssl-dev libssl-doc libuv1 libuv1-dev node-abbrev
               node-ansi node-ansi-color-table node-archy node-async node-balanced-match
               node-block-stream node-brace-expansion node-builtin-modules node-combined-stream
               node-concat-map node-cookie-jar node-delayed-stream node-forever-agent node-form-data
               node-fs.realpath node-fstream node-fstream-ignore node-github-url-from-git node-glob
               node-graceful-fs node-gyp node-hosted-git-info node-inflight node-inherits node-ini
               node-is-builtin-module node-isexe node-json-stringify-safe node-lockfile node-lru-cache
               node-mime node-minimatch node-mkdirp node-mute-stream node-node-uuid node-nopt
               node-normalize-package-data node-npmlog node-once node-osenv node-path-is-absolute
               node-pseudomap node-qs node-read node-read-package-json node-request node-retry
               node-rimraf node-semver node-sha node-slide node-spdx-correct
               node-spdx-expression-parse node-spdx-license-ids node-tar node-tunnel-agent
               node-underscore node-validate-npm-package-license node-which node-wrappy node-yallist
               nodejs-doc python-pkg-resources
               Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
               0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. 
              

              then again:

              npm rebuild
              sudo npm rebuild
              

              both with same errors.
              Maybe I am wrong but i think with sudo I am same as root.
              Or not?
              Do I have to login as root?
              [update]
              as root the first errors are gore (lock) but rest is the same.
              Then I tryed

              root@ioBroker-Pi:/opt/iobroker#  apt-get update
              Holen:1 http://archive.raspberrypi.org/debian stretch InRelease [25,3 kB]
              Holen:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15,0 kB]
              OK:3 https://deb.nodesource.com/node_8.x stretch InRelease
              Holen:4 http://archive.raspberrypi.org/debian stretch/main armhf Packages [199 kB]
              Holen:5 http://archive.raspberrypi.org/debian stretch/ui armhf Packages [39,2 kB]
              Es wurden 279 kB in 1 s geholt (198 kB/s).
              Paketlisten werden gelesen... Fertig
              root@ioBroker-Pi:/opt/iobroker#  apt-get upgrade -y
              Paketlisten werden gelesen... Fertig
              Abhängigkeitsbaum wird aufgebaut.
              Statusinformationen werden eingelesen.... Fertig
              Paketaktualisierung (Upgrade) wird berechnet... Fertig
              Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
                gyp javascript-common libc-ares2 libhttp-parser2.8 libjs-inherits libjs-jquery libjs-node-uuid libjs-underscore
                libssl-dev libssl-doc libuv1 libuv1-dev node-abbrev node-ansi node-ansi-color-table node-archy node-async
                node-balanced-match node-block-stream node-brace-expansion node-builtin-modules node-combined-stream node-concat-map
                node-cookie-jar node-delayed-stream node-forever-agent node-form-data node-fs.realpath node-fstream
                node-fstream-ignore node-github-url-from-git node-glob node-graceful-fs node-gyp node-hosted-git-info node-inflight
                node-inherits node-ini node-is-builtin-module node-isexe node-json-stringify-safe node-lockfile node-lru-cache
                node-mime node-minimatch node-mkdirp node-mute-stream node-node-uuid node-nopt node-normalize-package-data node-npmlog
                node-once node-osenv node-path-is-absolute node-pseudomap node-qs node-read node-read-package-json node-request
                node-retry node-rimraf node-semver node-sha node-slide node-spdx-correct node-spdx-expression-parse
                node-spdx-license-ids node-tar node-tunnel-agent node-underscore node-validate-npm-package-license node-which
                node-wrappy node-yallist nodejs-doc python-pkg-resources
              Verwenden Sie »apt autoremove«, um sie zu entfernen.
              0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
              

              But iobroker is still dead

              1 Antwort Letzte Antwort
              0
              • apollon77A Offline
                apollon77A Offline
                apollon77
                schrieb am zuletzt editiert von
                #22

                But you have seen that the path in the error Waage when starting iobroker is wrong?! /var/www/… inhale no idea where this path comes from.

                The rebuild log seems ok because authenticate-Pam is an optional package.

                Changing rights in system stuff like Dpkg is no good idea!!

                Gesendet vom Handy ...

                Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                1 Antwort Letzte Antwort
                0
                • AlCalzoneA Offline
                  AlCalzoneA Offline
                  AlCalzone
                  Developer
                  schrieb am zuletzt editiert von
                  #23

                  I think you guys can talk in german :D

                  Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                  1 Antwort Letzte Antwort
                  0
                  • A Offline
                    A Offline
                    Arnulf
                    schrieb am zuletzt editiert von
                    #24

                    it is because the thread started in english.

                    :lol:

                    1 Antwort Letzte Antwort
                    0
                    • A Offline
                      A Offline
                      Arnulf
                      schrieb am zuletzt editiert von
                      #25

                      @apollon77:

                      Changing rights in system stuff like Dpkg is no good idea!! `
                      sure. it was only for testing

                      maybe it is a good idea to reinstall (only) iobroker.

                      But are these instructions correct?

                      cd /opt/iobroker
                      sudo chmod 777 * -R
                      sudo npm install iobroker.js-controller --production
                      
                      1 Antwort Letzte Antwort
                      0
                      • AlCalzoneA Offline
                        AlCalzoneA Offline
                        AlCalzone
                        Developer
                        schrieb am zuletzt editiert von
                        #26

                        @Arnulf:

                        But are these instructions correct? `
                        They are pretty outdated. See viewtopic.php?f=8&t=19111 and viewtopic.php?f=8&t=19209

                        Since your installation is pretty fucked, I think one of the cleanest ways to get an almost fresh installation is deleting the old node_modules

                        cd /opt/iobroker
                        sudo rm -rf node_modules
                        
                        

                        and performing a clean install (while keeping iobroker-data)

                        curl -sL https://raw.githubusercontent.com/ioBroker/ioBroker/stable-installer/installer.sh | bash -
                        

                        ioBroker should then detect which adapters are missing and install them again.

                        Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                        1 Antwort Letzte Antwort
                        0
                        • A Offline
                          A Offline
                          Arnulf
                          schrieb am zuletzt editiert von
                          #27

                          hmmm

                          pi@ioBroker-Pi:/opt/iobroker $ cd /opt/iobroker
                          pi@ioBroker-Pi:/opt/iobroker $ sudo rm -rf node_modules
                          pi@ioBroker-Pi:/opt/iobroker $ curl -sL https://raw.githubusercontent.com/ioBroker/ioBroker/stable-installer/installer.sh | bash -
                          
                          ==========================================================================
                          
                              Welcome to the ioBroker installer!
                              You might need to enter your password a couple of times.
                          
                          ==========================================================================
                          
                          ==========================================================================
                              Creating ioBroker directory (1/4)
                          ==========================================================================
                          
                          ==========================================================================
                              Downloading installation files (2/4)
                          ==========================================================================
                          
                          npm ERR! code ENOSELF
                          npm ERR! Refusing to install package with name "iobroker" under a package
                          npm ERR! also called "iobroker". Did you name your project the same
                          npm ERR! as the dependency you're installing?
                          npm ERR!
                          npm ERR! For more information, see:
                          npm ERR!     <https: docs.npmjs.com/cli/install#limitations-of-npms-install-algorithm="">npm ERR! A complete log of this run can be found in:
                          npm ERR!     /home/pi/.npm/_logs/2018-12-06T15_47_56_194Z-debug.log
                          
                          ==========================================================================
                              Installing ioBroker (3/4)
                          ==========================================================================
                          
                          npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
                          npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
                          npm WARN deprecated nodemailer@1.11.0: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/
                          npm WARN deprecated mailparser@0.6.2: Mailparser versions older than v2.3.0 are deprecated
                          npm WARN deprecated mailcomposer@2.1.0: This project is unmaintained
                          npm WARN deprecated mimelib@0.3.1: This project is unmaintained
                          npm WARN deprecated buildmail@2.0.0: This project is unmaintained
                          npm ERR! code 128
                          npm ERR! Command failed: /usr/bin/git submodule update -q --init --recursive
                          npm ERR! fatal: Could not change back to '/root/.npm/_cacache/tmp/git-clone-5787434c': Keine Berechtigung
                          npm ERR!
                          
                          npm ERR! A complete log of this run can be found in:
                          npm ERR!     /root/.npm/_logs/2018-12-06T15_48_43_483Z-debug.log
                          
                          ==========================================================================
                              Finalizing installation (4/4)
                          ==========================================================================
                          
                          ==========================================================================
                          
                              ioBroker was installed successfully
                              Open http://localhost:8081 in a browser and start configuring!
                          
                          ==========================================================================</https:> 
                          

                          and after reboot:

                          pi@ioBroker-Pi:~ $ iobroker start
                          module.js:550
                              throw err;
                              ^
                          
                          Error: Cannot find module '/usr/local/www/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                              at Function.Module._resolveFilename (module.js:548:15)
                              at Function.Module._load (module.js:475:25)
                              at Function.Module.runMain (module.js:694:10)
                              at startup (bootstrap_node.js:204:16)
                              at bootstrap_node.js:625:3
                          
                          

                          I don't know why there is a call to the webserver

                          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
                          FAQ Cloud / IOT
                          HowTo: Node.js-Update
                          HowTo: Backup/Restore
                          Downloads
                          BLOG

                          639

                          Online

                          32.5k

                          Benutzer

                          81.7k

                          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