Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [How-to] Node.js für ioBroker richtig updaten

    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

    [How-to] Node.js für ioBroker richtig updaten

    This topic has been deleted. Only users with topic management privileges can see it.
    • MathiasJ
      MathiasJ @dslraser last edited by

      @dslraser

      danke tr-064 läuft! 👌

      1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 @Adnim last edited by

        @Adnim was hatte rebuild denn gesagt?

        A 1 Reply Last reply Reply Quote 0
        • A
          Adnim @apollon77 last edited by Adnim

          @apollon77 Habe den Log Auszug wieder rausgesucht. Sah so aus. Rebuild hat Tausend Sachen angezeigt dazu habe ich keinen Log leider. Gefunzt hat es danach aber nicht.

          2019-06-15 08:52:07.738  - error: Caught by controller[0]: internal/modules/cjs/loader.js:805
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:   return process.dlopen(module, path.toNamespacedPath(filename));
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:                  ^
          2019-06-15 08:52:07.738  - error: Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.sql/node_modules/mmmagic/build/Release/magic.node'
          2019-06-15 08:52:07.738  - error: Caught by controller[0]: was compiled against a different Node.js version using
          2019-06-15 08:52:07.738  - error: Caught by controller[0]: NODE_MODULE_VERSION 57. This version of Node.js requires
          2019-06-15 08:52:07.738  - error: Caught by controller[0]: NODE_MODULE_VERSION 64. Please try re-compiling or re-installing
          2019-06-15 08:52:07.738  - error: Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:     at Object.Module._extensions..node (internal/modules/cjs/loader.js:805:18)
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:     at Module.load (internal/modules/cjs/loader.js:653:32)
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
          2019-06-15 08:52:07.738  - error: Caught by controller[0]:     at Module.require (internal/modules/cjs/loader.js:690:17)
          2019-06-15 08:52:07.739  - error: Caught by controller[0]:     at require (internal/modules/cjs/helpers.js:25:18)
          2019-06-15 08:52:07.739  - error: Caught by controller[0]:     at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.sql/node_modules/mmmagic/lib/index.js:1:13)
          2019-06-15 08:52:07.739  - error: Caught by controller[0]:     at Module._compile (internal/modules/cjs/loader.js:776:30)
          2019-06-15 08:52:07.739  - error: Caught by controller[0]:     at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
          2019-06-15 08:52:07.739  - error: Caught by controller[0]:     at Module.load (internal/modules/cjs/loader.js:653:32)
          2019-06-15 08:52:07.739  - error: host.iobroker1 instance system.adapter.sql.0 terminated with code 1 ()
          2019-06-15 08:52:07.739  - info: host.iobroker1 Restart adapter system.adapter.sql.0 because enabled
          

          Beim Update meines Slaves RPI gab es hinterher auch noch probleme. NPM Rebuild hat immer abgebrochen. Fehlermeldung(BSP das kam zu diversen Node Paketen):

          2019-06-15 09:45:31.633  - info: iobroker make: *** [Release/obj.target/unix_dgram/src/unix_dgram.o] Fehler 1
          2019-06-15 09:45:31.638  - info: iobroker gyp
          2019-06-15 09:45:31.647  - info: iobroker  ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2
          gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
          gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
          gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
          gyp ERR! System Linux 4.19.42-v7+
          gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
          gyp ERR! cwd /opt/iobroker/node_modules/iobroker.js-controller/node_modules/winston-syslog/node_modules/unix-dgram
          gyp ERR! node -v v10.16.0
          gyp ERR! node-gyp -v v3.8.0
          gyp ERR! not ok 
          
          

          NPM Rebuild LOG

          
          gyp ERR! build error
          gyp ERR! stack Error: `make` failed with exit code: 2
          gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/lib/build.js:262:23)
          gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
          gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
          gyp ERR! System Linux 4.19.42-v7+
          gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/npm-lifecycle/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
          gyp ERR! cwd /opt/iobroker/node_modules/unix-dgram
          gyp ERR! node -v v10.16.0
          gyp ERR! node-gyp -v v3.8.0
          gyp ERR! not ok
          npm ERR! code ELIFECYCLE
          npm ERR! errno 1
          npm ERR! unix-dgram@0.2.3 install: `node-gyp rebuild`
          npm ERR! Exit status 1
          npm ERR!
          npm ERR! Failed at the unix-dgram@0.2.3 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:
          
          

          Entweder reichte Manuelles nachinstallieren per npm i node-gyp prebuild im jeweiligen Ordner oder der ganze adapter musste runter. Unix Dgram habe ich laut der Anleitung auch nochmal drüber installiert.Es funzt alles trotzdem läuft NPM rebuild auch auf dem Slave nicht durch. Was ist da bei mir anders?

          apollon77 1 Reply Last reply Reply Quote 0
          • A
            Adnim last edited by

            Habe nochmal nen neuen Container gemacht mit Debian 9 . Dort alles gemäß https://www.iobroker.net/#de/documentation/install/linux.md installiert.
            Minimal Backup eingespielt. Da kommt ein ähnlicher beim Installieren der Adapter im Iobroker LOG

            iobroker 2019-06-16 10:04:36.852 info npm
            iobroker 2019-06-16 10:04:36.463 info
            iobroker 2019-06-16 10:04:36.463 info ERR! not ok
            iobroker 2019-06-16 10:04:36.463 info node-gyp -v v3.8.0gyp
            iobroker 2019-06-16 10:04:36.463 info node -v v10.16.0gyp ERR!
            iobroker 2019-06-16 10:04:36.463 info gyp ERR!

            Kann man nicht Node-GYP irgendwo zentral aktualisieren?

            apollon77 1 Reply Last reply Reply Quote 0
            • O
              Olivbus @apollon77 last edited by

              @apollon77 danke für die Antwort. Habe mittlerweile reinstall.sh gemacht. Danach war das npm rebuild ohne Errors

              1 Reply Last reply Reply Quote 0
              • apollon77
                apollon77 @Adnim last edited by

                @Adnim also vor allem zu Unix-dgram gibt es Infos im zweiten post. Bitte lesen!!

                1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @Adnim last edited by

                  @Adnim bitte vollständige Meldung Posten node-gyp ist nicht die ursache des Problems und komme mir nodejs mir und passt daher dazu wie es sein soll.

                  Die Frage ist bei welcher nativen Library es Problem gibt. Die muss man prüfen und beheben.

                  1 Reply Last reply Reply Quote 0
                  • smartboart
                    smartboart @crunchip last edited by

                    @crunchip Hallo, bekomme die GPIO auch nicht mehr zum laufen nach dem Update...
                    Alles andere hat prima geklappt...
                    hier der log zum Thema wie bekomme ich meine gpio inputs wieder eingelesen...
                    rpi-gpio und epoll machen hier probleme...
                    wegen der admin Rechte für die gpio ist das installationsfixer skript keine option...habs trotzdem laufen lassen. hat auch nix gebracht...

                    
                    pi@192.168.1.47's password:
                    Linux ioBroker-RasPi 4.19.42-v7+ #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l
                    
                    The programs included with the Debian GNU/Linux system are free software;
                    the exact distribution terms for each program are described in the
                    individual files in /usr/share/doc/*/copyright.
                    
                    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
                    permitted by applicable law.
                    Last login: Mon Jun 17 16:02:36 2019 from 192.168.1.27
                    pi@ioBroker-RasPi:~ $ cd /opt/iobroker
                    pi@ioBroker-RasPi:/opt/iobroker $ sudo iobroker stop
                    Stopping iobroker controller daemon...
                    iobroker controller daemon stopped.
                    No "killall.sh" script found. Just stop.
                    pi@ioBroker-RasPi:/opt/iobroker $ cd
                    pi@ioBroker-RasPi:~ $ npm ls rpi-gpio
                    /home/pi
                    └── (empty)
                    
                    pi@ioBroker-RasPi:~ $ cd /opt/iobroker
                    pi@ioBroker-RasPi:/opt/iobroker $ npm ls rpi-gpio
                    iobroker.inst@1.1.2 /opt/iobroker
                    └─┬ iobroker.rpi2@1.0.0
                      └── UNMET OPTIONAL DEPENDENCY rpi-gpio@^1.0.0
                    
                    pi@ioBroker-RasPi:/opt/iobroker $ cd /opt/iobroker/iobroker.rpi2
                    -bash: cd: /opt/iobroker/iobroker.rpi2: Datei oder Verzeichnis nicht gefunden
                    pi@ioBroker-RasPi:/opt/iobroker $ cd /opt/iobroker/node_modulse/iobroker.rpi2
                    -bash: cd: /opt/iobroker/node_modulse/iobroker.rpi2: Datei oder Verzeichnis nich                      t gefunden
                    pi@ioBroker-RasPi:/opt/iobroker $ cd /opt/iobroker/node_modules/iobroker.rpi2
                    pi@ioBroker-RasPi:/opt/iobroker/node_modules/iobroker.rpi2 $ npm install rpi-gpi                      o
                    
                    > epoll@0.1.22 install /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epo                      ll
                    > node-gyp rebuild
                    
                    make: Verzeichnis „/opt/iobroker/node_modules/iobroker.rpi2/node_modules/epoll/b                      uild“ wird betreten
                      CXX(target) Release/obj.target/epoll/src/epoll.o
                    In file included from ../../nan/nan.h:192:0,
                                     from ../src/epoll.cc:15:
                    ../../nan/nan_maybe_43_inl.h: In function ‘Nan::Maybe<bool> Nan::ForceSet(v8::Lo                      cal<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribu                      te)’:
                    ../../nan/nan_maybe_43_inl.h:112:15: error: ‘class v8::Object’ has no member nam                      ed ‘ForceSet’
                       return obj->ForceSet(isolate->GetCurrentContext(), key, value, attribs);
                                   ^~~~~~~~
                    In file included from ../src/epoll.cc:15:0:
                    ../../nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v                      8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’:
                    ../../nan/nan.h:835:60: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Is                      olate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value                      >*)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarati                      ons]
                             v8::Isolate::GetCurrent(), target, func, argc, argv);
                                                                                ^
                    In file included from ../src/epoll.cc:12:0:
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:177:50: note: declared here
                                     NODE_EXTERN v8::Local<v8::Value> MakeCallback(
                                                                      ^
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:91:42: note: in definition of mac                      ro ‘NODE_DEPRECATED’
                         __attribute__((deprecated(message))) declarator
                                                              ^~~~~~~~~~
                    In file included from ../src/epoll.cc:15:0:
                    ../../nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v                      8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*)’:
                    ../../nan/nan.h:850:62: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Is                      olate*, v8::Local<v8::Object>, v8::Local<v8::String>, int, v8::Local<v8::Value>*                      )’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declaration                      s]
                             v8::Isolate::GetCurrent(), target, symbol, argc, argv);
                                                                                  ^
                    In file included from ../src/epoll.cc:12:0:
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:170:50: note: declared here
                                     NODE_EXTERN v8::Local<v8::Value> MakeCallback(
                                                                      ^
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:91:42: note: in definition of mac                      ro ‘NODE_DEPRECATED’
                         __attribute__((deprecated(message))) declarator
                                                              ^~~~~~~~~~
                    In file included from ../src/epoll.cc:15:0:
                    ../../nan/nan.h: In function ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v                      8::Object>, const char*, int, v8::Local<v8::Value>*)’:
                    ../../nan/nan.h:865:62: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Is                      olate*, v8::Local<v8::Object>, const char*, int, v8::Local<v8::Value>*)’ is depr                      ecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarations]
                             v8::Isolate::GetCurrent(), target, method, argc, argv);
                                                                                  ^
                    In file included from ../src/epoll.cc:12:0:
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:163:50: note: declared here
                                     NODE_EXTERN v8::Local<v8::Value> MakeCallback(
                                                                      ^
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:91:42: note: in definition of mac                      ro ‘NODE_DEPRECATED’
                         __attribute__((deprecated(message))) declarator
                                                              ^~~~~~~~~~
                    In file included from ../src/epoll.cc:15:0:
                    ../../nan/nan.h: In member function ‘v8::Local<v8::Value> Nan::Callback::Call_(v                      8::Isolate*, v8::Local<v8::Object>, int, v8::Local<v8::Value>*) const’:
                    ../../nan/nan.h:1479:5: warning: ‘v8::Local<v8::Value> node::MakeCallback(v8::Is                      olate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value                      >*)’ is deprecated: Use MakeCallback(..., async_context) [-Wdeprecated-declarati                      ons]
                         ));
                         ^
                    In file included from ../src/epoll.cc:12:0:
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:177:50: note: declared here
                                     NODE_EXTERN v8::Local<v8::Value> MakeCallback(
                                                                      ^
                    /home/pi/.node-gyp/10.16.0/include/node/node.h:91:42: note: in definition of mac                      ro ‘NODE_DEPRECATED’
                         __attribute__((deprecated(message))) declarator
                                                              ^~~~~~~~~~
                    ../src/epoll.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE E                      poll::Add(Nan::NAN_METHOD_ARGS_TYPE)’:
                    ../src/epoll.cc:210:44: warning: ‘int32_t v8::Value::Int32Value() const’ is depr                      ecated: Use maybe version [-Wdeprecated-declarations]
                       int err = epoll->Add(info[0]->Int32Value(), info[1]->Int32Value());
                                                                ^
                    In file included from /home/pi/.node-gyp/10.16.0/include/node/v8.h:26:0,
                                     from ../src/epoll.cc:11:
                    /home/pi/.node-gyp/10.16.0/include/node/v8.h:2478:46: note: declared here
                       V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                                                  ^
                    /home/pi/.node-gyp/10.16.0/include/node/v8config.h:324:3: note: in definition of                       macro ‘V8_DEPRECATED’
                       declarator __attribute__((deprecated(message)))
                       ^~~~~~~~~~
                    ../src/epoll.cc:210:67: warning: ‘int32_t v8::Value::Int32Value() const’ is depr                      ecated: Use maybe version [-Wdeprecated-declarations]
                       int err = epoll->Add(info[0]->Int32Value(), info[1]->Int32Value());
                                                                                       ^
                    In file included from /home/pi/.node-gyp/10.16.0/include/node/v8.h:26:0,
                                     from ../src/epoll.cc:11:
                    /home/pi/.node-gyp/10.16.0/include/node/v8.h:2478:46: note: declared here
                       V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                                                  ^
                    /home/pi/.node-gyp/10.16.0/include/node/v8config.h:324:3: note: in definition of                       macro ‘V8_DEPRECATED’
                       declarator __attribute__((deprecated(message)))
                       ^~~~~~~~~~
                    ../src/epoll.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE E                      poll::Modify(Nan::NAN_METHOD_ARGS_TYPE)’:
                    ../src/epoll.cc:230:47: warning: ‘int32_t v8::Value::Int32Value() const’ is depr                      ecated: Use maybe version [-Wdeprecated-declarations]
                       int err = epoll->Modify(info[0]->Int32Value(), info[1]->Int32Value());
                                                                   ^
                    In file included from /home/pi/.node-gyp/10.16.0/include/node/v8.h:26:0,
                                     from ../src/epoll.cc:11:
                    /home/pi/.node-gyp/10.16.0/include/node/v8.h:2478:46: note: declared here
                       V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                                                  ^
                    /home/pi/.node-gyp/10.16.0/include/node/v8config.h:324:3: note: in definition of                       macro ‘V8_DEPRECATED’
                       declarator __attribute__((deprecated(message)))
                       ^~~~~~~~~~
                    ../src/epoll.cc:230:70: warning: ‘int32_t v8::Value::Int32Value() const’ is depr                      ecated: Use maybe version [-Wdeprecated-declarations]
                       int err = epoll->Modify(info[0]->Int32Value(), info[1]->Int32Value());
                                                                                          ^
                    In file included from /home/pi/.node-gyp/10.16.0/include/node/v8.h:26:0,
                                     from ../src/epoll.cc:11:
                    /home/pi/.node-gyp/10.16.0/include/node/v8.h:2478:46: note: declared here
                       V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                                                  ^
                    /home/pi/.node-gyp/10.16.0/include/node/v8config.h:324:3: note: in definition of                       macro ‘V8_DEPRECATED’
                       declarator __attribute__((deprecated(message)))
                       ^~~~~~~~~~
                    ../src/epoll.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE E                      poll::Remove(Nan::NAN_METHOD_ARGS_TYPE)’:
                    ../src/epoll.cc:247:47: warning: ‘int32_t v8::Value::Int32Value() const’ is depr                      ecated: Use maybe version [-Wdeprecated-declarations]
                       int err = epoll->Remove(info[0]->Int32Value());
                                                                   ^
                    In file included from /home/pi/.node-gyp/10.16.0/include/node/v8.h:26:0,
                                     from ../src/epoll.cc:11:
                    /home/pi/.node-gyp/10.16.0/include/node/v8.h:2478:46: note: declared here
                       V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                                                  ^
                    /home/pi/.node-gyp/10.16.0/include/node/v8config.h:324:3: note: in definition of                       macro ‘V8_DEPRECATED’
                       declarator __attribute__((deprecated(message)))
                       ^~~~~~~~~~
                    epoll.target.mk:101: die Regel für Ziel „Release/obj.target/epoll/src/epoll.o“ s                      cheiterte
                    make: *** [Release/obj.target/epoll/src/epoll.o] Fehler 1
                    make: Verzeichnis „/opt/iobroker/node_modules/iobroker.rpi2/node_modules/epoll/b                      uild“ wird verlassen
                    gyp ERR! build error
                    gyp ERR! stack Error: `make` failed with exit code: 2
                    gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_module                      s/node-gyp/lib/build.js:262:23)
                    gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                    gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces                      s.js:248:12)
                    gyp ERR! System Linux 4.19.42-v7+
                    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy                      p/bin/node-gyp.js" "rebuild"
                    gyp ERR! cwd /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epoll
                    gyp ERR! node -v v10.16.0
                    gyp ERR! node-gyp -v v3.8.0
                    gyp ERR! not ok
                    npm ERR! code ELIFECYCLE
                    npm ERR! errno 1
                    npm ERR! epoll@0.1.22 install: `node-gyp rebuild`
                    npm ERR! Exit status 1
                    npm ERR!
                    npm ERR! Failed at the epoll@0.1.22 install script.
                    npm ERR! This is probably not a problem with npm. There is likely additional log                      ging output above.
                    
                    npm ERR! A complete log of this run can be found in:
                    npm ERR!     /home/pi/.npm/_logs/2019-06-17T14_19_01_263Z-debug.log
                    pi@ioBroker-RasPi:/opt/iobroker/node_modules/iobroker.rpi2 $ sudo npm install rp                      i-gpio
                    
                    > epoll@0.1.22 install /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epo                      ll
                    > node-gyp rebuild
                    
                    gyp WARN EACCES user "root" does not have permission to access the dev dir "/roo                      t/.node-gyp/10.16.0"
                    gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/n                      ode_modules/iobroker.rpi2/node_modules/epoll/.node-gyp"
                    gyp WARN install got an error, rolling back install
                    gyp WARN install got an error, rolling back install
                    gyp ERR! configure error
                    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modul                      es/iobroker.rpi2/node_modules/epoll/.node-gyp'
                    gyp ERR! System Linux 4.19.42-v7+
                    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy                      p/bin/node-gyp.js" "rebuild"
                    gyp ERR! cwd /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epoll
                    gyp ERR! node -v v10.16.0
                    gyp ERR! node-gyp -v v3.8.0
                    gyp ERR! not ok
                    npm ERR! code ELIFECYCLE
                    npm ERR! errno 1
                    npm ERR! epoll@0.1.22 install: `node-gyp rebuild`
                    npm ERR! Exit status 1
                    npm ERR!
                    npm ERR! Failed at the epoll@0.1.22 install script.
                    npm ERR! This is probably not a problem with npm. There is likely additional log                      ging output above.
                    
                    npm ERR! A complete log of this run can be found in:
                    npm ERR!     /root/.npm/_logs/2019-06-17T14_25_14_382Z-debug.log
                    pi@ioBroker-RasPi:/opt/iobroker/node_modules/iobroker.rpi2 $ sudo npm install ep                      oll
                    
                    > epoll@0.1.22 install /opt/iobroker/node_modules/iobroker.rpi2/node_modules/rpi                      -gpio/node_modules/epoll
                    > node-gyp rebuild
                    
                    gyp WARN EACCES user "root" does not have permission to access the dev dir "/roo                      t/.node-gyp/10.16.0"
                    gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/n                      ode_modules/iobroker.rpi2/node_modules/rpi-gpio/node_modules/epoll/.node-gyp"
                    gyp WARN install got an error, rolling back install
                    gyp WARN install got an error, rolling back install
                    gyp ERR! configure error
                    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modul                      es/iobroker.rpi2/node_modules/rpi-gpio/node_modules/epoll/.node-gyp'
                    gyp ERR! System Linux 4.19.42-v7+
                    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy                      p/bin/node-gyp.js" "rebuild"
                    gyp ERR! cwd /opt/iobroker/node_modules/iobroker.rpi2/node_modules/rpi-gpio/node                      _modules/epoll
                    gyp ERR! node -v v10.16.0
                    gyp ERR! node-gyp -v v3.8.0
                    gyp ERR! not ok
                    
                    > epoll@2.0.9 install /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epol                      l
                    > node-gyp rebuild
                    
                    gyp WARN EACCES user "root" does not have permission to access the dev dir "/roo                      t/.node-gyp/10.16.0"
                    gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/n                      ode_modules/iobroker.rpi2/node_modules/epoll/.node-gyp"
                    gyp WARN install got an error, rolling back install
                    gyp WARN install got an error, rolling back install
                    gyp ERR! configure error
                    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modul                      es/iobroker.rpi2/node_modules/epoll/.node-gyp'
                    gyp ERR! System Linux 4.19.42-v7+
                    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy                      p/bin/node-gyp.js" "rebuild"
                    gyp ERR! cwd /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epoll
                    gyp ERR! node -v v10.16.0
                    gyp ERR! node-gyp -v v3.8.0
                    gyp ERR! not ok
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: epoll@0.1.22 (node_modules/rpi-g                      pio/node_modules/epoll):
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: epoll@0.1.22 install: `node-gyp                       rebuild`
                    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                    
                    npm ERR! code ELIFECYCLE
                    npm ERR! errno 1
                    npm ERR! epoll@2.0.9 install: `node-gyp rebuild`
                    npm ERR! Exit status 1
                    npm ERR!
                    npm ERR! Failed at the epoll@2.0.9 install script.
                    npm ERR! This is probably not a problem with npm. There is likely additional log                      ging output above.
                    
                    npm ERR! A complete log of this run can be found in:
                    npm ERR!     /root/.npm/_logs/2019-06-17T14_26_06_404Z-debug.log
                    pi@ioBroker-RasPi:/opt/iobroker/node_modules/iobroker.rpi2 $ sudo npm install rp                      i-gpio
                    
                    > epoll@0.1.22 install /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epo                      ll
                    > node-gyp rebuild
                    
                    gyp WARN EACCES user "root" does not have permission to access the dev dir "/roo                      t/.node-gyp/10.16.0"
                    gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/n                      ode_modules/iobroker.rpi2/node_modules/epoll/.node-gyp"
                    gyp WARN install got an error, rolling back install
                    gyp WARN install got an error, rolling back install
                    gyp ERR! configure error
                    gyp ERR! stack Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modul                      es/iobroker.rpi2/node_modules/epoll/.node-gyp'
                    gyp ERR! System Linux 4.19.42-v7+
                    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gy                      p/bin/node-gyp.js" "rebuild"
                    gyp ERR! cwd /opt/iobroker/node_modules/iobroker.rpi2/node_modules/epoll
                    gyp ERR! node -v v10.16.0
                    gyp ERR! node-gyp -v v3.8.0
                    gyp ERR! not ok
                    npm ERR! code ELIFECYCLE
                    npm ERR! errno 1
                    npm ERR! epoll@0.1.22 install: `node-gyp rebuild`
                    npm ERR! Exit status 1
                    npm ERR!
                    npm ERR! Failed at the epoll@0.1.22 install script.
                    npm ERR! This is probably not a problem with npm. There is likely additional log                      ging output above.
                    
                    npm ERR! A complete log of this run can be found in:
                    npm ERR!     /root/.npm/_logs/2019-06-17T14_26_44_239Z-debug.log
                    pi@ioBroker-RasPi:/opt/iobroker/node_modules/iobroker.rpi2 $ cd
                    pi@ioBroker-RasPi:~ $ sudo reboot
                    
                    
                    crunchip Stabilostick 2 Replies Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @smartboart last edited by

                      @smartboart mit diesen ganzen Rechteproblemen blick ich selbst nicht durch.
                      Ich hatte bei mir eine alte Root Installation.
                      Ich habe das bei mir nicht weiter verfolgt und den Adapter gelöscht, da er aktuell nicht in gebrauch ist.
                      vllt kann ja @Stabilostick mal gucken

                      smartboart 1 Reply Last reply Reply Quote 0
                      • smartboart
                        smartboart @crunchip last edited by

                        @crunchip sind denn noch andere mit von der Partie bei Problemen mit dem Raspi und dem rpi Adapter bzw. dem einlesen der GPIO mit den Versionen Node.js
                        node.js v10.16.0 NPM 6.9.0? Funktioniert das bei irgendwem oder ist das ein generelles Problem mit dem adapter und den Admin Rechten oder der kompatibilität der Abhängikeiten des Adapters?

                        crunchip 1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @smartboart last edited by

                          @smartboart das weiss ich leider nicht, bisher hab ich diesbezüglich nichts gelesen, das irgendwer damit Probleme hat.
                          Du kannst folgendes machen.
                          Den Adapter einmal löschen und neu installieren, damit die benötigten node module neu geladen werden.

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

                            Das wäre auch für mich interessant. Obwohl es bei mir wahrscheinlich nicht zum Tragen kommt.
                            Ich habe IObroker komplett platt gemacht und neu installiert. Beim einspielen des Backups werden die Adapter sowieso neu installiert.

                            1 Reply Last reply Reply Quote 0
                            • Mic
                              Mic Developer @Stabilostick last edited by

                              @Stabilostick sagte in [How-to] Node.js für ioBroker richtig updaten:

                              @Mic sagte in [How-to] Node.js für ioBroker richtig updaten:

                              Ah, Du bist einer welcher, der die Sicherheit seines Systems täglich aufs neue herausfordert, indem Du als root-User arbeitest. 😈

                              npm i acme-dns-01-cli

                              Hattest Du das im ioBroker-Ordner (z.B. /opt/iobroker) ausgeführt?

                              Wegen root-User: Versuche es ggf. einmal mit dem ioBroker-Fixer, der einige Berechtigungen und Einstellungen korrigiert:

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

                              😱
                              Danke für Deine Antwort. ☺
                              Hat nichts gebracht, ich werde wohl mal gelegentlich eine Neuinstallation durchlaufen lassen. Geht ja relativ fix, außerhalt der Wartezeit nach Einspielen ioBroker-Backup.

                              crunchip 1 Reply Last reply Reply Quote 0
                              • crunchip
                                crunchip Forum Testing Most Active @Mic last edited by

                                @Mic mich hat er auch schon bekehrt😉

                                1 Reply Last reply Reply Quote 1
                                • Stabilostick
                                  Stabilostick @smartboart last edited by Stabilostick

                                  @smartboart

                                  Hi, bin gerade nicht am Rechner. rpi-gpio hat als Abhängigkeit epoll. Ich meine, dass bei epoll eine neuere Version für Node 10 benötigt wird. Gibt es nicht ein rpi-gpio@2.0.0 oder neuer? Der rpi2-Adapter müsste auch mit einem neueren rpi-gpio umgehen können.

                                  apollon77 MathiasJ 2 Replies Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 @Stabilostick last edited by

                                    @Stabilostick macht doch mal ein GitHub issue auf?‘

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

                                      Wollte es nur nochmal erwähnt haben, der sma-em Adapter funktioniert nicht mit node 10.x, was sehr schade ist, weil dieser Adapter extrem nützlich ist, sofern man ein sma engerymeter hat, siehe:

                                      https://forum.iobroker.net/topic/23121/problem-mit-iobroker-sma-em-adapter-nach-node-update

                                      apollon77 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @Winni last edited by

                                        @Winni dann GitHub issue auf machen. Mit dem Link am besten 😉

                                        1 Reply Last reply Reply Quote 0
                                        • MathiasJ
                                          MathiasJ @Stabilostick last edited by

                                          @Stabilostick
                                          ich habe gerade rein geschaut.
                                          Mit rpi2 funktionieren alle meine GPIO's
                                          Meine IObroker-Installation ist auf dem neuesten Stand.

                                          smartboart 1 Reply Last reply Reply Quote 0
                                          • smartboart
                                            smartboart @MathiasJ last edited by smartboart

                                            @MathiasJ hi, danke für deine Überprüfung... wie hast du das denn getestet? Hängen da Taster oder Relais dranne und werden die weiterhin angesteuert und eingelesen. oder hast du dir nur die states angeschaut ob sie angelegt werden? Das alleine sagt nämlich nichts aus...

                                            MathiasJ 2 Replies 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

                                            504
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            installation linux node node.js nodejs windows
                                            106
                                            1105
                                            676896
                                            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