WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar
-
Hallo,
seit gestern abend funktioniert bei mir der WebUI nicht mehr.
Wieder auf PC, noch am Mobilgeräten kann ich die Seiten nicht abrufen.Ich habe bereits verucht alles zu aktualisieren, leider ohne Erfolg.
hier der iob diag Auszug.
Script v.2025-02-23 *** BASE SYSTEM *** Static hostname: Raspi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.62+rpt-rpi-2712 Architecture: arm64 OS is similar to: Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 11:01:42 up 4:22, 2 users, load average: 3.80, 2.86, 1.91 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: Wed 2025-05-14 11:01:42 CEST Universal time: Wed 2025-05-14 09:01:42 UTC RTC time: Wed 2025-05-14 09:01:42 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': pi HOME=/home/pi GROUPS=pi adm dialout cdrom sudo audio www-data video plugdev games users input render netdev gpio i2c spi iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** DISPLAY-SERVER SETUP *** Display-Server: false Desktop: Terminal: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.4G 455M 7.0G 4.8M 1.1G 8.0G Swap: 536M 0B 536M Total: 9.0G 455M 7.5G Active iob-Instances: 1 8052 M total memory 435 M used memory 455 M active memory 639 M inactive memory 6661 M free memory 182 M buffer memory 874 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 11:01:43 up 4:22, 2 users, load average: 3.80, 2.86, 1.91 Tasks: 141 total, 1 running, 140 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 : 8052.2 total, 6661.4 free, 435.5 used, 1056.9 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 7616.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * vsftpd.service loaded failed failed vsftpd FTP 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 *** 26 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for details *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 806M 4.7M 801M 1% /run /dev/mmcblk0p2 ext4 28G 11G 16G 41% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/mmcblk0p1 vfat 510M 55M 456M 11% /boot/firmware tmpfs tmpfs 806M 0 806M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed May 14 06:39:02 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=D8:3A:DD:B4:E1:00 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=4f2c0a0f-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE [Wed May 14 06:39:05 2025] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none. [Wed May 14 06:39:07 2025] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. Quota mode: none. [Wed May 14 06:39:50 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm npm: corrupted in-inode xattr: bad e_name length [Wed May 14 06:39:53 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm npm: corrupted in-inode xattr: bad e_name length [Wed May 14 07:18:49 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 07:18:57 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 07:19:51 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 07:19:59 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 07:20:29 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_set_entry:1668: inode #304166: comm setfacl: corrupted xattr entries [Wed May 14 07:20:29 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm setfacl: corrupted in-inode xattr: bad e_name length [Wed May 14 07:20:29 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm setfacl: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 07:20:29 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm rm: corrupted in-inode xattr: bad e_name length [Wed May 14 07:32:23 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 07:32:32 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 07:33:08 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 07:33:19 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 07:33:54 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_set_entry:1668: inode #304166: comm setfacl: corrupted xattr entries [Wed May 14 07:33:54 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm setfacl: corrupted in-inode xattr: bad e_name length [Wed May 14 07:33:54 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm setfacl: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 07:33:54 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm rm: corrupted in-inode xattr: bad e_name length [Wed May 14 10:59:10 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 10:59:18 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 11:00:12 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 11:00:25 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 11:00:34 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_set_entry:1668: inode #304166: comm setfacl: corrupted xattr entries [Wed May 14 11:00:35 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm setfacl: corrupted in-inode xattr: bad e_name length [Wed May 14 11:00:35 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm setfacl: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled [Wed May 14 11:00:35 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm rm: corrupted in-inode xattr: bad e_name length Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 3.9G /var/ 2.8G /var/log/journal/0d56a9beb4d64b288a038a2796e66e50 2.8G /var/log/journal 2.8G /var/log 421M /var/cache Archived and active journals take up 2.7G in the file system. /opt/iobroker/backups: 325M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.2G /opt/iobroker/iobroker-data/files 1.2G /opt/iobroker/iobroker-data/ 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: 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 24M /opt/iobroker/iobroker-data/files/vis-2/static/js/main.f305bc29.js.map 24M /opt/iobroker/iobroker-data/files/vis-2/static/js/main.8e80ccb0.js.map 24M /opt/iobroker/iobroker-data/files/vis-2/customWidgets.js.map 24M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/main.c9369f6c.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' *** ZigBee Settings *** HINT: Your zigbee.0 COM-Port is NOT matching 'by-id'. Please check your setting: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2c00cdf9a5a4ed11826484582981d5c7-if00-port0 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 v22.15.0 /usr/bin/node v22.15.0 /usr/bin/npm 10.9.2 /usr/bin/npx 10.9.2 /usr/bin/corepack 0.32.0 nodejs: Installed: 22.15.0-1nodesource1 Candidate: 22.15.0-1nodesource1 Version table: *** 22.15.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 22.14.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.13.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.12.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.11.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.10.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.9.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.8.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.7.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.6.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.5.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.1-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.4.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.3.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.2.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.1.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.x nodistro/main arm64 Packages 22.0.0-1nodesource1 600 500 https://deb.nodesource.com/node_22.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: 1 Some problems detected, please run iob fix 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: Raspi Raspi (version: 7.0.6, hostname: Raspi , alive, uptime: 38) slave slave (version: 7.0.6, hostname: slave , alive, uptime: 7) Core adapters versions js-controller: 7.0.6 admin: 7.6.3 javascript: 8.8.3 nodejs modules from github: 4 +-- iobroker.govee@0.0.6 (git+ssh://git@github.com/nbuenger/ioBroker.govee.git#73ec80b6350890015d95428dd3bbd3f72417a073) +-- iobroker.mercedesme@0.3.7 (git+ssh://git@github.com/TA2k/ioBroker.mercedesme.git#2ef51a64577c1b40b6f074305cabead3b350bf2b) | +-- samsungtv@0.0.0 (git+https://git@github.com/luca-saggese/samsungtv.git#7fc20107455414e2afb94022682e0787e8635550) +-- iobroker.smartthings@0.2.2 (git+ssh://git@github.com/TA2k/ioBroker.smartthings.git#b055221990231cf4c8b7fbfd6bee94ff59b0fd75) Adapter State system.adapter.admin.0 : admin : Raspi - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : Raspi - enabled system.adapter.daswetter.0 : daswetter : Raspi - enabled system.adapter.devices.0 : devices : Raspi - enabled system.adapter.discovery.0 : discovery : Raspi - enabled system.adapter.doorbird.0 : doorbird : Raspi - enabled system.adapter.doorio.0 : doorio : slave - enabled, port: 8100 system.adapter.govee-local.0 : govee-local : Raspi - disabled system.adapter.govee.0 : govee : Raspi - disabled system.adapter.ical.0 : ical : Raspi - enabled system.adapter.icons-freepic.0 : icons-freepic : Raspi - enabled system.adapter.icons-smarthome.0 : icons-smarthome : Raspi - enabled system.adapter.iot.0 : iot : Raspi - enabled system.adapter.javascript.0 : javascript : Raspi - enabled system.adapter.knx.0 : knx : Raspi - enabled, bind: 127.0.0.1 system.adapter.mercedesme.0 : mercedesme : Raspi - enabled system.adapter.mielecloudservice.0 : mielecloudservice : Raspi - enabled system.adapter.nanoleaf-lightpanels.0 : nanoleaf-lightpanels : Raspi - enabled, port: 16021 system.adapter.nanoleaf-lightpanels.1 : nanoleaf-lightpanels : Raspi - enabled, port: 16021 system.adapter.openknx.0 : openknx : Raspi - enabled system.adapter.samsung.0 : samsung : Raspi - enabled system.adapter.scenes.0 : scenes : Raspi - enabled system.adapter.shelly.0 : shelly : Raspi - enabled, port: 1882, bind: 0.0.0.0 system.adapter.shelly.1 : shelly : Raspi - enabled, port: 1881, bind: 0.0.0.0 system.adapter.smartthings.0 : smartthings : Raspi - enabled system.adapter.telegram.0 : telegram : Raspi - disabled, port: 8443, bind: 0.0.0.0 system.adapter.tradfri.0 : tradfri : Raspi - enabled system.adapter.trashschedule.0 : trashschedule : Raspi - enabled system.adapter.vis-2-widgets-inventwo.0 : vis-2-widgets-inventwo: Raspi - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: Raspi - enabled system.adapter.vis-2-widgets-weather-and-heating.0: vis-2-widgets-weather-and-heating: Raspi - enabled system.adapter.vis-2.0 : vis-2 : Raspi - enabled system.adapter.vis-icontwo.0 : vis-icontwo : Raspi - enabled system.adapter.vis-inventwo.0 : vis-inventwo : Raspi - enabled system.adapter.vis-material.0 : vis-material : Raspi - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : Raspi - enabled system.adapter.vis-weather.0 : vis-weather : Raspi - enabled system.adapter.vis.0 : vis : Raspi - enabled system.adapter.weatherunderground.0 : weatherunderground : Raspi - enabled system.adapter.web.0 : web : Raspi - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.yahka.0 : yahka : Raspi - enabled system.adapter.zigbee.0 : zigbee : slave - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2c00cdf9a5a4ed11826484582981d5c7-if00-port0 + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : Raspi - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.doorio.0 : doorio : slave - enabled, port: 8100 system.adapter.nanoleaf-lightpanels.0 : nanoleaf-lightpanels : Raspi - enabled, port: 16021 system.adapter.nanoleaf-lightpanels.1 : nanoleaf-lightpanels : Raspi - enabled, port: 16021 system.adapter.shelly.0 : shelly : Raspi - enabled, port: 1882, bind: 0.0.0.0 system.adapter.shelly.1 : shelly : Raspi - enabled, port: 1881, bind: 0.0.0.0 system.adapter.web.0 : web : Raspi - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.zigbee.0 : zigbee : slave - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_2c00cdf9a5a4ed11826484582981d5c7-if00-port0 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 "daswetter" : 3.2.3 , installed 3.2.3 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "doorbird" : 3.0.0 , installed 3.0.0 Adapter "govee-local" : 0.2.8 , installed 0.2.7 [Updatable] Adapter "ical" : 1.16.1 , installed 1.16.1 Adapter "icons-freepic": 1.0.0 , installed 1.0.0 Adapter "icons-smarthome": 1.0.0 , installed 1.0.0 Adapter "iot" : 3.3.0 , installed 3.4.5 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 7.0.6 Adapter "knx" : 2.0.30 , installed 2.0.30 Adapter "mielecloudservice": 6.5.10, installed 6.5.10 Adapter "nanoleaf-lightpanels": 1.4.0, installed 1.4.0 Adapter "openknx" : 0.9.0 , installed 0.9.0 Adapter "samsung" : 0.6.1 , installed 0.6.1 Adapter "samsung_tizen": 1.1.0 , installed 1.1.0 Adapter "scenes" : 3.2.3 , installed 3.2.3 Adapter "shelly" : 9.2.0 , installed 9.2.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tradfri" : 3.1.3 , installed 3.1.3 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "vis" : 1.5.6 , installed 1.5.6 Adapter "vis-2" : 2.9.64 , installed 2.9.64 Adapter "vis-2-widgets-inventwo": 0.1.11, installed 0.1.11 Adapter "vis-2-widgets-material": 1.4.10, installed 1.4.10 Adapter "vis-2-widgets-weather-and-heating": 0.10.4, installed 0.10.4 Adapter "vis-icontwo" : 1.11.0 , installed 1.11.0 Adapter "vis-inventwo" : 3.3.4 , installed 3.3.4 Adapter "vis-material" : 0.2.0 , installed 0.2.0 Adapter "vis-materialdesign": 0.5.9, installed 0.5.9 Adapter "vis-weather" : 2.5.11 , installed 2.5.11 Adapter "weatherunderground": 3.7.0, installed 3.7.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "yahka" : 1.0.3 , installed 1.0.3 Adapter "zigbee" : 2.0.5 , installed 2.0.5 Objects and States Please stand by - This may take a while Objects: 15800 States: 11895 *** 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_22.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:22 0.0.0.0:* LISTEN 0 5610 610/sshd: /usr/sbin tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 257440 95009/iobroker.js-c tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 260134 95009/iobroker.js-c udp 0 0 0.0.0.0:41838 0.0.0.0:* 104 888 490/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 886 490/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-05-14 11:02:16.763 - error: host.Raspi Caught by controller[0]: at TracingChannel.traceSync (node:diagnostics_channel:322:14) 2025-05-14 11:02:16.763 - error: host.Raspi Caught by controller[0]: at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) 2025-05-14 11:02:16.763 - error: host.Raspi Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1487:12) 2025-05-14 11:02:16.763 - error: host.Raspi Caught by controller[0]: at require (node:internal/modules/helpers:135:16) 2025-05-14 11:02:16.763 - error: host.Raspi Caught by controller[0]: Node.js v22.15.0 2025-05-14 11:02:16.763 - error: host.Raspi instance system.adapter.admin.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2025-05-14 11:02:16.763 - info: host.Raspi Restart adapter system.adapter.admin.0 because enabled 2025-05-14 11:02:20.073 - info: host.Raspi instance system.adapter.vis-inventwo.0 in version "3.3.4" started with pid 96096 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: /opt/iobroker/node_modules/@iobroker/adapter-core/build/cjs/utils.js:96 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: throw new Error("Cannot resolve adapter class"); 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: ^ 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: Error: Cannot resolve adapter class 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at resolveAdapterConstructor (/opt/iobroker/node_modules/@iobroker/adapter-core/build/cjs/utils.js:96:9) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/@iobroker/adapter-core/build/cjs/utils.js:101:17) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1730:14) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at Object..js (node:internal/modules/cjs/loader:1895:10) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1465:32) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at Function._load (node:internal/modules/cjs/loader:1282:12) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at TracingChannel.traceSync (node:diagnostics_channel:322:14) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at wrapModuleLoad (node:internal/modules/cjs/loader:235:24) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1487:12) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: at require (node:internal/modules/helpers:135:16) 2025-05-14 11:02:20.252 - error: host.Raspi Caught by controller[0]: Node.js v22.15.0 2025-05-14 11:02:20.252 - error: host.Raspi instance system.adapter.vis-inventwo.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2025-05-14 11:02:20.252 - info: host.Raspi Restart adapter system.adapter.vis-inventwo.0 because enabled
-
@von-cartman sagte in WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar:
im Anhang der iob diag Auszug
bitte keinen Anhang und keinen Auszug!
die gesamte Langfassung hier in code-tags posten
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge/1
EDIT:
So weit ich das auf dem Handy entziffern kann ist dein Dateisystem geschrottet -
@homoran Danke für die Schnelle einschäzung,
aber 2 Fragen:- woran erkenne ich es?
- Wie kann ich so etwas in Zukunft vorbeugen?
EDIT:
bzw. 3:
3) kann ich die Instalation irgendwie noch retten bzw. aufs neues Sysem Übertragen? -
@von-cartman sagte in WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar:
woran erkenne ich es?
wenn du es wie gewünscht und verlinkt, in code-tags postest, kann ich es dir zitieren.
Das ist auch ein Grund für dieses Vorgehen.
Hast du ja auch gelesen. -
@von-cartman sagte in WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar:
woran erkenne ich es?
An sowas:
*** DMESG CRITICAL ERRORS *** 26 CRITICAL ERRORS DETECTED! Check 'sudo dmesg --level=emerg,alert,crit -T' for detailsund sowas:
Messages concerning ext4 filesystem in dmesg: [Wed May 14 06:39:02 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=D8:3A:DD:B4:E1:00 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=4f2c0a0f-02 rootfstype=ext4 fsck.repair=yes rootwait cfg80211.ieee80211_regdom=DE [Wed May 14 06:39:05 2025] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none. [Wed May 14 06:39:07 2025] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. Quota mode: none. [Wed May 14 06:39:50 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm npm: corrupted in-inode xattr: bad e_name length [Wed May 14 06:39:53 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm npm: corrupted in-inode xattr: bad e_name length [Wed May 14 07:18:49 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304211: comm chown: corrupted in-inode xattr: bad e_name length [Wed May 14 07:18:57 2025] EXT4-fs error (device mmcblk0p2): ext4_xattr_ibody_find:2235: inode #304209: comm chown: corrupted in-inode xattr: ea_inode specified without ea_inode feature enabled ...Wie kann ich so etwas in Zukunft vorbeugen?
Hast Du dem Pi mal hart den Stecker gezogen? Stromausfall?
Sowas mögen die nicht.
Auch eine möglichst hochwertige SD-Karte ist vorteilhaft. -
@homoran sagte in WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar:
wenn du es wie gewünscht und verlinkt, in code-tags postest, kann ich es dir zitieren.
Hatte ich Probleme beim speichern von diesen Post, deshalb habe ich es als Anhang.
Aber Danke für Hinweis, Bereits geändert.@codierknecht sagte in WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar:
Hast Du dem Pi mal hart den Stecker gezogen? Stromausfall?
Nein, und kein Stromausfall.
@codierknecht sagte in WebUI - Admin (8081) u. Visu (8082) - nicht erreichbar:
hochwertige SD-Karte
hast Du ein Vorschlag für eine gute bzw sehr gute.?
