Update js-controller - "nodejs is NOT correctly installed"

George_Best

iobroker del icons-open-icon-library-png

gings schon ziemlich rund

Delete adapter "icons-open-icon-library-png"
host.ioBroker-V2 Counted 1 instances of icons-open-icon-library-png
host.ioBroker-V2 Counted 1 meta of icons-open-icon-library-png
host.ioBroker-V2 Counted 1 adapter for icons-open-icon-library-png
host.ioBroker-V2 Counted 1 states of system.adapter.icons-open-icon-library-png
host.ioBroker-V2 Counted 1 states (system.adapter.icons-open-icon-library-png.*) from states
host.ioBroker-V2 file icons-open-icon-library-png deleted
host.ioBroker-V2 file icons-open-icon-library-png.admin deleted
host.ioBroker-V2 object icons-open-icon-library-png deleted
host.ioBroker-V2 object icons-open-icon-library-png.admin deleted
host.ioBroker-V2 Deleting 4 object(s).
host.ioBroker-V2 Deleting 1 state(s).
Error deleting adapter icons-open-icon-library-png from disk: host.ioBroker-V2: Cannot uninstall iobroker.icons-open-icon-library-png: 1
You might have to delete it yourself!

Es gab dann einiges an errors im iobroker-log:

15786	2023-11-02 15:39:10.158	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather.html: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather.html'

vis.0
15786	2023-11-02 15:39:10.158	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/jquery.mousewheel.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/jquery.mousewheel.js'

vis.0
15786	2023-11-02 15:39:10.156	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/globalize.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/globalize.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/jquery.event.drag.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/jquery.event.drag.js'

vis.0
15786	2023-11-02 15:39:10.152	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/globalize.culture.en-US.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/lib/globalize.culture.en-US.js'

vis.0
15786	2023-11-02 15:39:10.152	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.touchNavigate.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.touchNavigate.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.uiConstants.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.uiConstants.js'

vis.0
15786	2023-11-02 15:39:10.151	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.time.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.time.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.touch.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.touch.js'

vis.0
15786	2023-11-02 15:39:10.151	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.symbol.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.symbol.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.threshold.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.threshold.js'

vis.0
15786	2023-11-02 15:39:10.150	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.selection.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.selection.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.stack.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.stack.js'

vis.0
15786	2023-11-02 15:39:10.150	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.resize.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.resize.js'Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.saturated.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.saturated.js'

vis.0
15786	2023-11-02 15:39:10.149	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.pie.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.pie.js'

vis.0
15786	2023-11-02 15:39:10.149	error	Error: Cannot upload /opt/iobroker/node_modules/iobroker.vis/www/widgets/weather/lib/js/flot/jquery.flot.navigate.js: ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobr

George_Best

Hab ich irgendwie die Chance mein ioBroker ohne komplette Neuinstallation wieder hinzubekommen?

Thomas Braun

@george_best

iob update
iobroker upgrade icons-open-icon-library-png@0.1.2
iobroker upgrade vis-materialdesign@vis-materialdesign@0.5.9

versuchen.

George_Best

@thomas-braun sagte in Update js-controller - "nodejs is NOT correctly installed":

icons-open

iobroker upgrade icons-open-icon-library-png@0.1.2

Habe ich gerade gemacht. Offensichtlich habe ich - wie auch immer - für diesen Adapter eine Version höher installiert als verfügbar (installiert: 1.0.3, verfügbar 1.02.). Wie auch immer - das Upgrade hat dann wohl einen "Downgrade" auf 1.0.2 gemacht, was auch erfolgreich durchlief.

Aber dies hat mir irgendwie den js-controller zerschossen:

iobroker status

node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.18.2

Ich habe jetzt eine Rollback gemacht damit das System erstmal wieder läuft. Gibt es noch eine Idee?

Thomas Braun

@george_best

Den js-controller nochmal drüber installieren.

George_Best

@thomas-braun mit

sudo -H -u iobroker npm install iobroker.js-controller

?

Thomas Braun

@george_best
Ja, aber im richtigen Verzeichnis.

Vorher

cd /opt/iobroker

George_Best

@thomas-braun sieht leider nicht so gut as:

npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
npm ERR! dest /opt/iobroker/node_modules/.iobroker.js-controller-7Q8bmsba
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/iobroker.js-controller' -> '/opt/iobroker/node_modules/.iobroker.js-controller-7Q8bmsba'

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-03T10_47_37_114Z-debug-0.log

Das Log-file: 2023-11-03T10_47_43_654Z-debug-0.log

Thomas Braun

@george_best

iob stop
iob fix

George_Best

@thomas-braun
iob fix:

