UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[apollon77]

@Sneak-L8 Dann mach mal npm ls im Verzeichnis node_modules/iobroker.rpi2 und Zeig mal die Ausgabe

[Sneak-L8]

@apollon77 Bitte schön:

pi@ioBroker-RasPi:/opt/iobroker/node_modules/iobroker.rpi2 $ npm ls
iobroker.rpi2@1.1.1 /opt/iobroker/node_modules/iobroker.rpi2
├── UNMET DEPENDENCY @iobroker/adapter-core@^1.0.3
├─┬ rpi-gpio@2.1.5
│ ├── UNMET DEPENDENCY async-retry@^1.2.1
│ ├─┬ debug@3.2.6
│ │ └── ms@2.1.2
│ └─┬ epoll@2.0.10
│   ├── UNMET DEPENDENCY bindings@^1.5.0
│   └── UNMET DEPENDENCY nan@^2.14.0
└── UNMET DEPENDENCY sync-exec@^0.6.2

npm ERR! missing: @iobroker/adapter-core@^1.0.3, required by iobroker.rpi2@1.1.1
npm ERR! missing: sync-exec@^0.6.2, required by iobroker.rpi2@1.1.1
npm ERR! missing: async-retry@^1.2.1, required by rpi-gpio@2.1.5
npm ERR! missing: bindings@^1.5.0, required by epoll@2.0.10
npm ERR! missing: nan@^2.14.0, required by epoll@2.0.10

[Steff]

Hallo,
ich habe da auch mal eine Frage bzgl. dem richtigen Node updaten. Ich habe bei mir Node V10.17.0 am Laufen und mir wird ein mögliches Update auf die V10.20.1 angezeigt. Muss bei solch einem Update ebenfalls ein npm rebuild durchgeführt werden?
Gruß Steffen

[Thomas Braun]

@Steff Ich würde es machen. Steht auch wohl nicht ganz ohne Grund so in der Anleitung drin.

[Jan1]

@Thomas-Braun
Dann zeig mir mal die Anleitung wo das drin steht, dass wenn man innerhalb der Grundversion ein Update durchführt, ein rebuild durchführen muss ;-)

[Thomas Braun]

@Jan1 Bei minor-upgrades nicht unbedingt erforderlich, aber es schadet auch nicht. Und wenn man es gewohnheitsmäßig macht vergisst man es auch nicht bei major updates.

[cvidal]

Ich habe das selbe Problem wie @Sneak-L8, bei npm rebuild bekomme ich folgendes raus:

Spoiler

root@IoBroker:/home/christian# cd /opt/iobroker
root@IoBroker:/opt/iobroker# npm rebuild

iobroker.js-controller@2.2.9 preinstall /opt/iobroker/node_modules/iobroker.js-controller
node lib/preinstallCheck.js

NPM version: 6.14.4

iobroker.js-controller@2.2.9 install /opt/iobroker/node_modules/iobroker.js-controller
node iobroker.js setup first

acme-v2@1.8.6 postinstall /opt/iobroker/node_modules/acme-v2
node scripts/postinstall

Greenlock and ACME.js v3 are on the way!
Watch for updates at https://indiegogo.com/at/greenlock

authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ wird betreten
CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
../authenticate_pam.cc: In function ‘void after_doing_auth(uv_work_t*, int)’:
../authenticate_pam.cc:107:87: warning: ‘v8::Localv8::Value Nan::MakeCallback(v8::Localv8::Object, v8::Localv8::Function, int, v8::Localv8::Value)’ is deprecated [-Wdeprecated-declarations]
keCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);
^
In file included from ../authenticate_pam.cc:23:0:
../../nan/nan.h:1024:46: note: declared here
NAN_DEPRECATED inline v8::Localv8::Value MakeCallback(
^~~~~~~~~~~~
../authenticate_pam.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)’:
../authenticate_pam.cc:147:83: warning: ‘v8::Localv8::Value v8::Object::Get(v8::Localv8::Value)’ is deprecated: Use maybe version [-Wdeprecated-declaration ]
al<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());
^
In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8-internal.h:14:0,
from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:27,
from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
from ../../nan/nan.h:54,
from ../authenticate_pam.cc:23:
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:3553:51: note: declared here
V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
^
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);
^
In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
from ../../nan/nan.h:54,
from ../authenticate_pam.cc:23:
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate, char*, int, int*, int) const
int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
^~~~~~~~~
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
../authenticate_pam.cc:152:69: warning: ‘v8::Localv8::Value v8::Object::Get(v8::Localv8::Value)’ is deprecated: Use maybe version [-Wdeprecated-declaration ]
res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());
^
In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8-internal.h:14:0,
from /home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:27,
from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67,
from ../../nan/nan.h:54,
from ../authenticate_pam.cc:23:
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:3553:51: note: declared here
V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));
^
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^~~~~~~~~~
../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);
^
In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
from ../../nan/nan.h:54,
from ../authenticate_pam.cc:23:
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
^~~~~~~~~
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
username->WriteUtf8(m->username, sizeof(m->username) - 1);
^
In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
from ../../nan/nan.h:54,
from ../authenticate_pam.cc:23:
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
^~~~~~~~~
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’
password->WriteUtf8(m->password, sizeof(m->password) - 1);
^
In file included from /home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:67:0,
from ../../nan/nan.h:54,
from ../authenticate_pam.cc:23:
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const
int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,
^~~~~~~~~
/home/iobroker/.cache/node-gyp/12.16.2/include/node/v8.h:2878:7: note: no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
../authenticate_pam.cc: At global scope:
../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void
void init(Handle<Object> exports) {
^~~~~~
../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope
../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token
void init(Handle<Object> exports) {
^
../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope
void init(Handle<Object> exports) {
^~~~~~~
In file included from ../../nan/nan.h:54:0,
from ../authenticate_pam.cc:23:
../authenticate_pam.cc:175:31: error: ‘init’ was not declared in this scope
NODE_MODULE(authenticate_pam, init);
^
/home/iobroker/.cache/node-gyp/12.16.2/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’
(node::addon_register_func) (regfunc),
^~~~~~~
../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’
NODE_MODULE(authenticate_pam, init);
^~~~~~~~~~~
authenticate_pam.target.mk:111: die Regel für Ziel „Release/obj.target/authenticate_pam/authenticate_pam.o“ scheiterte
make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
make: Verzeichnis „/opt/iobroker/node_modules/authenticate-pam/build“ 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_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:310:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
gyp ERR! System Linux 4.9.0-11-amd64
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/authenticate-pam
gyp ERR! node -v v12.16.2
gyp ERR! node-gyp -v v5.1.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! authenticate-pam@1.0.2 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the authenticate-pam@1.0.2 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! /home/iobroker/.npm/_logs/2020-04-14T20_27_54_800Z-debug.log
root@IoBroker:/opt/iobroker#

Alles läuft soweit ohne Errors bei mir ist der VW Connect Adapter das Problem. Bekomme fehler im Log und der Adapter Startet nicht.

Spoiler

host.IoBroker 2020-04-14 22:30:58.371 info Restart adapter system.adapter.vw-connect.0 because enabled
host.IoBroker 2020-04-14 22:30:58.371 error instance system.adapter.vw-connect.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.IoBroker 2020-04-14 22:30:58.371 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:899:14)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:1000:32)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1156:30)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/canvas/lib/bindings.js:3:18)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at require (internal/modules/cjs/helpers.js:77:18)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:1042:19)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:899:14)
host.IoBroker 2020-04-14 22:30:58.370 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:1000:32)
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1206:18)
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: the module (for instance, using npm rebuild or npm install).
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: NODE_MODULE_VERSION 72. Please try re-compiling or re-installing
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: NODE_MODULE_VERSION 64. This version of Node.js requires
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: was compiled against a different Node.js version using
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/canvas/build/Release/canvas.node'
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: ^
host.IoBroker 2020-04-14 22:30:58.369 error Caught by controller[0]: return process.dlopen(module, path.toNamespacedPath(filename));
host.IoBroker 2020-04-14 22:30:58.368 error Caught by controller[0]: internal/modules/cjs/loader.js:1206
host.IoBroker 2020-04-14 22:30:57.978 info instance system.adapter.vw-connect.0 started with pid 28748

Hier komme ich nicht weiter.

[Thomas Braun]

@cvidal Welche Version von node ist installiert?

