NEWS
Limit der Objekte für eine Instanz
ioBroker Allgemein
6
Beiträge
5
Kommentatoren
165
Aufrufe
3
Watching
-
Liebe alle,
mein IOB wirft seit einige Wochen diesen Fehler aus : „This instance has 5788 objects, the limit for this instance is set to 5000.“
Es geht um den HM-Adapter, konkret ist es die Instanz, die die HMIP-Geräte abruft. Als Protokoll ist „XML-RPC“ gewählt. Ich nutze seit Jahren IOB zusammen mit HM(IP). Es sind immer mal ein paar Devices hinzugekommen. Der Objektbaum zeigt tatsächlkich so viele Objekte. Es sind vielleicht 80 Devices. Aber natürlich eröffnet jedes Devices zahlreiche Unterordnet; gertade bei HMIP ist es ja mehr als bei HM.
Auch mit den hier gefundenen Postings komme ich nicht weiter. Mir ist nicht klar, was ich jetzt tun soll:
Ich habe schon gelesen, dass der Fehler auf ein Konfigutarationsproblem hindeutet. Aber wenn ich unter „Objekte“ schaue, erscheint mir nichts unplausibel.
Kann ich das Limit hochsetzen? MIr ist leider nicht klar, wie.
Ich bin für jeden Fingerzeit dankbar.
Liebe Grüße!
-
Liebe alle,
mein IOB wirft seit einige Wochen diesen Fehler aus : „This instance has 5788 objects, the limit for this instance is set to 5000.“
Es geht um den HM-Adapter, konkret ist es die Instanz, die die HMIP-Geräte abruft. Als Protokoll ist „XML-RPC“ gewählt. Ich nutze seit Jahren IOB zusammen mit HM(IP). Es sind immer mal ein paar Devices hinzugekommen. Der Objektbaum zeigt tatsächlkich so viele Objekte. Es sind vielleicht 80 Devices. Aber natürlich eröffnet jedes Devices zahlreiche Unterordnet; gertade bei HMIP ist es ja mehr als bei HM.
Auch mit den hier gefundenen Postings komme ich nicht weiter. Mir ist nicht klar, was ich jetzt tun soll:
Ich habe schon gelesen, dass der Fehler auf ein Konfigutarationsproblem hindeutet. Aber wenn ich unter „Objekte“ schaue, erscheint mir nichts unplausibel.
Kann ich das Limit hochsetzen? MIr ist leider nicht klar, wie.
Ich bin für jeden Fingerzeit dankbar.
Liebe Grüße!
@Marc_St sagte in Limit der Objekte für eine Instanz:
Fingerzeit
-
Liebe alle,
mein IOB wirft seit einige Wochen diesen Fehler aus : „This instance has 5788 objects, the limit for this instance is set to 5000.“
Es geht um den HM-Adapter, konkret ist es die Instanz, die die HMIP-Geräte abruft. Als Protokoll ist „XML-RPC“ gewählt. Ich nutze seit Jahren IOB zusammen mit HM(IP). Es sind immer mal ein paar Devices hinzugekommen. Der Objektbaum zeigt tatsächlkich so viele Objekte. Es sind vielleicht 80 Devices. Aber natürlich eröffnet jedes Devices zahlreiche Unterordnet; gertade bei HMIP ist es ja mehr als bei HM.
Auch mit den hier gefundenen Postings komme ich nicht weiter. Mir ist nicht klar, was ich jetzt tun soll:
Ich habe schon gelesen, dass der Fehler auf ein Konfigutarationsproblem hindeutet. Aber wenn ich unter „Objekte“ schaue, erscheint mir nichts unplausibel.
Kann ich das Limit hochsetzen? MIr ist leider nicht klar, wie.
Ich bin für jeden Fingerzeit dankbar.
Liebe Grüße!
@Marc_St sagte in Limit der Objekte für eine Instanz:
Kann ich das Limit hochsetzen? MIr ist leider nicht klar, wie.
unter system.adapter im expertenmodus bei dem jeweiligen Adapter
als Beispiel
-
@Marc_St sagte in Limit der Objekte für eine Instanz:
Fingerzeit
@Homoran sagte in Limit der Objekte für eine Instanz:
@Marc_St sagte in Limit der Objekte für eine Instanz:
Fingerzeit
========== Start marking the full check here =========== ```bash Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 6.17.2-2-pve Architecture: x86-64 OS is similar to: model name : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 21:15:19 up 23:14, 0 users, load average: 1.33, 1.10, 0.73 CPU threads: 2 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Tue 2026-02-10 21:15:20 CET Universal time: Tue 2026-02-10 20:15:20 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/root GROUPS=iobroker tty dialout audio video plugdev A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'! A root login is not required in most Linux Distributions. Run 'iobroker fix' or use the system tools to create a user. *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 4.3G 2.1G 1.8G 3.4M 414M 2.2G Swap: 536M 0B 536M Total: 4.8G 2.1G 2.3G Active iob-Instances: 17 4096 M total memory 2033 M used memory 2155 M active memory 176 M inactive memory 1670 M free memory 0 M buffer memory 395 M swap cache 512 M total swap 0 M used swap 512 M free swap *** top - Table Of Processes *** top - 21:15:20 up 23:14, 0 users, load average: 1.33, 1.10, 0.73 Tasks: 44 total, 4 running, 40 sleeping, 0 stopped, 0 zombie %Cpu(s): 45.0 us, 15.0 sy, 0.0 ni, 35.0 id, 0.0 wa, 0.0 hi, 5.0 si, 0.0 st MiB Mem : 4096.0 total, 1668.3 free, 2035.2 used, 395.7 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 2060.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System Legend: 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 *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--103--disk--0 ext4 7.8G 3.8G 3.7G 51% / none tmpfs 492K 4.0K 488K 1% /dev none tmpfs 8.0K 4.0K 4.0K 50% /dev/ttyUSB0 udev devtmpfs 6.8G 0 6.8G 0% /dev/tty tmpfs tmpfs 6.8G 0 6.8G 0% /dev/shm tmpfs tmpfs 2.8G 104K 2.8G 1% /run tmpfs tmpfs 6.8G 3.2M 6.8G 1% /tmp tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--103--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 437M /var/ 282M /var/lib 121M /var/lib/redis 95M /var/cache 91M /var/cache/apt Archived and active journals take up 52.9M in the file system. /opt/iobroker/backups: 126M /opt/iobroker/backups/ 4.0K /opt/iobroker/backups/redistmp /opt/iobroker/iobroker-data: 312M /opt/iobroker/iobroker-data/ 64M /opt/iobroker/iobroker-data/files 47M /opt/iobroker/iobroker-data/files/admin.admin 46M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets 46M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 8.1M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-C_W7K-9p.js 5.8M /opt/iobroker/iobroker-data/objects.jsonl 3.7M /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/index-ConOsPbp.js 3.7M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-ZPb95xPG.js 3.7M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-IIKn7Ixx.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-FTDI_FT232R_USB_UART_A106Q3H7-if00-port0 No nvbackup.json found. *** 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 ✓ Node.js installation is correct nodejs: Installed: 22.22.0-1nodesource1 Candidate: 22.22.0-1nodesource1 Version table: *** 22.22.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.21.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.20.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/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 iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Hosts: iobroker iobroker (version: 7.1.0, hostname: iobroker , alive, uptime: 83675) Core adapters versions js-controller: 7.1.0 admin: 7.7.23 javascript: 9.0.18 nodejs modules from github: 1 +-- iobroker.sourceanalytix@0.4.15-alpha.1 (git+ssh://git@github.com/DrozmotiX/ioBroker.sourceanalytix.git#3b0259b526e1d855ca8db5f7cb5c0bfa58bd4270) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.daswetter.0 : daswetter : iobroker - enabled system.adapter.echarts.0 : echarts : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 12010 + system.adapter.hm-rpc.3 : hm-rpc : iobroker - enabled, port: 0 system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: iobroker - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker - disabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.material.0 : material : iobroker - disabled + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 system.adapter.schoolfree.0 : schoolfree : iobroker - enabled + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.smartmeter.0 : smartmeter : iobroker - enabled + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.statistics.0 : statistics : iobroker - enabled system.adapter.vis-bars.0 : vis : iobroker - disabled system.adapter.vis-canvas-gauges.0 : vis : iobroker - disabled system.adapter.vis-fancyswitch.0 : vis : iobroker - disabled system.adapter.vis-history.0 : vis : iobroker - disabled system.adapter.vis-hqwidgets.0 : vis : iobroker - disabled system.adapter.vis-jqui-mfd.0 : vis : iobroker - disabled system.adapter.vis-justgage.0 : vis : iobroker - disabled system.adapter.vis-material-advanced.0 : vis : iobroker - disabled system.adapter.vis-materialdesign.0 : vis : iobroker - disabled system.adapter.vis-metro.0 : vis : iobroker - disabled system.adapter.vis-rgraph.0 : vis : iobroker - disabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 12010 + system.adapter.hm-rpc.3 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ true │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Beta (latest) Upgrade policy: none Installed ioBroker-Adapters Used repository: Beta (latest) Adapter "admin" : 7.7.28 , installed 7.7.23 [Updatable] Adapter "daswetter" : 4.5.1 , installed 3.2.8 [Updatable] Adapter "echarts" : 2.0.10 , installed 2.0.10 Adapter "feiertage" : 1.2.1 , installed 1.2.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 3.0.1 , installed 3.0.1 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 5.0.12 , installed 5.0.12 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.1.0 , installed 7.1.0 Adapter "material" : 1.3.1 , installed 1.3.1 Adapter "modbus" : 7.0.6 , installed 7.0.6 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "schoolfree" : 1.1.13 , installed 1.1.13 Adapter "simple-api" : 3.0.7 , installed 3.0.7 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 7.0.8 , installed 7.0.8 Adapter "sourceanalytix": 0.4.14 , installed 0.4.15-alpha.1 Adapter "statistics" : 4.0.0 , installed 4.0.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.6.0 , installed 1.6.0 Adapter "vis-jqui-mfd" : 1.1.3 , installed 1.1.1 [Updatable] Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "web" : 7.0.9 , installed 7.0.9 Adapter "ws" : 3.0.19 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 20257 States: 18376 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Err:4 https://deb.nodesource.com/node_22.x nodistro InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Some index files failed to download. They have been ignored, or old ones used instead. Pending systemupdates: 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 0.0.0.0:111 0.0.0.0:* LISTEN 0 8322757 1/init tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 104 8326256 92/redis-server 127 tcp 0 0 10.0.1.152:12010 0.0.0.0:* LISTEN 1000 8331284 494/io.hm-rpc.2 tcp 0 0 10.0.1.152:12001 0.0.0.0:* LISTEN 1000 8327155 479/io.hm-rpc.1 tcp 0 0 10.0.1.152:18701 0.0.0.0:* LISTEN 1000 8329241 464/io.hm-rpc.0 tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 8326501 302/master tcp 0 0 10.0.1.152:502 0.0.0.0:* LISTEN 1000 8331359 524/io.modbus.0 tcp 0 0 127.0.0.1:8701 0.0.0.0:* LISTEN 1000 8329322 509/io.hm-rpc.3 tcp6 0 0 :::111 :::* LISTEN 0 8322759 1/init tcp6 0 0 :::22 :::* LISTEN 0 8323004 1/init tcp6 0 0 ::1:25 :::* LISTEN 0 8326502 302/master tcp6 0 0 ::1:6379 :::* LISTEN 104 8326257 92/redis-server 127 tcp6 0 0 :::8082 :::* LISTEN 1000 8329762 675/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1000 8327763 347/io.admin.0 tcp6 0 0 :::8087 :::* LISTEN 1000 8329618 615/io.simple-api.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 8327403 164/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 8322758 1/init udp6 0 0 :::111 :::* 0 8322760 1/init *** Log File - Last 25 Lines *** 2026-02-10 21:12:25.284 - warn: smartmeter.0 (2766) No or too long answer from Serial Device after last request. 2026-02-10 21:12:25.284 - debug: smartmeter.0 (2766) Error: No or too long answer from Serial Device after last request. 2026-02-10 21:12:25.284 - debug: smartmeter.0 (2766) Transport Reset!! Restart = true 2026-02-10 21:12:25.284 - debug: smartmeter.0 (2766) SCHEDULE NEXT RUN IN 60s 2026-02-10 21:13:25.284 - debug: smartmeter.0 (2766) CREATE SERIALPORT: 115200 8 1 none 2026-02-10 21:13:25.284 - debug: smartmeter.0 (2766) SET MESSAGE TIMEOUT TIMER: 60000 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) MESSAGE TIMEOUT TRIGGERED 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) Error: No or too long answer from Serial Device after last request. 2026-02-10 21:14:25.283 - warn: smartmeter.0 (2766) No or too long answer from Serial Device after last request. 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) Error: No or too long answer from Serial Device after last request. 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) Transport Reset!! Restart = true 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) SCHEDULE NEXT RUN IN 60s 2026-02-10 21:15:18.010 - info: host.iobroker instance system.adapter.daswetter.0 in version "3.2.8" started with pid 6776 2026-02-10 21:15:22.230 - info: host.iobroker instance system.adapter.daswetter.0 having pid 6776 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-02-10 21:15:25.284 - debug: smartmeter.0 (2766) CREATE SERIALPORT: 115200 8 1 none 2026-02-10 21:15:25.284 - debug: smartmeter.0 (2766) SET MESSAGE TIMEOUT TIMER: 60000 2026-02-10 21:15:43.878 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.memRss 2026-02-10 21:15:43.879 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.connected 2026-02-10 21:15:44.079 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.inputCount 2026-02-10 21:15:44.181 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.cpu 2026-02-10 21:15:44.383 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.memHeapTotal 2026-02-10 21:15:44.586 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.outputCount 2026-02-10 21:15:44.789 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.cputime 2026-02-10 21:15:44.789 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.uptime 2026-02-10 21:15:44.789 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.memHeapUsed============ Mark until here for C&P =============```
-
Liebe alle,
mein IOB wirft seit einige Wochen diesen Fehler aus : „This instance has 5788 objects, the limit for this instance is set to 5000.“
Es geht um den HM-Adapter, konkret ist es die Instanz, die die HMIP-Geräte abruft. Als Protokoll ist „XML-RPC“ gewählt. Ich nutze seit Jahren IOB zusammen mit HM(IP). Es sind immer mal ein paar Devices hinzugekommen. Der Objektbaum zeigt tatsächlkich so viele Objekte. Es sind vielleicht 80 Devices. Aber natürlich eröffnet jedes Devices zahlreiche Unterordnet; gertade bei HMIP ist es ja mehr als bei HM.
Auch mit den hier gefundenen Postings komme ich nicht weiter. Mir ist nicht klar, was ich jetzt tun soll:
Ich habe schon gelesen, dass der Fehler auf ein Konfigutarationsproblem hindeutet. Aber wenn ich unter „Objekte“ schaue, erscheint mir nichts unplausibel.
Kann ich das Limit hochsetzen? MIr ist leider nicht klar, wie.
Ich bin für jeden Fingerzeit dankbar.
Liebe Grüße!
-
@Homoran sagte in Limit der Objekte für eine Instanz:
@Marc_St sagte in Limit der Objekte für eine Instanz:
Fingerzeit
========== Start marking the full check here =========== ```bash Script v.2026-01-31 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 6.17.2-2-pve Architecture: x86-64 OS is similar to: model name : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 21:15:19 up 23:14, 0 users, load average: 1.33, 1.10, 0.73 CPU threads: 2 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Tue 2026-02-10 21:15:20 CET Universal time: Tue 2026-02-10 20:15:20 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/root GROUPS=iobroker tty dialout audio video plugdev A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'! A root login is not required in most Linux Distributions. Run 'iobroker fix' or use the system tools to create a user. *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: *** MEMORY *** total used free shared buff/cache available Mem: 4.3G 2.1G 1.8G 3.4M 414M 2.2G Swap: 536M 0B 536M Total: 4.8G 2.1G 2.3G Active iob-Instances: 17 4096 M total memory 2033 M used memory 2155 M active memory 176 M inactive memory 1670 M free memory 0 M buffer memory 395 M swap cache 512 M total swap 0 M used swap 512 M free swap *** top - Table Of Processes *** top - 21:15:20 up 23:14, 0 users, load average: 1.33, 1.10, 0.73 Tasks: 44 total, 4 running, 40 sleeping, 0 stopped, 0 zombie %Cpu(s): 45.0 us, 15.0 sy, 0.0 ni, 35.0 id, 0.0 wa, 0.0 hi, 5.0 si, 0.0 st MiB Mem : 4096.0 total, 1668.3 free, 2035.2 used, 395.7 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 2060.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System Legend: 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 *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--103--disk--0 ext4 7.8G 3.8G 3.7G 51% / none tmpfs 492K 4.0K 488K 1% /dev none tmpfs 8.0K 4.0K 4.0K 50% /dev/ttyUSB0 udev devtmpfs 6.8G 0 6.8G 0% /dev/tty tmpfs tmpfs 6.8G 0 6.8G 0% /dev/shm tmpfs tmpfs 2.8G 104K 2.8G 1% /run tmpfs tmpfs 6.8G 3.2M 6.8G 1% /tmp tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--103--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 437M /var/ 282M /var/lib 121M /var/lib/redis 95M /var/cache 91M /var/cache/apt Archived and active journals take up 52.9M in the file system. /opt/iobroker/backups: 126M /opt/iobroker/backups/ 4.0K /opt/iobroker/backups/redistmp /opt/iobroker/iobroker-data: 312M /opt/iobroker/iobroker-data/ 64M /opt/iobroker/iobroker-data/files 47M /opt/iobroker/iobroker-data/files/admin.admin 46M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets 46M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 8.1M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-C_W7K-9p.js 5.8M /opt/iobroker/iobroker-data/objects.jsonl 3.7M /opt/iobroker/iobroker-data/files/backitup.admin/custom/assets/index-ConOsPbp.js 3.7M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-ZPb95xPG.js 3.7M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-IIKn7Ixx.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-FTDI_FT232R_USB_UART_A106Q3H7-if00-port0 No nvbackup.json found. *** 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 ✓ Node.js installation is correct nodejs: Installed: 22.22.0-1nodesource1 Candidate: 22.22.0-1nodesource1 Version table: *** 22.22.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.21.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.20.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/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 iobroker is running on this host. At least one iobroker host is running. Objects type: redis States type: redis Hosts: iobroker iobroker (version: 7.1.0, hostname: iobroker , alive, uptime: 83675) Core adapters versions js-controller: 7.1.0 admin: 7.7.23 javascript: 9.0.18 nodejs modules from github: 1 +-- iobroker.sourceanalytix@0.4.15-alpha.1 (git+ssh://git@github.com/DrozmotiX/ioBroker.sourceanalytix.git#3b0259b526e1d855ca8db5f7cb5c0bfa58bd4270) Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.daswetter.0 : daswetter : iobroker - enabled system.adapter.echarts.0 : echarts : iobroker - disabled system.adapter.feiertage.0 : feiertage : iobroker - enabled + system.adapter.history.0 : history : iobroker - enabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 12010 + system.adapter.hm-rpc.3 : hm-rpc : iobroker - enabled, port: 0 system.adapter.icons-addictive-flavour-png.0: icons-addictive-flavour-png: iobroker - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : iobroker - disabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled system.adapter.material.0 : material : iobroker - disabled + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 system.adapter.schoolfree.0 : schoolfree : iobroker - enabled + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.smartmeter.0 : smartmeter : iobroker - enabled + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.statistics.0 : statistics : iobroker - enabled system.adapter.vis-bars.0 : vis : iobroker - disabled system.adapter.vis-canvas-gauges.0 : vis : iobroker - disabled system.adapter.vis-fancyswitch.0 : vis : iobroker - disabled system.adapter.vis-history.0 : vis : iobroker - disabled system.adapter.vis-hqwidgets.0 : vis : iobroker - disabled system.adapter.vis-jqui-mfd.0 : vis : iobroker - disabled system.adapter.vis-justgage.0 : vis : iobroker - disabled system.adapter.vis-material-advanced.0 : vis : iobroker - disabled system.adapter.vis-materialdesign.0 : vis : iobroker - disabled system.adapter.vis-metro.0 : vis : iobroker - disabled system.adapter.vis-rgraph.0 : vis : iobroker - disabled system.adapter.vis.0 : vis : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 12010 + system.adapter.hm-rpc.3 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories ┌─────────┬────────────────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼────────────────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'Stable (default)' │ 'http://download.iobroker.net/sources-dist.json' │ true │ │ 1 │ 'Beta (latest)' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴────────────────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): Beta (latest) Upgrade policy: none Installed ioBroker-Adapters Used repository: Beta (latest) Adapter "admin" : 7.7.28 , installed 7.7.23 [Updatable] Adapter "daswetter" : 4.5.1 , installed 3.2.8 [Updatable] Adapter "echarts" : 2.0.10 , installed 2.0.10 Adapter "feiertage" : 1.2.1 , installed 1.2.1 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 3.0.1 , installed 3.0.1 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-svg": 1.2.0 , installed 1.2.0 Adapter "iot" : 5.0.12 , installed 5.0.12 Adapter "javascript" : 9.0.18 , installed 9.0.18 Controller "js-controller": 7.1.0 , installed 7.1.0 Adapter "material" : 1.3.1 , installed 1.3.1 Adapter "modbus" : 7.0.6 , installed 7.0.6 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "schoolfree" : 1.1.13 , installed 1.1.13 Adapter "simple-api" : 3.0.7 , installed 3.0.7 Adapter "smartmeter" : 3.4.0 , installed 3.4.0 Adapter "socketio" : 7.0.8 , installed 7.0.8 Adapter "sourceanalytix": 0.4.14 , installed 0.4.15-alpha.1 Adapter "statistics" : 4.0.0 , installed 4.0.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-bars" : 0.1.4 , installed 0.1.4 Adapter "vis-canvas-gauges": 1.0.1, installed 1.0.1 Adapter "vis-fancyswitch": 1.1.0 , installed 1.1.0 Adapter "vis-history" : 1.0.0 , installed 1.0.0 Adapter "vis-hqwidgets": 1.6.0 , installed 1.6.0 Adapter "vis-jqui-mfd" : 1.1.3 , installed 1.1.1 [Updatable] Adapter "vis-justgage" : 2.1.7 , installed 2.1.7 Adapter "vis-material-advanced": 1.7.4, installed 1.7.4 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-metro" : 1.2.0 , installed 1.2.0 Adapter "vis-rgraph" : 0.0.2 , installed 0.0.2 Adapter "web" : 7.0.9 , installed 7.0.9 Adapter "ws" : 3.0.19 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 20257 States: 18376 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Err:4 https://deb.nodesource.com/node_22.x nodistro InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Failed to fetch https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound: No binding signature at time 2026-01-23T18:12:38Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z W: Some index files failed to download. They have been ignored, or old ones used instead. Pending systemupdates: 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 0.0.0.0:111 0.0.0.0:* LISTEN 0 8322757 1/init tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 104 8326256 92/redis-server 127 tcp 0 0 10.0.1.152:12010 0.0.0.0:* LISTEN 1000 8331284 494/io.hm-rpc.2 tcp 0 0 10.0.1.152:12001 0.0.0.0:* LISTEN 1000 8327155 479/io.hm-rpc.1 tcp 0 0 10.0.1.152:18701 0.0.0.0:* LISTEN 1000 8329241 464/io.hm-rpc.0 tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 8326501 302/master tcp 0 0 10.0.1.152:502 0.0.0.0:* LISTEN 1000 8331359 524/io.modbus.0 tcp 0 0 127.0.0.1:8701 0.0.0.0:* LISTEN 1000 8329322 509/io.hm-rpc.3 tcp6 0 0 :::111 :::* LISTEN 0 8322759 1/init tcp6 0 0 :::22 :::* LISTEN 0 8323004 1/init tcp6 0 0 ::1:25 :::* LISTEN 0 8326502 302/master tcp6 0 0 ::1:6379 :::* LISTEN 104 8326257 92/redis-server 127 tcp6 0 0 :::8082 :::* LISTEN 1000 8329762 675/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1000 8327763 347/io.admin.0 tcp6 0 0 :::8087 :::* LISTEN 1000 8329618 615/io.simple-api.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 8327403 164/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 8322758 1/init udp6 0 0 :::111 :::* 0 8322760 1/init *** Log File - Last 25 Lines *** 2026-02-10 21:12:25.284 - warn: smartmeter.0 (2766) No or too long answer from Serial Device after last request. 2026-02-10 21:12:25.284 - debug: smartmeter.0 (2766) Error: No or too long answer from Serial Device after last request. 2026-02-10 21:12:25.284 - debug: smartmeter.0 (2766) Transport Reset!! Restart = true 2026-02-10 21:12:25.284 - debug: smartmeter.0 (2766) SCHEDULE NEXT RUN IN 60s 2026-02-10 21:13:25.284 - debug: smartmeter.0 (2766) CREATE SERIALPORT: 115200 8 1 none 2026-02-10 21:13:25.284 - debug: smartmeter.0 (2766) SET MESSAGE TIMEOUT TIMER: 60000 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) MESSAGE TIMEOUT TRIGGERED 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) Error: No or too long answer from Serial Device after last request. 2026-02-10 21:14:25.283 - warn: smartmeter.0 (2766) No or too long answer from Serial Device after last request. 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) Error: No or too long answer from Serial Device after last request. 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) Transport Reset!! Restart = true 2026-02-10 21:14:25.283 - debug: smartmeter.0 (2766) SCHEDULE NEXT RUN IN 60s 2026-02-10 21:15:18.010 - info: host.iobroker instance system.adapter.daswetter.0 in version "3.2.8" started with pid 6776 2026-02-10 21:15:22.230 - info: host.iobroker instance system.adapter.daswetter.0 having pid 6776 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2026-02-10 21:15:25.284 - debug: smartmeter.0 (2766) CREATE SERIALPORT: 115200 8 1 none 2026-02-10 21:15:25.284 - debug: smartmeter.0 (2766) SET MESSAGE TIMEOUT TIMER: 60000 2026-02-10 21:15:43.878 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.memRss 2026-02-10 21:15:43.879 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.connected 2026-02-10 21:15:44.079 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.inputCount 2026-02-10 21:15:44.181 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.cpu 2026-02-10 21:15:44.383 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.memHeapTotal 2026-02-10 21:15:44.586 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.outputCount 2026-02-10 21:15:44.789 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.cputime 2026-02-10 21:15:44.789 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.uptime 2026-02-10 21:15:44.789 - silly: smartmeter.0 (2766) redis message expired/evicted __keyevent@0__:expired:io.system.adapter.daswetter.0.memHeapUsed============ Mark until here for C&P =============```
Und dann das übliche...
Hampel da nicht als root herum, auch nicht in 'nur einem LXC'.
Richte einen user ein.CPU threads: 2
Würde ich höher setzen.
Das nodesource-Repo möchtest du nochmal richtig einrichten. Mach es per
iob nodejs-update 22Rückfragen mit y beantworten.
Installier die Adapter-Updates.
628
Online32.6k
Benutzer82.3k
Themen1.3m
Beiträge