Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Visualisierung
    4. JS installation Error 243 ELIFECYCLE

    NEWS

    • Monatsrückblick – September 2025

    • Neues Video "KI im Smart Home" - ioBroker plus n8n

    • Neues Video über Aliase, virtuelle Geräte und Kategorien

    JS installation Error 243 ELIFECYCLE

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

      Hallo,

      bin noch relativ neu was ioBroker angeht aber habe es einfach mal auf meinen Raspberry gepackt und wollte so mit Alexa ein paar Sachen steuern. Nun habe ich versucht JS zu installieren und leider diesen Fehler bekommen:

      root@Nas-Server:~# npm install iobroker.javascript --production --save --prefix "/opt/iobroker"
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)

> iobroker.javascript@4.0.1 postinstall /opt/iobroker/node_modules/iobroker.javascript
> node ./install/installTypings.js

installing NodeJS typings...
npm ERR! path /root/.npm/_logs
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall scandir
npm ERR! Error: EACCES: permission denied, scandir '/root/.npm/_logs'
npm ERR!  { Error: EACCES: permission denied, scandir '/root/.npm/_logs'
npm ERR!   stack: 'Error: EACCES: permission denied, scandir \'/root/.npm/_logs\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'scandir',
npm ERR!   path: '/root/.npm/_logs' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).
glob error { Error: EACCES: permission denied, scandir '/root/.npm/_logs'
  stack: 'Error: EACCES: permission denied, scandir \'/root/.npm/_logs\'',
  errno: -13,
  code: 'EACCES',
  syscall: 'scandir',
  path: '/root/.npm/_logs' }
npm ERR! path /root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall open
npm ERR! Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'
npm ERR!  { Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'
npm ERR!   cause:
npm ERR!    { Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'
npm ERR!      errno: -13,
npm ERR!      code: 'EACCES',
npm ERR!      syscall: 'open',
npm ERR!      path: '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be' },
npm ERR!   isOperational: true,
npm ERR!   stack: 'Error: EACCES: permission denied, open \'/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be\'',
npm ERR!   errno: -13,
npm ERR!   code: 'EACCES',
npm ERR!   syscall: 'open',
npm ERR!   path: '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It is likely you do not have the permissions to access this file as the current user
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).
npm ERR! code ELIFECYCLE
npm ERR! errno 243
npm ERR! iobroker.javascript@4.0.1 postinstall: `node ./install/installTypings.js`
npm ERR! Exit status 243
npm ERR!
npm ERR! Failed at the iobroker.javascript@4.0.1 postinstall 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/2018-12-03T17_39_56_958Z-debug.log

      So wie ich das sehe sagt er was von Rechten. Allerdings läuft ioBroker standardmäßig doch als root und auch wenn ich über die Konsole über root versuche zu Installieren bekomme ich den Error. Vielleicht habt ihr ja noch eine Idee. Die .log habe ich angehangen.
      12226_2018-12-03t17_39_56_958z-debug.log

      1 Reply Last reply Reply Quote 0
      • Homer.J.
        Homer.J. last edited by

        Versuch es mal hiermit.

        ! cd /opt/iobroker
        ! npm install iobroker.javascript@4.0.1
        ! iobroker update javascript

        1 Reply Last reply Reply Quote 0
        • F
          Flumi last edited by

          Vielen Dank hat geholfen funktioniert jetzt!

          1 Reply Last reply Reply Quote 0
          • M
            Moditril last edited by

            Hallo zusammen,

            habe einen quasi ähnlichen Fehler und die hier dargestellte Lösung hat bei mir leider nicht funktioniert.

            Bei Eingabe von

             npm install iobroker.javascript@4.0.2

            erscheint der ganz unten dargestellte Code im Terminal. Habe es auch schon mit

            npm install iobroker.javascript@4.0.1
````und````
 npm install iobroker.javascript
````sowie über das WEBui von ioBroker probiert.