library: loaded
Library version=2023-10-13

==========================================================================

    Welcome to the ioBroker installation fixer!
    Script version: 2023-10-13

    You might need to enter your password a couple of times.

==========================================================================


==========================================================================
    Installing prerequisites (1/5)
==========================================================================

Ign:1 http://security.debian.org/debian-security bullseye/updates InRelease
OK:2 http://deb.debian.org/debian bullseye InRelease
Ign:3 http://security.debian.org/debian-security bullseyeupdates InRelease
OK:4 http://deb.debian.org/debian bullseye-updates InRelease
OK:5 http://deb.debian.org/debian bullseye-backports InRelease
Fehl:6 http://security.debian.org/debian-security bullseye/updates Release
  404  Not Found [IP: 199.232.190.132 80]
Fehl:7 http://security.debian.org/debian-security bullseyeupdates Release
  404  Not Found [IP: 199.232.190.132 80]
OK:8 https://deb.nodesource.com/node_18.x nodistro InRelease
Holen:9 https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease [24,5 kB]
Fehl:9 https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease
  Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 8E61C2AB9A6D1557
Paketlisten werden gelesen… Fertig
E: Das Depot »http://security.debian.org/debian-security bullseye/updates Release« enthält keine Release-Datei.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
E: Das Depot »http://security.debian.org/debian-security bullseyeupdates Release« enthält keine Release-Datei.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
W: GPG-Fehler: https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 8E61C2AB9A6D1557
E: Das Depot »https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease« ist nicht signiert.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).

==========================================================================
    Checking ioBroker user and directory permissions (2/5)
==========================================================================

Created /etc/sudoers.d/iobroker
Fixing directory permissions...

==========================================================================
    Check and cleanup npm temporary directories (3/5)
==========================================================================

Done.

==========================================================================
    Database maintenance (4/5)
==========================================================================

Checking for uncompressed JSONL databases... This might take a while!

Compressing /opt/iobroker/iobroker-data/states.jsonl
Compressing /opt/iobroker/iobroker-data/objects.jsonl
Compressed 2 JSONL files. Done

==========================================================================
    Checking autostart (5/5)
==========================================================================

Enabling autostart...
Autostart enabled!

==========================================================================

    Your installation was fixed successfully
    Run iobroker start to start ioBroker again!

==========================================================================

sudo -H -u iobroker npm install iobroker.js-controller

