Backitup stürzt ab beim wiederherstellen.
-
Hallo ich habe auf einer syno 918+ im Docker den Iobroker installiert.
Habe jetzt einen neuen Container im einem mount auf /opt/iobroker erstellt und den Iobroker neu installiert.
Wollte jetzt ein Backup des alten Containers im neuen einlesen.
Nach dem Download des Backups und starten der Wiederherstellung schmiert der admin ab und erst nach Neustart des Containers ist der IOB über x.x.x.x:8081 wieder erreichbar.Beim iob diag bekomme ich die Meldung das nodejs nicht installiert sein soll.
Könnte mir jemand helfen diesen Fehler zu beheben?
-
@mcbeath sagte in Backitup stürzt ab beim wiederherstellen.:
Könnte mir jemand helfen diesen Fehler zu beheben?
iob diagsagt in der Langfassung?
-
Hier das Log in Langfassung:
======== Start marking the full check here ========= Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : amd64 Docker : v6.1.0 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 22:35:29 up 4:55, 0 users, load average: 2.81, 2.77, 2.53 CPU threads: 4 *** Time and Time Zones *** Thu Nov 16 21:35:29 UTC 2023 Thu Nov 16 22:35:29 CET 2023 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 3.2G 528M 2.5G 4.1G 1.8G Swap: 6.7G 1.7G 5.1G Total: 14G 4.9G 5.6G 7802 M total memory 3192 M used memory 1815 M active memory 1809 M inactive memory 528 M free memory 740 M buffer memory 3341 M swap cache 6727 M total swap 1660 M used swap 5067 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 289G 99G 191G 34% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/vg1/volume_1 ext4 289G 99G 191G 34% /opt/iobroker tmpfs tmpfs 3.9G 0 3.9G 0% /proc/acpi tmpfs tmpfs 3.9G 0 3.9G 0% /proc/scsi tmpfs tmpfs 3.9G 0 3.9G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: [Thu Nov 16 17:41:13 2023] EXT4-fs (md0): barriers disabled [Thu Nov 16 17:41:13 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: [Thu Nov 16 17:41:15 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Thu Nov 16 17:41:17 2023] EXT4-fs (md0): re-mounted. Opts: (null) [Thu Nov 16 17:41:39 2023] EXT4-fs (dm-1): barriers disabled [Thu Nov 16 17:41:39 2023] EXT4-fs (dm-1): 6 orphan inodes deleted [Thu Nov 16 17:41:40 2023] EXT4-fs (dm-1): recovery complete [Thu Nov 16 17:41:40 2023] EXT4-fs (dm-1): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writeback Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=c2ca6b475292e9b,dio,dirperm1 |-/opt/iobroker /dev/vg1/volume_1[/docker/IOBroker/Mount/opt-iobroker] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group |-/opt/userscripts /dev/vg1/volume_1[/docker/IOBroker/Mount/opt-userscripts] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/vg1/volume_1[/@docker/containers/a910e7d23e46f1e40a9bf788d878f2eef09b7a744444e405a5c19d4c6ac0d974/resolv.conf] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/vg1/volume_1[/@docker/containers/a910e7d23e46f1e40a9bf788d878f2eef09b7a744444e405a5c19d4c6ac0d974/hostname] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/vg1/volume_1[/@docker/containers/a910e7d23e46f1e40a9bf788d878f2eef09b7a744444e405a5c19d4c6ac0d974/hosts] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: 34M /var/ 31M /var/lib 18M /var/lib/apt/lists 18M /var/lib/apt 13M /var/lib/dpkg/info /opt/iobroker/backups: 28M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 44M /opt/iobroker/iobroker-data/ 14M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 13M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 29M /opt/iobroker/iobroker-data/objects.jsonl 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 2.8M /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 1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map 944K /opt/iobroker/iobroker-data/states.jsonl 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 *** /home/iobroker/.diag.sh: line 277: nodejs: command not found /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 /home/iobroker/.diag.sh: line 288: nodejs: command not found *** nodejs is NOT correctly installed *** 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 amd64 Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.16 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : buanet-iobroker2 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : buanet-iobroker2 - enabled system.adapter.enocean.0 : enocean : buanet-iobroker2 - disabled system.adapter.viessmann.0 : viessmann : buanet-iobroker2 - disabled, port: 3002 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : buanet-iobroker2 - enabled, port: 8081, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): beta Installed ioBroker-Instances Used repository: beta Adapter "admin" : 6.12.4 , installed 6.12.0 [Updatable] Adapter "backitup" : 2.9.3 , installed 2.8.7 [Updatable] Adapter "enocean" : 0.9.2 , installed 0.9.2 Controller "js-controller": 5.0.16 , installed 5.0.16 Adapter "viessmann" : 1.4.6 , installed 1.4.6 Objects and States Please stand by - This may take a while Objects: 214 States: 113 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 https://deb.nodesource.com/node_18.x bullseye 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 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 1875031 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 1875024 - tcp6 0 0 :::8081 :::* LISTEN 1000 1874340 - *** Log File - Last 25 Lines *** 2023-11-16 22:33:37.275 - info: host.buanet-iobroker2 4 instances found 2023-11-16 22:33:37.288 - info: host.buanet-iobroker2 starting 2 instances 2023-11-16 22:33:37.348 - info: host.buanet-iobroker2 Delete state "system.host.buanet-iobroker2.versions.nodeNewest" 2023-11-16 22:33:37.359 - info: host.buanet-iobroker2 Delete state "system.host.buanet-iobroker2.versions.nodeNewestNext" 2023-11-16 22:33:37.366 - info: host.buanet-iobroker2 Delete state "system.host.buanet-iobroker2.versions.npmCurrent" 2023-11-16 22:33:37.372 - info: host.buanet-iobroker2 Delete state "system.host.buanet-iobroker2.versions.npmNewest" 2023-11-16 22:33:37.380 - info: host.buanet-iobroker2 Delete state "system.host.buanet-iobroker2.versions.npmNewestNext" 2023-11-16 22:33:37.387 - info: host.buanet-iobroker2 Some obsolete host states deleted. 2023-11-16 22:33:37.427 - info: host.buanet-iobroker2 instance system.adapter.admin.0 started with pid 142 2023-11-16 22:33:37.578 - warn: host.buanet-iobroker2 Error while trying to update capabilities after detecting new Node.js version: Command failed: sudo setcap cap_net_bind_service,cap_net_raw+ep i /usr/bin/node Failed to set capabilities on file `/usr/bin/node' (Operation not supported) The value of the capability argument is not permitted for a file. Or the file is not a regular (non-symlink) file 2023-11-16 22:33:41.375 - info: host.buanet-iobroker2 instance system.adapter.backitup.0 started with pid 150 2023-11-16 22:33:43.608 - info: backitup.0 (150) starting. Version 2.8.7 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.17.1, js-controller: 5.0.16 2023-11-16 22:33:44.144 - info: backitup.0 (150) [iobroker] backup will be activated at 02:40 every 1 day(s) 2023-11-16 22:33:45.569 - info: admin.0 (142) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.17.1, js-controller: 5.0.16 2023-11-16 22:33:45.617 - info: admin.0 (142) requesting all objects 2023-11-16 22:33:46.698 - info: admin.0 (142) received all objects 2023-11-16 22:33:47.025 - info: admin.0 (142) Request actual repository... 2023-11-16 22:33:47.048 - info: admin.0 (142) socket.io server listening on port 8081 2023-11-16 22:33:47.051 - info: admin.0 (142) http server listening on port 8081 2023-11-16 22:33:47.052 - info: admin.0 (142) Use link "http://127.0.0.1:8081" to configure. 2023-11-16 22:33:47.754 - info: host.buanet-iobroker2 Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json" 2023-11-16 22:33:51.112 - info: admin.0 (142) Repository received successfully. ============ Mark until here for C&P ============= iob diag has finished. Press any key for a summaryhat etwas gedauert alles aus dem Terminalfenster zu kopieren...
-
-
@thomas-braun
OKAY.... ?!?schau mal nach einem update....
-
Aktuell ist irgendwas mit 9.x
-
@thomas-braun said in Backitup stürzt ab beim wiederherstellen.:
@mcbeath sagte in Backitup stürzt ab beim wiederherstellen.:
Docker : v6.1.0
Steinalt.
Instalierte Version laut Syno: 20.10.3-0554
Vertügbare Verion laut Syno: 20.10.3-0554
-
Keine Ahnung was du da anschaust, aber die Docker-Büchsen finden sich hier:
-
@mcbeath said in Backitup stürzt ab beim wiederherstellen.:
@thomas-braun said in Backitup stürzt ab beim wiederherstellen.:
@mcbeath sagte in Backitup stürzt ab beim wiederherstellen.:
Docker : v6.1.0
Steinalt.
Instalierte Version laut Syno: 20.10.3-0554
Vertügbare Verion laut Syno: 20.10.3-0554Das war die Version von Docker selber, auf der Synology.
du meintest die Version vom iob.
Plattform: docker (official image - v6.1.0) das steht im IOB unter info
-
@mcbeath sagte in Backitup stürzt ab beim wiederherstellen.:
du meintest die Version vom iob.
Nein, ich meine die Version des Docker-Containers/Images (oder wie man es auch nennen mag).
-
@thomas-braun said in Backitup stürzt ab beim wiederherstellen.:
@mcbeath sagte in Backitup stürzt ab beim wiederherstellen.:
du meintest die Version vom iob.
Nein, ich meine die Version des Docker-Containers/Images (oder wie man es auch nennen mag).
Ich habe das über das offizielle Image buanet/iobroker:latest installiert.
Wenn ich das drauf klicke, lande ich auch bei 9.0.1 wie von dir oben angegeben. -
Ich hab mit Docker keinen Vertrag...
Ich weiß nur, dass die aktuelle Ausgabe V9.0.1 lautet, bei dir eine 6.1.0 erkannt wird. Also steinalt. -
@thomas-braun
Ich werf nochmal einen neuen Container an und schaue mal was da rauskommt.... -
Hier mal das lange Log vom neuen Container, ist auch jetzt 9.0.1
======== Start marking the full check here ========= Skript v.2023-10-10 *** BASE SYSTEM *** Hardware Vendor : Synology Kernel : x86_64 Userland : amd64 Docker : v9.0.1 Virtualization : Docker Kernel : x86_64 Userland : amd64 Systemuptime and Load: 23:36:33 up 5:56, 0 user, load average: 2.65, 3.10, 3.22 CPU threads: 4 *** Time and Time Zones *** Thu Nov 16 22:36:33 UTC 2023 Thu Nov 16 23:36:33 CET 2023 CET +0100 Etc/UTC *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: *** MEMORY *** total used free shared buff/cache available Mem: 8.2G 6.1G 407M 2.5G 4.5G 2.1G Swap: 7.1G 1.9G 5.1G Total: 15G 8.0G 5.5G 7802 M total memory 5818 M used memory 1681 M active memory 1766 M inactive memory 388 M free memory 236 M buffer memory 4066 M swap cache 6727 M total swap 1854 M used swap 4873 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on none aufs 289G 101G 188G 35% / tmpfs tmpfs 64M 0 64M 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup shm tmpfs 64M 0 64M 0% /dev/shm /dev/vg1/volume_1 ext4 289G 101G 188G 35% /opt/iobroker tmpfs tmpfs 3.9G 0 3.9G 0% /proc/acpi tmpfs tmpfs 3.9G 0 3.9G 0% /proc/scsi tmpfs tmpfs 3.9G 0 3.9G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: [Thu Nov 16 17:41:13 2023] EXT4-fs (md0): barriers disabled [Thu Nov 16 17:41:13 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: [Thu Nov 16 17:41:15 2023] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: barrier=1 [Thu Nov 16 17:41:17 2023] EXT4-fs (md0): re-mounted. Opts: (null) [Thu Nov 16 17:41:39 2023] EXT4-fs (dm-1): barriers disabled [Thu Nov 16 17:41:39 2023] EXT4-fs (dm-1): 6 orphan inodes deleted [Thu Nov 16 17:41:40 2023] EXT4-fs (dm-1): recovery complete [Thu Nov 16 17:41:40 2023] EXT4-fs (dm-1): mounted filesystem with writeback data mode. Opts: usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl,data=writeback Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / none aufs rw,relatime,si=c2ca6b43b8d3e9b,dio,dirperm1 |-/opt/iobroker /dev/vg1/volume_1[/docker/IOBroker/Mount/opt-iobbroker3] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group |-/etc/resolv.conf /dev/vg1/volume_1[/@docker/containers/069d97e9be89eb084e51c93507ea0f9f256a01f6e9c7c3e1c770a22a9218e9b1/resolv.conf] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group |-/etc/hostname /dev/vg1/volume_1[/@docker/containers/069d97e9be89eb084e51c93507ea0f9f256a01f6e9c7c3e1c770a22a9218e9b1/hostname] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group `-/etc/hosts /dev/vg1/volume_1[/@docker/containers/069d97e9be89eb084e51c93507ea0f9f256a01f6e9c7c3e1c770a22a9218e9b1/hosts] ext4 rw,relatime,synoacl,data=writeback,jqfmt=vfsv0,usrjquot a=aquota.user,grpjquota=aquota.group Files in neuralgic directories: /var: 34M /var/ 32M /var/lib 19M /var/lib/apt/lists 19M /var/lib/apt 13M /var/lib/dpkg /opt/iobroker/backups: 14M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 19M /opt/iobroker/iobroker-data/ 15M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 13M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 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 4.0M /opt/iobroker/iobroker-data/objects.jsonl 2.8M /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 1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map 652K /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.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 amd64 Packages 100 /var/lib/dpkg/status 18.18.1-1nodesource1 500 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.16 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker-iobroker1 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : iobroker-iobroker1 - enabled + system.adapter.discovery.0 : discovery : iobroker-iobroker1 - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker-iobroker1 - enabled, port: 8081, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "backitup" : 2.8.7 , installed 2.8.7 Adapter "discovery" : 4.2.0 , installed 4.2.0 Controller "js-controller": 5.0.16 , installed 5.0.16 Objects and States Please stand by - This may take a while Objects: 146 States: 103 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_18.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 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 2354108 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 2356763 - tcp6 0 0 :::8081 :::* LISTEN 1000 2359355 - *** Log File - Last 25 Lines *** 2023-11-16 23:34:12.041 - info: host.iobroker-iobroker1 Delete state "system.host.iobroker-iobroker1.versions.nodeNewestNext" 2023-11-16 23:34:12.046 - info: host.iobroker-iobroker1 Delete state "system.host.iobroker-iobroker1.versions.npmCurrent" 2023-11-16 23:34:12.052 - info: host.iobroker-iobroker1 Delete state "system.host.iobroker-iobroker1.versions.npmNewest" 2023-11-16 23:34:12.057 - info: host.iobroker-iobroker1 Delete state "system.host.iobroker-iobroker1.versions.npmNewestNext" 2023-11-16 23:34:12.062 - info: host.iobroker-iobroker1 Some obsolete host states deleted. 2023-11-16 23:34:14.273 - info: admin.0 (172) starting. Version 6.12.0 in /opt/iobroker/node_modules/iobroker.admin, node: v18.18.2, js-controller: 5.0.16 2023-11-16 23:34:14.325 - info: admin.0 (172) requesting all objects 2023-11-16 23:34:14.667 - info: admin.0 (172) received all objects 2023-11-16 23:34:14.808 - info: admin.0 (172) Request actual repository... 2023-11-16 23:34:14.843 - info: admin.0 (172) socket.io server listening on port 8081 2023-11-16 23:34:14.847 - info: admin.0 (172) http server listening on port 8081 2023-11-16 23:34:14.848 - info: admin.0 (172) Use link "http://127.0.0.1:8081" to configure. 2023-11-16 23:34:15.106 - info: host.iobroker-iobroker1 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-11-16 23:34:16.179 - info: host.iobroker-iobroker1 instance system.adapter.discovery.0 started with pid 217 2023-11-16 23:34:16.328 - info: admin.0 (172) Repository received successfully. 2023-11-16 23:34:17.984 - info: discovery.0 (217) starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.18.2, js-controller: 5.0.16 2023-11-16 23:34:19.968 - info: host.iobroker-iobroker1 instance system.adapter.backitup.0 started with pid 232 2023-11-16 23:34:21.781 - info: backitup.0 (232) starting. Version 2.8.7 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.18.2, js-controller: 5.0.16 2023-11-16 23:34:21.842 - error: backitup.0 (232) [ERROR] [iobroker] No host object found, your backup seems to be corrupted! 2023-11-16 23:34:21.870 - info: backitup.0 (232) [iobroker] backup will be activated at 02:40 every 1 day(s) 2023-11-16 23:34:55.321 - info: admin.0 (172) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-11-16 23:34:56.551 - info: admin.0 (172) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-11-16 23:35:00.033 - info: admin.0 (172) <== Disconnect system.user.admin from ::ffff:172.17.0.1 2023-11-16 23:35:41.347 - info: admin.0 (172) ==> Connected system.user.admin from ::ffff:172.17.0.1 2023-11-16 23:35:48.112 - info: admin.0 (172) <== Disconnect system.user.admin from ::ffff:172.17.0.1 ============ Mark until here for C&P ============= iob diag has finished. Press any key for a summaryHier sagt er bein Backup, es wäre coruppted
Kann das an der unterschiedlichen js-controller version liegen?
Das backup hat noch die version 4.0.24 der neue Container 5.0.12 -
@mcbeath sagte in Backitup stürzt ab beim wiederherstellen.:
Kann das an der unterschiedlichen js-controller version liegen?
Ja.
-
@thomas-braun
Das hatte ich befürchtet, weil der sich nicht aktualiesieren lassen will laut Anleitung, dachte ich mir das ich einfach auf einen neuen Container per Backup umziehen kann.
Gibt es denn noch einen Weg wie ich zumindes die ganzen Datenpunkte vom alten in den neuen bekomme, ohne alle manuell neu anlegen zu müssen?
edit:
Hab es schon gefunden, in den Objekten über die beiden Pfeile hoch und runter kann man Im- und Exportierne.
Hätte ich auch gleich sehen können, schande über mein Haupt....