Weiß jemand Rat?

            root@HomePi:/opt/iobroker# npm install iobroker.javascript@4.0.2
            installing NodeJS typings...
            npm ERR! path /root/.npm/_logs
            npm ERR! code EACCES
            npm ERR! errno -13
            npm ERR! syscall scandir
            npm ERR! Error: EACCES: permission denied, scandir '/root/.npm/_logs'
            npm ERR! { Error: EACCES: permission denied, scandir '/root/.npm/_logs'
            npm ERR! stack: 'Error: EACCES: permission denied, scandir '/root/.npm/_logs'',
            npm ERR! errno: -13,
            npm ERR! code: 'EACCES',
            npm ERR! syscall: 'scandir',
            npm ERR! path: '/root/.npm/_logs' }
            npm ERR!
            npm ERR! The operation was rejected by your operating system.
            npm ERR! It is likely you do not have the permissions to access this file as the current user
            npm ERR!
            npm ERR! If you believe this might be a permissions issue, please double-check the
            npm ERR! permissions of the file and its containing directories, or try running
            npm ERR! the command again as root/Administrator (though this is not recommended).
            glob error { Error: EACCES: permission denied, scandir '/root/.npm/_logs'
            stack: 'Error: EACCES: permission denied, scandir '/root/.npm/_logs'',
            errno: -13,
            code: 'EACCES',
            syscall: 'scandir',
            path: '/root/.npm/_logs' }
            npm ERR! path /root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be
            npm ERR! code EACCES
            npm ERR! errno -13
            npm ERR! syscall open
            npm ERR! Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'
            npm ERR! { Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'
            npm ERR! cause:
            npm ERR! { Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'
            npm ERR! errno: -13,
            npm ERR! code: 'EACCES',
            npm ERR! syscall: 'open',
            npm ERR! path: '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be' },
            npm ERR! isOperational: true,
            npm ERR! stack: 'Error: EACCES: permission denied, open '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be'',
            npm ERR! errno: -13,
            npm ERR! code: 'EACCES',
            npm ERR! syscall: 'open',
            npm ERR! path: '/root/.npm/_cacache/index-v5/fc/ee/fc3e1dd6706bd557d2840d92ff10cdd6928b92fb8c46d2195dfbd8d4b2be' }
            npm ERR!
            npm ERR! The operation was rejected by your operating system.
            npm ERR! It is likely you do not have the permissions to access this file as the current user
            npm ERR!
            npm ERR! If you believe this might be a permissions issue, please double-check the
            npm ERR! permissions of the file and its containing directories, or try running
            npm ERR! the command again as root/Administrator (though this is not recommended).
            npm ERR! code ELIFECYCLE
            npm ERR! errno 243
            npm ERR! iobroker.javascript@4.0.2 postinstall: node ./install/installTypings.js
            npm ERR! Exit status 243
            npm ERR!
            npm ERR! Failed at the iobroker.javascript@4.0.2 postinstall script.
            npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

            1 Reply Last reply Reply Quote 0
            • M
              Moditril last edited by

              Hab in der Zwischenzeit eine neue frische Installation von ioBroker nach der neuen Anleitung auf einer neuen SD durchgeführt. Jetzt funktionierte es ohne Probleme.

              Keine Ahnung wo das Problem lag, aber läuft jetzt.

              1 Reply Last reply Reply Quote 0
              • AlCalzone
                AlCalzone Developer last edited by

                @Moditril:

                Keine Ahnung wo das Problem lag, aber läuft jetzt. `
                ==> viewtopic.php?f=17&t=19209

                1 Reply Last reply Reply Quote 0
                • M
                  Moditril last edited by

                  Ach, super. Besten Dank für den Link. Wieder was gelernt…

                  Gesendet von meinem Pixel 2 mit Tapatalk

                  1 Reply Last reply Reply Quote 0
                  • AlCalzone
                    AlCalzone Developer last edited by

                    Bzw. in deinem Fall schien es daran zu liegen, dass du als Root angemeldet warst. Dann wird bei einigen Adaptern die –unsafe-perm Option nötig. Beim JavaScript-Adapter kam es ohne die Option einem Problem mit einem Paket-Skript - sollte in der nächsten Version gefixt sein.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    Support us

                    ioBroker
                    Community Adapters
                    Donate

                    881
                    Online

                    32.2k
                    Users

                    80.9k
                    Topics

                    1.3m
                    Posts

                    4
                    8
                    1933
                    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