[How-to] Node.js ioBroker richtig updaten-2021/22 Edition
-
@apollon77 Hallo, naja warum möchte ich das, weils nicht funktioniert und nein ich hab auch nichts mit Docker erwähnt!! Also was soll/kann ich in meinem Fall tun?
Vielleicht noch als info:node -v v14.19.0 npm -v 6.14.16bzw das ist auch recht interessant:
iobroker info Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.IoBrokerSmartHome"] Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"!host.IoBrokerSmartHome 2022-02-08 06:25:29.718 info Rebuild for adapter system.adapter.zigbee.0 not successful in 3 tries. Adapter will not be restarted again. Please execute "npm install --production" in adapter directory manually. host.IoBrokerSmartHome 2022-02-08 06:25:29.718 error instance system.adapter.zigbee.0 terminated with code 1 (JS_CONTROLLER_STOPPED) host.IoBrokerSmartHome 2022-02-08 06:25:29.717 error Caught by controller[0]: } host.IoBrokerSmartHome 2022-02-08 06:25:29.717 error Caught by controller[0]: code: 'ERR_DLOPEN_FAILED' host.IoBrokerSmartHome 2022-02-08 06:25:29.716 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:950:32) { host.IoBrokerSmartHome 2022-02-08 06:25:29.716 error Caught by controller[0]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10) host.IoBrokerSmartHome 2022-02-08 06:25:29.716 error Caught by controller[0]: at Module._compile (internal/modules/cjs/loader.js:1085:14) host.IoBrokerSmartHome 2022-02-08 06:25:29.715 error Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/lib/linux.js:2:36) host.IoBrokerSmartHome 2022-02-08 06:25:29.715 error Caught by controller[0]: at bindings (/opt/iobroker/node_modules/bindings/bindings.js:112:48) host.IoBrokerSmartHome 2022-02-08 06:25:29.714 error Caught by controller[0]: at require (internal/modules/cjs/helpers.js:101:18) host.IoBrokerSmartHome 2022-02-08 06:25:29.714 error Caught by controller[0]: at Module.require (internal/modules/cjs/loader.js:974:19) host.IoBrokerSmartHome 2022-02-08 06:25:29.713 error Caught by controller[0]: at Function.Module._load (internal/modules/cjs/loader.js:790:12) host.IoBrokerSmartHome 2022-02-08 06:25:29.713 error Caught by controller[0]: at Module.load (internal/modules/cjs/loader.js:950:32) host.IoBrokerSmartHome 2022-02-08 06:25:29.712 error Caught by controller[0]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1144:18) host.IoBrokerSmartHome 2022-02-08 06:25:29.712 error Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`). host.IoBrokerSmartHome 2022-02-08 06:25:29.712 error Caught by controller[0]: NODE_MODULE_VERSION 83. Please try re-compiling or re-installing host.IoBrokerSmartHome 2022-02-08 06:25:29.711 error Caught by controller[0]: NODE_MODULE_VERSION 72. This version of Node.js requires host.IoBrokerSmartHome 2022-02-08 06:25:29.711 error Caught by controller[0]: was compiled against a different Node.js version using host.IoBrokerSmartHome 2022-02-08 06:25:29.710 error Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.zigbee/node_modules/@serialport/bindings/build/Release/bindings.node' host.IoBrokerSmartHome 2022-02-08 06:25:29.709 error Caught by controller[0]: ^ host.IoBrokerSmartHome 2022-02-08 06:25:29.709 error Caught by controller[0]: throw e; host.IoBrokerSmartHome 2022-02-08 06:25:29.708 error Caught by controller[0]: /opt/iobroker/node_modules/bindings/bindings.js:121 host.IoBrokerSmartHome 2022-02-08 06:25:27.389 info instance system.adapter.zigbee.0 started with pid 10214 host.IoBrokerSmartHome 2022-02-08 06:25:23.624 info "system.adapter.zigbee.0" enabled -
@homecineplexx Ok, also ja in dem Fall braucht es einen rebuild. Am besten im /opt/iobroker ein "npm rebuil" ausführen. Das sollte das fixen.
Der "iobroker info" Fehler ist komisch. Der sollte nur passieren wenn er versucht die DB zwei mal zu öffnen ... läuft da irgendwas parallel?
-
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@homecineplexx Ok, also ja in dem Fall braucht es einen rebuild. Am besten im /opt/iobroker ein "npm rebuil" ausführen. Das sollte das fixen.
Der "iobroker info" Fehler ist komisch. Der sollte nur passieren wenn er versucht die DB zwei mal zu öffnen ... läuft da irgendwas parallel?
ob da etwas doppelt läuft, weiss ich nicht, wie find ich das raus?
also das "npm rebuild" war nicht sehr erfolgreich:
> iobroker.js-controller@4.0.4 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first Uncaught Rejection: Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at TCP.<anonymous> (net.js:686:12) Unable to subscribe to expiry Keyspace events from Redis Server: Connection is closed. Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed. Unable to subscribe to meta namespace "meta." changes: Connection is closed. Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! npm ERR! code ELIFECYCLE npm ERR! errno 24 npm ERR! iobroker.js-controller@4.0.4 install: `node iobroker.js setup first` npm ERR! Exit status 24 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.4 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/2022-02-08T07_47_46_047Z-debug.log root@IoBrokerSmartHome:/opt/iobroker# less /home/iobroker/.npm/_logs/2022-02-08T07_47_46_047Z-debug.log -
@homecineplexx
Lösch den npm cache mal.
Und eier nicht als root herum. -
@homecineplexx sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"!
Neee ich denke das hier ist die Ursache. Das JSONL File ist gelockt ... Und damit kann er die DB nicht öffnen. Ich sag mal so: Reboote mal ... oder finde raus welcher prozess das File lockt ...
@AlCalzone noch ne idee?
-
@thomas-braun said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
Und eier nicht als root herum
npm cache clear --force
und
das hab ich nun befolgt aber keine Änderungnode-pre-gyp WARN Using request for node-pre-gyp https download [lzma-native] Success: "/opt/iobroker/node_modules/iobroker.javascript/node_modules/lzma-native/binding-v4.0.6-node-v83-linux-x64/lzma_native.node" already installed Pass --update-binary to reinstall or --build-from-source to recompile > iobroker.javascript@5.2.21 postinstall /opt/iobroker/node_modules/iobroker.javascript > node ./install/installTypings.js Installing NodeJS typings... latest @types: 17, installed node: 14 > lzma-native@4.0.6 install /opt/iobroker/node_modules/iobroker.javascript/node_modules/lzma-native > node-pre-gyp install --fallback-to-build && rimraf build node-pre-gyp WARN Using request for node-pre-gyp https download [lzma-native] Success: "/opt/iobroker/node_modules/iobroker.javascript/node_modules/lzma-native/binding-v4.0.6-node-v83-linux-x64/lzma_native.node" already installed Pass --update-binary to reinstall or --build-from-source to recompile > iobroker.js-controller@4.0.4 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > iobroker.js-controller@4.0.4 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first Connection is closed. Uncaught Rejection: Error: States DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:579:23) at processTicksAndRejections (internal/process/task_queues.js:95:5) Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! npm ERR! code ELIFECYCLE npm ERR! errno 24 npm ERR! iobroker.js-controller@4.0.4 install: `node iobroker.js setup first` npm ERR! Exit status 24 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.4 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/2022-02-08T08_11_00_567Z-debug.log chris@IoBrokerSmartHome:/opt/iobroker$ -
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@homecineplexx sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"!
Neee ich denke das hier ist die Ursache. Das JSONL File ist gelockt ... Und damit kann er die DB nicht öffnen. Ich sag mal so: Reboote mal ... oder finde raus welcher prozess das File lockt ...
@AlCalzone noch ne idee?
reboot des systems hab ich durchgeführt
wenn du mir jetzt noch bitte sagen könntest, wie ich raus finde, was hier blockieren könnte...?chris@IoBrokerSmartHome:/opt/iobroker$ iobroker status (node:1354) Warning: Accessing non-existent property 'count' of module exports inside circular dependency (Use `node --trace-warnings ...` to show where the warning was created) (node:1354) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency (node:1354) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency (node:1354) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency iobroker is running on this host. Objects type: jsonl States type: jsonl -
@apollon77 sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@AlCalzone noch ne idee?
paar Sekunden warten. Das passiert eigentlich nur wenn innerhalb der letzen 10s der DB-Prozess abgeschmiert ist ohne die DB sauber zu schließen.
-
@alcalzone said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@apollon77 sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@AlCalzone noch ne idee?
paar Sekunden warten. Das passiert eigentlich nur wenn innerhalb der letzen 10s der DB-Prozess abgeschmiert ist ohne die DB sauber zu schließen.
also das warten wäre es nicht...hab ja gestern schon versucht und heute..also zeit hätte das teil ja genug.
ich finde auch das recht spannend (was auch immer redis damit zu tun hat):
node-pre-gyp WARN Using request for node-pre-gyp https download [lzma-native] Success: "/opt/iobroker/node_modules/iobroker.javascript/node_modules/lzma-native/binding-v4.0.6-node-v83-linux-x64/lzma_native.node" already installed Pass --update-binary to reinstall or --build-from-source to recompile > iobroker.js-controller@4.0.4 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.16 > iobroker.js-controller@4.0.4 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first Connection is closed. Uncaught Rejection: Error: States DB is not allowed to start in the current Multihost environment at Redis.<anonymous> (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:579:23) at processTicksAndRejections (internal/process/task_queues.js:95:5) Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! npm ERR! code ELIFECYCLE npm ERR! errno 24 npm ERR! iobroker.js-controller@4.0.4 install: `node iobroker.js setup first` npm ERR! Exit status 24 npm ERR! npm ERR! Failed at the iobroker.js-controller@4.0.4 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/2022-02-08T08_21_08_680Z-debug.log chris@IoBrokerSmartHome:/opt/iobroker$ -
Ok, kannst Du denn "iob setup first" generell aufrufen ... nicht im Rahmen des Rebuilds?
-
@homecineplexx Dann kann eigentlich nur ein anderer Controller/CLI-Prozess noch laufen, der die DB in Nutzung hat. @apollon77 ne Idee wie das sein kann?
-
@homecineplexx Das hietr ist auch komisch. Mach mal bitte in /opt/iobroker
node --trace-warnings node_modules/iobroker.js-controller/iobroker.js status -
@alcalzone sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@apollon77 ne Idee wie das sein kann?
Nope, müsste man prozessliste schauen
-
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@homecineplexx Das hietr ist auch komisch. Mach mal bitte in /opt/iobroker
node --trace-warnings node_modules/iobroker.js-controller/iobroker.js statuschris@IoBrokerSmartHome:/opt/iobroker$ node --trace-warnings node_modules/iobroker.js-controller/iobroker.js status iobroker is running on this host. Objects type: jsonl States type: jsonl -
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
iob setup first
ist das richtig so?
chris@IoBrokerSmartHome:/opt/iobroker$ iob setup first Uncaught Rejection: Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (events.js:520:26) at Socket.emit (events.js:400:28) at TCP.<anonymous> (net.js:686:12) Unable to subscribe to expiry Keyspace events from Redis Server: Connection is closed. Unable to subscribe to evicted Keyspace events from Redis Server: Connection is closed. Unable to subscribe to meta namespace "meta." changes: Connection is closed. Server Cannot start inMem-states on port 9000: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! -
@homecineplexx mmeeehhhhhhhh ... warum ises jetzt weg?
-
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@alcalzone sagte in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@apollon77 ne Idee wie das sein kann?
Nope, müsste man prozessliste schauen
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 740 iobroker 20 0 961420 391716 35652 R 90,1 7,7 15:51.29 io.javascript.0 648 iobroker 20 0 1071492 345812 35536 R 81,9 6,8 15:53.74 iobroker.js-con 2682 iobroker 20 0 773400 77984 32184 S 55,3 1,5 0:06.77 io.ical.0 812 iobroker 20 0 887992 320028 35728 S 37,2 6,3 7:16.57 io.javascript.1 1210 iobroker 20 0 691884 112144 31084 R 28,3 2,2 3:07.88 io.homepilot20. 834 iobroker 20 0 877164 302152 30764 S 28,0 5,9 5:04.49 io.javascript.2 827 iobroker 20 0 713120 117676 30932 S 21,1 2,3 4:32.82 io.influxdb.0 853 iobroker 20 0 717864 92828 30728 S 8,2 1,8 1:02.62 io.mqtt.0 1404 iobroker 20 0 699892 72076 31552 S 5,6 1,4 0:35.33 io.unifi.0 710 iobroker 20 0 1049460 161264 36348 S 3,6 3,2 0:48.42 io.admin.0 460 root 20 0 44256 4720 4228 S 3,0 0,1 0:00.57 systemd-journal 1047 iobroker 20 0 692692 62364 30720 S 1,6 1,2 0:04.51 io.text2command 725 iobroker 20 0 693964 63832 30628 S 1,3 1,3 0:12.87 io.history.0 782 iobroker 20 0 950172 66920 31624 S 1,3 1,3 0:13.74 io.telegram.1 797 iobroker 20 0 884356 66448 31632 S 1,3 1,3 0:13.21 io.telegram.2 766 iobroker 20 0 950200 67456 31492 S 1,0 1,3 0:14.05 io.telegram.0 1449 iobroker 20 0 811760 59540 31772 S 1,0 1,2 0:04.31 io.parser.0 1509 iobroker 20 0 692628 61876 31064 S 1,0 1,2 0:05.86 io.wled.0 667 root 20 0 250112 3036 2432 S 0,7 0,1 0:00.09 rsyslogd 994 iobroker 20 0 964656 68452 31804 S 0,7 1,3 0:15.78 io.alexa2.0 2667 iobroker 20 0 691740 59736 30804 S 0,7 1,2 0:03.60 io.meteoalarm.0 2710 chris 20 0 44932 3788 3144 R 0,7 0,1 0:00.09 top 7 root 20 0 0 0 0 R 0,3 0,0 0:01.62 rcu_sched 658 avahi 20 0 47132 3364 2956 S 0,3 0,1 0:00.75 avahi-daemon 751 iobroker 20 0 694264 61820 30584 S 0,3 1,2 0:04.74 io.scenes.0 1116 iobroker 20 0 669588 55876 30804 S 0,3 1,1 0:05.46 io.yeelight-2.0 1167 iobroker 20 0 968468 67660 31664 S 0,3 1,3 0:07.69 io.cloud.0 1 root 20 0 56888 6496 5112 S 0,0 0,1 0:01.73 systemd 2 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0,0 0,0 0:00.17 ksoftirqd/0 5 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kworker/0:0H 8 root 20 0 0 0 0 S 0,0 0,0 0:00.00 rcu_bh 9 root rt 0 0 0 0 S 0,0 0,0 0:00.00 migration/0 10 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 lru-add-drain 11 root rt 0 0 0 0 S 0,0 0,0 0:00.00 watchdog/0 12 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/0 13 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/1 14 root rt 0 0 0 0 S 0,0 0,0 0:00.00 watchdog/1 15 root rt 0 0 0 0 S 0,0 0,0 0:00.00 migration/1 16 root 20 0 0 0 0 S 0,0 0,0 0:00.67 ksoftirqd/1 18 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kworker/1:0H 19 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/2 20 root rt 0 0 0 0 S 0,0 0,0 0:00.00 watchdog/2 21 root rt 0 0 0 0 S 0,0 0,0 0:00.00 migration/2 22 root 20 0 0 0 0 S 0,0 0,0 0:00.17 ksoftirqd/2 24 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kworker/2:0H 25 root 20 0 0 0 0 S 0,0 0,0 0:00.00 cpuhp/3 -
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@homecineplexx mmeeehhhhhhhh ... warum ises jetzt weg?
ich hab keine ahnung...das darfst mich nicht fragen
-
@homecineplexx ok, dann beende mal iobroker bevor du den rebuild machst ... irgendwas ist dennoch phishy weil an sich sollte er keine neuen states DB verbinden wenn schon eine an ist
-
@apollon77 said in [How-to] Node.js für ioBroker richtig updaten - 2021 Edition:
@homecineplexx ok, dann beende mal iobroker bevor du den rebuild machst ... irgendwas ist dennoch phishy weil an sich sollte er keine neuen states DB verbinden wenn schon eine an ist
soviel dazu
Thank you for using serialport! If you rely on this package, please consider supporting our open collective: > https://opencollective.com/serialport/donate > @serialport/bindings@9.0.4 install /opt/iobroker/node_modules/@serialport/bindings > prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild > serialport@6.2.2 install /opt/iobroker/node_modules/serialport > prebuild-install || node-gyp rebuild prebuild-install WARN install No prebuilt binaries found (target=14.19.0 runtime=node arch=x64 platform=linux) make: Verzeichnis „/opt/iobroker/node_modules/serialport/build“ wird betreten CXX(target) Release/obj.target/serialport/src/serialport.o ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/serialport.cpp:41:48: error: no matching function for call to ‘v8::Value::ToString()’ v8::String::Utf8Value path(info[0]->ToString()); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2810:44: note: candidate: v8::MaybeLocal<v8::String> v8::Value::ToString(v8::Local<v8::Context>) const V8_WARN_UNUSED_RESULT MaybeLocal<String> ToString( ^~~~~~~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2810:44: note: candidate expects 1 argument, 0 provided ../src/serialport.cpp:48:53: error: no matching function for call to ‘v8::Value::ToObject()’ v8::Local<v8::Object> options = info[1]->ToObject(); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2822:44: note: candidate: v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject( ^~~~~~~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2822:44: note: candidate expects 1 argument, 0 provided ../src/serialport.cpp: In function ‘void EIO_AfterOpen(uv_work_t*)’: ../src/serialport.cpp:95:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(2, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/serialport.cpp:113:53: error: no matching function for call to ‘v8::Value::ToObject()’ v8::Local<v8::Object> options = info[1]->ToObject(); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2822:44: note: candidate: v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject( ^~~~~~~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2822:44: note: candidate expects 1 argument, 0 provided ../src/serialport.cpp: In function ‘void EIO_AfterUpdate(uv_work_t*)’: ../src/serialport.cpp:150:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(1, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘void EIO_AfterClose(uv_work_t*)’: ../src/serialport.cpp:188:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(1, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘void EIO_AfterFlush(uv_work_t*)’: ../src/serialport.cpp:231:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(1, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/serialport.cpp:250:53: error: no matching function for call to ‘v8::Value::ToObject()’ v8::Local<v8::Object> options = info[1]->ToObject(); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2822:44: note: candidate: v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject( ^~~~~~~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:2822:44: note: candidate expects 1 argument, 0 provided ../src/serialport.cpp: In function ‘void EIO_AfterSet(uv_work_t*)’: ../src/serialport.cpp:285:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(1, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’: ../src/serialport.cpp:329:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’ results->Set(Nan::New<v8::String>("cts").ToLocalChecked(), Nan::New<v8::Boolean>(data->cts)); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate expects 3 arguments, 2 provided /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate expects 3 arguments, 2 provided ../src/serialport.cpp:330:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’ results->Set(Nan::New<v8::String>("dsr").ToLocalChecked(), Nan::New<v8::Boolean>(data->dsr)); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate expects 3 arguments, 2 provided /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate expects 3 arguments, 2 provided ../src/serialport.cpp:331:96: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::FactoryBase<v8::Boolean>::return_t)’ results->Set(Nan::New<v8::String>("dcd").ToLocalChecked(), Nan::New<v8::Boolean>(data->dcd)); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate expects 3 arguments, 2 provided /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate expects 3 arguments, 2 provided ../src/serialport.cpp:336:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(2, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’: ../src/serialport.cpp:378:106: error: no matching function for call to ‘v8::Object::Set(v8::Local<v8::String>, Nan::imp::IntegerFactory<v8::Integer>::return_t)’ results->Set(Nan::New<v8::String>("baudRate").ToLocalChecked(), Nan::New<v8::Integer>(data->baudRate)); ^ In file included from /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:67:0, from ../../nan/nan.h:58, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3670:37: note: candidate expects 3 arguments, 2 provided /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate: v8::Maybe<bool> v8::Object::Set(v8::Local<v8::Context>, uint32_t, v8::Local<v8::Value>) V8_WARN_UNUSED_RESULT Maybe<bool> Set(Local<Context> context, uint32_t index, ^~~ /home/iobroker/.cache/node-gyp/14.19.0/include/node/v8.h:3673:37: note: candidate expects 3 arguments, 2 provided ../src/serialport.cpp:383:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(2, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: In function ‘void EIO_AfterDrain(uv_work_t*)’: ../src/serialport.cpp:424:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value>*) const’ is deprecated [-Wdeprecated-declarations] data->callback.Call(1, argv); ^ In file included from ../src/./serialport.h:6:0, from ../src/serialport.cpp:1: ../../nan/nan.h:1744:3: note: declared here Call(int argc, v8::Local<v8::Value> argv[]) const { ^~~~ ../src/serialport.cpp: At global scope: ../src/serialport.cpp:460:17: error: variable or field ‘init’ declared void void init(v8::Handle<v8::Object> target) { ^~~~~~ ../src/serialport.cpp:460:13: error: ‘Handle’ is not a member of ‘v8’ void init(v8::Handle<v8::Object> target) { ^~ ../src/serialport.cpp:460:34: error: expected primary-expression before ‘>’ token void init(v8::Handle<v8::Object> target) { ^ ../src/serialport.cpp:460:36: error: ‘target’ was not declared in this scope void init(v8::Handle<v8::Object> target) { ^~~~~~ In file included from ../../nan/nan.h:58:0, from ../src/./serialport.h:6, from ../src/serialport.cpp:1: ../src/serialport.cpp:485:25: error: ‘init’ was not declared in this scope NODE_MODULE(serialport, init); ^ /home/iobroker/.cache/node-gyp/14.19.0/include/node/node.h:793:36: note: in definition of macro ‘NODE_MODULE_X’ (node::addon_register_func) (regfunc), \ ^~~~~~~ ../src/serialport.cpp:485:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(serialport, init); ^~~~~~~~~~~ serialport.target.mk:114: die Regel für Ziel „Release/obj.target/serialport/src/serialport.o“ scheiterte make: *** [Release/obj.target/serialport/src/serialport.o] Fehler 1 make: Verzeichnis „/opt/iobroker/node_modules/serialport/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:400:28) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:282: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/serialport gyp ERR! node -v v14.19.0 gyp ERR! node-gyp -v v5.1.0 gyp ERR! not ok npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! serialport@6.2.2 install: `prebuild-install || node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the serialport@6.2.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/2022-02-08T08_35_50_311Z-debug.log chris@IoBrokerSmartHome:/opt/iobroker$
