nodejs -v && node -v && npm -v

npm rebuild canvas --build-from-source

Sieht gut aus, bis jetzt 3 Adapter erfolgreich geupdated. Danke.

cd /opt/iobroker
npm rebuild canvas --build-from-source

$ ./iobroker upgrade history
Update history from @1.8.7 to @1.9.6
NPM version: 6.13.4npm install iobroker.history@1.9.6 --loglevel error --prefix "/opt/iobroker" (System call)
../src/bmp/BMPParser.cc: In member function ‘void BMPParser::Parser::parse(uint8_t*, int, uint8_t*)’:../src/bmp/BMPParser.cc:189:16: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]   E(ptr - data > imgdOffset, "image data overlaps with another structure");
                ^../src/bmp/BMPParser.cc:10:25: note: in definition of macro ‘E’ #define E(cond, msg) if(cond) return setErr(msg)
                         ^../src/bmp/BMPParser.cc:204:27: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]   E(ptr - data + imgdSize > len, "not enough image data");
                           ^../src/bmp/BMPParser.cc:10:25: note: in definition of macro ‘E’ #define E(cond, msg) if(cond) return setErr(msg)
                         ^
../src/Canvas.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE Canvas::ToBuffer(Nan::NAN_METHOD_ARGS_TYPE)’:../src/Canvas.cc:415:26: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]     if (canvas->nBytes() > node::Buffer::kMaxLength) {                          ^
../src/Canvas.cc: At global scope:../src/Canvas.cc:935:1: fatal error: opening dependency file ./Release/.deps/Release/obj.target/canvas/src/Canvas.o.d.raw: Datei oder Verzeichnis nicht gefunden } ^
compilation terminated.
make: *** [Release/obj.target/canvas/src/Canvas.o] Error 1
gyp
 ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2gyp 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.9.24-v7+gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node" "--module_name=canvas" "--module_path=/opt/iobroker/node_modules/canvas/build/Release" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"
gyp ERR! cwd /opt/iobroker/node_modules/canvasgyp ERR! node -v v10.19.0gyp ERR! node-gyp -v v5.0.5gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/opt/iobroker/node_modules/canvas/build/Release/canvas.node --module_name=canvas --module_path=/opt/iobroker/node_modules/canvas/build/Release --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Linux 4.9.24-v7+node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp
 
ERR! UNCAUGHT EXCEPTION node-pre-gyp ERR! stack Error: ENOENT: no such file or directory, uv_cwdnode-pre-gyp ERR! stack     at errorMessage (/opt/iobroker/node_modules/node-pre-gyp/bin/node-pre-gyp:120:28)node-pre-gyp ERR! stack     at /opt/iobroker/node_modules/node-pre-gyp/bin/node-pre-gyp:86:7node-pre-gyp ERR! stack     at /opt/iobroker/node_modules/node-pre-gyp/lib/build.js:27:20node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:20)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)node-pre-gyp ERR! System Linux 4.9.24-v7+node-pre-gyp ERR!
 
command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"/opt/iobroker/node_modules/node-pre-gyp/bin/node-pre-gyp:120  log.error('cwd', process.cwd());                           ^Error: ENOENT: no such file or directory, uv_cwd    at errorMessage (/opt/iobroker/node_modules/node-pre-gyp/bin/node-pre-gyp:120:28)    at issueMessage (/opt/iobroker/node_modules/node-pre-gyp/bin/node-pre-gyp:126:3)    at process.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/bin/node-pre-gyp:111:3)    at process.emit (events.js:198:13)    at process._fatalException (internal/bootstrap/node.js:497:27)
npm ERR! code ELIFECYCLE
npm ERR! errno 7npm ERR! canvas@2.6.1 install: `node-pre-gyp install --fallback-to-build`npm ERR! Exit status 7
npm ERR! npm ERR! Failed at the canvas@2.6.1 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-05-16T23_26_17_232Z-debug.log
ERROR: host.ioBroker-RasPi Cannot install iobroker.history@1.9.6: 7
ERROR: process exited with code 25

sudo apt install libpixman-1-dev libpixman-1-0

Ja das steht etwas mit gyp: Call to 'pkg-config pixman-1 --libs' returned exit status 1 while in binding.gyp. while trying to load binding.gyp

Update fehlerfrei. Dann habe ich den Ping Adapter aktualisiert und siehe da, der Zigbee Adapter ist wieder 1.0.3

Man sieht nur das Ende vom Log ... !

Ist am Anfang eine Meldung mit " pixman- "

Update fehlerfrei. Dann habe ich den Ping Adapter aktualisiert und siehe da, der Zigbee Adapter ist wieder 1.0.3

Zum Mäuse melken

da das Aktualisieren im Webinterface nicht so sauber funktioniert,

Wie kommst du darauf bzw. Wie hat sich das denn geäußert?

Jetzt eine Erklärung kann ich dir auch nicht liefern da ohne jegliche logs hier keiner nachvollziehen kann was du auf welchem System (SW/HW) Gemacht hast.