iob fix und iob diag ohne Reaktion

Ro75

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

Ro75.

Thomas Braun

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

Thomas Braun

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

sieht das jetzt gut aus?

Ich würde sagen das geht in die richtige Richtung.
Gib mir nochmal ein

iob diag

George_Best

@thomas-braun

Oh nein...:cry: iobroker läuft wieder nicht an. iob fix lief schon drüber

jonny@ioBroker-V2:/opt/iobroker$ iob status
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0

iob diag:


========== Start marking the full check here ===========

```bash
Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 12 (bookworm)
 Static hostname: ioBroker-V2
       Icon name: computer-vm
         Chassis: vm 🖴
  Virtualization: kvm
          Kernel: Linux 6.1.0-41-amd64
    Architecture: x86-64
 Hardware Vendor: QEMU
  Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.16.1-0-g3208b098f51a-prebuilt.qemu.org
OS is similar to:

model name      : Common KVM processor
Docker          : false
Virtualization  : kvm
Kernel          : x86_64
Userland        : 64 bit

Systemuptime and Load:
 19:04:37 up  3:02,  2 users,  load average: 0.41, 0.73, 0.60
CPU threads: 8


*** LIFE CYCLE STATUS ***
Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time!

*** TIME AND TIMEZONES ***
               Local time: Wed 2025-11-12 19:04:37 CET
           Universal time: Wed 2025-11-12 18:04:37 UTC
                 RTC time: Wed 2025-11-12 18:04:37
                Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

*** Users and Groups ***
User that called 'iob diag':
jonny
HOME=/home/jonny
GROUPS=jonny adm cdrom floppy sudo audio dip video plugdev systemd-journal netdev iobroker

User that is running 'js-controller':
js-controller is not running

*** DISPLAY-SERVER SETUP ***
Display-Server:         false
Unit display-manager.service could not be found.
Display-Manager:
Desktop:
Session:                tty

*** MEMORY ***
               total        used        free      shared  buff/cache   available
Mem:             12G        528M        8.5G        565K        3.5G         11G
Swap:           4.3G          0B        4.3G
Total:           16G        528M         12G

Active iob-Instances:   0

        11644 M total memory
          503 M used memory
         1640 M active memory
         1318 M inactive memory
         8133 M free memory
          588 M buffer memory
         2732 M swap cache
         4093 M total swap
            0 M used swap
         4093 M free swap

*** top - Table Of Processes  ***
top - 19:04:37 up  3:02,  2 users,  load average: 0.41, 0.73, 0.60
Tasks: 123 total,   1 running, 122 sleeping,   0 stopped,   0 zombie
%Cpu(s): 33.3 us,  0.0 sy,  0.0 ni, 66.7 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  11644.7 total,   8133.2 free,    504.4 used,   3320.4 buff/cache
MiB Swap:   4094.0 total,   4094.0 free,      0.0 used.  11140.3 avail Mem

*** FAILED SERVICES ***

  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.


*** DMESG CRITICAL ERRORS ***
No critical errors detected

*** FILESYSTEM ***
Filesystem     Type      Size  Used Avail Use% Mounted on
udev           devtmpfs  5.7G     0  5.7G   0% /dev
tmpfs          tmpfs     1.2G  552K  1.2G   1% /run
/dev/sda1      ext4       28G  9.6G   17G  37% /
tmpfs          tmpfs     5.7G     0  5.7G   0% /dev/shm
tmpfs          tmpfs     5.0M     0  5.0M   0% /run/lock
tmpfs          tmpfs     1.2G     0  1.2G   0% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Wed Nov 12 16:01:54 2025] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
[Wed Nov 12 16:01:54 2025] EXT4-fs (sda1): re-mounted. Quota mode: none.

Show mounted filesystems:
TARGET SOURCE    FSTYPE OPTIONS
/      /dev/sda1 ext4   rw,relatime,errors=remount-ro

Files in neuralgic directories:

/var:
1.9G    /var/
889M    /var/cache
870M    /var/cache/apt
815M    /var/log
793M    /var/cache/apt/archives

Archived and active journals take up 790.1M in the file system.

/opt/iobroker/backups:
22M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
728M    /opt/iobroker/iobroker-data/
503M    /opt/iobroker/iobroker-data/files
166M    /opt/iobroker/iobroker-data/backup-objects
96M     /opt/iobroker/iobroker-data/files/vis-2
81M     /opt/iobroker/iobroker-data/files/vis

The five largest files in iobroker-data are:
25M     /opt/iobroker/iobroker-data/objects.jsonl
12M     /opt/iobroker/iobroker-data/objects.json.migrated
12M     /opt/iobroker/iobroker-data/objects.json.bak.migrated
9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json
4.6M    /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js

USB-Devices by-id:
USB-Sticks -  Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':

/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2195735-if00

Zigbee Network Settings on your coordinator/in nvbackup are:

zigbee.X
Extended Pan ID:
*** MASKED ***
Pan ID:
*** MASKED ***
Channel:
*** MASKED ***
Network Key:
*** MASKED ***

To unmask the settings run 'iob diag --unmask'


*** NodeJS-Installation ***

/usr/bin/nodejs         v22.21.0
/usr/bin/node           v22.21.0
/usr/bin/npm            10.9.4
/usr/bin/npx            10.9.4
/usr/bin/corepack       0.34.0

nodejs:
  Installed: 22.21.0-1nodesource1
  Candidate: 22.21.0-1nodesource1
  Version table:
 *** 22.21.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
        100 /var/lib/dpkg/status
     22.20.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.4.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     22.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages
     18.20.4+dfsg-1~deb12u1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        500 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages

Temp directories causing deletion problem: 0
No problems detected

Errors in npm tree: 0
No problems detected

Checking for nodejs vulnerability:


 █████  ██      ██           ██████   ██████   ██████  ██████         ██
██   ██ ██      ██          ██       ██    ██ ██    ██ ██   ██     ██  ██
███████ ██      ██          ██   ███ ██    ██ ██    ██ ██   ██         ██
██   ██ ██      ██          ██    ██ ██    ██ ██    ██ ██   ██     ██  ██
██   ██ ███████ ███████      ██████   ██████   ██████  ██████         ██



*** ioBroker-Installation ***

ioBroker Status
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0

Hosts:
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0

Core adapters versions
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0
js-controller:
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0
admin:
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0
javascript:

nodejs modules from github:     0

Adapter State


Enabled adapters with bindings

ioBroker-Repositories
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0

Installed ioBroker-Adapters
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0

Objects and States
Please stand by - This may take a while
Objects:        0
States:         0

*** OS-Repositories and Updates ***
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name
tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      0          17410      736/exim4
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          15485      553/sshd: /usr/sbin
tcp6       0      0 ::1:25                  :::*                    LISTEN      0          17411      736/exim4
tcp6       0      0 :::22                   :::*                    LISTEN      0          15487      553/sshd: /usr/sbin
udp        0      0 0.0.0.0:35015           0.0.0.0:*                           107        13947      440/avahi-daemon: r
udp        0      0 0.0.0.0:5353            0.0.0.0:*                           107        13945      440/avahi-daemon: r
udp        0      0 0.0.0.0:68              0.0.0.0:*                           0          13849      376/dhclient
udp6       0      0 :::36795                :::*                                107        13948      440/avahi-daemon: r
udp6       0      0 :::5353                 :::*                                107        13946      440/avahi-daemon: r

*** Log File - Last 25 Lines ***

2025-11-12 19:00:53.505  - info: javascript.0 (47593) terminating
2025-11-12 19:00:53.508  - info: javascript.0 (47593) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2025-11-12 19:00:53.549  - info: host.ioBroker-V2 stopInstance system.adapter.admin.0 send kill signal
2025-11-12 19:00:53.593  - info: host.ioBroker-V2 stopInstance system.adapter.javascript.0 send kill signal
2025-11-12 19:00:53.593  - info: host.ioBroker-V2 stopInstance system.adapter.javascript.1 send kill signal
2025-11-12 19:00:53.593  - info: host.ioBroker-V2 stopInstance system.adapter.email.0 send kill signal
2025-11-12 19:00:53.593  - info: host.ioBroker-V2 stopInstance system.adapter.telegram.0 send kill signal
2025-11-12 19:00:53.692  - info: history.0 (47655) Terminated (NO_ERROR): Without reason
2025-11-12 19:00:53.994  - info: javascript.1 (47625) terminating
2025-11-12 19:00:53.995  - info: telegram.0 (47670) terminating
2025-11-12 19:00:53.996  - info: telegram.0 (47670) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2025-11-12 19:00:53.996  - info: email.0 (47640) terminating
2025-11-12 19:00:53.999  - info: admin.0 (47501) terminating
2025-11-12 19:00:54.006  - info: javascript.0 (47593) terminating
2025-11-12 19:00:54.126  - info: host.ioBroker-V2 instance system.adapter.email.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-11-12 19:00:54.414  - info: host.ioBroker-V2 instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-11-12 19:00:54.440  - info: host.ioBroker-V2 instance system.adapter.javascript.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-11-12 19:00:54.491  - info: host.ioBroker-V2 instance system.adapter.javascript.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2025-11-12 19:00:59.547  - error: sql.0 (47561) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2025-11-12 19:00:59.548  - error: sql.0 (47561) States database error: connect ECONNREFUSED 0.0.0.0:9000
2025-11-12 19:01:04.552  - error: sql.0 (47561) States database error: connect ECONNREFUSED 0.0.0.0:9000
2025-11-12 19:01:04.553  - error: sql.0 (47561) Objects database error: connect ECONNREFUSED 0.0.0.0:9001
2025-11-12 19:01:05.552  - info: sql.0 (47561) terminating with timeout
2025-11-12 19:01:05.553  - info: sql.0 (47561) Terminated (NO_ERROR): Without reason
2025-11-12 19:01:09.556  - error: sql.0 (47561) Objects database error: connect ECONNREFUSED 0.0.0.0:9001

============ Mark until here for C&P =============

Thomas Braun

@george_best

cd /opt/iobroker && npm ci

George_Best

@thomas-braun sagte in iob fix und iob diag ohne Reaktion:

cd /opt/iobroker && npm ci

sieht wieder sehr wild aus...

jonny@ioBroker-V2:/opt/iobroker$ cd /opt/iobroker && npm ci
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
npm error Missing: iobroker.mqtt@6.1.4 from lock file
npm error Missing: iobroker.net-tools@1.1.2 from lock file
npm error Missing: iobroker.octoprint@5.1.0 from lock file
npm error Missing: iobroker.openweathermap@1.1.2 from lock file
npm error Missing: iobroker.parser@2.2.4 from lock file
npm error Missing: iobroker.ping@1.6.2 from lock file
npm error Missing: iobroker.proxmox@2.4.0 from lock file
[2025-11-12T18_10_30_372Z-debug-0.log](/assets/uploads/files/1762971379377-2025-11-12t18_10_30_372z-debug-0.log)

Thomas Braun

@george_best

Dann bin ich raus.

George_Best

Irgendjemand eine Idee, wie ich das wieder hinbekomme?


jonny@ioBroker-V2:~$ iob status
node:internal/modules/package_json_reader:314
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'deep-clone' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:314:9)
    at packageResolve (node:internal/modules/esm/resolve:767:81)
    at moduleResolve (node:internal/modules/esm/resolve:853:18)
    at defaultResolve (node:internal/modules/esm/resolve:983:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:731:20)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:708:38)
    at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:310:38)
    at ModuleJob._link (node:internal/modules/esm/module_job:182:49) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v22.21.0

crunchip

@thomas-braun sagte in iob fix und iob diag ohne Reaktion:

Dann bin ich raus.

was hälst du davon?

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

eine Idee

Hauptprobleme

Fehlende Dependency "deep-clone"

Das Package deep-clone wird vom js-controller (bzw. js-controller-cli) im ESM-Modus benötigt und fehlt komplett in deinem node_modules-Verzeichnis. Der js-controller 7.0.7 benötigt deep-clone@^3.0.3 als kritische Abhängigkeit.

Package-Lock.json massiv desynchronisiert

Dein package-lock.json ist völlig veraltet und passt nicht mehr zur package.json:

Lock-File enthält admin@3.5.10, tatsächlich installiert ist aber admin@7.7.19

Lock-File enthält js-controller@1.4.2, installiert ist aber js-controller@7.0.7

Dutzende Adapter fehlen komplett im Lock-File (accuweather, alias-manager, chromecast, cloud, etc.)

Node.js 22.x Kompatibilitätsprobleme

Der js-controller 7.0.7 unterstützt zwar "probably" Node.js 22.x, ist aber primär für 18.x und 20.x getestet. Einige Adapter-Dependencies haben explizite Node-Restriktionen (wie @homebridge/ciao), die Node.js 22 blockieren.

npm ci schlägt fehl

npm ci kann nur funktionieren, wenn package.json und package-lock.json synchron sind. Bei dir sind sie massiv inkonsistent, weshalb npm ci mit "old lockfile" und "Missing/Invalid" Fehlern abbricht.

Warum ist das passiert?
Höchstwahrscheinlich wurde:

Ein Node.js-Update von einer älteren Version direkt auf 22.x gemacht

Adapter und js-controller über die Admin-Oberfläche aktualisiert (ohne npm-Kommandos)

Der package-lock.json wurde dabei nie neu generiert

Jetzt ist der node_modules-Ordner teilweise defekt/unvollständig

Lösung: Schritt-für-Schritt-Reparatur
Option A: Saubere Neuinstallation der Dependencies (empfohlen)

# 1. ioBroker stoppen
iob stop

# 2. Ins ioBroker-Verzeichnis wechseln
cd /opt/iobroker

# 3. Korrupte Dateien entfernen
sudo rm -rf node_modules package-lock.json

# 4. Dependencies komplett neu installieren
npm install --loglevel=verbose

# 5. Optional: ioBroker-Reparatur
iob fix

# 6. ioBroker starten
iob start

Falls Fehler auftreten, versuche zusätzlich:

npm cache clean --force
npm install --loglevel=verbose

oder

**Option B : ** Node.js auf LTS 20.x downgraden (sicherer)

Node.js 22.x ist noch zu neu für viele ioBroker-Adapter. Downgrade auf die empfohlene Version 20.x:

# 1. Node.js 20.x installieren (siehe ioBroker-Forum-Anleitung)
# Beispiel mit NodeSource:
curl -fsSL https://deb.nodesource.com/setup_20.x | sudo -E bash -
sudo apt-get install -y nodejs

# 2. Verifizieren
node -v  # sollte v20.x.x zeigen
npm -v

# 3. Dann Option A durchführen

oder

Option C : Manuelles Nachinstallieren (Notlösung)

Falls du nicht alles löschen willst:

cd /opt/iobroker

# deep-clone explizit installieren
npm install deep-clone@^3.0.3

# Weitere fehlende Core-Dependencies
npm install @iobroker/db-objects-file @iobroker/db-objects-jsonl \
            @iobroker/adapter-core fs-extra jsonwebtoken

# Lock-File neu generieren
npm install --package-lock-only

# Dann normales install
npm install --production

Debugging-Befehle zur Überprüfung

# Dependency-Baum prüfen
npm ls deep-clone
npm ls @iobroker/js-controller-cli

# Lock-File neu generieren (ohne Installation)
npm install --package-lock-only

# Verwaiste Packages entfernen
npm prune

George_Best · Lock-File enthält admin@3.5.10, tatsächlich installiert ist aber admin@7.7.19

@crunchip
Vielen, Vielen Dank - ich habe Option A gewählt. Bis jetzt läuft es wieder.

Aber was meinst du mit "Neuinstallation" (der Dependencies) bzw. dann bei C "falls du nicht alles löschen willst".
Bei A wurde doch nichts gelöscht.

Und kann ich nun irgendwo/irgendwie überprüfen wo es noch haken könnte?

crunchip

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

Bei A wurde doch nichts gelöscht

ja doch, deine veraltete package-lock.json, die noch diese alten "Bausteine", wie admin@3.5.10, js-controller@1.4.2 beinhaltet

nochmal ein ìob diag preisgeben

George_Best

@crunchip
ok - aber es wurden keine Objekte, Aliase, Scripte, Adapter-Konfigurationen o.ä. gelöscht.

Community Forum

NEWS

iob fix und iob diag ohne Reaktion

Support us

335

32.5k

81.6k

1.3m