Skip to content
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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

  • Default (No Skin)
  • No Skin
Collapse
Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 2.0 ab sofort im Latest Repo

NEWS

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

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.8k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.0k

js-controller 2.0 ab sofort im Latest Repo

js-controller 2.0 ab sofort im Latest Repo

Scheduled Pinned Locked Moved ioBroker Allgemein
js-controller
1.1k Posts 89 Posters 352.5k Views 64 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • DiginixD Diginix

    @apollon77
    Ich habe noch einen PI3 der früher für den ioBroker geknechtet wurde.
    Also auch machbar. Der muss ja sicher nur für den Zeitraum der Tests laufen.

    apollon77A Online
    apollon77A Online
    apollon77
    wrote on last edited by
    #1021

    @Diginix Zum Beispiel :-))

    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 Reply Last reply
    0
    • C Offline
      C Offline
      ChrisXY
      wrote on last edited by ChrisXY
      #1022

      jemand erfahrungen mit dem firetv adapter ? Der scheint noch nicht zu laufen?

      host.iobroker	2019-12-14 20:50:49.958	error	instance system.adapter.firetv.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at startup (internal/bootstrap/node.js:283:19)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:653:32)
      host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:778:30)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.firetv/firetv.js:6:14)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:25:18)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:692:17)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:562:25)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: Error: Cannot find module './node_modules/adbkit/lib/adb/client'
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: ^
      host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: throw err;
      host.iobroker	2019-12-14 20:50:49.956	error	Caught by controller[0]: internal/modules/cjs/loader.js:638
      
      apollon77A 1 Reply Last reply
      0
      • C ChrisXY

        jemand erfahrungen mit dem firetv adapter ? Der scheint noch nicht zu laufen?

        host.iobroker	2019-12-14 20:50:49.958	error	instance system.adapter.firetv.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at startup (internal/bootstrap/node.js:283:19)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:585:3)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:653:32)
        host.iobroker	2019-12-14 20:50:49.958	error	Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:778:30)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.firetv/firetv.js:6:14)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at require (internal/modules/cjs/helpers.js:25:18)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:692:17)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:562:25)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: Error: Cannot find module './node_modules/adbkit/lib/adb/client'
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: ^
        host.iobroker	2019-12-14 20:50:49.957	error	Caught by controller[0]: throw err;
        host.iobroker	2019-12-14 20:50:49.956	error	Caught by controller[0]: internal/modules/cjs/loader.js:638
        
        apollon77A Online
        apollon77A Online
        apollon77
        wrote on last edited by
        #1023

        @ChrisXY das scheint weniger mit Controller 2 zu tun zu haben. Installiert den Adapter mal neu. Bzw GitHub issue öffnen.

        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 Reply Last reply
        0
        • F Offline
          F Offline
          frankyboy73
          wrote on last edited by Negalein
          #1024

          Hi, bei mir klappt es leider nicht mit dem Update. Nach dem Update Versuch geht leider gar nichts mehr und ich muss neu aufsetzten.
          Ich habe nen Raspberry pi 4 und Raspian Buster drauf, neuste Version.
          Folgendes habe ich als Ausgabe.

          Update js-controller from @1.2.3 to @2.1.1
          npm install iobroker.js-controller@2.1.1 --unsafe-perm  --production --prefix "/opt/iobroker" (System call)
          npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
          In file included from ../src/unix_dgram.cc:5:
          ../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
          ../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
               , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                                        ^
          In file included from ../../nan/nan.h:54,
                           from ../src/unix_dgram.cc:5:
          ../src/unix_dgram.cc: At global scope:
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/node.h:573:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                 (node::addon_register_func) (regfunc),                          \
                                                     ^
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/node.h:607:3: note: in expansion of macro ‘NODE_MODULE_X’
             NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
             ^~~~~~~~~~~~~
          ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
           NODE_MODULE(unix_dgram, Initialize)
           ^~~~~~~~~~~
          In file included from /home/iobroker/.cache/node-gyp/10.18.0/include/node/node.h:63,
                           from ../../nan/nan.h:54,
                           from ../src/unix_dgram.cc:5:
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/node_object_wrap.h:84:78:   required from here
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
                          reinterpret_cast<Callback>(callback), type);
                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
          ../../nan/nan_object_wrap.h:65:61:   required from here
          /home/iobroker/.cache/node-gyp/10.18.0/include/node/v8.h:9502:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
          (node:916) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
              at handleError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:190:15)
              at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:304:14)
          (node:916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
          (node:916) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
          (node:916) UnhandledPromiseRejectionWarning: ParserError: Protocol error, got "H" as reply type byte. Please report this.
              at handleError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:190:15)
              at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:304:14)
          (node:916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
          
          
          ╭─────────────────────────────────────────────────────────╮
          │                                                         │
          │ Manual installation of ioBroker is no longer supported  │
          │ on Linux, OSX and FreeBSD!                              │
          │ Please refer to the documentation on how to install it! │
          │ https://github.com/ioBroker/ioBroker/wiki/Installation  │
          │                                                         │
          ╰─────────────────────────────────────────────────────────╯
          
          
          npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
          npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
          
          npm ERR! code ELIFECYCLE
          npm ERR! errno 100
          npm ERR! iobroker@2.0.3 postinstall: `node lib/install.js`
          npm ERR! Exit status 100
          npm ERR!
          npm ERR! Failed at the iobroker@2.0.3 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!     /home/iobroker/.npm/_logs/2020-01-14T16_45_21_540Z-debug.log
          host.raspberrypi Cannot install iobroker.js-controller@2.1.1: 100
          

          Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
          Hier gehts zur Hilfe.

          Schöne Grüße Frank

          1 Reply Last reply
          0
          • F Offline
            F Offline
            frankyboy73
            wrote on last edited by
            #1025

            Hi, ich habe das Problem gefunden. Ich hatte für meinen neuen PI 4 ein Backup vom Pi 3 genommen. Bei meiner Backup Variante speicher ich den Iobroker Data und den Node Modules Ordner und kopiere die für das Wiederherstellen wieder in den Iobroker Ordner. Damit habe ich dann wohl auf dem neuen System ein bisschen was vermurkst. Ich habe jetzt über mein System noch mal die Iobroker Installation drübergebügelt und es läuft alles inklusive js-controller Version 2.1.1

            Schöne Grüße Frank

            apollon77A 1 Reply Last reply
            0
            • F frankyboy73

              Hi, ich habe das Problem gefunden. Ich hatte für meinen neuen PI 4 ein Backup vom Pi 3 genommen. Bei meiner Backup Variante speicher ich den Iobroker Data und den Node Modules Ordner und kopiere die für das Wiederherstellen wieder in den Iobroker Ordner. Damit habe ich dann wohl auf dem neuen System ein bisschen was vermurkst. Ich habe jetzt über mein System noch mal die Iobroker Installation drübergebügelt und es läuft alles inklusive js-controller Version 2.1.1

              apollon77A Online
              apollon77A Online
              apollon77
              wrote on last edited by
              #1026

              @frankyboy73 node_modules zu kopieren ist eine extrem "blöde Idee" weil hier viel mit symbolischen Links und solchen Dingen gearbeitet wird die durch ein "Normales" copy kaputt gehen ... Aber super das Du es gelöst hast.

              PS: WOW einen js.controller 1.2.3 hat ich schon ewig nimmer gesehn 😉

              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 Reply Last reply
              0
              • F Offline
                F Offline
                frankyboy73
                wrote on last edited by
                #1027

                OK, da werde ich in Zukunft wohl doch nur noch die normale Backup Methode nutzen. Der Vorteil war, das man ruck zuck alles wieder am laufen hatte.

                Lief bis jetzt alles super mit dem js-controller 1.2.3. Ich wollte nur auf größer 2 weil sonst der ALexa2 Adapter in der neuen Version nicht mehr geht.

                Danke für deine Antwort/Info

                Schöne Grüße Frank

                1 Reply Last reply
                0
                • G Offline
                  G Offline
                  gentlel
                  wrote on last edited by
                  #1028

                  Kann hier jemand helfen? Hier funktioniert nichts mehr 😞

                  iobroker:/opt/iobroker$ sudo npm install iobroker.js-controller@2.0.25
                  
                  > iobroker.js-controller@2.0.25 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                  > node lib/preinstallCheck.js
                  
                  NPM version: 6.13.0
                  
                  > iobroker.js-controller@2.0.25 install /opt/iobroker/node_modules/iobroker.js-controller
                  > node iobroker.js setup first
                  
                  Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
                  Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
                  Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iob.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:752:3)
                      at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:586:58)
                      at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:233:23)
                      at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2312:5)
                      at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:86)
                      at Module._compile (internal/modules/cjs/loader.js:701:30)
                      at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
                      at Module.load (internal/modules/cjs/loader.js:600:32)
                      at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
                      at Function.Module._load (internal/modules/cjs/loader.js:531:3)
                  npm WARN ELOOP: too many symbolic links encountered, stat '/opt/iobroker/node_modules/noble'
                  npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):
                  npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                  
                  npm ERR! code ELIFECYCLE
                  npm ERR! errno 1
                  npm ERR! iobroker.js-controller@2.0.25 install: `node iobroker.js setup first`
                  npm ERR! Exit status 1
                  npm ERR! 
                  npm ERR! Failed at the iobroker.js-controller@2.0.25 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/2020-01-17T20_16_38_051Z-debug.log
                  
                  sigi234S 1 Reply Last reply
                  0
                  • G gentlel

                    Kann hier jemand helfen? Hier funktioniert nichts mehr 😞

                    iobroker:/opt/iobroker$ sudo npm install iobroker.js-controller@2.0.25
                    
                    > iobroker.js-controller@2.0.25 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                    > node lib/preinstallCheck.js
                    
                    NPM version: 6.13.0
                    
                    > iobroker.js-controller@2.0.25 install /opt/iobroker/node_modules/iobroker.js-controller
                    > node iobroker.js setup first
                    
                    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
                    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
                    Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iob.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:752:3)
                        at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:586:58)
                        at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:233:23)
                        at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2312:5)
                        at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:86)
                        at Module._compile (internal/modules/cjs/loader.js:701:30)
                        at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
                        at Module.load (internal/modules/cjs/loader.js:600:32)
                        at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
                        at Function.Module._load (internal/modules/cjs/loader.js:531:3)
                    npm WARN ELOOP: too many symbolic links encountered, stat '/opt/iobroker/node_modules/noble'
                    npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@0.1.4 (node_modules/xpc-connection):
                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
                    
                    npm ERR! code ELIFECYCLE
                    npm ERR! errno 1
                    npm ERR! iobroker.js-controller@2.0.25 install: `node iobroker.js setup first`
                    npm ERR! Exit status 1
                    npm ERR! 
                    npm ERR! Failed at the iobroker.js-controller@2.0.25 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/2020-01-17T20_16_38_051Z-debug.log
                    
                    sigi234S Online
                    sigi234S Online
                    sigi234
                    Forum Testing Most Active
                    wrote on last edited by
                    #1029

                    @gentlel

                    Fixer mal laufen lassen?

                    Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                    Immer Daten sichern!

                    G 1 Reply Last reply
                    0
                    • sigi234S sigi234

                      @gentlel

                      Fixer mal laufen lassen?

                      G Offline
                      G Offline
                      gentlel
                      wrote on last edited by Negalein
                      #1030

                      @sigi234 Ja aber der zeigt das hier an obwohl iobroker in /opt/iobroker ist 6⃣

                      iobroker:~$ curl -sL https://iobroker.net/fix.sh | bash -
                      
                      library: loaded
                      Library version=2020-01-13
                      ioBroker is not installed in /opt/iobroker! Cannot fix anything...
                      

                      Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
                      Hier gehts zur Hilfe.

                      sigi234S 1 Reply Last reply
                      0
                      • G gentlel

                        @sigi234 Ja aber der zeigt das hier an obwohl iobroker in /opt/iobroker ist 6⃣

                        iobroker:~$ curl -sL https://iobroker.net/fix.sh | bash -
                        
                        library: loaded
                        Library version=2020-01-13
                        ioBroker is not installed in /opt/iobroker! Cannot fix anything...
                        

                        Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
                        Hier gehts zur Hilfe.

                        sigi234S Online
                        sigi234S Online
                        sigi234
                        Forum Testing Most Active
                        wrote on last edited by
                        #1031

                        @gentlel sagte in js-controller 2.0 ab sofort im Latest Repo:

                        @sigi234 Ja aber der zeigt das hier an obwohl iobroker in /opt/iobroker ist 6⃣

                        iobroker:~$ curl -sL https://iobroker.net/fix.sh | bash -

                        library: loaded
                        Library version=2020-01-13
                        ioBroker is not installed in /opt/iobroker! Cannot fix anything...

                        Was kommt bei:

                        cd /opt/iobroker
                        iobroker list instances
                        node -v
                        nodejs -v
                        npm -v

                        Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
                        Immer Daten sichern!

                        1 Reply Last reply
                        0
                        • G Offline
                          G Offline
                          gentlel
                          wrote on last edited by Negalein
                          #1032

                          @sigi234 said in js-controller 2.0 ab sofort im Latest Repo:

                          iobroker list instances

                          elmar@iobroker:/opt/iobroker$ iobroker list instances
                          internal/modules/cjs/loader.js:584
                              throw err;
                              ^
                          
                          Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                              at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
                              at Function.Module._load (internal/modules/cjs/loader.js:508:25)
                              at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
                              at startup (internal/bootstrap/node.js:283:19)
                              at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
                          

                          node -v
                          v10.15.3
                          nodejs -v
                          npm -v
                          6.13.0

                          Bis gerade eben lief iobroker ganz normal. Dann habe ich die homematic adapter upgedatet und die wollten js controller 2.0 haben 😞 seit dem geht nichts mehr 😞

                          Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
                          Hier gehts zur Hilfe.

                          dslraserD apollon77A 2 Replies Last reply
                          0
                          • G gentlel

                            @sigi234 said in js-controller 2.0 ab sofort im Latest Repo:

                            iobroker list instances

                            elmar@iobroker:/opt/iobroker$ iobroker list instances
                            internal/modules/cjs/loader.js:584
                                throw err;
                                ^
                            
                            Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                                at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
                                at Function.Module._load (internal/modules/cjs/loader.js:508:25)
                                at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
                                at startup (internal/bootstrap/node.js:283:19)
                                at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
                            

                            node -v
                            v10.15.3
                            nodejs -v
                            npm -v
                            6.13.0

                            Bis gerade eben lief iobroker ganz normal. Dann habe ich die homematic adapter upgedatet und die wollten js controller 2.0 haben 😞 seit dem geht nichts mehr 😞

                            Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
                            Hier gehts zur Hilfe.

                            dslraserD Offline
                            dslraserD Offline
                            dslraser
                            Forum Testing Most Active
                            wrote on last edited by
                            #1033

                            @gentlel

                            wieso diese Version ?

                            iobroker.js-controller@2.0.25
                            
                            1 Reply Last reply
                            0
                            • G Offline
                              G Offline
                              gentlel
                              wrote on last edited by
                              #1034

                              Habe es auch nur mit js-controller versucht... gleiches Bild. 2.0.25 habe ich irgendwo im FOrum gelesen

                              apollon77A 1 Reply Last reply
                              0
                              • G gentlel

                                @sigi234 said in js-controller 2.0 ab sofort im Latest Repo:

                                iobroker list instances

                                elmar@iobroker:/opt/iobroker$ iobroker list instances
                                internal/modules/cjs/loader.js:584
                                    throw err;
                                    ^
                                
                                Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                                    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
                                    at Function.Module._load (internal/modules/cjs/loader.js:508:25)
                                    at Function.Module.runMain (internal/modules/cjs/loader.js:754:12)
                                    at startup (internal/bootstrap/node.js:283:19)
                                    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)
                                

                                node -v
                                v10.15.3
                                nodejs -v
                                npm -v
                                6.13.0

                                Bis gerade eben lief iobroker ganz normal. Dann habe ich die homematic adapter upgedatet und die wollten js controller 2.0 haben 😞 seit dem geht nichts mehr 😞

                                Mod-Edit: Code/Log in Code Tags gepackt. Bitte benutzt die Code Tags Funktion -> </>
                                Hier gehts zur Hilfe.

                                apollon77A Online
                                apollon77A Online
                                apollon77
                                wrote on last edited by
                                #1035

                                @gentlel dann siehe erster Post bzw faq Post. Manuell Controller per npm drüber installieren.

                                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 Reply Last reply
                                1
                                • G gentlel

                                  Habe es auch nur mit js-controller versucht... gleiches Bild. 2.0.25 habe ich irgendwo im FOrum gelesen

                                  apollon77A Online
                                  apollon77A Online
                                  apollon77
                                  wrote on last edited by
                                  #1036

                                  @gentlel Stable ist 2.1.1 und im Latest Test gerade die 2.2.7

                                  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 Reply Last reply
                                  0
                                  • NightlyN Offline
                                    NightlyN Offline
                                    Nightly
                                    wrote on last edited by
                                    #1037

                                    Hallo, beim Updaten auf js-controller 2.2.9 kommen diverse Fehlermeldungen. Nach dem Update funktioniert alles soweit, ausser dass beim Updaten von Adaptern der selbe Fehler ebenso kommt. Danke für Hinweise, was unternommen werden kann.

                                    root@ioBroker2:~# iobroker upgrade self
                                    Update js-controller from @1.5.3 to @2.2.9
                                    NPM version: 4.6.1
                                    npm install iobroker.js-controller@2.2.9 --unsafe-perm --production --save --prefix "/opt/iobroker" (System call)
                                    ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden
                                     #include <security/pam_appl.h>
                                                                   ^
                                    compilation terminated.
                                    make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                                    gyp ERR! build error 
                                    gyp ERR! stack Error: `make` failed with exit code: 2
                                    gyp ERR! stack     at ChildProcess.onExit (/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
                                    gyp ERR! stack     at emitTwo (events.js:126:13)
                                    gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
                                    gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
                                    gyp ERR! System Linux 4.9.0-8-amd64
                                    gyp ERR! command "/root/.nvm/versions/node/v8.11.3/bin/node" "/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                    gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
                                    gyp ERR! node -v v8.11.3
                                    gyp ERR! node-gyp -v v3.6.0
                                    gyp ERR! not ok 
                                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                                    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
                                    npm WARN ws@7.2.3 requires a peer of bufferutil@^4.0.1 but none was installed.
                                    npm WARN ws@7.2.3 requires a peer of utf-8-validate@^5.0.2 but none was installed.
                                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):
                                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
                                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                                    Host "ioBroker2" (linux) updated
                                    Execute: chmod -R 777 /opt/iobroker
                                    Chmod finished. Restart controller
                                    Starting node restart.js
                                    

                                    Update von Adapter:

                                    $ ./iobroker upgrade cloud
                                    Update cloud from @3.0.2 to @3.0.3
                                    NPM version: 4.6.1
                                    npm install iobroker.cloud@3.0.3 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                    ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden #include <security/pam_appl.h>                               ^compilation terminated.
                                    make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                                    gyp
                                     ERR! build error
                                     
                                    gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)gyp ERR!
                                     stack     at emitTwo (events.js:126:13)gyp ERR! stack     at ChildProcess.emit (events.js:214:7)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)gyp
                                     ERR! System Linux 4.9.0-8-amd64gyp ERR! command "/root/.nvm/versions/node/v8.11.3/bin/node" "/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd
                                     /opt/iobroker/node_modules/authenticate-pamgyp ERR! node -v v8.11.3gyp ERR! node-gyp -v v3.6.0gyp ERR! not ok 
                                    upload [6] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/words.js words.js application/javascript
                                    Update "system.adapter.cloud.0"
                                    upload [5] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/index_m.html index_m.html text/html
                                    upload [4] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/index.html index.html text/html
                                    upload [3] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/cloud.png cloud.png image/png
                                    upload [2] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/blockly.js blockly.js application/javascript
                                    upload [1] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/alexalogo.png alexalogo.png image/png
                                    upload [0] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/actions.js actions.js application/javascript
                                    Adapter "cloud" updated
                                    process exited with code 0
                                    
                                    Thomas BraunT paul53P 2 Replies Last reply
                                    0
                                    • NightlyN Nightly

                                      Hallo, beim Updaten auf js-controller 2.2.9 kommen diverse Fehlermeldungen. Nach dem Update funktioniert alles soweit, ausser dass beim Updaten von Adaptern der selbe Fehler ebenso kommt. Danke für Hinweise, was unternommen werden kann.

                                      root@ioBroker2:~# iobroker upgrade self
                                      Update js-controller from @1.5.3 to @2.2.9
                                      NPM version: 4.6.1
                                      npm install iobroker.js-controller@2.2.9 --unsafe-perm --production --save --prefix "/opt/iobroker" (System call)
                                      ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden
                                       #include <security/pam_appl.h>
                                                                     ^
                                      compilation terminated.
                                      make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                                      gyp ERR! build error 
                                      gyp ERR! stack Error: `make` failed with exit code: 2
                                      gyp ERR! stack     at ChildProcess.onExit (/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
                                      gyp ERR! stack     at emitTwo (events.js:126:13)
                                      gyp ERR! stack     at ChildProcess.emit (events.js:214:7)
                                      gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
                                      gyp ERR! System Linux 4.9.0-8-amd64
                                      gyp ERR! command "/root/.nvm/versions/node/v8.11.3/bin/node" "/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                                      gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
                                      gyp ERR! node -v v8.11.3
                                      gyp ERR! node-gyp -v v3.6.0
                                      gyp ERR! not ok 
                                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
                                      npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
                                      npm WARN ws@7.2.3 requires a peer of bufferutil@^4.0.1 but none was installed.
                                      npm WARN ws@7.2.3 requires a peer of utf-8-validate@^5.0.2 but none was installed.
                                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):
                                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
                                      npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                                      Host "ioBroker2" (linux) updated
                                      Execute: chmod -R 777 /opt/iobroker
                                      Chmod finished. Restart controller
                                      Starting node restart.js
                                      

                                      Update von Adapter:

                                      $ ./iobroker upgrade cloud
                                      Update cloud from @3.0.2 to @3.0.3
                                      NPM version: 4.6.1
                                      npm install iobroker.cloud@3.0.3 --unsafe-perm --loglevel error --prefix "/opt/iobroker" (System call)
                                      ../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: Datei oder Verzeichnis nicht gefunden #include <security/pam_appl.h>                               ^compilation terminated.
                                      make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                                      gyp
                                       ERR! build error
                                       
                                      gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)gyp ERR!
                                       stack     at emitTwo (events.js:126:13)gyp ERR! stack     at ChildProcess.emit (events.js:214:7)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)gyp
                                       ERR! System Linux 4.9.0-8-amd64gyp ERR! command "/root/.nvm/versions/node/v8.11.3/bin/node" "/root/.nvm/versions/node/v8.11.3/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd
                                       /opt/iobroker/node_modules/authenticate-pamgyp ERR! node -v v8.11.3gyp ERR! node-gyp -v v3.6.0gyp ERR! not ok 
                                      upload [6] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/words.js words.js application/javascript
                                      Update "system.adapter.cloud.0"
                                      upload [5] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/index_m.html index_m.html text/html
                                      upload [4] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/index.html index.html text/html
                                      upload [3] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/cloud.png cloud.png image/png
                                      upload [2] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/blockly.js blockly.js application/javascript
                                      upload [1] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/alexalogo.png alexalogo.png image/png
                                      upload [0] cloud.admin /opt/iobroker/node_modules/iobroker.cloud/admin/actions.js actions.js application/javascript
                                      Adapter "cloud" updated
                                      process exited with code 0
                                      
                                      Thomas BraunT Online
                                      Thomas BraunT Online
                                      Thomas Braun
                                      Most Active
                                      wrote on last edited by Thomas Braun
                                      #1038

                                      @Nightly Da versuchst du aber einen Sprung...

                                      nodejs -v
                                      node -v
                                      

                                      Und wenn du da auf einem Debian unterwegs bist: Ich bin kein Freund von root-shells...

                                      lsb_release -a
                                      

                                      Linux-Werkzeugkasten:
                                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                      NodeJS Fixer Skript:
                                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                      NightlyN 1 Reply Last reply
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @Nightly Da versuchst du aber einen Sprung...

                                        nodejs -v
                                        node -v
                                        

                                        Und wenn du da auf einem Debian unterwegs bist: Ich bin kein Freund von root-shells...

                                        lsb_release -a
                                        
                                        NightlyN Offline
                                        NightlyN Offline
                                        Nightly
                                        wrote on last edited by
                                        #1039

                                        @Thomas-Braun

                                        root@ioBroker2:~# nodejs -v
                                        v8.12.0
                                        root@ioBroker2:~# node -v
                                        v8.11.3
                                        root@ioBroker2:~# lsb_release -a
                                        No LSB modules are available.
                                        Distributor ID:	Debian
                                        Description:	Debian GNU/Linux 9.5 (stretch)
                                        Release:	9.5
                                        Codename:	stretch
                                        
                                        Thomas BraunT 1 Reply Last reply
                                        0
                                        • NightlyN Nightly

                                          @Thomas-Braun

                                          root@ioBroker2:~# nodejs -v
                                          v8.12.0
                                          root@ioBroker2:~# node -v
                                          v8.11.3
                                          root@ioBroker2:~# lsb_release -a
                                          No LSB modules are available.
                                          Distributor ID:	Debian
                                          Description:	Debian GNU/Linux 9.5 (stretch)
                                          Release:	9.5
                                          Codename:	stretch
                                          
                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          wrote on last edited by Thomas Braun
                                          #1040

                                          @Nightly node falsch installiert (und in einer zu niedrigen Version für iobroker 2.2.9, denke ich) .

                                          Und melde dich als root ab! Das wird als normaler user ausgeführt. (Es sei denn, das läuft im Docker ab...)

                                          Linux-Werkzeugkasten:
                                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                          NodeJS Fixer Skript:
                                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                          NightlyN 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          563

                                          Online

                                          32.4k

                                          Users

                                          81.3k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe