Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. FATAL ERROR: Reached heap limit Allocation failed JavaS....

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    FATAL ERROR: Reached heap limit Allocation failed JavaS....

    This topic has been deleted. Only users with topic management privileges can see it.
    • bugs
      bugs last edited by

      Hallo

      Ich habe einen Raspberry 4B+ 4GB mit einer SDD 120GB neu aufgesetzt und IoBroker installiert.
      Soweit funktioniert alles wie es soll ausser dass gelegentlich, ca. einmal pro Tag, IoBroker (Node Red) abstürzt und aber sofort automatisch wieder startet. Meistens geschieht das am Morgen wenn die Benutzeroberfläche (Projektiert in Node Red) geöffnet wird. Solange am System, insbesondere in Node Red projektiert wird gab es auch über längere Zeit kein Absturtz.
      Auf dem Raspberry läuft nur der IoBroker und das integrierte Node Red. Node Red dient für verschiedene Kommunikationen und für die Visualisierung und Bedienung.

      Folgendes zeigt iob diag:


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

      Script v.2025-03-08
      
      *** BASE SYSTEM ***
       Static hostname: raspberrypi
             Icon name: computer
      Operating System: Debian GNU/Linux 12 (bookworm)
                Kernel: Linux 6.12.34+rpt-rpi-v8
          Architecture: arm64
      OS is similar to: 
      
      Model		: Raspberry Pi 4 Model B Rev 1.5
      Docker          : false
      Virtualization  : none
      Kernel          : aarch64
      Userland        : 64 bit
      
      Systemuptime and Load:
       14:09:15 up 22:17,  3 users,  load average: 0.74, 0.50, 0.47
      CPU threads: 4
      
      
      *** LIFE CYCLE STATUS ***
      Operating System is the current Debian stable version codenamed 'bookworm'!
      
      *** RASPBERRY THROTTLING ***
      Current issues:
      No throttling issues detected.
      
      Previously detected issues:
      No throttling issues detected.
      
      *** TIME AND TIMEZONES ***
                     Local time: Tue 2025-08-05 14:09:15 CEST
                 Universal time: Tue 2025-08-05 12:09:15 UTC
                       RTC time: n/a
                      Time zone: Europe/Zurich (CEST, +0200)
      System clock synchronized: yes
                    NTP service: active
                RTC in local TZ: no
      
      *** Users and Groups ***
      User that called 'iob diag':
      pi
      XDG_CONFIG_HOME=/home/pi/.config
      HOME=/home/pi
      GROUPS=pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker
      
      User that is running 'js-controller':
      iobroker
      HOME=/home/iobroker
      GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c
      
      *** DISPLAY-SERVER SETUP ***
      Display-Server: true
      Desktop: 	LXDE-pi
      Terminal: 	x11
      
      System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'
      
      *** MEMORY ***
                     total        used        free      shared  buff/cache   available
      Mem:            4.0G        2.1G        172M         51M        1.9G        1.9G
      Swap:           209M          0B        209M
      Total:          4.2G        2.1G        381M
      
      Active iob-Instances: 	15
      
               3795 M total memory
               1971 M used memory
               1649 M active memory
               1713 M inactive memory
                164 M free memory
                 94 M buffer memory
               1683 M swap cache
                199 M total swap
                  0 M used swap
                199 M free swap
      
      *** top - Table Of Processes  ***
      top - 14:09:15 up 22:17,  3 users,  load average: 0.74, 0.50, 0.47
      Tasks: 258 total,   1 running, 257 sleeping,   0 stopped,   0 zombie
      %Cpu(s): 28.6 us, 14.3 sy,  0.0 ni, 57.1 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
      MiB Mem :   3795.9 total,    164.2 free,   1971.2 used,   1777.8 buff/cache     
      MiB Swap:    200.0 total,    200.0 free,      0.0 used.   1824.7 avail Mem 
      
      *** FAILED SERVICES ***
      
        UNIT                   LOAD   ACTIVE SUB    DESCRIPTION
      * resize2fs_once.service loaded failed failed LSB: Resize the root filesystem to fill partition
      
      LOAD   = Reflects whether the unit definition was properly loaded.
      ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
      SUB    = The low-level unit activation state, values depend on unit type.
      1 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  1.4M  758M   1% /run
      /dev/sda2      ext4       29G   15G   13G  53% /
      tmpfs          tmpfs     1.9G     0  1.9G   0% /dev/shm
      tmpfs          tmpfs     5.0M   16K  5.0M   1% /run/lock
      /dev/sda1      vfat      253M   51M  202M  20% /boot/firmware
      tmpfs          tmpfs     380M   48K  380M   1% /run/user/1000
      
      Messages concerning ext4 filesystem in dmesg:
      [Mon Aug  4 15:51:54 2025] 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 video=HDMI-A-1:1280x1024M@60 numa=fake=2 system_heap.max_order=0 smsc95xx.macaddr=2C:CF:67:03:31:2C vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000  console=tty1 root=PARTUUID=3c32cc87-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
      [Mon Aug  4 15:51:55 2025] EXT4-fs (sda2): mounted filesystem beab8cae-e02a-45a5-891b-24338dd458d2 ro with ordered data mode. Quota mode: none.
      [Mon Aug  4 15:51:56 2025] EXT4-fs (sda2): re-mounted beab8cae-e02a-45a5-891b-24338dd458d2 r/w.
      
      Show mounted filesystems:
      TARGET                       SOURCE       FSTYPE            OPTIONS
      /                            /dev/sda2    ext4              rw,noatime
      |-/run/user/1000/doc         portal       fuse.portal       rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
      |-/boot/firmware             /dev/sda1    vfat              rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
      `-/home/pi/thinclient_drives xrdp-chansrv fuse.xrdp-chansrv rw,nosuid,nodev,relatime,user_id=1000,group_id=1000
      
      Files in neuralgic directories:
      
      /var:
      1.1G	/var/
      520M	/var/log
      509M	/var/log/journal/e68efd1718194c4bbcec847cd7831919
      509M	/var/log/journal
      242M	/var/lib
      
      Archived and active journals take up 508.3M in the file system.
      
      /opt/iobroker/backups:
      12M	/opt/iobroker/backups/
      
      /opt/iobroker/iobroker-data:
      361M	/opt/iobroker/iobroker-data/
      174M	/opt/iobroker/iobroker-data/node-red
      173M	/opt/iobroker/iobroker-data/node-red/node_modules
      127M	/opt/iobroker/iobroker-data/files
      49M	/opt/iobroker/iobroker-data/backup-objects
      
      The five largest files in iobroker-data are:
      20M	/opt/iobroker/iobroker-data/files/opcua.admin/static/js/main.02eaa611.js.map
      11M	/opt/iobroker/iobroker-data/objects.jsonl
      8.6M	/opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js
      7.4M	/opt/iobroker/iobroker-data/files/opcua.admin/static/js/main.02eaa611.js
      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':
      
      No Devices found 'by-id'
      
      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 	v20.19.4
      /usr/bin/node 		v20.19.4
      /usr/bin/npm 		10.8.2
      /usr/bin/npx 		10.8.2
      /usr/bin/corepack 	0.32.0
      
      nodejs:
        Installed: 20.19.4-1nodesource1
        Candidate: 20.19.4-1nodesource1
        Version table:
       *** 20.19.4-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
              100 /var/lib/dpkg/status
           20.19.3-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.19.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.19.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.19.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.3-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.18.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.17.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.16.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.15.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.15.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.14.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.13.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.13.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.12.2-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.12.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.12.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.11.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.11.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.10.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.9.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.8.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.8.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.7.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.6.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.6.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.5.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.5.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.4.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.3.1-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.3.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.2.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.1.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           20.0.0-1nodesource1 1001
              500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages
           18.19.0+dfsg-6~deb12u2 500
              500 http://deb.debian.org/debian bookworm/main arm64 Packages
           18.19.0+dfsg-6~deb12u1 500
              500 http://security.debian.org/debian-security bookworm-security/main arm64 Packages
      
      Temp directories causing deletion problem: 0
      No problems detected
      
      Errors in npm tree: 0
      No problems detected
      
      *** ioBroker-Installation ***
      
      ioBroker Status
      iobroker is running on this host.
      
      
      Objects type: jsonl
      States  type: jsonl
      
      Hosts:
      raspberrypi         raspberrypi (version: 7.0.6, hostname: raspberrypi   , alive, uptime: 80234)
      
      Core adapters versions
      js-controller: 	7.0.6
      admin: 		7.6.17
      javascript: 	8.9.2
      
      nodejs modules from github: 	0
      
      Adapter State
      + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
        system.adapter.backitup.0               : backitup              : raspberrypi                              - disabled
      + system.adapter.digitalstrom.0           : digitalstrom          : raspberrypi                              -  enabled
      + system.adapter.discovery.0              : discovery             : raspberrypi                              -  enabled
      + system.adapter.enigma2.0                : enigma2               : raspberrypi                              -  enabled
      + system.adapter.fritzdect.0              : fritzdect             : raspberrypi                              -  enabled
      + system.adapter.history.0                : history               : raspberrypi                              -  enabled
      + system.adapter.javascript.0             : javascript            : raspberrypi                              -  enabled
      + system.adapter.mqtt.0                   : mqtt                  : raspberrypi                              -  enabled, port: 1883, bind: 0.0.0.0
      + system.adapter.node-red.0               : node-red              : raspberrypi                              -  enabled, port: 1880, bind: 0.0.0.0
      + system.adapter.opcua.0                  : opcua                 : raspberrypi                              -  enabled, port: 4334
      + system.adapter.opcua.1                  : opcua                 : raspberrypi                              -  enabled, port: 4334
        system.adapter.parser.0                 : parser                : raspberrypi                              - disabled
      + system.adapter.rpi2.0                   : rpi2                  : raspberrypi                              -  enabled
      + system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 0.0.0.0
      + system.adapter.shelly.1                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 0.0.0.0
        system.adapter.tr-064.0                 : tr-064                : raspberrypi                              - disabled
      
      + instance is alive
      
      Enabled adapters with bindings
      + system.adapter.admin.0                  : admin                 : raspberrypi                              -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
      + system.adapter.mqtt.0                   : mqtt                  : raspberrypi                              -  enabled, port: 1883, bind: 0.0.0.0
      + system.adapter.node-red.0               : node-red              : raspberrypi                              -  enabled, port: 1880, bind: 0.0.0.0
      + system.adapter.opcua.0                  : opcua                 : raspberrypi                              -  enabled, port: 4334
      + system.adapter.opcua.1                  : opcua                 : raspberrypi                              -  enabled, port: 4334
      + system.adapter.shelly.0                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 0.0.0.0
      + system.adapter.shelly.1                 : shelly                : raspberrypi                              -  enabled, port: 1882, bind: 0.0.0.0
      
      ioBroker-Repositories
      ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐
      │ (index) │ name     │ url                                                     │ auto upgrade │
      ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤
      │ 0       │ 'stable' │ 'http://download.iobroker.net/sources-dist.json'        │ false        │
      │ 1       │ 'beta'   │ 'http://download.iobroker.net/sources-dist-latest.json' │ false        │
      └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘
      
      Active repo(s): stable
      Upgrade policy: none
      
      Installed ioBroker-Adapters
      Used repository: stable
      Adapter    "admin"        : 7.6.17   , installed 7.6.17
      Adapter    "backitup"     : 3.3.5    , installed 3.3.5
      Adapter    "digitalstrom" : 2.3.0    , installed 2.3.0
      Adapter    "discovery"    : 5.0.0    , installed 5.0.0
      Adapter    "enigma2"      : 2.2.3    , installed 2.2.3
      Adapter    "fritzdect"    : 2.6.2    , installed 2.6.2
      Adapter    "history"      : 3.0.1    , installed 3.0.1
      Adapter    "javascript"   : 8.9.2    , installed 8.9.2
      Controller "js-controller": 7.0.6    , installed 7.0.6
      Adapter    "mqtt"         : 6.1.2    , installed 6.1.2
      Adapter    "node-red"     : 5.2.1    , installed 5.2.1
      Adapter    "opcua"        : 1.1.0    , installed 1.1.0
      Adapter    "parser"       : 2.2.4    , installed 2.2.4
      Adapter    "rpi2"         : 2.4.0    , installed 2.4.0
      Adapter    "shelly"       : 10.1.0   , installed 10.1.0
      Adapter    "tr-064"       : 4.3.0    , installed 4.3.0
      
      Objects and States
      Please stand by - This may take a while
      Objects: 	4336
      States: 	3593
      
      *** 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://security.debian.org/debian-security bookworm-security InRelease
      Hit:4 http://archive.raspberrypi.org/debian bookworm InRelease
      Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
      Reading package lists...
      Pending Updates: 3
      
      *** 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 0.0.0.0:5900            0.0.0.0:*               LISTEN      0          1790       809/vncserver-x11-c 
      tcp        0      0 0.0.0.0:1883            0.0.0.0:*               LISTEN      1001       10236      2414/io.mqtt.0      
      tcp        0      0 0.0.0.0:1882            0.0.0.0:*               LISTEN      1001       13570      2516/io.shelly.1    
      tcp        0      0 0.0.0.0:1880            0.0.0.0:*               LISTEN      1001       779864     223244/node-red     
      tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      0          1763       840/sshd: /usr/sbin 
      tcp        0      0 127.0.0.1:631           0.0.0.0:*               LISTEN      0          401448     113471/cupsd        
      tcp        0      0 127.0.0.1:9000          0.0.0.0:*               LISTEN      1001       11265      793/iobroker.js-con 
      tcp        0      0 127.0.0.1:9001          0.0.0.0:*               LISTEN      1001       7157       793/iobroker.js-con 
      tcp6       0      0 :::3389                 :::*                    LISTEN      117        6826       858/xrdp            
      tcp6       0      0 :::8081                 :::*                    LISTEN      1001       8967       1490/io.admin.0     
      tcp6       0      0 ::1:631                 :::*                    LISTEN      0          401447     113471/cupsd        
      tcp6       0      0 :::5900                 :::*                    LISTEN      0          1789       809/vncserver-x11-c 
      tcp6       0      0 ::1:3350                :::*                    LISTEN      0          6143       826/xrdp-sesman     
      tcp6       0      0 :::22                   :::*                    LISTEN      0          1765       840/sshd: /usr/sbin 
      udp        0      0 0.0.0.0:58402           0.0.0.0:*                           108        6633       608/avahi-daemon: r 
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           108        6631       608/avahi-daemon: r 
      udp        0      0 0.0.0.0:5683            0.0.0.0:*                           1001       14414      2495/io.shelly.0    
      udp6       0      0 :::5353                 :::*                                108        6632       608/avahi-daemon: r 
      udp6       0      0 :::52725                :::*                                108        6634       608/avahi-daemon: r 
      udp6       0      0 fe80::9d98:aed3:620:546 :::*                                0          8568       703/NetworkManager  
      
      *** Log File - Last 25 Lines ***
      
      2025-08-05 14:04:28.487  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 
      2025-08-05 14:04:36.071  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.temperature" has to be type "number" but received type "string" 
      2025-08-05 14:04:53.797  - info: shelly.1 (2516) [MQTT] Device with client id "shellyplusht-c049ef8ba63c" connected from 192.168.178.102!
      2025-08-05 14:04:54.503  - info: shelly.1 (2516) [authEnabled] 192.168.178.102 (shellyplusht / shellyplusht-c049ef8ba63c / shellyplusht#c049ef8ba63c#1): This device is not protected via restricted login (see adapter documentation for details)
      2025-08-05 14:05:00.184  - info: shelly.1 (2516) [MQTT] Client Close: 192.168.178.102 (shellyplusht / shellyplusht-c049ef8ba63c / shellyplusht#c049ef8ba63c#1) (false)
      2025-08-05 14:05:28.306  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 
      2025-08-05 14:05:28.408  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 
      2025-08-05 14:05:44.598  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.humidity" has to be type "number" but received type "string" 
      2025-08-05 14:06:28.100  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 
      2025-08-05 14:06:28.189  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 
      2025-08-05 14:07:03.663  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.brightness" has to be type "number" but received type "string" 
      2025-08-05 14:07:03.696  - info: node-red.0 (223244) State value to set for "opcua.0.vars.Objects.Server.CODESYS Control for Raspberry Pi SL.Resources.Application.Programs.HomeServer_NodeRed.rdS_Outdoor_relative_Feuchtigkeit" has to be type "number" but received type "string" 
      2025-08-05 14:07:28.452  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 
      2025-08-05 14:07:28.550  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 
      2025-08-05 14:07:53.114  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.0.61833.sensors.TemperatureValue" has to be type "number" but received type "string" 
      2025-08-05 14:07:58.128  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.temperature" has to be type "number" but received type "string" 
      2025-08-05 14:08:28.033  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 
      2025-08-05 14:08:28.130  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 
      2025-08-05 14:09:11.724  - warn: fritzdect.0 (2849) State value to set for "fritzdect.0.DECT_087610360627.energy_stats.datatimem" has value "1754395751717" greater than max "2147483648"
      2025-08-05 14:09:11.865  - warn: fritzdect.0 (2849) State value to set for "fritzdect.0.DECT_087610360627.energy_stats.datatimed" has value "1754395751864" greater than max "2147483648"
      2025-08-05 14:09:28.316  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunazimuth" has to be type "number" but received type "string" 
      2025-08-05 14:09:28.412  - info: digitalstrom.0 (2443) State value to set for "digitalstrom.0.apartment.sensors.outdoor.sunelevation" has to be type "number" but received type "string" 
      2025-08-05 14:09:54.470  - info: shelly.1 (2516) [MQTT] Device with client id "shellyplusht-c049ef8ba63c" connected from 192.168.178.102!
      2025-08-05 14:09:55.317  - info: shelly.1 (2516) [authEnabled] 192.168.178.102 (shellyplusht / shellyplusht-c049ef8ba63c / shellyplusht#c049ef8ba63c#1): This device is not protected via restricted login (see adapter documentation for details)
      2025-08-05 14:10:01.960  - info: shelly.1 (2516) [MQTT] Client Close: 192.168.178.102 (shellyplusht / shellyplusht-c049ef8ba63c / shellyplusht#c049ef8ba63c#1) (false)
      
      

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

      Ausschnitt aus der Log-Datei von iobroker:

      <--- Last few GCs --->
      
      [2335:0x3fa20cd0] 58199875 ms: Scavenge (reduce) 125.2 (129.9) -> 125.1 (130.9) MB, 3.72 / 0.00 ms  (average mu = 0.997, current mu = 0.353) allocation failure; 
      [2335:0x3fa20cd0] 58200056 ms: Mark-Compact (reduce) 126.1 (130.9) -> 125.7 (131.9) MB, 132.68 / 0.01 ms  (average mu = 0.993, current mu = 0.484) allocation failure; scavenge might not succeed
      
      
      <--- JS stacktrace --->
      
      FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
      ----- Native stack trace -----
      
       1: 0xb8859c node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node-red]
      
      2025-08-05 08:02:24.711  - warn: node-red.0 (2145)  2: 0xecd59c v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node-red]
       3: 0xecd76c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node-red]
       4: 0x10d53fc  [node-red]
       5: 0x10eb8d4 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node-red]
       6: 0x10c463c v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node-red]
       7: 0x10c5400 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node-red]
       8: 0x10a4420 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node-red]
       9: 0x1095c98 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [node-red]
      10: 0x109845c v8::internal::FactoryBase<v8::internal::Factory>::NewRawOneByteString(int, v8::internal::AllocationType) [node-red]
      11: 0x150aef0 v8::internal::IncrementalStringBuilder::Extend() [node-red]
      12: 0x11f79e8 v8::internal::JsonStringifier::SerializeDouble(double) [node-red]
      13: 0x11fdca4 v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<false>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      14: 0x11fd8d0 v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<false>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      15: 0x11fb38c v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<true>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      16: 0x11fb6f8 v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<true>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      17: 0x11fdca4 v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<false>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      18: 0x11fb38c v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<true>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      19: 0x11fdca4 v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<false>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      20: 0x11fd8d0 v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<false>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node-red]
      21: 0x11fe8e0 v8::internal::JsonStringify(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>) [node-red]
      22: 0xf603c0 v8::internal::Builtin_JsonStringify(int, unsigned long*, v8::internal::Isolate*) [node-red]
      23: 0x18b7964  [node-red]
      
      2025-08-05 08:02:24.749  - info: node-red.0 (2145) Node-RED exited with null
      
      

      Wenn ich das richtig intepretiere gibt es einen Speicherüberlauf durch die Ausführung eines JavaScript innerhlab von Node Red.

      Wie finde ich die Ursache des Problems (Vorgehen)?

      Vielen Dank
      Heinz

      Marc Berg 1 Reply Last reply Reply Quote 0
      • Marc Berg
        Marc Berg Most Active @bugs last edited by Marc Berg

        @bugs sagte in FATAL ERROR: Reached heap limit Allocation failed JavaS....:

        Wie finde ich die Ursache des Problems (Vorgehen)?

        In den Node-RED Instanzeinstellungen kannst du die Speicherzuweisung erhöhen, die steht im Standard auf 128MB. Das ist für größere Flows etwas knapp, also einfach mal auf z.B. 256 MB erhöhen, das sollte reichen. RAM hast du genug.

        EDIT:
        Über den Endpunkt "/diagnostics" in Node-RED kannst du übrigens den Speicherverbrauch überwachen. Entscheidend ist der Wert "heapUsed". Der sollte sich nach einer Weile auf einen Wert einpendeln und nicht weiter steigen.

        Codierknecht bugs 2 Replies Last reply Reply Quote 2
        • Codierknecht
          Codierknecht Developer Most Active @Marc Berg last edited by

          @marc-berg sagte in FATAL ERROR: Reached heap limit Allocation failed JavaS....:

          RAM hast du genug.

          @bugs
          Und das könnte man noch optimieren, indem man keinen Desktop verwendet.

          *** DISPLAY-SERVER SETUP ***
          Display-Server: true
          Desktop: 	LXDE-pi
          Terminal: 	x11
           
          System is booting into 'graphical.target'. Usually a server is running in 'multi-user.target'. Please set BootTarget to 'multi-user.target' or run 'iobroker fix'
          
          1 Reply Last reply Reply Quote 0
          • bugs
            bugs @Marc Berg last edited by

            @marc-berg
            Vielen Dank für die rasche Antwort und treffende, fachkundige Rückmeldung.

            Der Raspberry läuft nun seit 24h ohne Absturz, ich bin sehr zuversichtlich dass die projektierte Speichergzuweisung zu knapp war. Neu ist sie auf 256 MB eingestellt, wie von dir vorgeschlagen. Der aktuelle "heapUsed" Wert liegt aktuell im Bereich 130MB bis 145MB, sollte der Wert steigen werde ich die Speicherzuweisung weiter erhöhen.

            @Codierknecht
            Dass der Desktop suboptimal ist ist mir bewusst, solange jedoch alles ohne Probleme läuft behalte ich die Version mit Desktop.

            Thomas Braun 1 Reply Last reply Reply Quote 0
            • Thomas Braun
              Thomas Braun Most Active @bugs last edited by

              @bugs sagte in FATAL ERROR: Reached heap limit Allocation failed JavaS....:

              Dass der Desktop suboptimal ist ist mir bewusst, solange jedoch alles ohne Probleme läuft behalte ich die Version mit Desktop.

              Wozu? Macht das Ganze nur unnötig komplex. Updates sind aufwändiger, Sicherheitslücken wahrscheinlicher (mehr Code da unnötigerweise mitläuft), Ressourcen werden verballert usw.

              Ein Desktop ist auf einem Server überflüssig wie ein Kropf.

              bugs 1 Reply Last reply Reply Quote 1
              • bugs
                bugs @Thomas Braun last edited by

                @thomas-braun sagte in FATAL ERROR: Reached heap limit Allocation failed JavaS....:

                @bugs sagte in FATAL ERROR: Reached heap limit Allocation failed JavaS....:

                Dass der Desktop suboptimal ist ist mir bewusst, solange jedoch alles ohne Probleme läuft behalte ich die Version mit Desktop.

                Wozu? Macht das Ganze nur unnötig komplex. Updates sind aufwändiger, Sicherheitslücken wahrscheinlicher (mehr Code da unnötigerweise mitläuft), Ressourcen werden verballert usw.

                Ein Desktop ist auf einem Server überflüssig wie ein Kropf.

                Da ich nicht häufig mit Linux arbeite sind mir die Befehle und der Syntax im Terminal nicht geläufig.
                Für mich ist dann die Bedienung über den Desktop z.B. Dateimanager, Geany oder das Kopieren der Speicherkarte mit 'SD Card Copier' usw. einfacher, übersichtlicher und schneller.

                Codierknecht 1 Reply Last reply Reply Quote 0
                • Codierknecht
                  Codierknecht Developer Most Active @bugs last edited by

                  @bugs sagte in FATAL ERROR: Reached heap limit Allocation failed JavaS....:

                  Da ich nicht häufig mit Linux arbeite sind mir die Befehle und der Syntax im Terminal nicht geläufig.

                  Da ich hauptsächlich unter Windows unterwegs bin, sind mir seltener verwendete Befehle auch nicht geläufig.
                  Die schreibe ich mir dann in meine eigene "Knowledgebase" oder schlage sie nach.

                  Dafür spare ich mir aber das herumschleppen eines Desktop, der nur unnötig Ressourcen frisst.
                  Was nicht installiert ist muss auch nicht aktualisiert werden, kann keine Fehler produzieren oder Lücken ins System reißen.
                  Insbesondere auf einem nicht so üppig ausgestatteten System.

                  Und da man ja auch nicht alle Nase lang an einem gut funktionierenden System rumschrauben muss, vermisse ich auch keine grafische Oberfläche.

                  1 Reply Last reply Reply Quote 1
                  • First post
                    Last post

                  Support us

                  ioBroker
                  Community Adapters
                  Donate

                  376
                  Online

                  32.0k
                  Users

                  80.4k
                  Topics

                  1.3m
                  Posts

                  4
                  7
                  145
                  Loading More Posts
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes
                  Reply
                  • Reply as topic
                  Log in to reply
                  Community
                  Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                  The ioBroker Community 2014-2023
                  logo