heap zu klein?
-
Hallo IOBroker Forum,
Bisher lief der iobroker mit dem Nuc eigentlich ganz gut und relativ schnell. Meine Updates wurden sporadisch eingespielt, täglich automatisch ein Backup erstellt und immer wieder ein neues Feature für mein Smarthome eingebaut. Das letzte war dann der Energieflussadapter.
Leider Absturz beim Ausschalten der USV. Seither zickt alles rum. Habe ein backup eingespielt, aber iobroker startet nicht mehr zuverlässig, und wenn, dann sehr langsam.Nach einigem ermitteln der Ursache konnte ich dann ein ausgeschöpften heap ermitteln.
Hier mal das wichtigste:FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Kann mir jemand sagen, wie man diesen erweitert?
Oder erkennt jemand ein anderes Problem, das ich fixen sollte?======================= SUMMARY ======================= v.2024-04-21 Static hostname: debian-uli Icon name: computer-desktop Chassis: desktop Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-28-amd64 Architecture: x86-64 Installation: native Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1003 Display-Server: true Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 13 Nodejs-Installation: /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 Recommended versions are nodejs No connection to databases possible ... and npm Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.5G 4.8G 2.3G 0.0K 410M 2.5G Swap: 7.8G 3.8G 4.0G Total: 15G 8.6G 6.2G Active iob-Instances: 0 Active repo(s): stable ioBroker Core: js-controller 5.0.19 admin 6.13.16 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: Objects: 13870 States: 12343 Size of iob-Database: 532M /opt/iobroker/iobroker-data/objects.jsonl 11M /opt/iobroker/iobroker-data/objects.json.migrated 11M /opt/iobroker/iobroker-data/objects.json.bak.migrated 11M /opt/iobroker/iobroker-data/states.jsonl 1.6M /opt/iobroker/iobroker-data/states.json.migrated 1.6M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ==================== -
@pingps sagte in heap zu klein?:
Display-Server: true
Boot Target: graphical.targetAuf einem Server den Desktop ausschalten.
Pending iob updates: 13
Updates einspielen.
-
@pingps desktop sollte aus sein
Updates sind eingespielt:Uli@debian-uli:~$ iobroker status
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! -
@pingps Die Antwort auf alle Fragen sollte in der Langfassung von
iob diagzu finden sein -
@homoran said in heap zu klein?:
iob diag
======== Start marking the full check here =========
Skript v.2024-04-21 *** BASE SYSTEM *** Static hostname: debian-uli Icon name: computer-desktop Chassis: desktop Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-28-amd64 Architecture: x86-64 model name : Intel(R) Celeron(R) J4005 CPU @ 2.00GHz Docker : false Virtualization : none Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 15:46:28 up 35 min, 1 user, load average: 0.67, 0.93, 0.89 CPU threads: 2 *** Time and Time Zones *** Local time: Sun 2024-05-05 15:46:28 CEST Universal time: Sun 2024-05-05 13:46:28 UTC RTC time: Sun 2024-05-05 13:46:28 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': Uli HOME=/home/Uli GROUPS=Uli iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth redis *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 7.5G 881M 5.0G 3.0M 1.7G 6.3G Swap: 7.8G 0B 7.8G Total: 15G 881M 12G Active iob-Instances: 0 7528 M total memory 884 M used memory 931 M active memory 1224 M inactive memory 4972 M free memory 244 M buffer memory 1427 M swap cache 7771 M total swap 0 M used swap 7771 M free swap *** top - Table Of Processes *** top - 15:46:29 up 35 min, 1 user, load average: 0.67, 0.93, 0.89 Tasks: 136 total, 2 running, 134 sleeping, 0 stopped, 0 zombie %Cpu(s): 39.4 us, 15.2 sy, 0.0 ni, 45.5 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7529.0 total, 4923.7 free, 933.0 used, 1672.3 buff/cache MiB Swap: 7772.0 total, 7772.0 free, 0.0 used. 6289.5 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.7G 0 3.7G 0% /dev tmpfs tmpfs 753M 1.3M 752M 1% /run /dev/sda2 ext4 102G 36G 62G 37% / tmpfs tmpfs 3.7G 0 3.7G 0% /dev/shm tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 511M 11M 501M 3% /boot/efi tmpfs tmpfs 753M 60K 753M 1% /run/user/1003 Messages concerning ext4 filesystem in dmesg: [Sun May 5 15:10:40 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) [Sun May 5 15:10:41 2024] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,relatime,errors=remount-ro |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/firmware/efi/efivars efivarfs efivarfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime | `-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=970 |-/dev udev devtmpfs rw,nosuid,relatime,size=3830252k,nr_inodes=957563,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/hugepages hugetlbfs hugetlbfs rw,relatime,pagesize=2M | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=770968k,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1003 tmpfs tmpfs rw,nosuid,nodev,relatime,size=770964k,nr_inodes=192741,mode=700,uid=1003,gid=1003 `-/boot/efi /dev/sda1 vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro Files in neuralgic directories: /var: 5.1G /var/ 2.2G /var/log/journal/39a0a1b1f40b4d4e9516e7737b580120 2.2G /var/log/journal 2.2G /var/log 2.1G /var/cache Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 16.0M in the file system. /opt/iobroker/backups: 14G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 2.9G /opt/iobroker/iobroker-data/ 1.4G /opt/iobroker/iobroker-data/backup-objects 512M /opt/iobroker/iobroker-data/history 498M /opt/iobroker/iobroker-data/files 89M /opt/iobroker/iobroker-data/files/echarts.admin The five largest files in iobroker-data are: 539M /opt/iobroker/iobroker-data/objects.jsonl 53M /opt/iobroker/iobroker-data/backup-objects/2024-05-05_10-16_objects.jsonl.gz 53M /opt/iobroker/iobroker-data/backup-objects/2024-05-05_08-16_objects.jsonl.gz 53M /opt/iobroker/iobroker-data/backup-objects/2024-05-05_06-16_objects.jsonl.gz 53M /opt/iobroker/iobroker-data/backup-objects/2024-05-05_04-16_objects.jsonl.gz 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_08190dbe5b29ec11a566757840c9ce8d-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.20.2 /usr/bin/node v18.20.2 /usr/bin/npm 10.5.0 /usr/bin/npx 10.5.0 /usr/bin/corepack 0.25.2 nodejs: Installed: 18.20.2-1nodesource1 Candidate: 18.20.2-1nodesource1 Version table: *** 18.20.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.20.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://ftp.de.debian.org/debian bullseye/main amd64 Packages 500 https://security.debian.org/debian-security bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.19 admin: 6.13.16 javascript: 7.8.0 nodejs modules from github: 2 | `-- xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc | +-- syno@3.0.0 invalid: "git+https://git@github.com/MeisterTR/syno.git" from node_modules/iobroker.synology Adapter State No connection to databases possible ... Enabled adapters with bindings ioBroker-Repositories Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! Installed ioBroker-Instances Used repository: stable <--- Last few GCs ---> [5316:0x614b850] 22264 ms: Mark-sweep 1999.4 (2093.7) -> 1997.2 (2092.7) MB, 110.2 / 0.0 ms (average mu = 0.841, current mu = 0.559) allocation failure; scavenge might not succeed [5316:0x614b850] 22519 ms: Mark-sweep 2012.9 (2092.7) -> 2008.8 (2114.2) MB, 192.9 / 0.0 ms (average mu = 0.663, current mu = 0.243) allocation failure; scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory 1: 0xb9a330 node::Abort() [node] 2: 0xaa07ee [node] 3: 0xd71ed0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node] 4: 0xd72277 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node] 5: 0xf4f635 [node] 6: 0xf61b0d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [node] 7: 0xf3c1fe v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 8: 0xf3d5c7 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [node] 9: 0xf1db40 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [node] 10: 0xf155b4 v8::internal::FactoryBase<v8::internal::Factory>::AllocateRawWithImmortalMap(int, v8::internal::AllocationType, v8::internal::Map, v8::internal::AllocationAlignment) [node] 11: 0xf17948 v8::internal::FactoryBase<v8::internal::Factory>::NewRawTwoByteString(int, v8::internal::AllocationType) [node] 12: 0x134923c v8::internal::IncrementalStringBuilder::Extend() [node] 13: 0x105d588 v8::internal::JsonStringifier::SerializeSmi(v8::internal::Smi) [node] 14: 0x106164f v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<true>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node] 15: 0x1063eaf v8::internal::JsonStringifier::Result v8::internal::JsonStringifier::Serialize_<false>(v8::internal::Handle<v8::internal::Object>, bool, v8::internal::Handle<v8::internal::Object>) [node] 16: 0x1064bff 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] 17: 0xdf7d57 v8::internal::Builtin_JsonStringify(int, unsigned long*, v8::internal::Isolate*) [node] 18: 0x1710839 [node] /usr/bin/iob: line 12: 5315 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Objects and States Please stand by - This may take a while Objects: 1 States: 11606 *** OS-Repositories and Updates *** Hit:1 https://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://ftp.de.debian.org/debian bullseye InRelease Hit:3 http://ftp.de.debian.org/debian bullseye-updates InRelease Hit:4 https://deb.nodesource.com/node_18.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:1883 0.0.0.0:* LISTEN 120 16284 571/mosquitto tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 123 16310 541/redis-server 12 tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 11928 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16257 568/sshd: /usr/sbin tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17425 539/cupsd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 17626 889/exim4 tcp6 0 0 ::1:1883 :::* LISTEN 120 16285 571/mosquitto tcp6 0 0 :::3389 :::* LISTEN 118 17472 582/xrdp tcp6 0 0 ::1:6379 :::* LISTEN 123 16311 541/redis-server 12 tcp6 0 0 :::9999 :::* LISTEN 0 16364 597/apache2 tcp6 0 0 :::111 :::* LISTEN 0 11932 1/init tcp6 0 0 :::80 :::* LISTEN 0 16360 597/apache2 tcp6 0 0 ::1:3350 :::* LISTEN 0 16486 563/xrdp-sesman tcp6 0 0 :::22 :::* LISTEN 0 16259 568/sshd: /usr/sbin tcp6 0 0 ::1:631 :::* LISTEN 0 17424 539/cupsd tcp6 0 0 ::1:25 :::* LISTEN 0 17627 889/exim4 udp 0 0 0.0.0.0:111 0.0.0.0:* 0 11929 1/init udp 0 0 0.0.0.0:631 0.0.0.0:* 0 17437 607/cups-browsed udp 0 0 0.0.0.0:5353 0.0.0.0:* 113 15259 482/avahi-daemon: r udp 0 0 0.0.0.0:1900 0.0.0.0:* 0 17537 639/minissdpd udp 0 0 0.0.0.0:59982 0.0.0.0:* 113 15261 482/avahi-daemon: r udp6 0 0 :::111 :::* 0 11935 1/init udp6 0 0 fe80::96c6:91ff:fe1:546 :::* 0 17487 486/NetworkManager udp6 0 0 :::45648 :::* 113 15262 482/avahi-daemon: r udp6 0 0 :::5353 :::* 113 15260 482/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-05-05 15:47:21.006 - info: host.debian-uli iobroker.js-controller version 5.0.19 js-controller starting 2024-05-05 15:47:21.009 - info: host.debian-uli Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-05-05 15:47:21.009 - info: host.debian-uli hostname: debian-uli, node: v18.20.2 2024-05-05 15:47:21.009 - info: host.debian-uli ip addresses: 192.168.0.9 2003:d0:3f1b:dc00:bc2d:140f:fd70:2430 2003:d0:3f1b:dc00:96c6:91ff:fe1c:266c fe80::96c6:91ff:fe1c:266c 2024-05-05 15:47:27.483 - info: host.debian-uli connected to Objects and States 2024-05-05 15:47:27.530 - info: host.debian-uli added notifications configuration of host 2024-05-05 15:47:28.033 - info: host.debian-uli 74 instances found 2024-05-05 15:47:28.074 - info: host.debian-uli starting 72 instances 2024-05-05 15:47:28.190 - info: host.debian-uli instance system.adapter.admin.0 started with pid 5388 2024-05-05 15:47:29.914 - info: admin.0 (5388) starting. Version 6.13.16 in /opt/iobroker/node_modules/iobroker.admin, node: v18.20.2, js-controller: 5.0.19 2024-05-05 15:47:29.938 - info: admin.0 (5388) requesting all objects 2024-05-05 15:47:34.203 - error: admin.0 (5388) States database error: read ECONNRESET 2024-05-05 15:47:34.208 - info: admin.0 (5388) terminating http server on port 8081 2024-05-05 15:47:35.712 - info: admin.0 (5388) terminating with timeout 2024-05-05 15:47:35.715 - info: admin.0 (5388) Terminated (NO_ERROR): Without reason 2024-05-05 15:47:39.216 - error: admin.0 (5388) Objects database error: connect ECONNREFUSED 127.0.0.1:9001 2024-05-05 15:47:43.394 - info: host.debian-uli iobroker.js-controller version 5.0.19 js-controller starting 2024-05-05 15:47:43.398 - info: host.debian-uli Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-05-05 15:47:43.398 - info: host.debian-uli hostname: debian-uli, node: v18.20.2 2024-05-05 15:47:43.399 - info: host.debian-uli ip addresses: 192.168.0.9 2003:d0:3f1b:dc00:bc2d:140f:fd70:2430 2003:d0:3f1b:dc00:96c6:91ff:fe1c:266c fe80::96c6:91ff:fe1c:266c 2024-05-05 15:47:45.475 - error: host.debian-uli-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! 2024-05-05 15:47:49.542 - info: host.debian-uli iobroker.js-controller version 5.0.19 js-controller starting 2024-05-05 15:47:49.545 - info: host.debian-uli Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker 2024-05-05 15:47:49.545 - info: host.debian-uli hostname: debian-uli, node: v18.20.2 2024-05-05 15:47:49.545 - info: host.debian-uli ip addresses: 192.168.0.9 2003:d0:3f1b:dc00:bc2d:140f:fd70:2430 2003:d0:3f1b:dc00:96c6:91ff:fe1c:266c fe80::96c6:91ff:fe1c:266c============ Mark until here for C&P =============
in /opt/iobroker/iobroker-data/ ist die Datei
-rw-rwxr--+ 1 iobroker iobroker 564240347 5. Mai 15:47 objects.jsonldoch etwas groß? Ein halbes Gigabyte???
Kann ja doch nicht sein?-rw-rwxr--+ 1 iobroker iobroker 11066570 8. Feb 2022 objects.json.bak.migrated -rw-rwxr--+ 1 iobroker iobroker 564240347 5. Mai 15:47 objects.jsonl drwxrwxr-x+ 2 iobroker iobroker 4096 5. Mai 15:50 objects.jsonl.lock -rw-rwxr--+ 1 iobroker iobroker 11067202 8. Feb 2022 objects.json.migrated drwxrwxr-x+ 2 iobroker iobroker 4096 16. Feb 2020 sqlite -rw-rwxr--+ 1 iobroker iobroker 1630625 8. Feb 2022 states.json.bak.migratedAber du hast hier sicher den richtigen Tipp?
LG Uli
-
-
@thomas-braun said in heap zu klein?:
ls -lah /opt/iobroker/iobroker-data/backup-objects/
Uli@debian-uli:~$ ls -lah /opt/iobroker/iobroker-data/backup-objects/ insgesamt 1,4G drwxrwxrwx+ 2 iobroker iobroker 72K 5. Mai 10:19 . drwxrwxrwx+ 19 iobroker iobroker 4,0K 5. Mai 16:19 .. -rw-rwxr--+ 1 iobroker iobroker 2,4M 6. Feb 2022 2022-02-06_17-35_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 312K 6. Feb 2022 2022-02-06_18-22_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 6. Feb 2022 2022-02-06_19-35_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 306K 6. Feb 2022 2022-02-06_20-23_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 6. Feb 2022 2022-02-06_21-36_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 307K 6. Feb 2022 2022-02-06_22-23_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 6. Feb 2022 2022-02-06_23-40_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 307K 7. Feb 2022 2022-02-07_00-24_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_01-45_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 307K 7. Feb 2022 2022-02-07_02-24_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_03-45_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 307K 7. Feb 2022 2022-02-07_04-24_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_05-45_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_06-25_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_07-50_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_08-25_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_09-55_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_10-25_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_11-55_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_12-26_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_13-55_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_14-26_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_16-00_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_16-26_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_18-00_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_18-26_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_20-00_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 308K 7. Feb 2022 2022-02-07_20-27_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 7. Feb 2022 2022-02-07_22-00_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 7. Feb 2022 2022-02-07_22-27_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_00-00_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_00-27_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_02-05_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_02-27_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_04-06_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_04-28_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_06-06_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_06-28_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_08-10_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_08-28_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_10-10_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_10-29_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_12-10_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_12-29_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_14-10_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 310K 8. Feb 2022 2022-02-08_14-29_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_16-11_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 309K 8. Feb 2022 2022-02-08_16-11_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,4M 8. Feb 2022 2022-02-08_16-12_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 310K 8. Feb 2022 2022-02-08_16-13_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 197K 8. Feb 2022 2022-02-08_16-22_states.json.gz -rw-rwxr--+ 1 iobroker iobroker 2,2M 8. Feb 2022 2022-02-08_16-23_objects.json.gz -rw-rwxr--+ 1 iobroker iobroker 53M 3. Mai 11:09 2024-05-03_11-08_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 303K 3. Mai 11:12 2024-05-03_11-12_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 3. Mai 13:10 2024-05-03_13-08_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 3. Mai 13:12 2024-05-03_13-12_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 3. Mai 15:25 2024-05-03_15-24_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 294K 3. Mai 15:25 2024-05-03_15-25_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 3. Mai 17:25 2024-05-03_17-24_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 303K 3. Mai 17:25 2024-05-03_17-25_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 3. Mai 20:16 2024-05-03_20-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 299K 3. Mai 20:16 2024-05-03_20-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 3. Mai 22:16 2024-05-03_22-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 3. Mai 22:16 2024-05-03_22-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 00:16 2024-05-04_00-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 293K 4. Mai 00:16 2024-05-04_00-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 02:16 2024-05-04_02-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 4. Mai 02:16 2024-05-04_02-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 04:16 2024-05-04_04-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 4. Mai 04:16 2024-05-04_04-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 06:16 2024-05-04_06-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 294K 4. Mai 06:16 2024-05-04_06-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 08:16 2024-05-04_08-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 300K 4. Mai 08:16 2024-05-04_08-16_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 10:19 2024-05-04_10-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 300K 4. Mai 10:19 2024-05-04_10-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 12:16 2024-05-04_12-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 4. Mai 12:18 2024-05-04_12-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 14:16 2024-05-04_14-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 4. Mai 14:18 2024-05-04_14-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 16:16 2024-05-04_16-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 4. Mai 16:18 2024-05-04_16-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 18:16 2024-05-04_18-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 4. Mai 18:18 2024-05-04_18-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 20:16 2024-05-04_20-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 303K 4. Mai 20:18 2024-05-04_20-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 4. Mai 22:16 2024-05-04_22-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 303K 4. Mai 22:18 2024-05-04_22-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 5. Mai 00:16 2024-05-05_00-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 5. Mai 00:18 2024-05-05_00-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 5. Mai 02:16 2024-05-05_02-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 5. Mai 02:18 2024-05-05_02-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 5. Mai 04:16 2024-05-05_04-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 5. Mai 04:18 2024-05-05_04-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 5. Mai 06:16 2024-05-05_06-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 5. Mai 06:18 2024-05-05_06-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 5. Mai 08:16 2024-05-05_08-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 5. Mai 08:18 2024-05-05_08-18_states.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 53M 5. Mai 10:19 2024-05-05_10-16_objects.jsonl.gz -rw-rwxr--+ 1 iobroker iobroker 302K 5. Mai 10:19 2024-05-05_10-18_states.jsonl.gz Uli@debian-uli:~$ -
@pingps sagte in heap zu klein?:
Die Files von 2022 kannste löschen, braucht keiner mehr.
Die aktuelle Datenbank ist aber ungewöhnlich groß, würde ich behaupten.
Auf meiner Kiste schaut das so aus:echad@chet:~ $ ls -lah /opt/iobroker/iobroker-data/backup-objects/ total 156M drwxrwxr-x+ 2 iobroker iobroker 4.0K May 5 15:50 . drwxrwxr-x+ 12 iobroker iobroker 4.0K May 5 16:14 .. -rw-rw-r--+ 1 iobroker iobroker 6.3M May 3 17:50 2024-05-03_17-50_objects.jsonl.gz -rw-rw-r--+ 1 iobroker iobroker 275K May 3 17:50 2024-05-03_17-50_states.jsonl.gz -rw-rw-r--+ 1 iobroker iobroker 6.3M May 3 19:50 2024-05-03_19-50_objects.jsonl.gz -rw-rw-r--+ 1 iobroker iobroker 275K May 3 19:50 2024-05-03_19-50_states.jsonl.gzWobei ich jetzt aber auch nicht der große Datenhamster bin.
-
2024-05-05 15:47:28.033 - info: host.debian-uli 74 instances found
2024-05-05 15:47:28.074 - info: host.debian-uli starting 72 instancesUi. Da könnte der kleine Celeron etwas überlastet sein.
-
@thomas-braun ok, also instanzen löschen?
Eigentlich war er jetzt nicht unnötig langsam. Ok, das System hat auch schon einige Jahre auf dem Buckel und könnte langsam ersetzt werden. Bisher lief er aber immer noch ganz gut.
Was hast du für eine HW? Würdest du sie aktuell wieder beschaffen oder was würdest du empfehlen?
Aber aktuell startet der iob nicht mehr - kein Kringel beim Starten...Grüße
Uli -
@pingps sagte in heap zu klein?:
Was hast du für eine HW? Würdest du sie aktuell wieder beschaffen oder was würdest du empfehlen?
echad@chet _,met$$$$$gg. ---------- ,g$$$$$$$$$$$$$$$P. OS: Debian GNU/Linux trixie/sid (trixie) aarch64 ,g$$P" "\""Y$$.". Host: Raspberry Pi 4 Model B Rev 1.4 ,$$P' `$$$. Kernel: 6.6.28+rpt-rpi-v8 ',$$P ,ggs. `$$b: Uptime: 5 days, 21 hours, 35 mins `d$$' ,$P"' . $$$ Packages: 2 (npm), 994 (dpkg) $$P d$' , $$P Shell: bash 5.2.21 $$: $$. - ,d$$' Terminal: /dev/pts/0 $$; Y$b._ _,d$P' CPU: ARM Cortex-A72 (4) @ 1.80 GHz Y$$. `.`"Y$$$$P"' Memory: 3.12 GiB / 7.62 GiB (41%) `$$b "-.__ Network: 1 Gbps `Y$$ `Y$$. `$$b. `Y$$b. `"Y$b._ `"\""Der dürfte dir bei 72 Instanzen aber auch zu klein sein.
-
@thomas-braun ein Pi kommt mir hier für den iobroker nicht mehr ins Haus.
Also dürfte eigentlich mein Nuc schon starten. Momentan sind mir aber keine Fehler bekannt und nix tut sich.
Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!Ich denke, das Problem sollte lösbar sein?
Grüße
Uli -
Die Datei dürfte zu groß sein.
Stop mal ein paar der 70 Instanzen und starte den ioBroker oder besser den kompletten Rechner mal durch.
Und dann mal kritischen Auges durch die Instanzen gehen und überlegen, ob man wirklich mehr als 70 Instanzen von irgendwas braucht. -
@pingps sagte in heap zu klein?:
ein Pi kommt mir hier für den iobroker nicht mehr ins Haus.
wieso nicht?
ich bin gerade vom NUC mit Proxmox wieder zurück auf einen Pi5, auf den dann auch noch die Instanzen zweier Slaves gebracht wurden.
-
@homoran sagte in heap zu klein?:
wieso nicht?
Läuft vermutlich zu gut. Da muss man dann ja nix mehr dran basteln. ;-D
-
@thomas-braun das System soll ja laufen und ich will da nicht viel basteln.
Hatte auch schon ein paar Instanzen gelöscht. Aber seit dem Absturz läuft garnix mehr. Da muss noch was im Argen liegen.
Ich spiele mal ein backup ein. Auch wenn das die Instanzen beibehält.
-
@pingps sagte in heap zu klein?:
das System soll ja laufen und ich will da nicht viel basteln.
Ja, eben. Deswegen verwende ich da einen Raspberry...
-
@thomas-braun also die RPIs, die ich bisher verwende, brauchen 5,2V Spannung. Das ist ja ein Nogo. Die Probleme, die ich mit den RPIs bisher hatte, kannte ich vom Nuc überhaupt nicht. Das Ding läuft - ok, lief bisher, und tat seinen Dienst. Beim RPI geht ständig die SD Karte kaputt. Sowas gibts beim Nuc nicht.
Ok, den RPI5 habe ich jetzt noch nicht angeguckt. Womöglich hat er das Problem nicht. -
@pingps sagte in heap zu klein?:
Beim RPI geht ständig die SD Karte kaputt.
Hier nicht. Du machst also da im Umgang mit der Kiste irgendwas verkehrt... Wird aber OT.
-
@pingps sagte in heap zu klein?:
Beim RPI geht ständig die SD Karte kaputt
hab ich ihn 10 Jahren kein einziges mal gehabt!
Dabei habe ich 50GB History Daten drauf, die teilweise im Sekundentakt geschrieben werden.