npm WARN skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.esphome.git
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/raw-socket',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/raw-socket'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/raw-socket'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/raw-socket',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/raw-socket'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/raw-socket'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/node-snap7',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/node-snap7'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/node-snap7'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/pcap',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/pcap'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/pcap'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/node-snap7',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/node-snap7'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/node-snap7'
npm WARN cleanup     }
npm WARN cleanup   ],
npm WARN cleanup   [
npm WARN cleanup     '/opt/iobroker/node_modules/pcap',
npm WARN cleanup     [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/pcap'] {
npm WARN cleanup       errno: -39,
npm WARN cleanup       code: 'ENOTEMPTY',
npm WARN cleanup       syscall: 'rmdir',
npm WARN cleanup       path: '/opt/iobroker/node_modules/pcap'
npm WARN cleanup     }
npm WARN cleanup   ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path /opt/iobroker/node_modules/node-libcurl
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install --fallback-to-build
npm ERR! Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node --module_name=node_libcurl --module_path=/opt/iobroker/node_modules/node-libcurl/lib/binding --napi_version=9 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v108' (1)
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@1.0.5
npm ERR! node-pre-gyp info using node@18.18.2 | linux | x64
npm ERR! node-pre-gyp info check checked for "/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node" (not found)
npm ERR! node-pre-gyp http GET https://github.com/JCMais/node-libcurl/releases/download/v2.3.4/node_libcurl-v2.3.4-node-v108-linux-x64-glibc.tar.gz
npm ERR! node-pre-gyp ERR! install response status 404 Not Found on https://github.com/JCMais/node-libcurl/releases/download/v2.3.4/node_libcurl-v2.3.4-node-v108-linux-x64-glibc.tar.gz
npm ERR! node-pre-gyp WARN Pre-built binaries not installable for node-libcurl@2.3.4 and node@18.18.2 (node-v108 ABI, glibc) (falling back to source compile with node-gyp)
npm ERR! node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/JCMais/node-libcurl/releases/download/v2.3.4/node_libcurl-v2.3.4-node-v108-linux-x64-glibc.tar.gz
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@9.4.0
npm ERR! gyp info using node@18.18.2 | linux | x64
npm ERR! gyp info ok
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using node-gyp@9.4.0
npm ERR! gyp info using node@18.18.2 | linux | x64
npm ERR! gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
npm ERR! gyp info spawn args   'binding.gyp',
npm ERR! gyp info spawn args   '-f',
npm ERR! gyp info spawn args   'make',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/opt/iobroker/node_modules/node-libcurl/build/config.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args   '-I',
npm ERR! gyp info spawn args   '/home/iobroker/.cache/node-gyp/18.18.2/include/node/common.gypi',
npm ERR! gyp info spawn args   '-Dlibrary=shared_library',
npm ERR! gyp info spawn args   '-Dvisibility=default',
npm ERR! gyp info spawn args   '-Dnode_root_dir=/home/iobroker/.cache/node-gyp/18.18.2',
npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/home/iobroker/.cache/node-gyp/18.18.2/<(target_arch)/node.lib',
npm ERR! gyp info spawn args   '-Dmodule_root_dir=/opt/iobroker/node_modules/node-libcurl',
npm ERR! gyp info spawn args   '-Dnode_engine=v8',
npm ERR! gyp info spawn args   '--depth=.',
npm ERR! gyp info spawn args   '--no-parallel',
npm ERR! gyp info spawn args   '--generator-output',
npm ERR! gyp info spawn args   'build',
npm ERR! gyp info spawn args   '-Goutput_dir=.'
npm ERR! gyp info spawn args ]
npm ERR! Could not run curl-config, please make sure libcurl dev package is installed.
npm ERR! Output: /bin/sh: 1: curl-config: not found
npm ERR!
npm ERR! gyp: Call to 'node /opt/iobroker/node_modules/node-libcurl/scripts/curl-config.js --prefix' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: `gyp` failed with exit code: 1
npm ERR! gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:325:16)
npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:292:12)
npm ERR! gyp ERR! System Linux 5.10.0-26-amd64
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node" "--module_name=node_libcurl" "--module_path=/opt/iobroker/node_modules/node-libcurl/lib/binding" "--napi_version=9" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v108"
npm ERR! gyp ERR! cwd /opt/iobroker/node_modules/node-libcurl
npm ERR! gyp ERR! node -v v18.18.2
npm ERR! gyp ERR! node-gyp -v v9.4.0
npm ERR! gyp ERR! not ok
npm ERR! node-pre-gyp ERR! build error
npm ERR! 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 configure --fallback-to-build --module=/opt/iobroker/node_modules/node-libcurl/lib/binding/node_libcurl.node --module_name=node_libcurl --module_path=/opt/iobroker/node_modules/node-libcurl/lib/binding --napi_version=9 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v108' (1)
npm ERR! node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-libcurl/node_modules/@mapbox/node-pre-gyp/lib/util/compile.js:89:23)
npm ERR! node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:517:28)
npm ERR! node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1098:16)
npm ERR! node-pre-gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:303:5)
npm ERR! node-pre-gyp ERR! System Linux 5.10.0-26-amd64
npm ERR! node-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/node-libcurl/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
npm ERR! node-pre-gyp ERR! cwd /opt/iobroker/node_modules/node-libcurl
npm ERR! node-pre-gyp ERR! node -v v18.18.2
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v1.0.5
npm ERR! node-pre-gyp ERR! not ok

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-03T11_01_57_465Z-debug-0.log

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

Thomas Braun

@george_best

Du hast auch Chaos in den Repos. Insbesondere im Security-Repo. Und das Speedtest-Rrpo muss auch angepasst werden. Sieht man sowas nicht beim üblichen System-Update?

sudo apt update
apt policy libcurl*

sagt?

George_Best

@thomas-braun
sudo apt update:

OK:1 http://deb.debian.org/debian bullseye InRelease
Ign:2 http://security.debian.org/debian-security bullseye/updates InRelease
OK:3 http://deb.debian.org/debian bullseye-updates InRelease
Ign:4 http://security.debian.org/debian-security bullseyeupdates InRelease
OK:5 http://deb.debian.org/debian bullseye-backports InRelease
Fehl:6 http://security.debian.org/debian-security bullseye/updates Release
  404  Not Found [IP: 199.232.190.132 80]
Fehl:7 http://security.debian.org/debian-security bullseyeupdates Release
  404  Not Found [IP: 199.232.190.132 80]
OK:8 https://deb.nodesource.com/node_18.x nodistro InRelease
Holen:9 https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease [24,5 kB]
Fehl:9 https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease
  Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 8E61C2AB9A6D1557
