IoB web page nicht erreichbar Update Admin adapter
-
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:
den gesamten Ausgabetext
als Text in code-tags
trotzdem sieht man, dass der Vorschlag von @paul53 erfolgreich sein müsste/könnte
-
@paul53 : Hab ich gemacht. Kann aber die Web-Page immer noch nicht aufrufen.
-
Der gesamte Text der Langfassung ist gefragt.
Ich sehe aber jetzt schon, dass die komplette Kiste schwer sanierungsbedürftig ist. -
@homoran ```
========== Start marking the full check here ===========Script v.2025-02-23 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.74+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: 18:57:05 up 1 day, 1:54, 2 users, load average: 0.03, 0.02, 0.02 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'bookworm'! *** RASPBERRY THROTTLING *** Current issues: ~ Under-voltage detected ~ Arm frequency capped Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** TIME AND TIMEZONES *** Local time: Mon 2025-03-31 18:57:05 CEST Universal time: Mon 2025-03-31 16:57:05 UTC RTC time: Mon 2025-03-31 16:57:05 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 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 995M 6.2G 5.5M 1.3G 7.4G Swap: 536M 0B 536M Total: 9.0G 995M 6.8G Active iob-Instances: 9 8052 M total memory 949 M used memory 1095 M active memory 793 M inactive memory 5935 M free memory 126 M buffer memory 1142 M swap cache 511 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 18:57:05 up 1 day, 1:54, 2 users, load average: 0.11, 0.03, 0.02 Tasks: 165 total, 2 running, 163 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 33.3 sy, 0.0 ni, 66.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 8052.2 total, 5935.6 free, 949.9 used, 1268.9 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 7102.4 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** 1 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 5.2M 801M 1% /run /dev/mmcblk0p2 ext4 117G 9.2G 102G 9% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /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: [Sun Mar 30 17:02:30 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:66:EC:20 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=f9e3762a-02 rootfstype=ext4 fsck.repair=yes rootwait [Sun Mar 30 17:02:35 2025] EXT4-fs (mmcblk0p2): mounted filesystem ce208fd3-38a8-424a-87a2-cd44114eb820 ro with ordered data mode. Quota mode: none. [Sun Mar 30 17:02:36 2025] EXT4-fs (mmcblk0p2): re-mounted ce208fd3-38a8-424a-87a2-cd44114eb820 r/w. Quota mode: none. 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: 4.0G /var/ 2.8G /var/log/journal/a787909f1af9441ba59c4ccec33e25d4 2.8G /var/log/journal 2.8G /var/log 437M /var/lib Archived and active journals take up 2.7G in the file system. /opt/iobroker/backups: 19M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 696M /opt/iobroker/iobroker-data/ 644M /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: 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.js.map 8.6M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/310.89a60ae1.chunk.js.map 7.0M /opt/iobroker/iobroker-data/objects.jsonl 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.a9c6d34a.chunk.js.map 7.0M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/675.7e9d7842.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' 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.18.3 /usr/bin/node v20.18.3 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.30.0 nodejs: Installed: 20.18.3-1nodesource1 Candidate: 20.19.0-1nodesource1 Version table: 20.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages *** 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 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 running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker iobroker (version: 6.0.11, hostname: iobroker , alive, uptime: 1367) Core adapters versions js-controller: 6.0.11 admin: "admin" not found 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.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1885, bind: 0.0.0.0 system.adapter.telegram.0 : telegram : iobroker - disabled, port: 8443, bind: 0.0.0.0 + 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.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1885, bind: 0.0.0.0 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 Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common//../node_modules/iobroker.admin/io-package.json: /opt/iobroker/node_modules/iobroker.admin/package.json: Unexpected end of JSON input Cannot read or parse /opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common//../node_modules/iobroker.admin/io-package.json: /opt/iobroker/node_modules/iobroker.admin/package.json: Unexpected end of JSON input Adapter "backitup" : 3.0.31 , installed 3.0.31 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "javascript" : 8.8.3 , installed 8.8.3 Controller "js-controller": 7.0.6 , installed 6.0.11 [Updatable] Adapter "shelly" : 8.5.1 , installed 8.5.1 Adapter "telegram" : 4.0.0 , installed 4.0.0 Objects and States Please stand by - This may take a while Objects: 1887 States: 1411 *** 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 https://repos.influxdata.com/debian stable InRelease Hit:5 http://deb.debian.org/debian bookworm-updates InRelease Hit:6 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 36 *** 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 192.168.178.188:2001 0.0.0.0:* LISTEN 1001 541872 9091/io.hm-rpc.0 tcp 0 0 192.168.178.188:2010 0.0.0.0:* LISTEN 1001 541289 9121/io.hm-rpc.1 tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 2976 655/sshd: /usr/sbin tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 541059 9013/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 541064 9013/iobroker.js-co tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 539600 9076/io.shelly.0 tcp6 0 0 :::22 :::* LISTEN 0 2978 655/sshd: /usr/sbin tcp6 0 0 :::3000 :::* LISTEN 106 6203 770/grafana tcp6 0 0 :::8086 :::* LISTEN 999 6179 709/influxd udp 0 0 0.0.0.0:35230 0.0.0.0:* 104 4899 529/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 4897 529/avahi-daemon: r udp6 0 0 :::5353 :::* 104 4898 529/avahi-daemon: r udp6 0 0 :::59283 :::* 104 4900 529/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-03-31 18:57:42.338 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.memHeapUsed:{"val":49.39,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440262334} 2025-03-31 18:57:42.339 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.load:{"val":0.37,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440262334} 2025-03-31 18:57:42.339 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.uptime:{"val":1412,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440262334} 2025-03-31 18:57:42.339 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.mem:{"val":13,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440247335} 2025-03-31 18:57:42.340 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.freemem:{"val":7022,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440262334} 2025-03-31 18:57:42.340 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.memAvailable:{"val":7364,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440262334} 2025-03-31 18:57:42.340 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.inputCount:{"val":9,"ack":true,"ts":1743440262334,"q":0,"from":"system.host.iobroker","lc":1743440262334} 2025-03-31 18:57:42.340 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.outputCount:{"val":13,"ack":true,"ts":1743440262335,"q":0,"from":"system.host.iobroker","lc":1743440082335} 2025-03-31 18:57:42.341 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.eventLoopLag:{"val":1,"ack":true,"ts":1743440262335,"q":0,"from":"system.host.iobroker","lc":1743440262335} 2025-03-31 18:57:42.341 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.compactgroupProcesses:{"val":0,"ack":true,"ts":1743440262335,"q":0,"from":"system.host.iobroker","lc":1732122139005} 2025-03-31 18:57:42.346 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.instancesAsProcess:{"val":8,"ack":true,"ts":1743440262335,"q":0,"from":"system.host.iobroker","lc":1743438882325} 2025-03-31 18:57:42.346 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.instancesAsCompact:{"val":0,"ack":true,"ts":1743440262335,"q":0,"from":"system.host.iobroker","lc":1732122139005} 2025-03-31 18:57:42.346 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.cpu:{"val":2.13,"ack":true,"ts":1743440262344,"q":0,"from":"system.host.iobroker","lc":1743440262344} 2025-03-31 18:57:42.346 - silly: influxdb.0 (9046) States user redis pmessage */system.host.iobroker.cputime:{"val":26.96,"ack":true,"ts":1743440262344,"q":0,"from":"system.host.iobroker","lc":1743440262344} 2025-03-31 18:57:42.586 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.alive:{"val":true,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743438882553,"expire":true} 2025-03-31 18:57:42.586 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.connected:{"val":true,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743438882553,"expire":true} 2025-03-31 18:57:42.587 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.memRss:{"val":69.42,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743440217584,"expire":true} 2025-03-31 18:57:42.587 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.memHeapTotal:{"val":23.19,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743439077547,"expire":true} 2025-03-31 18:57:42.588 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.memHeapUsed:{"val":21.25,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743440262585,"expire":true} 2025-03-31 18:57:42.588 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.eventLoopLag:{"val":2,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743440217584,"expire":true} 2025-03-31 18:57:42.589 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.uptime:{"val":1382,"ack":true,"ts":1743440262585,"q":0,"from":"system.adapter.discovery.0","lc":1743440262585,"expire":true} 2025-03-31 18:57:42.590 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.inputCount:{"val":0,"ack":true,"ts":1743440262588,"q":0,"from":"system.adapter.discovery.0","lc":1743438912542,"expire":true} 2025-03-31 18:57:42.590 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.outputCount:{"val":11,"ack":true,"ts":1743440262589,"q":0,"from":"system.adapter.discovery.0","lc":1743438912542,"expire":true} 2025-03-31 18:57:42.593 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.cpu:{"val":0.07,"ack":true,"ts":1743440262592,"q":0,"from":"system.adapter.discovery.0","lc":1743440262592,"expire":true} 2025-03-31 18:57:42.594 - silly: influxdb.0 (9046) States user redis pmessage */system.adapter.discovery.0.cputime:{"val":2.99,"ack":true,"ts":1743440262592,"q":0,"from":"system.adapter.discovery.0","lc":1743440262592,"expire":true}============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
-
@thomas-braun : Ich befürchte, dass du mir sagen wirst, dass ich grundlegende Fehler bei der Installation vom IoBroker gemacht habe?!?
Kannst du bitte etwas genauer werden?
-
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:
Kannst du bitte etwas genauer werden?
geht erst jetzt mit der vollständigen Langfassung
stay tuned
-
Deine Spannungsversorgung ist zu schwach auf der Brust.
Der Admin ist kaputt.
Der Js-Controller ist veraltet.
-
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:
Under-voltage has occurred
Netzteilprobleme!
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:
Arm frequency capping has occurred
thermische Probleme
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:
admin: "admin" not found
warum, müssen wir suchen.
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:
Controller "js-controller": 7.0.6 , installed 6.0.11 [Updatable]
Das könnte fue Ursache sein
-
-
@takahara würde ich mit anfangen, und dann nochmal den admin
-
@homoran : wäre es in Ordnung, wenn du mir die Befehle unten auflisten kannst?
Vielen Dank für deine Unterstützung! -
@Takahara
erst einmal den controlleriob stop iob update iob upgrade self iob starteinzeln nacheinander eingeben
-
Zuvor würde ich die Basis noch aktualisieren.
iob stop sudo apt update sudo apt full-upgrade sudo reboot -
@Thomas-Braun
ooops!
Hatte ich schon geschrieben und wieder gelöscht.Hatte diese
@takahara sagte in IoB web page nicht erreichbar Update Admin adapter:Pending Updates: 36
übersehen
-
Heute kam auch der aktuelle LTS-Kernel per update rein:
Linux chet 6.12.20+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.20-1+rpt1~bpo12+1 (2025-03-19) aarch64 GNU/LinuxWichtig.
-
@thomas-braun : Primar
Hat funktioniert. Vielen Dank nochmals für deine / eure Unterstützung. -
Wo stehst du denn jetzt mit dem Ding?
-
Auch ich habe ähnliche Erfahrungen nach dem Update des Admin-Adapters gemacht. Anders als bei dir sollte jedoch mein System auf aktuellem Stand sein.
Ich rettete mich in diesen Situationen mit einem Neustart des Safari-Browsers auf meinem MacBook. Irgendwie vermag ich das Ganze wohl noch nicht so richtig einzuschätzen. Nun werde ich ebenfalls einmal alle hier vorgeschlagenen Schritte durchführen. Ich habe bisher upgrade anstelle von full-upgrade verwendet.
-
Mit solchen allgemeinen Aussagen kann man nichts anfangen. Schau dir an, ob die Dienste laufen, ob die per SSL abgesichert sind, auf welchem Port die lauschen usw.
Das und noch mehr steht alles iniob diagdrin
-
@thomas-braun sagte in IoB web page nicht erreichbar Update Admin adapter:
Mit solchen allgemeinen Aussagen kann man nichts anfangen. ..
Stimmt. Aber wenn ich‘s genauer eingrenzen könnte, hätte ich es auch getan.
iob diag zeigt keine Auffälligkeiten. Auch wurde mittels der Option full-upgrade nichts nachträglich installiert.
Da dieses seltsame und seltene Verhalten nach dem Update auftrat, hatte ich die Hoffnung, hier Ideen für eine Lösung zu finden. Aber es scheint wohl bei mir etwas mit dem Safari Browser auf dem MacBook zu tun zu haben: Wenn der Admin Adapter auf dem MacBook sich nicht zeigt, kann ich mittels Aufruf vom iPad aus oder Neustarten von Safari das Problem beheben. Einfach bloß seltsam.