node -v
nodejs -v

Also root würde ich mich auch nicht anmelden.

[crunchip]

wie komme ich am dümmsten von v10.19 auf die 10.20, ohne den apt update && apt upgrade Befehl?
Hintergrund,
Bluetooth bekomme ich nicht mehr zum laufen, wenn ich die übliche Variante wähle. Daher bin ich erstmal wieder zurück via backup.

[cvidal]

@Thomas-Braun Ich nutze 12.16.2, ich weiß wird noch nicht empfohlen aber das sollte dem Adapter nichts ausmachen.

[Thomas Braun]

@crunchip

sudo apt install nodejs

Ich würde aber schauen, dass die 10.20.1 angeboten wird. Die 10.20.0 hat einen Fehler.
Bluetooth würde ich allerdings auch aktuell halten. Das Update kommt aus Security, das hat wohl einen Grund...

[Thomas Braun]

@cvidal Dann bin ich raus.
Permanent als root angemeldet und dann eine noch nicht vorgesehene Version macht Hilfe schwer.

[apollon77]

@Sneak-L8 Sehr interessant, da ist von der epoll 0.x nix zu sehen ... Dann halt der Harte weg:

Lösche mal /opt/iobroker/node_modules/rpi-gpio/node_modules/epoll komplett. Dann gehst Du in /opt/iobroker/node_modules/rpi-gpio und sagst "npm install --production".

Dann versuch nochmal

[apollon77]

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

authenticate_pam

Versuch mal "apt install libpam0g-dev" und danach nochmal

[cvidal]

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

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

authenticate_pam

Versuch mal "apt install libpam0g-dev" und danach nochmal

Sollte ich das unter cd /opt/iobroker machen?

Edit: ich habe jetzt erstmal auf NodeJS 10.20.1 am laufen, das geht erst mal ohne Probleme. Node 12 werde ich erstmal die finger von lassen.

[cvidal]

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

@cvidal Dann bin ich raus.
Permanent als root angemeldet und dann eine noch nicht vorgesehene Version macht Hilfe schwer.

Ist mein Testsystem, da versuche ich irgendwie alles mal, normal bin ich nicht dauerhaft als Root angemeldet.

[Sneak-L8]

@apollon77 Guten Morgen, hab ich gemacht. Das Löschen wir nur mit root-User möglich (also sudo rm -rf ...).
Aber schon der

npm install --production

schlägt wieder mit demselben Befehl fehl:

Spoiler

pi@ioBroker-RasPi:/opt/iobroker/node_modules/rpi-gpio $ npm install --production
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated istanbul@0.2.7: This module is no longer maintained, try this instead:
npm WARN deprecated   npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated mkdirp@0.3.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated formatio@1.0.2: This package is unmaintained. Use @sinonjs/formatio instead
npm WARN deprecated graceful-fs@2.0.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated minimatch@0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated samsam@1.1.3: This package has been deprecated in favour of @sinonjs/samsam
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

> epoll@0.1.22 install /opt/iobroker/node_modules/rpi-gpio/node_modules/epoll
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/rpi-gpio/node_modules/epoll/build“ 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:
[...]
/home/iobroker/.cache/node-gyp/10.20.1/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
epoll.target.mk:103: die Regel für Ziel „Release/obj.target/epoll/src/epoll.o“ scheiterte
make: *** [Release/obj.target/epoll/src/epoll.o] Fehler 1
make: Verzeichnis „/opt/iobroker/node_modules/rpi-gpio/node_modules/epoll/build“ 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_modules/node-gyp/lib/build.js:191: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.14.34-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/rpi-gpio/node_modules/epoll
gyp ERR! node -v v10.20.1
gyp ERR! node-gyp -v v5.1.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 logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2020-04-15T07_59_33_981Z-debug.log

Er will erneut epoll 0.1.22 installieren...

[apollon77]

@Sneak-L8 Ok, dann noch härter:

Lösche /opt/iobroker/node_modules/rpi-gpio

gehe in /opt/iobroker/node_modules/iobroker.rpi2 und mache dort

npm install --production

[Sneak-L8]

Super, jetzt hat's geklappt! Vielen Dank!!

[crunchip]

@Thomas-Braun das klappt so aber nicht