Paketlisten werden gelesen… Fertig
E: Das Depot »http://security.debian.org/debian-security bullseye/updates Release« enthält keine Release-Datei.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
E: Das Depot »http://security.debian.org/debian-security bullseyeupdates Release« enthält keine Release-Datei.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8).
W: GPG-Fehler: https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease: Die folgenden Signaturen konnten nicht überprüft werden, weil ihr öffentlicher Schlüssel nicht verfügbar ist: NO_PUBKEY 8E61C2AB9A6D1557
E: Das Depot »https://packagecloud.io/ookla/speedtest-cli/debian stretch InRelease« ist nicht signiert.
N: Eine Aktualisierung von solch einem Depot kann nicht auf eine sichere Art durchgeführt werden, daher ist es standardmäßig deaktiviert.
N: Weitere Details zur Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite

apt policy libcurl*

libcurl4-openssl-dev:
  Installiert:           (keine)
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
     7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl3:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl4:
  Installiert:           7.74.0-1.3+deb11u9
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
 *** 7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
libcurl3-gnutls:
  Installiert:           7.74.0-1.3+deb11u9
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
 *** 7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
libcurl-ocaml:
  Installiert:           (keine)
  Installationskandidat: 0.9.1-1+b4
  Versionstabelle:
     0.9.1-1+b4 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl3-openssl-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl3-gnutls-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl4-gnutls-dev:
  Installiert:           (keine)
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
     7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurlpp0:
  Installiert:           (keine)
  Installationskandidat: 0.8.1-3
  Versionstabelle:
     0.8.1-3 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl-ocaml-dev:
  Installiert:           (keine)
  Installationskandidat: 0.9.1-1+b4
  Versionstabelle:
     0.9.1-1+b4 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl-ocaml-30vr0:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurlpp-dev:
  Installiert:           (keine)
  Installationskandidat: 0.8.1-3
  Versionstabelle:
     0.8.1-3 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl-ssl-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl-ocaml-dev-30vr0:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl3-nss-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl3-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl4-dev:
  Installiert:           (keine)
  Installationskandidat: (keine)
  Versionstabelle:
libcurl4-doc:
  Installiert:           (keine)
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
     7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl3-nss:
  Installiert:           (keine)
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
     7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
libcurl4-nss-dev:
  Installiert:           (keine)
  Installationskandidat: 7.74.0-1.3+deb11u9
  Versionstabelle:
     7.88.1-10+deb12u3~bpo11+1 100
        100 http://deb.debian.org/debian bullseye-backports/main amd64 Packages
     7.74.0-1.3+deb11u9 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages

Thomas Braun

@george_best

Joh, ran an die Meldungen.
Danach:

sudo apt install libcurl4-gnutls-dev

George_Best

@thomas-braun

jonny@ioBroker-V2:/etc/apt/sources.list.d$ sudo apt update
OK:1 http://deb.debian.org/debian bullseye InRelease
OK:2 http://deb.debian.org/debian bullseye-updates InRelease
OK:3 http://deb.debian.org/debian bullseye-backports InRelease
OK:4 http://deb.debian.org/debian-security bullseye-security InRelease
OK:5 https://deb.nodesource.com/node_18.x nodistro InRelease
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 53 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.

jonny@ioBroker-V2:/etc/apt/sources.list.d$ sudo apt install libcurl4-gnutls-dev
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
  aspell-de-alt bsdmainutils cpp-8 dh-python fdisk geoip-database irqbalance libasan5 libbind9-140 libbind9-161
  libdbus-glib-1-2 libdns-export1104 libdns1104 libdns1110 libdns162 libevent-2.1-6 libgeoip1 libgl1-mesa-glx
  libicu57 libio-stringy-perl libisc-export1100 libisc1100 libisc1105 libisc160 libisccc140 libisccc161
  libisccfg140 libisccfg163 libisl19 libjson-c3 libjsoncpp1 liblwres141 liblwres161 libmpdec2 libnftables0 libnuma1
  libonig4 libperl5.24 libprocps7 libpython3.5 libpython3.5-dev libpython3.5-minimal libpython3.5-stdlib
  libpython3.7 libpython3.7-dev libpython3.7-minimal libpython3.7-stdlib libxt-dev python3-asn1crypto
  python3-entrypoints python3-jeepney python3-keyring python3-keyrings.alt python3-pyasn1 python3-pycryptodome
  python3-secretstorage python3-xdg python3.5 python3.5-dev python3.5-minimal python3.5-venv python3.7-minimal
  rename sgml-base tcpd usb.ids x11proto-input-dev x11proto-kb-dev xml-core
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
  libcurl3-gnutls
Vorgeschlagene Pakete:
  libcurl4-doc libgnutls28-dev libidn11-dev libkrb5-dev libldap2-dev librtmp-dev libssh2-1-dev
