Iobroker nicht mehr erreichbar
-
@thomas-braun Sorry da kam noch mehr. Kann man daraus etwas erkennen:
Ich hatte auch eigentlich einen aderen Host, den kann ich aber gar nicht mehr finden bzw. erreichen
Wie kann das sein, dass ohne eine Änderungung das Ganze von heute auf morgen nicht mehr läuft?
Bin etwas ratlos
VG Sven
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 400 Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 12:43:55 up 51 min, 2 users, load average: 5.30, 5.43, 4.78 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 2024-05-01 12:43:55 CEST Universal time: Wed 2024-05-01 10:43:55 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) 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: 3.8G 295M 2.6G 1.0M 925M 3.4G Swap: 99M 0B 99M Total: 3.9G 295M 2.7G 3794 M total memory 295 M used memory 522 M active memory 391 M inactive memory 2572 M free memory 145 M buffer memory 780 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 /dev/root ext4 29G 17G 12G 61% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 1.2M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: [Wed May 1 11:51:57 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:3C:72:9F vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=e6bc09a5-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed May 1 11:51:58 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Wed May 1 11:51:58 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Wed May 1 11:51:59 2024] EXT4-fs (mmcblk0p2): recovery complete [Wed May 1 11:51:59 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed May 1 11:51:59 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed May 1 11:52:01 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.1G /var/ 1022M /var/log 897M /var/log/journal/a6947f3f150d40ff92fc95ef6b744298 897M /var/log/journal 612M /var/cache Archived and active journals take up 896.0M in the file system. /opt/iobroker/backups: 9.6G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 545M /opt/iobroker/iobroker-data/ 383M /opt/iobroker/iobroker-data/files 102M /opt/iobroker/iobroker-data/backup-objects 78M /opt/iobroker/iobroker-data/files/icons-open-icon-library-png 71M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 31M /opt/iobroker/iobroker-data/states.jsonl 30M /opt/iobroker/iobroker-data/objects.jsonl 20M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.becd2d7c.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 8.0M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.becd2d7c.js 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 /usr/bin/node /usr/bin/npm /usr/bin/npx /usr/bin/corepack nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status /usr/bin/iobroker: line 12: 3450 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Core adapters versions /usr/bin/iob: line 12: 3469 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" js-controller: /usr/bin/iob: line 12: 3498 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" admin: /usr/bin/iob: line 12: 3528 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" javascript: Adapters from github: 0 Adapter State /usr/bin/iob: line 12: 3542 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Enabled adapters with bindings /usr/bin/iob: line 12: 3571 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" ioBroker-Repositories /usr/bin/iob: line 12: 3577 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Installed ioBroker-Instances /usr/bin/iob: line 12: 3585 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.grafana.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://apt.grafana.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://repos.influxdata.com/debian bullseye InRelease Get:7 https://apt.grafana.com stable InRelease [7660 B] Hit:8 https://deb.nodesource.com/node_18.x bullseye InRelease Err:7 https://apt.grafana.com stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.grafana.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://apt.grafana.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. Pending Updates: 0 -
Auch das ist nicht vollständig. Es gibt in der Ausgabe Markierungen was von wo bis wo zu kopieren ist.
-
@thomas-braun weiter geht es bei mir leider nicht. Der hängt da jetztseit ner halben Stunde an der Stelle
-
@thomas-braun
jetzt hates doch geklappt:======= Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 400 Rev 1.1 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 12:43:55 up 51 min, 2 users, load average: 5.30, 5.43, 4.78 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 2024-05-01 12:43:55 CEST Universal time: Wed 2024-05-01 10:43:55 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) 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: 3.8G 295M 2.6G 1.0M 925M 3.4G Swap: 99M 0B 99M Total: 3.9G 295M 2.7G 3794 M total memory 295 M used memory 522 M active memory 391 M inactive memory 2572 M free memory 145 M buffer memory 780 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 /dev/root ext4 29G 17G 12G 61% / devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 759M 1.2M 758M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 380M 0 380M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [sudo] password for iobroker: [Wed May 1 11:51:57 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:3C:72:9F vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=e6bc09a5-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed May 1 11:51:58 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Wed May 1 11:51:58 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Wed May 1 11:51:59 2024] EXT4-fs (mmcblk0p2): recovery complete [Wed May 1 11:51:59 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed May 1 11:51:59 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed May 1 11:52:01 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.1G /var/ 1022M /var/log 897M /var/log/journal/a6947f3f150d40ff92fc95ef6b744298 897M /var/log/journal 612M /var/cache Archived and active journals take up 896.0M in the file system. /opt/iobroker/backups: 9.6G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 545M /opt/iobroker/iobroker-data/ 383M /opt/iobroker/iobroker-data/files 102M /opt/iobroker/iobroker-data/backup-objects 78M /opt/iobroker/iobroker-data/files/icons-open-icon-library-png 71M /opt/iobroker/iobroker-data/files/vis The five largest files in iobroker-data are: 31M /opt/iobroker/iobroker-data/states.jsonl 30M /opt/iobroker/iobroker-data/objects.jsonl 20M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.becd2d7c.js.map 18M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.274a4d8d.js.map 8.0M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.becd2d7c.js 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 /usr/bin/node /usr/bin/npm /usr/bin/npx /usr/bin/corepack nodejs: Installed: 18.17.1-deb-1nodesource1 Candidate: 18.17.1-deb-1nodesource1 Version table: *** 18.17.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main arm64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status /usr/bin/iobroker: line 12: 3450 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Core adapters versions /usr/bin/iob: line 12: 3469 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" js-controller: /usr/bin/iob: line 12: 3498 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" admin: /usr/bin/iob: line 12: 3528 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" javascript: Adapters from github: 0 Adapter State /usr/bin/iob: line 12: 3542 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Enabled adapters with bindings /usr/bin/iob: line 12: 3571 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" ioBroker-Repositories /usr/bin/iob: line 12: 3577 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Installed ioBroker-Instances /usr/bin/iob: line 12: 3585 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.grafana.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://apt.grafana.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://repos.influxdata.com/debian bullseye InRelease Get:7 https://apt.grafana.com stable InRelease [7660 B] Hit:8 https://deb.nodesource.com/node_18.x bullseye InRelease Err:7 https://apt.grafana.com stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.grafana.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://apt.grafana.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. Pending Updates: 0 [sudo] password for iobroker: *** Listening Ports *** Sorry, try again. [sudo] password for iobroker: 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 12938 561/sshd: /usr/sbin tcp6 0 0 :::8086 :::* LISTEN 999 1710 429/influxd tcp6 0 0 :::22 :::* LISTEN 0 12940 561/sshd: /usr/sbin tcp6 0 0 :::3000 :::* LISTEN 110 20602 2872/grafana udp 0 0 0.0.0.0:56384 0.0.0.0:* 108 12709 373/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12707 373/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14401 627/dhcpcd udp6 0 0 :::58098 :::* 108 12710 373/avahi-daemon: r udp6 0 0 :::5353 :::* 108 12708 373/avahi-daemon: r udp6 0 0 :::546 :::* 0 13014 627/dhcpcd *** Log File - Last 25 Lines *** 2024-04-26 00:05:55.669 - info: web.0 (1569547) terminated http server on port 8082 2024-04-26 00:05:55.669 - info: web.0 (1569547) terminating 2024-04-26 00:05:55.670 - info: web.0 (1569547) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-04-26 00:06:11.955 - info: web.0 (1569547) terminating with timeout 2024-04-26 00:05:15.267 - info: volvo.1 (1569537) Got terminate signal TERMINATE_YOURSELF 2024-04-26 00:06:11.955 - info: volvo.1 (1569537) cleaned everything up... 2024-04-26 00:06:11.957 - info: volvo.1 (1569537) terminating 2024-04-26 00:06:20.177 - info: volvo.1 (1569537) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-04-26 00:06:21.685 - info: volvo.1 (1569537) terminating with timeout 2024-04-26 00:05:15.150 - info: pollenflug.0 (1569386) Got terminate signal TERMINATE_YOURSELF 2024-04-26 00:06:11.954 - info: pollenflug.0 (1569386) Closing Adapter 2024-04-26 00:06:11.954 - info: pollenflug.0 (1569386) terminating 2024-04-26 00:06:20.177 - info: pollenflug.0 (1569386) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-04-26 00:06:46.089 - info: pollenflug.0 (1569386) terminating with timeout 2024-04-26 00:07:01.969 - error: roomba.0 (1569414) Objects database error: read ECONNRESET 2024-04-26 00:07:01.990 - error: homeconnect.0 (1569254) Objects database error: read ECONNRESET 2024-04-26 00:07:01.993 - warn: sonoff.0 (1568933) redis get sonoff.0.Stromverbrauch WP.alive, error - DB closed 2024-04-26 00:07:02.006 - error: admin.0 (1568600) Objects database error: read ECONNRESET 2024-04-26 00:07:02.044 - error: knx.0 (1569374) Objects database error: read ECONNRESET 2024-04-26 00:07:10.079 - warn: javascript.0 (1569202) get state error: Connection is closed. 2024-04-26 00:05:15.161 - info: terminal.0 (1569408) Got terminate signal TERMINATE_YOURSELF 2024-04-26 00:06:28.386 - info: terminal.0 (1569408) terminated http server on port 8089 2024-04-26 00:06:28.390 - info: terminal.0 (1569408) terminating 2024-04-26 00:06:28.392 - info: terminal.0 (1569408) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-04-26 00:07:18.232 - info: terminal.0 (1569408) terminating with timeout============ Mark until here for C&P =============
-
@sven-muthke sagte in Iobroker nicht mehr erreichbar:
[Wed May 1 11:51:58 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
[Wed May 1 11:51:58 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recoveryDa ist was mit deinem Dateisystem nicht in Ordnung.
/opt/iobroker/backups:
9.6G /opt/iobroker/backups/Lokal vorgehaltene Backups sind nur sehr begrenzt sinnvoll. Immer nach extern auslagern.
nodejs:
Installed: 18.17.1-deb-1nodesource1
Candidate: 18.17.1-deb-1nodesource1Dein nodejs-(Repo) ist veraltet. Funktioniert
iobroker nodejs-updatenoch?
Err:7 https://apt.grafana.com stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545Dein Grafana-Repo (bzw. der Key dazu) ist veraltet. Leg das nochmal neu an.
cat /usr/bin/iobsagt?
-
@sven-muthke sagte in Iobroker nicht mehr erreichbar:
Operating System: Debian GNU/Linux 11 (bullseye)
Wäre vielleicht eine gute Gelegenheit komplett NEU das Bookworm-Release auf die Kiste zu werfen.
-
@thomas-braun said in Iobroker nicht mehr erreichbar:
iobroker nodejs-update
Vielen Dank.
Ich bekomme folgende Meldung:
sudo iobroker nodejs-update [sudo] password for iobroker: You should not use root directly on your system! Better use your standard user! ioBroker node-update v2023-10-13 is starting. Please be patient! /usr/bin/iobroker: line 12: 1995 Bus error sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@"und dann kommt das:
ioBroker nodejs updater 2023-10-13 No recommendation for a nodejs version found on your system. We recommend to install latest version from nodejs v18 tree. Your current setup is: /usr/bin/nodejscat /usr/bin/iob #!/usr/bin/bash if (( $# == 1 )) && ([ "$1" = "start" ] || [ "$1" = "stop" ] || [ "$1" = "restart" ]); then sudo systemctl $1 iobroker elif [ "$1" = "fix" ]; then curl -sL https://iobroker.net/fix.sh | bash - elif [ "$1" = "nodejs-update" ]; then sudo -u iobroker curl -sLf https://iobroker.net/node-update.sh --output /home/iobroker/.nodejs-update.sh && bash /home/iobroker/.nodejs-update.sh "$2" elif [ "$1" = "diag" ]; then sudo -u iobroker curl -sLf https://iobroker.net/diag.sh --output /home/iobroker/.diag.sh && bash /home/iobroker/.diag.sh | sudo -u iobroker tee /home/iobroker/iob_diag.log else sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@" fiWie kann ich das Backup da runter holen?
VG Sven
-
@thomas-braun Wie geht das und wie kann ich dann meine Daten wieder herstellen?
Vielen Dank für die Hilfe!!!
VG Sven
-
wie kann ich herausfinden, on mein eigentlihcer Host noch läuft? Ich kann mich nur mit dem Iobroker Host einloggen, aber nicht mit meinem eigentlichen.
-
Und wo bitte stand, dass du das als root/per sudo machen sollst?
Pflügst du da immer mit sudo drüber?
Dann wundert es mich auch nicht, das die Kiste spinnt.
NIE NIE NIE als root anmelden und NIE NIE NIE den iobroker mit sudo anpacken.curl -sL https://iobroker.net/fix.sh | bash -ausführen.
wie kann ich herausfinden, on mein eigentlihcer Host noch läuft? Ich kann mich nur mit dem Iobroker Host einloggen, aber nicht mit meinem eigentlichen.
Was meinst du mit 'eigentlichem Host' und 'iobroker Host'?
-
Sorry dachte das muss mit rein.
hab es jetzt noch einmal gemacht, läuft aber immer noch nicht.
iobroker@iobroker:~ $ curl -sL https://iobroker.net/fix.sh | bash - library: loaded Library version=2024-01-04 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-01-04 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://security.debian.org/debian-security bullseye-security InRelease Hit:5 https://repos.influxdata.com/debian stable InRelease Hit:6 https://repos.influxdata.com/debian bullseye InRelease Get:7 https://apt.grafana.com stable InRelease [7,660 B] Hit:8 https://deb.nodesource.com/node_18.x bullseye InRelease Err:7 https://apt.grafana.com stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.grafana.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://apt.grafana.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Some index files failed to download. They have been ignored, or old ones used instead. ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== [sudo] password for iobroker: Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! main: line 14: [: -lt: unary operator expected main: line 8: 3001 Bus error ( sudo -H -u iobroker npm x --yes @iobroker/jsonltool@latest "$IOB_DIR/iobroker-data" ) ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Ich hatte damals laut internet Anleitung das ganze auf iobroker@iobroker.local aufgesetzt, bekam dann aber den Hinweis, dass man das ciht macht. Dann habe ich neu installiert und Delapena@delapena.local genommen. Hatte damals auch geklappt, ist jetzt aber nicht mehr vorhanden, bzw. ich komme nur mit dem Login: iobroker und dann das Passwort rein bzw. ssh. Aber die Oberfläche ist nciht erreichbar.
Soll ich das neu installieren? Dann muss ich nur irgendiwe an mein lokales Backup kommen.
Ich bin leider echt überfragt.
-
@sven-muthke sagte in Iobroker nicht mehr erreichbar:
Soll ich das neu installieren?
Am besten. Wer weiß was da alles verfummelt worden ist.
Dann muss ich nur irgendiwe an mein lokales Backup kommen.
Per SCP/filezilla oder einem anderen Filemanager, der sich auf SCP versteht.
-
Dank Dir. Ich komme mit File Zilla nicht drauf. Ich habe das damals schon einmal geschafft, weiß aber nicht mehr wie ich das gemacht habe. IP Adresse vom Iobroker mit den Login daten funktoniert leider nicht.
Hast Du da nen Tip?
-
Noch eine Frage, welche Version soll ich am besten installieren? Ohne Desktop wenn ich das richtig verstanden habe. 64 BIT?
-
@sven-muthke sagte in Iobroker nicht mehr erreichbar:
IP Adresse vom Iobroker mit den Login daten funktoniert leider nicht.
Hast Du da nen Tip?Schau im Router nach, welche IP da vergeben wurde. Oder verwende den hostname.
Installation:
https://forum.iobroker.net/topic/51869/installation-auf-raspi-einfacher-geht-s-nicht
-
@sven-muthke sagte in Iobroker nicht mehr erreichbar:
IP Adresse vom Iobroker mit den Login daten funktoniert leider nicht.
wo willst du genau hin?
welche Logindaten?
welcher User?Hast du nach deiner exzessiven Nutzung von root/sudo die Rechte mit
iob fixwieder geradegezogen? -
hab es neu installiert und per backup wieder hergestellt. Die meisten Adapter laufen noch nicht. Ich kann mich dunkel dran erinnern, dass das etwas dauert.
Muss ich Influx und Grafna neu installieren, oder sollte das über das Update passiernen? Influx sehe ich zumindest als Adapter.
Vielen Dank für Deine unermüdliche Hilfe!!!
VG Sven
-
@sven-muthke sagte in Iobroker nicht mehr erreichbar:
Muss ich Influx und Grafna neu installieren
Ja, muss separat im Betriebssysytem installiert werden, das ist ja kein Bestandteil des ioBroker.
Ich kann mich dunkel dran erinnern, dass das etwas dauert.
Kann schon mal 'ne Stunde dauern. Beobachte das LogFile:
iob logs --watch -
Dank Dir. Hast Du eine Anleitung zur Installation von Influx und Grafana bzw. passt diese hier:?
wget -qO- https://repos.influxdata.com/influxdb.key | sudo apt-key add - source /etc/os-release echo "deb https://repos.influxdata.com/debian $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/influxdb.list Danach die Installation durchführen mit diesen beiden Befehlen: sudo apt-get update sudo apt-get install influxdb Und als letzten Schritt erst mal die Datenbank starten: sudo service influxdb start Ist diese nun gestartet, so können wir uns mit dem folgenden Befehl einfach diese öffnen: sudo influx -
Die Anleitung mit apt-key ist veraltet, macht man nicht mehr so.
Leg die entsprechenden Repos danach an:https://forum.iobroker.net/topic/59231/phantastische-repositories-und-wo-sie-zu-finden-sind
Installation dann wie üblich über deinen Paketmanager:
sudo apt update
sudo apt install grafana influxdb (oder influxdb2)
