Troubleshooting NodeJS update
-
@thomas-braun OK, dachte das wäre bekannt. Ich schaue mal weiter
-
@jens-lattwesen sagte in Troubleshooting NodeJS update:
?
dito!
Wann und wo taucht das auf?
wie
@thomas-braun sagte in Troubleshooting NodeJS update:Sieht aber nach kaputten Fenstern aus
scheint da dein Rechner an dem du da werkelst ein Problem zu haben.
-
@homoran
ja, etwas betagteres Modell mit Windows7.Scheinbar ist die Grafikkarte das Problem.
-
@jens-lattwesen sagte in Troubleshooting NodeJS update:
Windows7
nicht dein Ernst!
Da wird die Ursache schon sein, was im Fenster steht.
Aber den Rechner würd ich definitiv nicht mehr ins Internet lassen -
@jens-lattwesen sagte in Troubleshooting NodeJS update:
OK, dachte das wäre bekannt.
Nein, das dein Windows nicht alle benötigten Grafik-Treiber an Bord hat ist nicht bekannt. Mir jedenfalls nicht.
-
@markusk1407 bei mir funktioniert das alles nicht. Mein User ist nur in der iobroker und der adm Gruppe, trotzdem bekomme ich : Sorry, user Ingo is not allowed to execute '/usr/bin/curl -sLf https...
Kann ich das irgendwie lösen? --> hab einen neun User erstellt, den in die iobroker Gruppe aufgenommen, jetzt startet das Node updateDanke und Gruß Ingo
-
@elcriminale sagte in Troubleshooting NodeJS update:
Kann ich das irgendwie lösen? --> hab einen neun User erstellt, den in die iobroker Gruppe aufgenommen, jetzt startet das Node update
Dann schau dir die Rechte der user an.
Hast du es periob nodejs-update
gemacht?
-
@thomas-braun
ja, mit und ohne 20 dahinter, mit dem neuen User hats auf Anhieb funktioniert -
-
-
Bitte KEINE windschiefen Bildchen von Konsolentexten.
-
Admin@ioBroker:~$ id Ingo uid=1001(Ingo) gid=1000(iobroker) groups=1000(iobroker) Admin@ioBroker:~$ id Admin uid=1002(Admin) gid=1000(iobroker) groups=1000(iobroker)Admin@ioBroker:~$ iob fix Your system is booting into 'graphical.target', which means that a user interface or desktop is available. Usually a server is running without a desktop to have more RAM available. Do you want to switch to 'multi-user.target'? (y/N) library: loaded Library version=2024-10-22 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 205-02-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ==========================================================================Admin@ioBroker:~$ iob diag [sudo] password for Admin: Sorry, user Admin is not allowed to execute '/usr/bin/curl -sLf https://iobroker.net/diag.sh --output /home/iobroker/.diag.sh' as iobroker on ioBroker.local. Admin@ioBroker:~$Admin@ioBroker:~$ iob nodejs-update iobroker nodejs-update [<major-version>] Upgrade the Node.JS installation to the current LTS Options: --help Show help [boolean] Admin@ioBroker:~$ich wollte dem Problem auf die Schliche kommen und habe den ganzen ioB Container aus einem Backup wiederhergestellt, bevor ich den User Admin und Ingo angelegt hatte.
Dann den User Ingo angelegt und in die iobroker Gruppe aufgenommen -- Update Nodejs versucht, klappt nicht, dann den User Admin angelegt in die iobroker Gruppe aufgenommen -- Update Nodejs versucht, klappt nicht. -
@elcriminale
Mal eine Frage:
Was verstehst du anBitte KEINE windschiefen Bildchen von Konsolentexten.
nicht?
Bitte KEINE Screenshots / Bildchen. posten sondern den Text markieren und unter Code Tage posten.
EDIT: Vorposting zwischenzeitlich korrigiert
-
Beiden usern fehlen die root-Rechte. Setz deinen Hauptuser in die Gruppen
sudoundadmrein.
Dann die Kiste einmal komplett durchstarten.Erst dann kann auch an den Systemeinstellungen hantiert werden.
Am Rande: user und hostnames am besten in durchgehender Kleinschreibung. Gute Praxis.
Und eigentlich ist der user 'Admin' ohnehin entbehrlich, wenn der 'Ingo' dann schon mit den passenden Rechten ausgestattet ist. Lösch den wieder, ist nur ein unnötiger Angriffsvektor.
-
@thomas-braun
@mcm1957
Danke Thomas!
Danke mcm1957!Habe einen "kleinen" Ingo angelegt, in die entsprechenden Gruppen aufgenommen und das Update hat funktioniert. Die anderen beiden User hab ich anschließend gelöscht.
Gruß Ingo
-
-
======================= SUMMARY ======================= v.2025-02-23 Static hostname: ioBroker Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Ubuntu 22.04.5 LTS Kernel: Linux 6.8.12-9-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1001 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 1 Nodejs-Installation: /usr/bin/nodejs v20.19.2 /usr/bin/node v20.19.2 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.31.0 Recommended versions are nodejs 20.19.2 and npm 10.8.2 nodeJS installation is correct MEMORY: total used free shared buff/cache available Mem: 4.1G 1.9G 1.6G 0.0K 621M 2.2G Swap: 512M 9.0M 502M Total: 4.6G 1.9G 2.1G Active iob-Instances: 21 Upgrade policy: none ioBroker Core: js-controller 7.0.6 admin 7.6.3 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : ioBroker - enabled, port: 8081, 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 Objects: 15728 States: 12901 Size of iob-Database: 21M /opt/iobroker/iobroker-data/objects.jsonl 4.9M /opt/iobroker/iobroker-data/objects.json.migrated 4.9M /opt/iobroker/iobroker-data/objects.json.bak.migrated 34M /opt/iobroker/iobroker-data/states.jsonl 980K /opt/iobroker/iobroker-data/states.json.migrated 980K /opt/iobroker/iobroker-data/states.json.bak.migrated Operating System codenamed 'jammy' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time! =================== END OF SUMMARY ==================== -
Das ist nicht die Langfassung sondern die Zusammenfassung.
-
Script v.2025-02-23 *** 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-9-pve Architecture: x86-64 OS is similar to: debian model name : Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 10:56:43 up 1 day, 23:52, 2 users, load average: 0.16, 0.13, 0.15 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: Mon 2025-05-19 10:56:44 CEST Universal time: Mon 2025-05-19 08:56:44 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': ingo HOME=/home/ingo GROUPS=ingo adm sudo iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev *** 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 1.9G 1.5G 0.0K 630M 2.2G Swap: 512M 9.0M 502M Total: 4.6G 1.9G 2.0G Active iob-Instances: 21 4096 M total memory 1934 M used memory 1600 M active memory 843 M inactive memory 1530 M free memory 0 M buffer memory 630 M swap cache 512 M total swap 9 M used swap 502 M free swap *** top - Table Of Processes *** top - 10:56:44 up 1 day, 23:52, 2 users, load average: 0.16, 0.13, 0.15 Tasks: 48 total, 1 running, 47 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, 1529.9 free, 1935.3 used, 630.8 buff/cache MiB Swap: 512.0 total, 502.9 free, 9.1 used. 2160.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * systemd-networkd-wait-online.service loaded failed failed Wait for Network to be Configured 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. 2 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--104--disk--0 ext4 16G 12G 3.8G 75% / none tmpfs 492K 4.0K 488K 1% /dev efivarfs efivarfs 192K 75K 113K 41% /sys/firmware/efi/efivars tmpfs tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs tmpfs 3.1G 112K 3.1G 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--104--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 2.5G /var/ 1.5G /var/log/journal/a0fdcde6ae484c568cf39989f5d3f88a 1.5G /var/log/journal 1.5G /var/log 690M /var/cache Archived and active journals take up 1.4G in the file system. /opt/iobroker/backups: 75M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.1G /opt/iobroker/iobroker-data/ 831M /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: 36M /opt/iobroker/iobroker-data/states.jsonl 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 24M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.c9369f6c.js.map 21M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.02fc3820.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': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_7c7fded56ad9eb118ed1148e6fe9f4d9-if00-port0 *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/ttyUSB0 Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v20.19.2 /usr/bin/node v20.19.2 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.31.0 nodejs: Installed: 20.19.2-1nodesource1 Candidate: 20.19.2-1nodesource1 Version table: *** 20.19.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main 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: 172332) Core adapters versions js-controller: 7.0.6 admin: 7.6.3 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.alexa2.0 : alexa2 : ioBroker - enabled + system.adapter.backitup.0 : backitup : ioBroker - enabled + system.adapter.device-reminder.0 : device-reminder : ioBroker - enabled system.adapter.devices.0 : devices : ioBroker - enabled system.adapter.discovery.0 : discovery : ioBroker - disabled system.adapter.dwd.0 : dwd : ioBroker - enabled + system.adapter.fb-checkpresence.0 : fb-checkpresence : ioBroker - enabled system.adapter.feiertage.0 : feiertage : ioBroker - enabled + system.adapter.heatingcontrol.0 : heatingcontrol : ioBroker - enabled + system.adapter.hm-rega.0 : hm-rega : ioBroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : ioBroker - enabled, port: 0 + system.adapter.hue.0 : hue : ioBroker - enabled, port: 443 system.adapter.ical.0 : ical : ioBroker - enabled + system.adapter.info.0 : info : ioBroker - enabled + system.adapter.iot.0 : iot : ioBroker - enabled + system.adapter.javascript.0 : javascript : ioBroker - enabled + system.adapter.ping.0 : ping : ioBroker - enabled + system.adapter.sayit.0 : sayit : ioBroker - enabled + system.adapter.scenes.0 : scenes : ioBroker - enabled system.adapter.simple-api.0 : simple-api : ioBroker - disabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonos.0 : sonos : ioBroker - enabled system.adapter.spotify-premium.0 : spotify-premium : ioBroker - disabled + system.adapter.telegram.0 : telegram : ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.0 : text2command : ioBroker - enabled + system.adapter.web.0 : web : ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.yr.0 : yr : ioBroker - enabled + system.adapter.zigbee.0 : zigbee : ioBroker - enabled, port: /dev/ttyUSB0 + 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.hm-rpc.0 : hm-rpc : ioBroker - enabled, port: 0 + system.adapter.hue.0 : hue : ioBroker - enabled, port: 443 + system.adapter.telegram.0 : telegram : ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : ioBroker - enabled, port: /dev/ttyUSB0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.6.3 , installed 7.6.3 Adapter "alexa2" : 3.26.5 , installed 3.26.5 Adapter "backitup" : 3.0.31 , installed 3.0.31 Adapter "device-reminder": 3.1.2 , installed 3.1.2 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "fb-checkpresence": 1.3.1 , installed 1.3.1 Adapter "feiertage" : 1.2.1 , installed 1.2.1 Adapter "heatingcontrol": 2.12.14 , installed 2.12.14 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "hue" : 3.16.1 , installed 3.16.1 Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "iot" : 3.3.0 , installed 3.3.0 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "sayit" : 5.0.0 , installed 5.0.0 Adapter "scenes" : 3.2.3 , installed 3.2.3 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 "spotify-premium": 1.5.2 , installed 1.5.2 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "text2command" : 3.0.3 , installed 3.0.3 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yr" : 5.3.0 , installed 5.3.0 Adapter "zigbee" : 2.0.5 , installed 1.10.14 [Updatable] Objects and States Please stand by - This may take a while Objects: 15728 States: 12901 *** OS-Repositories and Updates *** Hit:1 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu focal-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu focal-backports InRelease Hit:6 https://deb.nodesource.com/node_20.x nodistro InRelease Hit:7 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:8 http://archive.ubuntu.com/ubuntu jammy-updates 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.53:53 0.0.0.0:* LISTEN 106 64800121 101/systemd-resolve tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 64798673 1/init tcp 0 0 192.168.180.4:42010 0.0.0.0:* LISTEN 1000 64803919 354/io.hm-rpc.0 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 64799640 116/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 64800143 116/iobroker.js-con tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 64807797 1086/master tcp6 0 0 ::1:25 :::* LISTEN 0 64807798 1086/master tcp6 0 0 :::8081 :::* LISTEN 1000 64800178 147/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1000 64805655 849/io.web.0 tcp6 0 0 :::111 :::* LISTEN 0 64798675 1/init tcp6 0 0 :::22 :::* LISTEN 0 64799573 1/init tcp6 0 0 :::3500 :::* LISTEN 1000 64805918 417/io.sonos.0 udp 0 0 127.0.0.53:53 0.0.0.0:* 106 64800120 101/systemd-resolve udp 0 0 0.0.0.0:111 0.0.0.0:* 0 64798674 1/init udp6 0 0 :::111 :::* 0 64798676 1/init *** Log File - Last 25 Lines *** 2025-05-19 10:57:02.594 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.c0543fb5c1054be9a4a11aff57a4d1bb.Player.mediaProgress: {"val":60,"ack":true,"ts":1747645022594,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645022594} 2025-05-19 10:57:02.595 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.c0543fb5c1054be9a4a11aff57a4d1bb.Player.mediaProgressStr: {"val":"01:00","ack":true,"ts":1747645022594,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645022594} 2025-05-19 10:57:02.595 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.c0543fb5c1054be9a4a11aff57a4d1bb.Player.mediaRemaining: {"val":0,"ack":true,"ts":1747645022594,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747504223046} 2025-05-19 10:57:02.595 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.c0543fb5c1054be9a4a11aff57a4d1bb.Player.mediaLengthStr: {"val":"0","ack":true,"ts":1747645022594,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747504223007} 2025-05-19 10:57:02.790 - debug: ping.0 (399) Ping result for 192.168.180.101: false in -ms (Tried 0/3 times) 2025-05-19 10:57:02.790 - debug: ping.0 (399) System command: /bin/ping -n -w 2 -c 1 192.168.180.101 2025-05-19 10:57:03.198 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.6221b935a00f474bbcfe5b9f482882bc.Player.mediaProgressPercent: {"val":89,"ack":true,"ts":1747645023197,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645023197} 2025-05-19 10:57:03.239 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.6221b935a00f474bbcfe5b9f482882bc.Player.mediaProgress: {"val":91,"ack":true,"ts":1747645023238,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645023238} 2025-05-19 10:57:03.239 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.6221b935a00f474bbcfe5b9f482882bc.Player.mediaProgressStr: {"val":"01:31","ack":true,"ts":1747645023238,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645023238} 2025-05-19 10:57:03.239 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.6221b935a00f474bbcfe5b9f482882bc.Player.mediaRemaining: {"val":11,"ack":true,"ts":1747645023238,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645023238} 2025-05-19 10:57:03.240 - debug: alexa2.0 (463) State changed alexa2.0.Echo-Devices.6221b935a00f474bbcfe5b9f482882bc.Player.mediaLengthStr: {"val":"00:11","ack":true,"ts":1747645023238,"q":0,"from":"system.adapter.alexa2.0","user":"system.user.admin","lc":1747645023238} 2025-05-19 10:57:03.285 - debug: device-reminder.0 (911) "1" 2025-05-19 10:57:03.285 - debug: device-reminder.0 (911) ["Waschmaschine"]: Berechnung gestartet 2025-05-19 10:57:03.285 - debug: device-reminder.0 (911) ["Waschmaschine"]: arrStart gelöscht 2025-05-19 10:57:03.285 - debug: device-reminder.0 (911) ["Waschmaschine"]: berechnung "standby" wird ausgefuehrt 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: resultTemp standby: 0 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: Länge array standby: 10, Inhalt: [0,0,0,0,0,0,0,0,0,0] 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: Berechnung beendet 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: Auswertung gestartet 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: WERTE für START: 0W; Schwelle Start: 30W; gestartet: false 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: value status: end 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) Device Ende 2025-05-19 10:57:03.286 - debug: device-reminder.0 (911) ["Waschmaschine"]: Auswertung beendet 2025-05-19 10:57:03.870 - debug: ping.0 (399) Ping result for 192.168.180.101: false in -ms (Tried 1/3 times) 2025-05-19 10:57:03.870 - debug: ping.0 (399) System command: /bin/ping -n -w 2 -c 1 192.168.180.101 -
@elcriminale sagte in Troubleshooting NodeJS update:
Operating System codenamed 'jammy' is an aging Ubuntu release! Please upgrade to the latest LTS release 'noble' in due time!
Bring das in nächster Zeit auf Ubuntu 24.04 LTS 'Noble'
(Oder besser gleich auf ein Debian, im Sommer dürfte Debian 12 'Trixie' veröffentlich werden.).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'
Stell das um.
USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id':
Würde ich auch umstellen.
Update empfohlen:
Adapter "zigbee" : 2.0.5 , installed 1.10.14 [Updatable]
Und nimm das debug-Logging für die ganzen Adapter raus. Übermäßiges loggen kann dazu führen, das die Kiste die Grätsche macht.
