@markus2805
Muss mich korrigieren.
geht doch.
Ich denke euch beiden für die superschnelle Hilfe
M
Latest posts made by Markus2805
-
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
-
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
@reutli said in Nach Restore kein Zugriff mehr auf WebUI:
@thomas-braun sagte in Nach Restore kein Zugriff mehr auf WebUI:
ion upgrade@Markus2805
bzw.iob upgradesorry, war mein Fehler.
jetzt sind die iobroker updates durch, WebUI geht allerdings immernoch nicht├── iobroker.admin@6.12.0
├── iobroker.alexa2@3.26.1
├── iobroker.backitup@2.8.7
├── iobroker.cloud@4.4.1
├── iobroker.daswetter@3.1.10
├── iobroker.discovery@4.2.0
├── iobroker.doorbird@1.3.0
├── iobroker.hm-rega@4.0.0
├── iobroker.hm-rpc@1.15.19
├── iobroker.hue-extended@2.0.0
├── iobroker.info@2.0.0
├── iobroker.iot@2.0.11
├── iobroker.javascript@7.1.4
├── iobroker.js-controller@5.0.16
├── iobroker.lightify@0.2.16
├── iobroker.melcloud@1.3.6
├── iobroker.mobile@1.0.1
├── iobroker.simple-api@2.7.2
├── iobroker.vis-history@1.0.0
├── iobroker.vis-hqwidgets@1.4.0
├── iobroker.vis-metro@1.2.0
├── iobroker.vis-timeandweather@1.2.2
├── iobroker.vis-weather@2.5.6
├── iobroker.vis@1.4.16
├── iobroker.web@6.1.10
└── iobroker.zigbee@1.8.24 -
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
@thomas-braun said in Nach Restore kein Zugriff mehr auf WebUI:
Knall die Updates rein, inkl.der iob-relevanten.
Bei 21 ist da vermutlich gar nix mehr aktuell...hab das was "reutli" geschrieben hat durchgeführt. nach einem erneuten npm ls sehe ich keine Unterschiede
iobroker.inst@3.0.0 /opt/iobroker
├── @types/caseless@0.12.5 extraneous
├── @types/request@2.48.12 extraneous
├── @types/tough-cookie@4.0.5 extraneous
├── coffee-compiler@0.3.2 extraneous
├── coffee-script@1.12.7 extraneous
├── define-properties@1.2.1 extraneous
├── iobroker.admin@4.2.1
├── iobroker.alexa2@3.9.1
├── iobroker.backitup@2.1.11
├── iobroker.cloud@4.0.11
├── iobroker.daswetter@3.0.7
├── iobroker.discovery@2.6.2
├── iobroker.doorbird@0.1.5
├── iobroker.hm-rega@3.0.25
├── iobroker.hm-rpc@1.14.41
├── iobroker.hue-extended@2.0.0
├── iobroker.info@1.7.14
├── iobroker.iot@1.8.22
├── iobroker.javascript@5.1.3
├── iobroker.js-controller@5.0.16
├── iobroker.lightify@0.2.16
├── iobroker.melcloud@1.1.4
├── iobroker.mobile@1.0.1
├── iobroker.simple-api@2.6.1
├── iobroker.vis-history@1.0.0
├── iobroker.vis-hqwidgets@1.1.7
├── iobroker.vis-metro@1.1.2
├── iobroker.vis-timeandweather@1.1.7
├── iobroker.vis-weather@2.5.3
├── iobroker.vis@1.3.10
├── iobroker.web@3.4.1
├── iobroker.zigbee@1.5.6
├── is-nan@1.3.2 extraneous
├── jsonata@1.8.6 extraneous
├── mdns@ extraneous
├── moment-timezone@0.5.43 extraneous
├── node-inspect@2.0.0 extraneous
├── object-keys@1.1.1 extraneous
├── picocolors@1.0.0 extraneous
├── suncalc2@1.8.1 extraneous
├── virtual-tsc@0.6.2 extraneous
├── vm2@3.9.19 extraneous
└── wake_on_lan@1.0.0 extraneous -
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
@thomas-braun said in Nach Restore kein Zugriff mehr auf WebUI:
Dann konzentriere dich auf die npm Fehler.
cd /opt/iobroker npm lsiobroker.inst@3.0.0 /opt/iobroker
├── @types/caseless@0.12.5 extraneous
├── @types/request@2.48.12 extraneous
├── @types/tough-cookie@4.0.5 extraneous
├── coffee-compiler@0.3.2 extraneous
├── coffee-script@1.12.7 extraneous
├── define-properties@1.2.1 extraneous
├── iobroker.admin@4.2.1
├── iobroker.alexa2@3.9.1
├── iobroker.backitup@2.1.11
├── iobroker.cloud@4.0.11
├── iobroker.daswetter@3.0.7
├── iobroker.discovery@2.6.2
├── iobroker.doorbird@0.1.5
├── iobroker.hm-rega@3.0.25
├── iobroker.hm-rpc@1.14.41
├── iobroker.hue-extended@2.0.0
├── iobroker.info@1.7.14
├── iobroker.iot@1.8.22
├── iobroker.javascript@5.1.3
├── iobroker.js-controller@5.0.16
├── iobroker.lightify@0.2.16
├── iobroker.melcloud@1.1.4
├── iobroker.mobile@1.0.1
├── iobroker.simple-api@2.6.1
├── iobroker.vis-history@1.0.0
├── iobroker.vis-hqwidgets@1.1.7
├── iobroker.vis-metro@1.1.2
├── iobroker.vis-timeandweather@1.1.7
├── iobroker.vis-weather@2.5.3
├── iobroker.vis@1.3.10
├── iobroker.web@3.4.1
├── iobroker.zigbee@1.5.6
├── is-nan@1.3.2 extraneous
├── jsonata@1.8.6 extraneous
├── moment-timezone@0.5.43 extraneous
├── node-inspect@2.0.0 extraneous
├── object-keys@1.1.1 extraneous
├── picocolors@1.0.0 extraneous
├── suncalc2@1.8.1 extraneous
├── virtual-tsc@0.6.2 extraneous
├── vm2@3.9.19 extraneous
└── wake_on_lan@1.0.0 extraneous -
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
@markus2805 said in Nach Restore kein Zugriff mehr auf WebUI:
@reutli said in Nach Restore kein Zugriff mehr auf WebUI:
@markus2805 sagte in Nach Restore kein Zugriff mehr auf WebUI:
Pending OS-Updates: 16 Pending iob updates: 21
Welches OS installiert?
@markus2805 sagte in Nach Restore kein Zugriff mehr auf WebUI:
======================= SUMMARY =======================
Das ist nicht die Langfassung, sondern das Summary!
OS habe ich Raspberry PI OS Lite (64bit)
und hier die Langfassung:
======== Start marking the full check here =========Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi4-rpi-v8 Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 17:50:38 up 52 min, 3 users, load average: 0.06, 0.31, 0.89 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Wed 2023-11-15 17:50:38 CET Universal time: Wed 2023-11-15 16:50:38 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** iobroker /home/iobroker iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth gpio i2c spi *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 537M 4.5G 1.3M 3.3G 7.7G Swap: 104M 0B 104M Total: 8.3G 537M 4.6G 7811 M total memory 512 M used memory 483 M active memory 2687 M inactive memory 4246 M free memory 161 M buffer memory 3014 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 782M 1.2M 780M 1% /run /dev/mmcblk0p2 ext4 29G 4.0G 24G 15% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 62M 449M 13% /boot/firmware tmpfs tmpfs 782M 0 782M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Nov 15 16:57:50 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:D6:35:F0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=786e84b5-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed Nov 15 16:57:54 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Nov 15 16:57:56 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): 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: 490M /var/ 202M /var/cache 197M /var/cache/apt 159M /var/lib 131M /var/lib/apt/lists Archived and active journals take up 28.0M in the file system. /opt/iobroker/backups: 3.1M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 146M /opt/iobroker/iobroker-data/ 96M /opt/iobroker/iobroker-data/files 29M /opt/iobroker/iobroker-data/files/javascript.admin 15M /opt/iobroker/iobroker-data/files/vis 15M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 25M /opt/iobroker/iobroker-data/objects.jsonl 9.3M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/2.b6edad9e.chunk.js.map 9.2M /opt/iobroker/iobroker-data/objects.json.migrated 9.2M /opt/iobroker/iobroker-data/objects.json.bak.migrated 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 nodejs: Installed: 18.18.2-1nodesource1 Candidate: 18.18.2-1nodesource1 Version table: *** 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.5 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.12 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.5 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: coffee-compiler@0.3.2 /opt/iobroker/node_modules/coffee-compiler npm ERR! extraneous: coffee-script@1.12.7 /opt/iobroker/node_modules/coffee-scriptDas ganze File lässt er mich nicht einfügen
-
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
@reutli said in Nach Restore kein Zugriff mehr auf WebUI:
@markus2805 sagte in Nach Restore kein Zugriff mehr auf WebUI:
Pending OS-Updates: 16 Pending iob updates: 21
Welches OS installiert?
@markus2805 sagte in Nach Restore kein Zugriff mehr auf WebUI:
======================= SUMMARY =======================
Das ist nicht die Langfassung, sondern das Summary!
OS habe ich Raspberry PI OS Lite (64bit)
und hier die Langfassung:
======== Start marking the full check here =========Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi4-rpi-v8 Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 17:50:38 up 52 min, 3 users, load average: 0.06, 0.31, 0.89 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Wed 2023-11-15 17:50:38 CET Universal time: Wed 2023-11-15 16:50:38 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** iobroker /home/iobroker iobroker adm tty dialout cdrom sudo audio video plugdev games users input render netdev bluetooth gpio i2c spi *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 537M 4.5G 1.3M 3.3G 7.7G Swap: 104M 0B 104M Total: 8.3G 537M 4.6G 7811 M total memory 512 M used memory 483 M active memory 2687 M inactive memory 4246 M free memory 161 M buffer memory 3014 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 782M 1.2M 780M 1% /run /dev/mmcblk0p2 ext4 29G 4.0G 24G 15% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 16K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 62M 449M 13% /boot/firmware tmpfs tmpfs 782M 0 782M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Nov 15 16:57:50 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:D6:35:F0 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=786e84b5-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed Nov 15 16:57:54 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Nov 15 16:57:56 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): 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: 490M /var/ 202M /var/cache 197M /var/cache/apt 159M /var/lib 131M /var/lib/apt/lists Archived and active journals take up 28.0M in the file system. /opt/iobroker/backups: 3.1M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 146M /opt/iobroker/iobroker-data/ 96M /opt/iobroker/iobroker-data/files 29M /opt/iobroker/iobroker-data/files/javascript.admin 15M /opt/iobroker/iobroker-data/files/vis 15M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 25M /opt/iobroker/iobroker-data/objects.jsonl 9.3M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/2.b6edad9e.chunk.js.map 9.2M /opt/iobroker/iobroker-data/objects.json.migrated 9.2M /opt/iobroker/iobroker-data/objects.json.bak.migrated 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 nodejs: Installed: 18.18.2-1nodesource1 Candidate: 18.18.2-1nodesource1 Version table: *** 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.5 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.12 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.5 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: coffee-compiler@0.3.2 /opt/iobroker/node_modules/coffee-compiler npm ERR! extraneous: coffee-script@1.12.7 /opt/iobroker/node_modules/coffee-script -
RE: (gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
@thomas-braun said in Nach Restore kein Zugriff mehr auf WebUI:
Schau dir 'das große Ganze' an:
iob diagAusgabe (die Langfassung) hier rein, da kann man u. U. sehen wo es klemmt.
Copy text starting here:So hab das Log mal erstellt
======================= SUMMARY ======================= v.2023-10-10 Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi4-rpi-v8 Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 16 Pending iob updates: 21 Nodejs-Installation: /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 8.2G 1.4G 3.6G 1.3M 3.3G 6.8G Swap: 104M 0B 104M Total: 8.3G 1.4G 3.7G Active iob-Instances: 2 Active repo(s): latest ioBroker Core: js-controller 5.0.16 admin 4.2.1 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.admin.1 : admin : iobroker - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : iobroker - disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 12364 States: 10021 Size of iob-Database: 25M /opt/iobroker/iobroker-data/objects.jsonl 9.2M /opt/iobroker/iobroker-data/objects.json.migrated 9.2M /opt/iobroker/iobroker-data/objects.json.bak.migrated 2.5M /opt/iobroker/iobroker-data/states.jsonl 2.3M /opt/iobroker/iobroker-data/states.json.migrated 2.3M /opt/iobroker/iobroker-data/states.json.bak.migrated =================== END OF SUMMARY ======================= Mark text until here for copying ===
-
(gelöst) Nach Restore kein Zugriff mehr auf WebUIposted in ioBroker Allgemein
Hallo zusammen,
bin neu hier, habe den IoBroker schonlänger am laufen.
Nach einem Stromausfall bekam dich den IoBroker nicht mehr ans laufen, weshalb ich mir die SD Karte meines Raspberry PI neu beschrieben habe mit dem Line Image und der IoBroker neu installiert habe.
Danach habe ich ein Backup auf die Karte gespielt und mittels Backitup die Daten wiederhergestellt.
Dies habe ich nun schon mehrfach und auch mit 2 verschiedenen Image gemacht. Leider kann ich nach dem Rektor nicht mehr an das WebUI.Da ich den IoBroker zwar schon länger am laufen habe, jedoch keinerlei Erfahrung wo ich welches Log zur Verfügung habe, die Frage an die Profis unter euch.
Was kann denn das Problem sein, dass ich nach dem Rektor nicht mehr ans WebUI komme?Gruß
Markus
