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

[Westfale]

Hallo zusammen,

habe das Problem das mein Javascript Adapter nicht mehr grün wird

Log:
host.ioBroker-RasPi4
	2026-01-21 16:15:02.321	error	instance system.adapter.javascript.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.321	error	Caught by controller[0]: Node.js v22.22.0
host.ioBroker-RasPi4
	2026-01-21 16:15:02.321	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.javascript/build/lib/typescriptSettings.js:4:22)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at require (node:internal/modules/helpers:147:16)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1463:12)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at wrapModuleLoad (node:internal/modules/cjs/loader:237:24)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at TracingChannel.traceSync (node:diagnostics_channel:328:14)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at Function._load (node:internal/modules/cjs/loader:1263:12)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1441:32)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.320	error	Caught by controller[0]: at Object..js (node:internal/modules/cjs/loader:1839:10)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.319	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1680:20)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.319	error	Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1638:18)
host.ioBroker-RasPi4
	2026-01-21 16:15:02.319	error	Caught by controller[0]: SyntaxError: Unexpected end of input
host.ioBroker-RasPi4
	2026-01-21 16:15:02.319	error	Caught by controller[0]:
host.ioBroker-RasPi4
	2026-01-21 16:15:02.319	error	Caught by controller[0]: const importOrExport = ((_h = findAncestor(location, isImportDeclaration)) == null ? void 0 : _h.importClause) || findAncestor(location,
host.ioBroker-RasPi4
	2026-01-21 16:15:02.318	error	Caught by controller[0]: /opt/iobroker/node_modules/typescript/lib/typescript.js:53781

MOD-EDIT: Code in code-tags gesetzt!

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

Script v.2025-08-09

*** BASE SYSTEM ***
Operating System: Debian GNU/Linux 13 (trixie)
 Static hostname: ioBroker-RasPi4
       Icon name: computer
          Kernel: Linux 6.12.62+rpt-rpi-v8
    Architecture: arm64
OS is similar to:

Model           : Raspberry Pi 4 Model B Rev 1.1
Docker          : false
Virtualization  : none
Kernel          : aarch64
Userland        : 64 bit

Systemuptime and Load:
 16:44:49 up 10 min,  1 user,  load average: 7.07, 9.55, 5.43
CPU threads: 4


*** LIFE CYCLE STATUS ***
Operating System is the current Debian stable version codenamed 'trixie'!

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** TIME AND TIMEZONES ***
               Local time: Wed 2026-01-21 16:44:49 CET
           Universal time: Wed 2026-01-21 15:44:49 UTC
                 RTC time: n/a
                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':
pi
HOME=/home/pi
GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi iobroker

User that is running 'js-controller':
iobroker
HOME=/home/iobroker
SUDO_HOME=/home/pi
GROUPS=iobroker tty dialout audio video plugdev bluetooth redis gpio i2c

*** 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:            4.0G        2.9G        306M        5.2M        827M        1.0G
Swap:           536M        198M        338M
Total:          4.5G        3.1G        645M

Active iob-Instances:   23

         3796 M total memory
         2809 M used memory
         3253 M active memory
           57 M inactive memory
          290 M free memory
           73 M buffer memory
          716 M swap cache
          511 M total swap
          189 M used swap
          322 M free swap

*** top - Table Of Processes  ***
top - 16:44:50 up 10 min,  1 user,  load average: 7.07, 9.55, 5.43
Tasks: 227 total,   4 running, 223 sleeping,   0 stopped,   0 zombie
%Cpu(s): 81.1 us, 15.1 sy,  0.0 ni,  3.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :   3796.7 total,    299.9 free,   2799.9 used,    790.2 buff/cache
MiB Swap:    512.0 total,    322.8 free,    189.2 used.    996.8 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  1.6G     0  1.6G   0% /dev
tmpfs          tmpfs     760M  9.8M  750M   2% /run
/dev/mmcblk0p2 ext4       59G   11G   45G  19% /
tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
tmpfs          tmpfs     1.9G  3.2M  1.9G   1% /tmp
tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p1 vfat      510M   74M  437M  15% /boot/firmware
tmpfs          tmpfs     1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs          tmpfs     380M  8.0K  380M   1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Wed Jan 21 16:34:17 2026] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0  numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=DC:A6:32:0A:5B:54 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=d2f9a308-02 rootfstype=ext4 fsck.repair=yes rootwait
[Wed Jan 21 16:34:20 2026] EXT4-fs (mmcblk0p2): mounted filesystem d4cc7d63-da78-48ad-9bdd-64ffbba449a8 ro with ordered data mode. Quota mode: none.
[Wed Jan 21 16:34:22 2026] EXT4-fs (mmcblk0p2): re-mounted d4cc7d63-da78-48ad-9bdd-64ffbba449a8 r/w.

