Slave iobroker restore Fehler
-
Hallo zusammen,
ich habe gerade mein Slave-System Raspberry Pi 3b auf Bookworm umgestellt.
Ich habe den iobroker installiert und das Slave-System mit dem Master verbunden. Wird auch erkannt und richtig angezeigt.
nun versuche ich das Backup auf dem Slave-System einzuspielen und bekomme die Fehlermeldung
No connection to databases possible ...
Kann mir bitte jemand weiter helfen?
Vielen Dank!
-
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.6.47+rpt-rpi-v8 Architecture: arm64 Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 11:47:44 up 1:10, 2 users, load average: 0.26, 0.12, 0.10 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Thu 2024-09-12 11:47:45 CEST Universal time: Thu 2024-09-12 09:47:45 UTC RTC time: n/a 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 User that is running 'js-controller': js-controller is not running *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 951M 148M 208M 909K 662M 802M Swap: 209M 23M 186M Total: 1.2G 172M 394M Active iob-Instances: 0 907 M total memory 142 M used memory 156 M active memory 426 M inactive memory 198 M free memory 28 M buffer memory 603 M swap cache 199 M total swap 22 M used swap 177 M free swap *** top - Table Of Processes *** top - 11:47:45 up 1:10, 2 users, load average: 0.26, 0.12, 0.10 Tasks: 148 total, 1 running, 147 sleeping, 0 stopped, 0 zombie %Cpu(s): 11.1 us, 11.1 sy, 0.0 ni, 77.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 907.3 total, 198.6 free, 149.7 used, 632.2 buff/cache MiB Swap: 200.0 total, 177.7 free, 22.2 used. 757.5 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * iobroker.service loaded failed failed ioBroker Server LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 318M 0 318M 0% /dev tmpfs tmpfs 91M 1.1M 90M 2% /run /dev/mmcblk0p2 ext4 59G 3.4G 52G 7% / tmpfs tmpfs 454M 0 454M 0% /dev/shm tmpfs tmpfs 5.0M 12K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 64M 447M 13% /boot/firmware tmpfs tmpfs 91M 0 91M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Sep 12 10:36:52 2024] 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 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=b128265a-02 rootfstype=ext4 fsck.repair=yes rootwait [Thu Sep 12 10:36:56 2024] EXT4-fs (mmcblk0p2): mounted filesystem 56f80fa2-e005-4cca-86e6-19da1069914d ro with ordered data mode. Quota mode: none. [Thu Sep 12 10:36:59 2024] EXT4-fs (mmcblk0p2): re-mounted 56f80fa2-e005-4cca-86e6-19da1069914d r/w. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime | `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=430 | `-/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime |-/dev udev devtmpfs rw,nosuid,relatime,size=325264k,nr_inodes=81316,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=92904k,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/credentials/systemd-sysctl.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/credentials/systemd-sysusers.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/credentials/systemd-tmpfiles-setup-dev.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | |-/run/credentials/systemd-tmpfiles-setup.service ramfs ramfs ro,nosuid,nodev,noexec,relatime,mode=700 | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=92904k,nr_inodes=23226,mode=700,uid=1000,gid=1000 `-/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: 619M /var/ 206M /var/cache 200M /var/cache/apt 166M /var/lib 133M /var/lib/apt/lists Archived and active journals take up 47.6M in the file system. /opt/iobroker/backups: 25M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 67M /opt/iobroker/iobroker-data/ 62M /opt/iobroker/iobroker-data/files 31M /opt/iobroker/iobroker-data/files/backitup.admin 31M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 31M /opt/iobroker/iobroker-data/files/admin.admin/custom/static The five largest files in iobroker-data are: 14M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.2cca4954.js 7.0M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_icons-material_esm_index_js.0c96b194.chunk.js.map 5.6M /opt/iobroker/iobroker-data/files/backitup.admin/custom/static/js/vendors-node_modules_file-saver_dist_FileSaver_min_js-node_modules_react-icons_di_index_mjs-n-f0ed96.6c33ff1f.chunk.js 5.5M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-2d33e4.42bb0640.chunk.js.map 4.9M /opt/iobroker/iobroker-data/objects.jsonl USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 nodejs: Installed: 20.17.0-1nodesource1 Candidate: 20.17.0-1nodesource1 Version table: *** 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 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 npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status No connection to databases possible ... Core adapters versions js-controller: 6.0.11 admin: 7.0.23 javascript: "javascript" not found nodejs modules from github: 0 Adapter State No connection to databases possible ... Enabled adapters with bindings ioBroker-Repositories No connection to databases possible ... Installed ioBroker-Instances No connection to databases possible ... Objects and States Please stand by - This may take a while Objects: 1 States: 1 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 5414 610/sshd: /usr/sbin tcp6 0 0 :::22 :::* LISTEN 0 5416 610/sshd: /usr/sbin udp 0 0 0.0.0.0:37187 0.0.0.0:* 104 3060 456/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 3058 456/avahi-daemon: r udp6 0 0 :::43018 :::* 104 3061 456/avahi-daemon: r udp6 0 0 fe80::2b0f:cce2:5d2:546 :::* 0 6328 520/NetworkManager udp6 0 0 :::5353 :::* 104 3059 456/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-09-12 11:02:18.690 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 (force=false, process=true) 2024-09-12 11:02:18.703 - info: enigma2.0 (9627) Got terminate signal TERMINATE_YOURSELF 2024-09-12 11:02:18.703 - info: rpi2.1 (10367) Got terminate signal TERMINATE_YOURSELF 2024-09-12 11:02:18.689 - info: zigbee.0 (10473) Zigbee: disabling joining new devices. 2024-09-12 11:02:18.725 - info: zigbee.0 (10473) Got terminate signal TERMINATE_YOURSELF 2024-09-12 11:02:18.750 - info: host.raspberrypi stopInstance system.adapter.enigma2.0 send kill signal 2024-09-12 11:02:18.754 - info: host.raspberrypi stopInstance system.adapter.rpi2.1 send kill signal 2024-09-12 11:02:18.755 - info: host.raspberrypi stopInstance system.adapter.zigbee.0 send kill signal 2024-09-12 11:02:19.192 - info: rpi2.1 (10367) terminating 2024-09-12 11:02:19.194 - info: enigma2.0 (9627) terminating 2024-09-12 11:02:19.197 - info: enigma2.0 (9627) Terminated (NO_ERROR): Without reason 2024-09-12 11:02:19.240 - info: zigbee.0 (10473) terminating 2024-09-12 11:02:19.248 - info: zigbee.0 (10473) Terminated (NO_ERROR): Without reason 2024-09-12 11:02:19.790 - info: host.raspberrypi instance system.adapter.rpi2.1 terminated with code 0 (NO_ERROR) 2024-09-12 11:02:19.793 - info: host.raspberrypi stopInstance timeout system.adapter.enigma2.0 killing pid 9627 2024-09-12 11:02:19.796 - info: host.raspberrypi stopInstance timeout system.adapter.zigbee.0 killing pid 10473 2024-09-12 11:02:20.167 - info: host.raspberrypi instance system.adapter.enigma2.0 terminated with code 0 (NO_ERROR) 2024-09-12 11:02:20.169 - info: host.raspberrypi All instances are stopped. 2024-09-12 11:02:20.511 - error: host.raspberrypi Caught by controller[0]: zhc:lixee: Was not able to detect the Linky linky_mode. Default to historique 2024-09-12 11:02:20.512 - error: host.raspberrypi Caught by controller[1]: zhc:lixee: Was not able to detect the Linky energy_phase. Default to single_phase 2024-09-12 11:02:20.513 - error: host.raspberrypi Caught by controller[1]: zhc:lixee: Not able to detect the current tarif. Not filtering any expose... 2024-09-12 11:02:20.514 - warn: host.raspberrypi instance system.adapter.zigbee.0 terminated due to SIGKILL 2024-09-12 11:02:20.514 - info: host.raspberrypi instance system.adapter.zigbee.0 terminated with code null () 2024-09-12 11:02:20.515 - info: host.raspberrypi All instances are stopped. 2024-09-12 11:02:20.622 - info: host.raspberrypi terminated -
@djsirius sagte in Slave iobroker restore Fehler:
Ich habe den iobroker installiert und das Slave-System mit dem Master verbunden. Wird auch erkannt und richtig angezeigt.
Damit wäre doch alles gut gewesen!?
nun versuche ich das Backup auf dem Slave-System einzuspielen und bekomme die Fehlermeldung
Welche Daten möchtest du noch zurückspielen? Die Datenbank liegt auf dem Master und nur dort. Der Slave hat keine eigene Datenbank.
-
@marc-berg Oh......., SORRY! Das wusste ich nicht!
Vielen Dank für die Info!
-
@djsirius sagte in Slave iobroker restore Fehler:
SORRY! Das wusste ich nicht!
Das sollte so sein!
Wenn du den Multihost allerdings nicht korrekt aufgesetzt hast, kann es auch anders sein.So sollten sich vor der Kopplung an den Master auf dem Slave keinerlei Adapter befinden.
Die später dort laufenden Instanzen werden über den admin des Masters installiert.
Dann sind sie auch im Backup des Masters enthalten.
