Controller Update Probleme wegen veralteten OS
-
@haselchen said in Controller Update Probleme wegen veralteten OS:
Definitiv eigenen Thread.
JS Controller Alt
Node Version nicht aktuell
Und wieso hast Du diesmal 2 Admin Instanzen aktiv laufen ?
Dazu 2 Web Instanzen , verschlüsselt und unverschlüsselt .Eine Web Instanz verwende ich im lokalen Netz. Die Verschlüsselte ist über den Router freigegeben. Der 2. Admin ist nur deshalb da, weil ich mich einmal ausgesperrt hatte. Wir aber nicht mehr benötigt.
-
Du musst über den Router nichts freigeben .
Auch wenn der PI5 neu ist , ist das , was Du installierst hast, ein absolutes Durcheinander.Desktop ausschalten
Node updaten auf Version 20
JS Controller updaten
Admin.1 ausschalten -
Desktop ausschalten, das komische giteduberger-Repo rauswerfen (oder richtig aufsetzen), nodejs auf v20 bringen, iob-Adapter auf Stand bringen.
-
Ich möchte wieder ein kurzes Update geben. Ich habe nodejs geupdated. Es lief ohne Probleme. Admin.1 habe ich deaktiviert und das giteduberger-Repo deaktiviert. Das js-controller update funktioniert trotzdem nicht.
Als nächstes habe ich iobroker mit js-controller 7.0.6 neu installiert, die Adapter manuell installiert und die Einstellungen pro Adapter einzeln aus Backups wiederhergestellt. iobroker hat sich auch da nach einer Weile aufgehängt. Ich konnte es jetzt etwas eingrenzen. Ich verwende die Adapter VIS + VIS-lcars. Wenn ich anschließend im VIS Editor die alten VIS-Oberfläche importiere (SETUP->Importieren), fängt iobroker nach einem Neustart des Raspberry an zu hängen. Habt ihr Ideen woran das liegen kann? -
@hag74 sagte in Controller Update Probleme wegen veralteten OS:
Das js-controller update funktioniert trotzdem nicht.
mit welchen Meldungen?
@hag74 sagte in Controller Update Probleme wegen veralteten OS:
Habt ihr Ideen woran das liegen kann?
ohne irgendwelche handfeste Fakten natürlich nicht.
Iob diag in der Langfassung solltest du inzwischen kennen
-
@homoran
Ich komme meist noch auf die Admin-Webseite zum Einloggen, danach hängt iobroker. Iobroker lastet einen Kern zu 100% aus. Im Log steht anschließend folgendes:2025-04-06 18:57:51.900 - warn: admin.0 (813) Cannot check node.js versions: Error: getaddrinfo EAI_AGAIN nodejs.org 2025-04-06 18:57:52.179 - info: admin.0 (813) received all objects 2025-04-06 18:57:52.233 - warn: admin.0 (813) Cannot update news: getaddrinfo EAI_AGAIN iobroker.live 2025-04-06 18:57:52.363 - info: admin.0 (813) Secure socket.io server listening on port 8081 2025-04-06 18:57:52.364 - info: admin.0 (813) https server listening on port 8081 2025-04-06 18:57:52.364 - info: admin.0 (813) Use link "https://127.0.0.1:8081" to configure. 2025-04-06 18:57:52.371 - warn: admin.0 (813) Cannot update rating: getaddrinfo EAI_AGAIN rating.iobroker.net 2025-04-06 18:57:54.595 - info: host.server instance system.adapter.backitup.0 in version "3.0.31" started with pid 829 2025-04-06 18:57:55.501 - info: backitup.0 (829) starting. Version 3.0.31 in /opt/iobroker/node_modules/iobroker.backitup, node: v20.19.0, js-controller: 7.0.6 2025-04-06 18:57:55.527 - info: backitup.0 (829) [iobroker] backup will be activated at 02:48 every 1 day(s) 2025-04-06 18:57:58.597 - info: host.server instance system.adapter.discovery.0 in version "5.0.0" started with pid 974 2025-04-06 18:57:59.283 - info: discovery.0 (974) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v20.19.0, js-controller: 7.0.6 2025-04-06 18:58:02.615 - info: host.server instance system.adapter.web.0 in version "7.0.8" started with pid 996 2025-04-06 18:58:03.503 - info: web.0 (996) starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v20.19.0, js-controller: 7.0.6 2025-04-06 18:58:03.541 - info: web.0 (996) http server listening on port 8077 2025-04-06 18:58:03.608 - info: web.0 (996) socket.io server listening on port 8077 2025-04-06 18:58:07.566 - info: vis.0 (1290) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.19.0, js-controller: 7.0.6 2025-04-06 18:58:08.238 - info: vis.0 (1290) Terminated (NO_ERROR): Without reason 2025-04-06 18:58:08.753 - info: host.server instance system.adapter.vis.0 terminated while should be started once 2025-04-06 18:58:54.901 - info: admin.0 (813) ==> Connected system.user.admin from 2a02:810a:1700:2c00:7139:7db2:e47f:4123 2025-04-06 18:59:35.283 - info: admin.0 (813) <== Disconnect system.user.admin from 2a02:810a:1700:2c00:7139:7db2:e47f:4123 admin 2025-04-06 18:59:38.810 - info: admin.0 (813) terminating https server on port 8081 2025-04-06 18:59:38.813 - info: backitup.0 (829) cleaned everything up... 2025-04-06 18:59:38.813 - warn: web.0 (996) setTimeout called, but adapter is shutting down 2025-04-06 18:59:40.313 - info: admin.0 (813) terminating with timeout 2025-04-06 18:59:40.314 - info: admin.0 (813) Terminated (NO_ERROR): Without reason 2025-04-06 18:59:40.315 - info: web.0 (996) terminating with timeout 2025-04-06 18:59:40.316 - info: web.0 (996) Terminated (NO_ERROR): Without reason 2025-04-06 18:59:40.317 - info: discovery.0 (974) terminating with timeout 2025-04-06 18:59:40.318 - info: discovery.0 (974) Terminated (NO_ERROR): Without reason 2025-04-06 18:59:40.318 - info: backitup.0 (829) terminating with timeout 2025-04-06 18:59:40.319 - info: backitup.0 (829) Terminated (NO_ERROR): Without reasonDeinstallieren des VIS Adapters über die Kommandozeile führt dazu, dass iobroker wieder funktioniert.
iob diag liefert:```bash Script v.2025-02-23 *** BASE SYSTEM *** Static hostname: server Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.12.20+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 19:08:46 up 5 min, 1 user, load average: 0.39, 0.52, 0.27 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** TIME AND TIMEZONES *** Local time: Sun 2025-04-06 19:08:46 CEST Universal time: Sun 2025-04-06 17:08:46 UTC RTC time: Sun 2025-04-06 17:08:46 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': hagen XDG_CONFIG_HOME=/home/hagen/.config HOME=/home/hagen GROUPS=hagen adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin sambashare gpio i2c spi iobroker User that is running 'js-controller': js-controller is not running *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: LXDE-pi Terminal: x11 *** MEMORY *** total used free shared buff/cache available Mem: 16G 815M 14G 126M 2.2G 16G Swap: 40G 0B 40G Total: 57G 815M 54G Active iob-Instances: 1 16195 M total memory 778 M used memory 803 M active memory 1486 M inactive memory 13603 M free memory 438 M buffer memory 1657 M swap cache 38470 M total swap 0 M used swap 38470 M free swap *** top - Table Of Processes *** top - 19:08:46 up 5 min, 1 user, load average: 0.39, 0.52, 0.27 Tasks: 210 total, 1 running, 209 sleeping, 0 stopped, 0 zombie %Cpu(s): 33.3 us, 33.3 sy, 0.0 ni, 33.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 16195.7 total, 13603.2 free, 778.9 used, 2095.5 buff/cache MiB Swap: 38471.0 total, 38471.0 free, 0.0 used. 15416.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * iobroker.service loaded failed failed ioBroker Server LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 7.9G 0 7.9G 0% /dev tmpfs tmpfs 1.6G 8.0M 1.6G 1% /run /dev/sda2 ext4 193G 33G 150G 18% / tmpfs tmpfs 8.0G 4.5M 8.0G 1% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock /dev/sdb1 ext4 11T 3.7T 6.6T 36% /mnt/sdb1 /dev/sda1 vfat 510M 68M 443M 14% /boot/firmware tmpfs tmpfs 1.6G 192K 1.6G 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sun Apr 6 19:03:27 2025] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe cgroup_disable=memory numa_policy=interleave smsc95xx.macaddr=2C:CF:67:E3:F3:30 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=d552a77f-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE [Sun Apr 6 19:03:30 2025] EXT4-fs (sda2): mounted filesystem d4ba6ec5-aeed-4cda-967b-d004c1b2cb5c ro with ordered data mode. Quota mode: none. [Sun Apr 6 19:03:31 2025] EXT4-fs (sda2): re-mounted d4ba6ec5-aeed-4cda-967b-d004c1b2cb5c r/w. Quota mode: none. [Sun Apr 6 19:03:32 2025] EXT4-fs (sdb1): mounted filesystem 3130c808-198e-4865-aab4-5b6235fa1938 r/w with ordered data mode. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime |-/mnt/sdb1 /dev/sdb1 ext4 rw,nosuid,relatime |-/boot/firmware /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro |-/media/hagen/NAS /dev/sdb1[/NAS-Dateien] ext4 rw,nosuid,relatime `-/home/hagen/thinclient_drives xrdp-chansrv fuse.xrdp-chansrv rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 Files in neuralgic directories: /var: 2.3G /var/ 1.4G /var/cache/apt 1.4G /var/cache 1.3G /var/cache/apt/archives 252M /var/lib Archived and active journals take up 145.0M in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 88M /opt/iobroker/iobroker-data/ 82M /opt/iobroker/iobroker-data/files 38M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets 38M /opt/iobroker/iobroker-data/files/admin.admin/custom 38M /opt/iobroker/iobroker-data/files/admin.admin The five largest files in iobroker-data are: 6.8M /opt/iobroker/iobroker-data/files/backitup.admin/custom/static/js/vendors-node_modules_file-saver_dist_FileSaver_min_js-node_modules_react-icons_di_index_mjs-n-0fd47d.a444afaa.chunk.js 5.3M /opt/iobroker/iobroker-data/objects.jsonl 3.9M /opt/iobroker/iobroker-data/files/vis.0/main/vis-views.json 3.9M /opt/iobroker/iobroker-data/files/backitup.admin/custom/static/js/vendors-node_modules_mui_icons-material_esm_index_js.92169c09.chunk.js 3.7M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets/index-ZPb95xPG.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-0658_0200-if00 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.0 /usr/bin/node v20.19.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.31.0 nodejs: Installed: 20.19.0-1nodesource1 Candidate: 20.19.0-1nodesource1 Version table: *** 20.19.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.18.3-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.2-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.17.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.16.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is not running on this host. Objects type: jsonl States type: jsonl Hosts: server server (version: 7.0.6, hostname: server , dead, uptime: 47) Core adapters versions js-controller: 7.0.6 admin: 7.6.3 javascript: "javascript" not found nodejs modules from github: 0 Adapter State system.adapter.admin.0 : admin : server - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.backitup.0 : backitup : server - enabled system.adapter.discovery.0 : discovery : server - enabled system.adapter.vis-lcars.0 : vis-lcars : server - enabled system.adapter.vis-weather.0 : vis-weather : server - enabled system.adapter.vis.0 : vis : server - enabled system.adapter.web.0 : web : server - enabled, port: 8077, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : server - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.web.0 : web : server - enabled, port: 8077, bind: 0.0.0.0, run as: admin 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 "backitup" : 3.0.31 , installed 3.0.31 Adapter "discovery" : 5.0.0 , installed 5.0.0 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "socketio" : 6.7.1 , installed 7.0.8 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-lcars" : 1.1.1 , installed 1.1.1 Adapter "vis-weather" : 2.5.11 , installed 2.5.11 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 3.0.19 Objects and States Please stand by - This may take a while Objects: 422 States: 299 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://archive.raspberrypi.com/debian bookworm InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 http://deb.debian.org/debian bookworm-updates InRelease Hit:5 https://deb.nodesource.com/node_20.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 0.0.0.0:80 0.0.0.0:* LISTEN 999 5876 920/pihole-FTL tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 999 5870 920/pihole-FTL tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 7069 774/sshd: /usr/sbin tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 5948 940/smbd tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 5947 940/smbd tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 999 5877 920/pihole-FTL tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 5740 738/cupsd tcp6 0 0 ::1:3350 :::* LISTEN 0 7516 759/xrdp-sesman tcp6 0 0 :::80 :::* LISTEN 999 5878 920/pihole-FTL tcp6 0 0 :::53 :::* LISTEN 999 5872 920/pihole-FTL tcp6 0 0 :::22 :::* LISTEN 0 7071 774/sshd: /usr/sbin tcp6 0 0 :::139 :::* LISTEN 0 5946 940/smbd tcp6 0 0 :::445 :::* LISTEN 0 5945 940/smbd tcp6 0 0 :::443 :::* LISTEN 999 5879 920/pihole-FTL tcp6 0 0 :::3389 :::* LISTEN 113 7562 775/xrdp tcp6 0 0 ::1:631 :::* LISTEN 0 5739 738/cupsd udp 0 0 0.0.0.0:43965 0.0.0.0:* 104 6901 584/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 6899 584/avahi-daemon: r udp 0 0 0.0.0.0:53 0.0.0.0:* 999 5869 920/pihole-FTL udp 0 0 0.0.0.0:123 0.0.0.0:* 999 8316 920/pihole-FTL udp 0 0 192.168.178.255:137 0.0.0.0:* 0 9370 925/nmbd udp 0 0 192.168.178.51:137 0.0.0.0:* 0 9369 925/nmbd udp 0 0 192.168.178.255:137 0.0.0.0:* 0 9366 925/nmbd udp 0 0 192.168.178.60:137 0.0.0.0:* 0 9365 925/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 0 9344 925/nmbd udp 0 0 192.168.178.255:138 0.0.0.0:* 0 9372 925/nmbd udp 0 0 192.168.178.51:138 0.0.0.0:* 0 9371 925/nmbd udp 0 0 192.168.178.255:138 0.0.0.0:* 0 9368 925/nmbd udp 0 0 192.168.178.60:138 0.0.0.0:* 0 9367 925/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 0 9345 925/nmbd udp6 0 0 :::5353 :::* 104 6900 584/avahi-daemon: r udp6 0 0 :::47283 :::* 104 6902 584/avahi-daemon: r udp6 0 0 :::53 :::* 999 5871 920/pihole-FTL udp6 0 0 :::123 :::* 999 9470 920/pihole-FTL udp6 0 0 fe80::a3b1:eb99:e93:546 :::* 0 5975 654/NetworkManager udp6 0 0 fe80::19aa:e6ae:2a2:546 :::* 0 5820 654/NetworkManager *** Log File - Last 25 Lines *** 2025-04-06 19:03:39.898 - error: host.server instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-04-06 19:03:39.898 - info: host.server Restart adapter system.adapter.backitup.0 because enabled 2025-04-06 19:03:42.539 - info: host.server instance system.adapter.discovery.0 in version "5.0.0" started with pid 952 2025-04-06 19:03:43.224 - error: discovery.0 (952) discovery.0 already running 2025-04-06 19:03:43.226 - warn: discovery.0 (952) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-04-06 19:03:43.746 - error: host.server instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-04-06 19:03:43.747 - info: host.server Restart adapter system.adapter.discovery.0 because enabled 2025-04-06 19:03:46.529 - info: host.server instance system.adapter.web.0 in version "7.0.8" started with pid 1066 2025-04-06 19:03:47.735 - error: web.0 (1066) web.0 already running 2025-04-06 19:03:47.737 - warn: web.0 (1066) Terminated (ADAPTER_ALREADY_RUNNING): Without reason 2025-04-06 19:03:48.293 - error: host.server instance system.adapter.web.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2025-04-06 19:03:48.294 - info: host.server Restart adapter system.adapter.web.0 because enabled 2025-04-06 19:03:51.197 - info: vis.0 (1434) starting. Version 1.5.6 in /opt/iobroker/node_modules/iobroker.vis, node: v20.19.0, js-controller: 7.0.6 2025-04-06 19:03:51.822 - info: vis.0 (1434) Terminated (NO_ERROR): Without reason 2025-04-06 19:03:52.336 - info: host.server instance system.adapter.vis.0 terminated while should be started once 2025-04-06 19:04:06.904 - info: host.server instance system.adapter.admin.0 in version "7.6.3" started with pid 1980 2025-04-06 19:04:07.873 - info: admin.0 (1980) starting. Version 7.6.3 in /opt/iobroker/node_modules/iobroker.admin, node: v20.19.0, js-controller: 7.0.6 2025-04-06 19:04:07.895 - info: admin.0 (1980) requesting all objects 2025-04-06 19:04:08.238 - info: admin.0 (1980) received all objects 2025-04-06 19:04:08.412 - info: admin.0 (1980) Secure socket.io server listening on port 8081 2025-04-06 19:04:08.413 - info: admin.0 (1980) https server listening on port 8081 2025-04-06 19:04:08.413 - info: admin.0 (1980) Use link "https://127.0.0.1:8081" to configure. 2025-04-06 19:04:43.656 - info: admin.0 (1980) terminating https server on port 8081 2025-04-06 19:04:45.159 - info: admin.0 (1980) terminating with timeout 2025-04-06 19:04:45.160 - info: admin.0 (1980) Terminated (NO_ERROR): Without reason -
-
@hag74 said in Controller Update Probleme wegen veralteten OS:
getaddrinfo EAI_AGAIN nodejs.org
getaddrinfo EAI_AGAIN iobroker.live
getaddrinfo EAI_AGAIN rating.iobroker.netDa gibst Probleme mit der DNS Namensauflösung
-
@hag74 sagte in Controller Update Probleme wegen veralteten OS:
EAI_AGAIN
du hast Probleme mit dem Nezwerk!
wahrscheinlich mit dem DNSbist du sicher dass dein pihole keine Probleme macht?
-
@homoran sagte in Controller Update Probleme wegen veralteten OS:
wahrscheinlich mit dem DNS
Vermutlich den pihole falsch konfiguriert.
-
@thomas-braun
Pihole habe ich jetzt deaktiviert. Das löst das Problem nicht. Wie gesagt:
ohne VIS geht es, mit VIS und alten Projekt geht es nicht.
Es muss als am VIS in der Verbindung mit meinem Projekt liegen.