Die folgenden NEUEN Pakete werden installiert:
  libcurl4-gnutls-dev
Die folgenden Pakete werden aktualisiert (Upgrade):
  libcurl3-gnutls
1 aktualisiert, 1 neu installiert, 0 zu entfernen und 52 nicht aktualisiert.
Es müssen 778 kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 1.619 kB Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren? [J/n] j
Holen:1 http://deb.debian.org/debian-security bullseye-security/main amd64 libcurl3-gnutls amd64 7.74.0-1.3+deb11u10 [344 kB]
Holen:2 http://deb.debian.org/debian-security bullseye-security/main amd64 libcurl4-gnutls-dev amd64 7.74.0-1.3+deb11u10 [435 kB]
Es wurden 778 kB in 0 s geholt (4.014 kB/s).
Changelogs werden gelesen... Fertig
(Lese Datenbank ... 64938 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libcurl3-gnutls_7.74.0-1.3+deb11u10_amd64.deb ...
Entpacken von libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u10) über (7.74.0-1.3+deb11u9) ...
Vormals nicht ausgewähltes Paket libcurl4-gnutls-dev:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../libcurl4-gnutls-dev_7.74.0-1.3+deb11u10_amd64.deb ...
Entpacken von libcurl4-gnutls-dev:amd64 (7.74.0-1.3+deb11u10) ...
libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u10) wird eingerichtet ...
libcurl4-gnutls-dev:amd64 (7.74.0-1.3+deb11u10) wird eingerichtet ...
Trigger für libc-bin (2.31-13+deb11u6) werden verarbeitet ...
Trigger für man-db (2.9.4-2) werden verarbeitet ...

Thomas Braun

@george_best

In der /etc/apt/sources.list muss die Zeile bezüglich Security so aussehen:

deb http://deb.debian.org/debian-security/ bullseye-security main contrib non-free non-free-firmware

Alle anderen Zeilen mit Security drin müssen raus.
Dann die .list-Datei mit den Backports löschen. Liegt vermutlich in /etc/apt/sources.list.d
Und die .list-Datei zum Speedtest muss auch auf bullseye statt stretch lauten.

Thomas Braun

@george_best

Okay, hat sich überschnitten...

Die mehr als 50 Updates reinziehen!

sudo apt full-upgrade
sudo reboot

Vorher die Backports aber ausschalten.

George_Best

@thomas-braun sagte in Update js-controller - "nodejs is NOT correctly installed":

Dann die .list-Datei mit den Backports löschen. Liegt vermutlich in /etc/apt/sources.list.d
Und die .list-Datei zum Speedtest muss auch auf bullseye statt stretch lauten.

da liegt nur:

nodesource.list
ookla_speedtest-cli.list

In der sources.list sind diese Einträge drin:

deb http://deb.debian.org/debian bullseye-backports main
deb-src http://deb.debian.org/debian bullseye-backports main

Soll ich diese Einträge aus der sources.list rausnehmen?

Thomas Braun

@george_best

Ja. Backports will man eigentlich nicht verwenden.

George_Best

@thomas-braun Ich versuch mich mal nun wieder nach oben zu hangeln..

sudo -H -u iobroker npm install iobroker.js-controller

sagt nun:

npm WARN skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.esphome.git
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0
npm ERR! code 6
npm ERR! path /opt/iobroker/node_modules/iobroker.vis-google-fonts
npm ERR! command failed
npm ERR! command sh -c node main.js --install

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-11-03T12_24_45_263Z-debug-0.log

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

Qix- created this issue in visionmedia/debug

closed ReDos Vulnerability Regression Visibility Notice #797

mikeal created this issue in request/request

open Request’s Past, Present and Future #3142

George_Best

sehr seltsam... Beim 2.

sudo -H -u iobroker npm install iobroker.js-controller

wurde der js-controller nun installiert...

NEWS

Update js-controller - "nodejs is NOT correctly installed"

open Request’s Past, Present and Future #3142

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

open Request’s Past, Present and Future #3142

open Request’s Past, Present and Future #3142

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

open Request’s Past, Present and Future #3142

Support us

661
Online

31.7k
Users

79.7k
Topics

1.3m
Posts

NEWS

Update js-controller - "nodejs is NOT correctly installed"

open Request’s Past, Present and Future #3142

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

open Request’s Past, Present and Future #3142

open Request’s Past, Present and Future #3142

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

closed ReDos Vulnerability Regression Visibility Notice #797

open Request’s Past, Present and Future #3142

Support us

661Online

31.7kUsers

79.7kTopics

1.3mPosts

661
Online

31.7k
Users

79.7k
Topics

1.3m
Posts