Show mounted filesystems:
TARGET           SOURCE         FSTYPE OPTIONS
/                /dev/mmcblk0p2 ext4   rw,noatime
`-/boot/firmware /dev/mmcblk0p1 vfat   rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro

Files in neuralgic directories:

/var:
1.9G    /var/
1.2G    /var/lib
969M    /var/lib/mysql
749M    /var/lib/mysql/iobroker
177M    /var/cache

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

/opt/iobroker/backups:
19M     /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
718M    /opt/iobroker/iobroker-data/
548M    /opt/iobroker/iobroker-data/files
132M    /opt/iobroker/iobroker-data/backup-objects
115M    /opt/iobroker/iobroker-data/files/vis
109M    /opt/iobroker/iobroker-data/files/vis-2

The five largest files in iobroker-data are:
38M     /opt/iobroker/iobroker-data/objects.jsonl
27M     /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js.map
9.8M    /opt/iobroker/iobroker-data/files/vis-2/material-icons/knx-uf.json
9.2M    /opt/iobroker/iobroker-data/files/tankerkoenig.admin/build/index.js
8.2M    /opt/iobroker/iobroker-data/files/heatingcontrol.admin/assets/index-D7e4bkMV.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-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_54ef2b627e12ec11b53520c7bd930c07-if00-port0

*** ZigBee Settings ***

HINT:
Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting:
/dev/ttyUSB0
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.22.0
/usr/bin/node           v22.22.0
/usr/bin/npm            10.9.4
/usr/bin/npx            10.9.4
/usr/bin/corepack       0.34.0

nodejs:
  Installed: 22.22.0-1nodesource1
  Candidate: 22.22.0-1nodesource1
  Version table:
 *** 22.22.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
        100 /var/lib/dpkg/status
     22.21.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.20.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.19.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.18.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.17.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.17.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.16.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.15.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.15.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.14.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.13.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.13.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.12.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.11.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.10.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.9.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.8.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.7.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.6.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.5.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.5.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.4.1-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.4.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.3.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.2.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.1.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     22.0.0-1nodesource1 1001
        500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages
     20.19.2+dfsg-1 500
        500 http://deb.debian.org/debian trixie/main arm64 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
iobroker is running on this host.


Objects type: jsonl
States  type: redis



Hat jemand eine Idee ?? Habe den Adapter  schon neu installiert, jedoch ohne Erfolg

Danke

[Thomas Braun]

@Westfale

Die Ausgabe von iob diag ist nicht vollständig.
Bis dahin sehe ich aber keine Auffälligkeiten.
Bis auf vielleicht den Part mit dem zigbee-Stick. Hat aber mit dem Problem nichts zu tun.

[peterfido]

@Westfale sagte in Javascript Adapter startet nicht mehr:

Systemuptime and Load:
16:44:49 up 10 min, 1 user, load average: 7.07, 9.55, 5.43
CPU threads: 4

4 Kerne und dann so eine load average? Da sollte das Maximum doch 4.00 sein.

[fuzzy1955]

@Westfale sagte in Javascript Adapter startet nicht mehr:

Problem das mein Javascript Adapter nicht mehr grün wird

Hatte ich auch schon. Halte mal alle Skripte an. Wenn der Adapter dann grün wird, schaltest du sie der Reihe nach wieder ein. Evt. siehst du dann , wo es klemmt.

[Thomas Braun]

@peterfido sagte in Javascript Adapter startet nicht mehr:

4 Kerne und dann so eine load average? Da sollte das Maximum doch 4.00 sein.

Oh, hatte ich übersehen. Das ist natürlich komplett im dunkelroten Bereich.