Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [GELÖST] HILFE - Nach update js-controller nicht installierbar

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    [GELÖST] HILFE - Nach update js-controller nicht installierbar

    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Georgius last edited by

      Das muß jetzt noch nichts heißen. Als Pi hast Du vermutlich nur Standardrechte.

      Probiere mal ob ein Sudo ls -l was hilft. Sonst wie oben geschrieben

      sudo iobroker update
      sudo iobroker upgrade self
      sudo iobroker start
      
      

      noch einmal durchführen.

      Sicherheitshalber vorher nochmals````
      sudo systemctl stop iobroker

      1 Reply Last reply Reply Quote 0
      • H
        Hans last edited by

        leider kein Erfolg Georgius.

        Hat jemand ansonsten noch eine Idee?

        Ansonsten könnte ich auch den iobroker neu aufsetzten und das backup einspielen.

        Könnte mir jemand sagen, wie das dann funktioniert?

        Am liebsten würde ich natürlich diese Installation retten :?

        1 Reply Last reply Reply Quote 0
        • G
          Georgius last edited by

          Anleitung von Github

          https://github.com/simatec/ioBroker.bac … ackitup.md

          1 Reply Last reply Reply Quote 0
          • H
            Hans last edited by

            Das Backup einspielen ansich ist nicht das Problem. Aber wie installiere ich iobroker auf dem Pi?

            Ich hatte damals ein "All-In-One" Paket installiert.

            Aber es muss doch trotzdem eine Möglichkeit geben, irgendwie mein Problem in den Griff zu bekommen?

            1 Reply Last reply Reply Quote 0
            • H
              Hans last edited by

              Hilft das evtl. jemanden weiter? :idea:

              ! ````
              pi@Raspberry:/opt/iobroker $ systemctl status iobroker.service
              ● iobroker.service - LSB: starts ioBroker
              Loaded: loaded (/etc/init.d/iobroker.sh; generated; vendor preset: enabled)
              Active: failed (Result: exit-code) since Mon 2018-12-31 16:53:58 CET; 47s ago
              Docs: man:systemd-sysv-generator(8)
              Process: 1318 ExecStart=/etc/init.d/iobroker.sh start (code=exited, status=1/FAILURE)
              CPU: 296ms
              ! Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at Function.Module._resolveFilename (module
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at Function.Module._load (module.js:474:25)
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at Function.Module.runMain (module.js:693:1
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at startup (bootstrap_node.js:188:16)
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at bootstrap_node.js:609:3
              Dez 31 16:53:58 Raspberry sudo[1319]: pam_unix(sudo:session): session closed for user root
              Dez 31 16:53:58 Raspberry systemd[1]: iobroker.service: Control process exited, code=exited
              Dez 31 16:53:58 Raspberry systemd[1]: Failed to start LSB: starts ioBroker.
              Dez 31 16:53:58 Raspberry systemd[1]: iobroker.service: Unit entered failed state.
              Dez 31 16:53:58 Raspberry systemd[1]: iobroker.service: Failed with result 'exit-code'.
              lines 1-17/17 (END)
              ! pi@Raspberry:/opt/iobroker $ journalctl -xe
              --
              -- Unit iobroker.service has begun starting up.
              Dez 31 16:53:57 Raspberry sudo[1319]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/
              Dez 31 16:53:57 Raspberry sudo[1319]: pam_unix(sudo:session): session opened for user root b
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: Starting ioBrokermodule.js:549
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: throw err;
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: ^
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: Error: Cannot find module '/opt/iobroker/node_m
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at Function.Module._resolveFilename (module
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at Function.Module._load (module.js:474:25)
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at Function.Module.runMain (module.js:693:1
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at startup (bootstrap_node.js:188:16)
              Dez 31 16:53:58 Raspberry iobroker.sh[1318]: at bootstrap_node.js:609:3
              Dez 31 16:53:58 Raspberry sudo[1319]: pam_unix(sudo:session): session closed for user root
              Dez 31 16:53:58 Raspberry sudo[1312]: pam_unix(sudo:session): session closed for user root
              Dez 31 16:53:58 Raspberry systemd[1]: iobroker.service: Control process exited, code=exited
              Dez 31 16:53:58 Raspberry systemd[1]: Failed to start LSB: starts ioBroker.
              -- Subject: Unit iobroker.service has failed
              -- Defined-By: systemd
              -- Support: https://www.debian.org/support
              --
              -- Unit iobroker.service has failed.
              --
              -- The result is failed.
              Dez 31 16:53:58 Raspberry systemd[1]: iobroker.service: Unit entered failed state.
              Dez 31 16:53:58 Raspberry systemd[1]: iobroker.service: Failed with result 'exit-code'.
              lines 1492-1517/1517 (END)

              
              Edit by eric2905, Logs & Co. bitte immer in Code- und ggf. Spoiler-Tags setzen
              1 Reply Last reply Reply Quote 0
              • G
                Georgius last edited by

                Ich würde es neu machen. Gibt eh eine Anleitung im Forum.

                Kostet mit einem Backup weniger Zeit als die Fehlersuche.

                Hatte mit einem fertigen Image auch nur Probleme. Wenn alles funktioniert ist es super, aber wehe es spinnt.

                1 Reply Last reply Reply Quote 0
                • H
                  Hans last edited by

                  Danke Dir!

                  Hast Du evtl den link zur Anleitung?

                  Guten Rutsch!!!

                  1 Reply Last reply Reply Quote 0
                  • G
                    Georgius last edited by

                    Ist in jedem Forum als 4. Thread angepinnt. viewtopic.php?f=8&t=19111

                    Alte Weisheit: "Willst Du was verstecken pinne es an" 😉

                    1 Reply Last reply Reply Quote 0
                    • H
                      Hans last edited by

                      Hallo zusammen und ein Frohes neues Jahr !!!

                      Ich konnte den js-controller mit diesem Befehl wieder installieren und iobroker wieder zum laufen bringen 😄

                      sudo npm install iobroker.js-controller –unsafe-perm

                      Jetzt habe ich nur noch das Problem, dass ja mein eigentliches Ziel war, iobroker auf eine neuere Version zu updaten.

                      Wo alles wieder funktioniert, habe ich leider immer noch die alter Ansicht, obwohl das update anscheinend funktioniert hat s.u.

                      Kann man irgendwo die Ansicht umstellen?

                      Nachher:

                      pi@Raspberry:/opt/iobroker $ node -v

                      v8.15.0

                      pi@Raspberry:/opt/iobroker $ npm -v

                      6.4.1

                      Vorher:

                      pi@Raspberry:/opt/iobroker $ node -v

                      v8.11.1

                      pi@Raspberry:/opt/iobroker $ npm -v

                      5.8.0

                      10144_bildschirmfoto_2019-01-01_um_11.56.16.png

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

                        @Hans:

                        habe ich leider immer noch die alter Ansicht `
                        Die Ansicht wird durch den Admin-Adapter bestimmt. Deiner hat noch Version 2.0.9.

                        1 Reply Last reply Reply Quote 0
                        • H
                          Hans last edited by

                          Top, Danke! 😄

                          1 Reply Last reply Reply Quote 0
                          • G
                            Glarios last edited by

                            Ich habe genau des gleiche Problem nach einem Update von Node.js. Bei mir läuft leider der unsafe Befehl nicht:

                            
                            pi@ioBroker-RasPi:/opt/iobroker $ sudo npm install iobroker.js-controller –unsafe-perm
                            npm ERR! code EINVALIDTAGNAME
                            npm ERR! Invalid tag name "–unsafe-perm": Tags may not have any characters that encodeURIComponent encodes.
                            
                            npm ERR! A complete log of this run can be found in:
                            npm ERR!     /root/.npm/_logs/2019-09-01T14_48_36_805Z-debug.log
                            
                            

                            Hat jemand eine Idee?

                            1 Reply Last reply Reply Quote 0
                            • G
                              Glarios last edited by

                              Ich habe jetzt mal einfach nur -unsafe ausprobiert. Ergebnis aber wie vorher ohne diese Zusatz:

                              pi@ioBroker-RasPi:/opt/iobroker $ sudo npm install iobroker.js-controller unsafe
                              
                              > iobroker.js-controller@1.5.14 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                              > node lib/preinstallCheck.js
                              
                              NPM version: 6.9.0
                              npm version >= 5: disabling package-lock
                              
                              > serialport@4.0.7 install /opt/iobroker/node_modules/serialport
                              > node-pre-gyp install --fallback-to-build
                              
                              node-pre-gyp info it worked if it ends with ok
                              node-pre-gyp verb cli [ '/usr/bin/node',
                              node-pre-gyp verb cli   '/opt/iobroker/node_modules/serialport/node_modules/.bin/node-pre-gyp',
                              node-pre-gyp verb cli   'install',
                              node-pre-gyp verb cli   '--fallback-to-build' ]
                              node-pre-gyp info using node-pre-gyp@0.6.32
                              node-pre-gyp info using node@10.16.3 | linux | arm
                              node-pre-gyp verb command install []
                              node-pre-gyp info check checked for "/opt/iobroker/node_modules/serialport/build/Release/serialport.node" (not found)
                              node-pre-gyp http GET https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-                                                                      v4.0.7-node-v64-linux-arm.tar.gz
                              node-pre-gyp ERR! Tried to download(undefined): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/                                                                      download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
                              node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.16.3 (node-v64 ABI) (falling back to so                                                                      urce compile with node-gyp)
                              node-pre-gyp http EACCES: permission denied, mkdir '/opt/iobroker/node_modules/serialport/build'
                              node-pre-gyp verb command build [ 'rebuild' ]
                              node-pre-gyp http 404 https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-                                                                      v4.0.7-node-v64-linux-arm.tar.gz
                              node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/downlo                                                                      ad/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
                              node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.16.3 (node-v64 ABI) (falling back to so                                                                      urce compile with node-gyp)
                              node-pre-gyp http 404 status code downloading tarball https://github.com/EmergingTechnologyAdvisors/node-serialport/rel                                                                      eases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
                              node-pre-gyp verb command build [ 'rebuild' ]
                              node-pre-gyp ERR! Tried to download(undefined): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/                                                                      download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
                              node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.16.3 (node-v64 ABI) (falling back to so                                                                      urce compile with node-gyp)
                              node-pre-gyp http Connection closed while downloading tarball file
                              node-pre-gyp verb command build [ 'rebuild' ]
                              gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/10.16.3"
                              gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
                              gyp ERR! configure error
                              gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/serialport/build'
                              gyp ERR! System Linux 4.19.66-v7+
                              gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallb                                                                      ack-to-build" "--module=/opt/iobroker/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport"                                                                       "--module_path=/opt/iobroker/node_modules/serialport/build/Release"
                              gyp ERR! cwd /opt/iobroker/node_modules/serialport
                              gyp ERR! node -v v10.16.3
                              gyp ERR! node-gyp -v v3.8.0
                              gyp ERR! not ok
                              node-pre-gyp ERR! build error
                              node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/nod                                                                      e-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/serialport/build/Release/serialport.node --m                                                                      odule_name=serialport --module_path=/opt/iobroker/node_modules/serialport/build/Release' (1)
                              node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/serialport/node_modules/node-pre-gy                                                                      p/lib/util/compile.js:83:29)
                              node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                              node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
                              node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
                              node-pre-gyp ERR! System Linux 4.19.66-v7+
                              node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/serialport/node_modules/.bin/node-pre-gyp" "insta                                                                      ll" "--fallback-to-build"
                              node-pre-gyp ERR! cwd /opt/iobroker/node_modules/serialport
                              node-pre-gyp ERR! node -v v10.16.3
                              node-pre-gyp ERR! node-pre-gyp -v v0.6.32
                              node-pre-gyp ERR! not ok
                              Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-t                                                                      o-build --module=/opt/iobroker/node_modules/serialport/build/Release/serialport.node --module_name=serialport --module_                                                                      path=/opt/iobroker/node_modules/serialport/build/Release' (1)
                              
                              > iobroker.js-controller@1.5.14 install /opt/iobroker/node_modules/iobroker.js-controller
                              > node iobroker.js setup first
                              
                              gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/10.16.3"
                              gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
                              gyp ERR! configure error
                              gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/serialport/build'
                              gyp ERR! System Linux 4.19.66-v7+
                              gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallb                                                                      ack-to-build" "--module=/opt/iobroker/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport"                                                                       "--module_path=/opt/iobroker/node_modules/serialport/build/Release"
                              gyp ERR! cwd /opt/iobroker/node_modules/serialport
                              gyp ERR! node -v v10.16.3
                              gyp ERR! node-gyp -v v3.8.0
                              gyp ERR! not ok
                              gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/10.16.3"
                              gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
                              gyp ERR! configure error
                              gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/serialport/build'
                              gyp ERR! System Linux 4.19.66-v7+
                              gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallb                                                                      ack-to-build" "--module=/opt/iobroker/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport"                                                                       "--module_path=/opt/iobroker/node_modules/serialport/build/Release"
                              gyp ERR! cwd /opt/iobroker/node_modules/serialport
                              gyp ERR! node -v v10.16.3
                              gyp ERR! node-gyp -v v3.8.0
                              gyp ERR! not ok
                              Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-cont                                                                      roller/lib/setup/../../_service_iobroker.bat'
                              Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-cont                                                                      roller/lib/setup/../../iobroker.bat'
                              fs.js:114
                                  throw err;
                                  ^
                              
                              Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../tmp'
                                  at Object.mkdirSync (fs.js:757:3)
                                  at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:189:58)
                                  at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:653:27
                                  at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:691:15)
                                  at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3193:5)
                                  at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:38)
                                  at Module._compile (internal/modules/cjs/loader.js:778:30)
                                  at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
                                  at Module.load (internal/modules/cjs/loader.js:653:32)
                                  at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
                              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: serialport@4.0.7 (node_modules/serialport):
                              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: serialport@4.0.7 install: `node-pre-gyp install --fallback-to-build`
                              npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                              
                              npm ERR! code ELIFECYCLE
                              npm ERR! errno 1
                              npm ERR! iobroker.js-controller@1.5.14 install: `node iobroker.js setup first`
                              npm ERR! Exit status 1
                              npm ERR!
                              npm ERR! Failed at the iobroker.js-controller@1.5.14 install script.
                              npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
                              
                              npm ERR! A complete log of this run can be found in:
                              npm ERR!     /root/.npm/_logs/2019-09-01T14_57_46_659Z-debug.log
                              
                              

                              Ist da noch etwas zu retten, oder muss ich alles neu aufsetzen? 😞

                              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

                              409
                              Online

                              31.9k
                              Users

                              80.2k
                              Topics

                              1.3m
                              Posts

                              5
                              22
                              4779
                              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