Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[George_Best]

Neuer Versuch - und wieder:

2025-11-12 17:36:08.400  - info: web.0 (28941) starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v22.21.0, js-controller: 7.0.7
2025-11-12 17:36:08.571  - info: web.0 (28941) socket.io server listening on port 8082
2025-11-12 17:36:08.572  - info: web.0 (28941) Connecting extension "habpanel/lib/habpanelapi.js"
2025-11-12 17:36:08.572  - info: web.0 (28941) habpanel server listening on port 8082
2025-11-12 17:36:08.573  - info: web.0 (28941) habpanel web extension - Install extension on /rest/habpanel/
2025-11-12 17:36:08.575  - info: web.0 (28941) http server listening on port 8082
2025-11-12 17:36:10.873  - error: host.ioBroker-V2 uncaught exception: Could not determine controller directory
2025-11-12 17:36:10.873  - error: host.ioBroker-V2 Error: Could not determine controller directory
    at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11)
    at Module.getAdapterDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1306:37)
    at startInstance (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:3219:30)

Es scheint fast so, als wird immer der js-controller gekillt....

Hat jemand eine Idee wie ich das lösen kann?

[Ro75]

@george_best

nodejs modules from github:     2
|   `-- xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc
| +-- tplink-smarthome-api@5.0.0 invalid: "https://github.com/arteck/tplink-smarthome-api/tarball/08bcca9334c701b60d1eeb18b0ec72350aa3bf7a" from node_modules/iobroker.hs100
 

Was ist das? Woher kommt das?

Ro75.

[George_Best]

@ro75
ersteres ist wohl vom hometmatic adapter
letzeres ist ein Adapter von TP-Link für smarte Steckdosen

[Ro75]

@george_best mir geht es mehr um das "invalid"

Ro75.

[George_Best]

@ro75
woher hast du die Zeilen genau?

Weil der npm-tree am Anfang war als der js-controller nicht mehr da war. Da war/ist so ziemlich alles auf "invalid"

[Ro75]

@george_best sagte in iob fix und iob diag ohne Reaktion:

woher hast du die Zeilen genau?

aus deinem iob diag log

Ro75.

[George_Best]

@ro75
ok.

Adapter mal löschen? Neu installieren?

[Ro75]

@george_best keine Ahnung. Auf alle Fälle, die, die man nicht (mehr) braucht können auch weg. Weniger Last, weniger Probleme.

Ro75.

[Thomas Braun]

@george_best sagte in iob fix und iob diag ohne Reaktion:

├── semver@5.7.2

├── semver@5.7.2
└── yargs@7.1.2
iobroker.inst@2.0.2 /opt/iobroker
├─┬ fs-extra@7.0.1

Die Stelle schau auch komisch aus...
Bitte NICHT die LogInPrompts löschen und IMMER die vollständigen Ein- und Ausgaben posten. Man kann sich ohne die Dinger als Helfer nur schlecht durch die zusammenkopierten Ausgaben hangeln.

[George_Best]

hm... es läuft nun schon einige Minuten stabil...
Möglicherweise war es der HS100 Adapter

[Ro75]

@george_best der HS100 läuft bei mir. Installiere den, falls du den brauchst, einfach mal neu.

Ro75.

[Thomas Braun]

@george_best

Du kannst auch mal schauen, was da passiert:

cd /opt/iobroker && npm ci

Wird was länger laufen, vermutlich.

[George_Best]

@thomas-braun

Ich glaube das sieht nicht gut aus:

jonny@ioBroker-V2:/opt/iobroker$ cd /opt/iobroker && npm ci
[sudo] Passwort für jonny:
npm warn old lockfile
npm warn old lockfile The package-lock.json file was created with an old version of npm,
npm warn old lockfile so supplemental metadata must be fetched from the registry.
npm warn old lockfile
npm warn old lockfile This is a one-time fix-up, please be patient...
npm warn old lockfile
npm error code EUSAGE
npm error
npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm error
npm error Missing: @iobroker-javascript.0/moment@2.30.1 from lock file
npm error Missing: @iobroker-javascript.0/moment-parseformat@4.0.0 from lock file
npm error Missing: iobroker.accuweather@2.1.1 from lock file
npm error Invalid: lock file's iobroker.admin@3.5.10 does not satisfy iobroker.admin@7.7.19
npm error Missing: iobroker.alias-manager@2.0.0 from lock file
npm error Missing: iobroker.amazon-dash@1.2.0 from lock file
npm error Missing: iobroker.chromecast@4.0.0 from lock file
npm error Missing: iobroker.cloud@5.0.1 from lock file
npm error Missing: iobroker.daswetter@3.2.3 from lock file
npm error Missing: iobroker.deconz@1.6.4 from lock file
npm error Missing: iobroker.devices@1.2.8 from lock file
npm error Invalid: lock file's iobroker.discovery@1.2.4 does not satisfy iobroker.discovery@5.0.0
npm error Missing: iobroker.email@2.0.4 from lock file
npm error Missing: iobroker.flot@1.12.0 from lock file
npm error Missing: iobroker.fronius@2.1.1 from lock file
npm error Missing: iobroker.fronius-solarweb@0.0.3 from lock file
npm error Missing: iobroker.frontier_silicon@0.5.0 from lock file
npm error Missing: iobroker.habpanel@0.5.0 from lock file
npm error Missing: iobroker.history@3.0.1 from lock file
npm error Missing: iobroker.hm-rega@5.1.0 from lock file
npm error Missing: iobroker.hm-rpc@2.0.2 from lock file
npm error Missing: iobroker.hs100@3.0.5 from lock file
npm error Missing: iobroker.icons-addictive-flavour-png@0.1.0 from lock file
npm error Missing: iobroker.icons-fatcow-hosting@0.1.0 from lock file
npm error Missing: iobroker.icons-icons8@0.0.1 from lock file
npm error Missing: iobroker.icons-material-png@0.1.0 from lock file
npm error Missing: iobroker.icons-material-svg@0.1.0 from lock file
npm error Missing: iobroker.icons-mfd-png@1.2.1 from lock file
npm error Missing: iobroker.icons-mfd-svg@1.2.0 from lock file
npm error Missing: iobroker.icons-open-icon-library-png@0.1.2 from lock file
npm error Missing: iobroker.icons-ultimate-png@1.0.1 from lock file
npm error Missing: iobroker.influxdb@4.0.2 from lock file
npm error Missing: iobroker.info@2.0.0 from lock file
npm error Missing: iobroker.iot@5.0.7 from lock file
npm error Missing: iobroker.javascript@8.9.2 from lock file
npm error Invalid: lock file's iobroker.js-controller@1.4.2 does not satisfy iobroker.js-controller@7.0.7
npm error Missing: iobroker.mihome-vacuum@5.2.0 from lock file

==> weitere ist im file.2025-11-12T17_36_48_294Z-debug-0.log

Oder hätte ich iobroker vorher stoppen sollen?

[Thomas Braun]

@george_best sagte in iob fix und iob diag ohne Reaktion:

npm error npm ci can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with npm install before continuing.

Das dürfte das auslösende Moment sein.

[Thomas Braun]

@george_best sagte in iob fix und iob diag ohne Reaktion:

npm error Invalid: lock file's iobroker.js-controller@1.4.2 does not satisfy iobroker.js-controller@7.0.7

Ist die Installation echt so alt?

[George_Best]

@thomas-braun

Naja - schon ein paar Jährchen...

Wie kann ich das lösen?

Ich kann auch aktuell keinen Adapter bzw. Instanz mehr installieren:

Installing iobroker.lg-ess-home@0.4.1... (System call)

npm error code ENOTEMPTYnpm error syscall rename

npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-11-12T17_47_52_218Z-debug-0.log

Try to solve ENOTEMPTY error automatically

Could not handle ENOTEMPTY, because no deletable files were foundnpm error code ENOTEMPTYnpm error syscall renamenpm error path /opt/iobroker/node_modules/abbrevnpm error dest /opt/iobroker/node_modules/.abbrev-5eNud0FYnpm error errno -39npm error ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abbrev' -> '/opt/iobroker/node_modules/.abbrev-5eNud0FY'npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-11-12T17_47_52_218Z-debug-0.loghost.ioBroker-V2 Cannot install iobroker.lg-ess-home@0.4.1: 217

ERROR: Process exited with code 25

[Thomas Braun]

@george_best

npm i

im Verzeichnis /opt/iobroker probieren.

[George_Best]

@thomas-braun

hm... irgendwie auch immer die gleiche Fehlermeldung:

jonny@ioBroker-V2:/opt/iobroker$ npm i
npm error code ENOTEMPTY
npm error syscall rename
npm error path /opt/iobroker/node_modules/abbrev
npm error dest /opt/iobroker/node_modules/.abbrev-5eNud0FY
npm error errno -39
npm error ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abbrev' -> '/opt/iobroker/node_modules/.abbrev-5eNud0FY'
npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2025-11-12T17_50_28_886Z-debug-0.log

[Thomas Braun]

@george_best

Da hilft ein

iob stop
iob fix

[George_Best]

@thomas-braun
Ok - sieht das jetzt gut aus?

jonny@ioBroker-V2:/opt/iobroker$ npm i
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 inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated lodash.get@4.4.2: This package is deprecated. Use the optional chaining (?.) operator instead.
npm warn deprecated uid-number@0.0.6: This package is no longer supported.
npm warn deprecated npmlog@5.0.1: This package is no longer supported.
npm warn deprecated npmlog@6.0.2: This package is no longer supported.
npm warn deprecated lodash.isequal@4.5.0: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
npm warn deprecated lodash.clone@4.5.0: This package is deprecated. Use structuredClone instead.
npm warn deprecated har-validator@5.1.5: this library is no longer supported
npm warn deprecated npmlog@4.1.2: This package is no longer supported.
npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported.
npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported.
npm warn deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
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 gauge@3.0.2: This package is no longer supported.
npm warn deprecated gauge@4.0.4: This package is no longer supported.
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 gauge@2.7.4: This package is no longer supported.
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 deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0

> iobroker.inst@2.0.2 install
> node lib/checkVersions.js

NPM version: 10.9.4

> iobroker.inst@2.0.2 postinstall
> node lib/install.js

lib/install.js is not being run as part of an installation - skipping...

added 1019 packages, and changed 826 packages in 3m

205 packages are looking for funding
  run `npm fund` for details