NEWS
openDTU-Adapter läßt sich nicht updaten
ioBroker Allgemein
7
Beiträge
4
Kommentatoren
392
Aufrufe
4
Watching
-
Sorry, sollte das Thema hier falsch sein. Aber ich komme leider nicht weiter:
Ich kann den openDTU-Adapter nicht updaten. Es wird eine Fehlermeldung angezeigt.
Hat jemand eine Idee?
-
Sorry, sollte das Thema hier falsch sein. Aber ich komme leider nicht weiter:
Ich kann den openDTU-Adapter nicht updaten. Es wird eine Fehlermeldung angezeigt.
Hat jemand eine Idee?
@hape1 sagte in openDTU-Adapter läßt sich nicht updates:
Hat jemand eine Idee?
Ja: Deine Node-Version scheint zu alt.
Was hast Du da laufen?
Bitte mal die Langfassung voniob diaghier in Code-Tags </> posten.
-
Heute: Deutsche Meisterschaft im Synchronposten :grin: :grin: :grin:
-
@hape1 sagte in openDTU-Adapter läßt sich nicht updates:
Hat jemand eine Idee?
Ja: Deine Node-Version scheint zu alt.
Was hast Du da laufen?
Bitte mal die Langfassung voniob diaghier in Code-Tags </> posten.
@codierknecht sagte in openDTU-Adapter läßt sich nicht updates:
iob diag
========== Start marking the full check here =========== ```bash Script v.2025-02-02 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Ubuntu 22.04.5 LTS Kernel: Linux 6.8.12-8-pve Architecture: x86-64 OS is similar to: debian model name : Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 21:19:16 up 24 min, 2 users, load average: 0.08, 0.07, 0.10 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System codenamed 'jammy' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time! *** TIME AND TIMEZONES *** Local time: Tue 2025-02-04 21:19:16 CET Universal time: Tue 2025-02-04 20:19:16 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 GROUPS=iobroker tty dialout audio video 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 Desktop: Terminal: 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.1G 908M 2.6G 0.0K 633M 3.2G Swap: 1.0G 0B 1.0G Total: 5.1G 908M 3.6G Active iob-Instances: 11 4096 M total memory 909 M used memory 961 M active memory 477 M inactive memory 2553 M free memory 0 M buffer memory 633 M swap cache 1024 M total swap 0 M used swap 1024 M free swap *** top - Table Of Processes *** top - 21:19:16 up 24 min, 2 users, load average: 0.08, 0.07, 0.10 Tasks: 38 total, 1 running, 37 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 4096.0 total, 2553.5 free, 909.3 used, 633.2 buff/cache MiB Swap: 1024.0 total, 1024.0 free, 0.0 used. 3186.6 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System 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--102--disk--1 ext4 7.8G 5.2G 2.3G 70% / none tmpfs 492K 4.0K 488K 1% /dev efivarfs efivarfs 256K 40K 212K 16% /sys/firmware/efi/efivars tmpfs tmpfs 32G 0 32G 0% /dev/shm tmpfs tmpfs 13G 108K 13G 1% /run 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--102--disk--1 ext4 rw,relatime,stripe=32 Files in neuralgic directories: /var: 1006M /var/ 505M /var/cache 498M /var/cache/apt 392M /var/cache/apt/archives 309M /var/lib Archived and active journals take up 189.6M in the file system. /opt/iobroker/backups: 5.4M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.1G /opt/iobroker/iobroker-data/ 871M /opt/iobroker/iobroker-data/files 617M /opt/iobroker/iobroker-data/files/javascript.admin 560M /opt/iobroker/iobroker-data/files/javascript.admin/static 558M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 23M /opt/iobroker/iobroker-data/objects.jsonl 9.3M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map 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' *** NodeJS-Installation *** nodejs: N/A /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 *** nodejs is NOT correctly installed *** nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x jammy/main amd64 Packages 100 /var/lib/dpkg/status 12.22.9~dfsg-1ubuntu3.6 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 12.22.9~dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 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: iobroker iobroker (version: 7.0.6, hostname: iobroker , alive, uptime: 1486) Core adapters versions js-controller: 7.0.6 admin: 7.4.10 javascript: 8.8.3 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.discovery.0 : discovery : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.modbus.0 : modbus : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.1.233 + system.adapter.opendtu.0 : opendtu : iobroker - enabled + system.adapter.opendtu.1 : opendtu : iobroker - enabled + system.adapter.opendtu.2 : opendtu : iobroker - enabled system.adapter.shelly.0 : shelly : iobroker - disabled, port: 1882, bind: 0.0.0.0 system.adapter.sonos.0 : sonos : iobroker - disabled system.adapter.web.0 : web : iobroker - disabled, 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, run as: admin + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 192.168.1.233 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-Instances Used repository: stable Adapter "admin" : 7.4.10 , installed 7.4.10 Adapter "backitup" : 3.0.31 , installed 3.0.31 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "modbus" : 6.3.2 , installed 6.3.2 Adapter "mqtt" : 6.1.2 , installed 6.1.2 Adapter "node-red" : 5.2.1 , installed 5.2.1 Adapter "opendtu" : 3.1.0 , installed 2.1.0 [Updatable] Adapter "shelly" : 8.5.1 , installed 8.5.1 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "web" : 6.2.5 , installed 6.2.5 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 810 States: 1012 *** OS-Repositories and Updates *** Hit:1 https://deb.nodesource.com/node_18.x jammy InRelease Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-security InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** sudo: netstat: command not found *** Log File - Last 25 Lines *** 2025-02-04 21:12:41.452 - info: opendtu.0 (601) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.opendtu, node: v18.17.1, js-controller: 7.0.6 2025-02-04 21:12:41.475 - info: opendtu.0 (601) Polling every 30 seconds... 2025-02-04 21:12:41.639 - info: opendtu.0 (601) Connect to OpenDTU over websocket connection. 2025-02-04 21:12:57.405 - info: host.iobroker stopInstance system.adapter.opendtu.1 (force=false, process=true) 2025-02-04 21:12:57.406 - info: opendtu.1 (501) Got terminate signal TERMINATE_YOURSELF 2025-02-04 21:12:57.407 - info: opendtu.1 (501) terminating 2025-02-04 21:12:57.408 - info: opendtu.1 (501) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-02-04 21:12:57.447 - info: host.iobroker stopInstance system.adapter.opendtu.1 send kill signal 2025-02-04 21:12:57.908 - info: opendtu.1 (501) terminating 2025-02-04 21:12:57.923 - info: host.iobroker instance system.adapter.opendtu.1 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-02-04 21:13:01.079 - info: host.iobroker instance system.adapter.opendtu.1 in version "2.1.0" started with pid 616 2025-02-04 21:13:01.600 - info: opendtu.1 (616) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.opendtu, node: v18.17.1, js-controller: 7.0.6 2025-02-04 21:13:01.620 - info: opendtu.1 (616) Polling every 30 seconds... 2025-02-04 21:13:01.699 - info: opendtu.1 (616) Connect to OpenDTU over websocket connection. 2025-02-04 21:13:23.091 - info: host.iobroker stopInstance system.adapter.opendtu.2 (force=false, process=true) 2025-02-04 21:13:23.092 - info: opendtu.2 (516) Got terminate signal TERMINATE_YOURSELF 2025-02-04 21:13:23.093 - info: opendtu.2 (516) terminating 2025-02-04 21:13:23.093 - info: opendtu.2 (516) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-02-04 21:13:23.133 - info: host.iobroker stopInstance system.adapter.opendtu.2 send kill signal 2025-02-04 21:13:23.593 - info: opendtu.2 (516) terminating 2025-02-04 21:13:23.607 - info: host.iobroker instance system.adapter.opendtu.2 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-02-04 21:13:26.711 - info: host.iobroker instance system.adapter.opendtu.2 in version "2.1.0" started with pid 631 2025-02-04 21:13:27.199 - info: opendtu.2 (631) starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.opendtu, node: v18.17.1, js-controller: 7.0.6 2025-02-04 21:13:27.219 - info: opendtu.2 (631) Polling every 30 seconds... 2025-02-04 21:13:27.377 - info: opendtu.2 (631) Connect to OpenDTU over websocket connection. -
Wie gesagt: Node ist zu alt.
iob nodejs-update 20Man hampelt im System aber nicht als
rootrum!Zum Rest kann ich nix sagen - ist Schnubuntu.
726
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge