NEWS
2 Fehler beim Backitup Restore
-
@crunchip sagte in 2 Fehler beim Backitup Restore:
er braucht doch nur die Backupdateien ansehen
stimmt auffallend
-
-
pi@iobroker:~ $ file /opt/iobroker/backups /opt/iobroker/backups: directory pi@iobroker:~ $
ist jetzt im alten iobroker
im Container das gleiche
-
Nein, zur der Datei, nicht zum Verzeichnis.
-
@thomas-braun im alten iobroker oder Container?
-
@thomas-braun
das ist im alten iobrokerpi@iobroker:/opt/iobroker/backups $ file /opt/iobroker/backups/iobroker_2023_04_09-18_09_27_backupiobroker.tar.gz /opt/iobroker/backups/iobroker_2023_04_09-18_09_27_backupiobroker.tar.gz: gzip compressed data, from Unix, original size 77511680
-
Da wird die Datei offenbar korrekt erkannt.
-
@thomas-braun
ja, sieht mal im alten gut aus.Frage, wie lange wird das Restore so ca. gehen?
Sollte da im Statusfenster schnell was kommen? -
@cbrocker sagte in 2 Fehler beim Backitup Restore:
Frage, wie lange wird das Restore so ca. gehen?
Hängt davon ab...
Von wenigen Minuten bis einer Stunde und mehr ist da alles drin. -
ich habe schon paar minuten gewartet, dann kam ein Adapterfenster
mit Error { }Aber jetzt steht da noch:
-
@cbrocker sagte in 2 Fehler beim Backitup Restore:
ich habe schon paar minuten gewartet, dann kam ein Adapterfenster
Dann schau in das LogFile rein:
iob logs --watch | uniq
-
habe gerade im Proxmox LXC iobroker restore über onedrive gemacht.
ABer kommt im Protokoll:
backitup.0 2023-04-09 20:45:15.043 error Onedrive list error: TypeError: oneDriveAPI.items.download(...).pipe is not a function
-
root@iobroker-prox:/opt/iobroker/backups# iob logs --watch | uniq 2023-04-09 18:37:55.170 - info: admin.0 (302) ==> Connected system.user.admin from ::ffff:192.168.178.88 2023-04-09 18:37:56.864 - info: host.iobroker-prox Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-04-09 18:38:15.385 - info: admin.0 (302) <== Disconnect system.user.admin from ::ffff:192.168.178.88 2023-04-09 18:38:21.217 - info: admin.0 (302) ==> Connected system.user.admin from ::ffff:192.168.178.88 2023-04-09 18:38:22.982 - info: host.iobroker-prox Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-04-09 18:40:15.464 - info: admin.0 (302) <== Disconnect system.user.admin from ::ffff:192.168.178.88 2023-04-09 18:40:15.465 - info: admin.0 (302) <== Disconnect system.user.admin from ::ffff:192.168.178.88 admin 2023-04-09 18:40:15.616 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:10:49.167 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:10:49.228 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:13:05.570 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:13:05.631 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:13:12.480 - info: admin.0 (302) ==> Connected system.user.admin from ::ffff:192.168.178.88 2023-04-09 20:13:17.417 - info: admin.0 (302) <== Disconnect system.user.admin from ::ffff:192.168.178.88 admin 2023-04-09 20:13:17.542 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:13:58.328 - info: admin.0 (302) terminating http server on port 8081 2023-04-09 20:13:58.330 - info: backitup.0 (344) cleaned everything up... 2023-04-09 20:13:58.331 - info: info.0 (359) cleaned everything up... 2023-04-09 20:13:58.332 - info: host.iobroker-prox received SIGTERM 2023-04-09 20:13:58.333 - info: host.iobroker-prox stopInstance system.adapter.admin.0 (force=false, process=true) 2023-04-09 20:13:58.334 - info: host.iobroker-prox stopInstance system.adapter.discovery.0 (force=false, process=true) 2023-04-09 20:13:58.334 - info: host.iobroker-prox stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-04-09 20:13:58.334 - info: host.iobroker-prox stopInstance system.adapter.info.0 (force=false, process=true) 2023-04-09 20:13:58.338 - info: admin.0 (302) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-04-09 20:13:58.338 - info: discovery.0 (329) Got terminate signal TERMINATE_YOURSELF 2023-04-09 20:13:58.338 - info: admin.0 (302) Got terminate signal TERMINATE_YOURSELF 2023-04-09 20:13:58.339 - info: backitup.0 (344) Got terminate signal TERMINATE_YOURSELF 2023-04-09 20:13:58.339 - info: info.0 (359) Got terminate signal TERMINATE_YOURSELF 2023-04-09 20:13:58.340 - info: discovery.0 (329) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-04-09 20:13:58.341 - info: info.0 (359) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-04-09 20:13:58.341 - info: backitup.0 (344) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-04-09 20:13:58.342 - info: host.iobroker-prox stopInstance system.adapter.admin.0 send kill signal 2023-04-09 20:13:58.342 - info: host.iobroker-prox stopInstance system.adapter.discovery.0 send kill signal 2023-04-09 20:13:58.342 - info: host.iobroker-prox stopInstance system.adapter.backitup.0 send kill signal 2023-04-09 20:13:58.342 - info: host.iobroker-prox stopInstance system.adapter.info.0 send kill signal 2023-04-09 20:13:58.874 - info: host.iobroker-prox instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-04-09 20:13:58.882 - info: host.iobroker-prox instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-04-09 20:13:58.882 - info: host.iobroker-prox instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-04-09 20:13:58.882 - info: host.iobroker-prox instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-04-09 20:13:58.882 - info: host.iobroker-prox All instances are stopped. 2023-04-09 20:13:58.954 - info: host.iobroker-prox terminated 2023-04-09 20:34:55.974 - info: host.iobroker-prox iobroker.js-controller version 4.0.24 js-controller starting 2023-04-09 20:34:55.976 - info: host.iobroker-prox Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-04-09 20:34:55.976 - info: host.iobroker-prox hostname: iobroker-prox, node: v18.15.0 2023-04-09 20:34:55.977 - info: host.iobroker-prox ip addresses: 192.168.178.226 fe80::308f:c3ff:feb5:d78e 2023-04-09 20:34:56.289 - info: host.iobroker-prox connected to Objects and States 2023-04-09 20:34:56.296 - info: host.iobroker-prox added notifications configuration of host 2023-04-09 20:34:56.493 - info: host.iobroker-prox Delete state "system.host.iobroker-prox.versions.nodeCurrent" 2023-04-09 20:34:56.495 - info: host.iobroker-prox 4 instances found 2023-04-09 20:34:56.502 - info: host.iobroker-prox starting 4 instances 2023-04-09 20:34:56.516 - info: host.iobroker-prox Delete state "system.host.iobroker-prox.versions.nodeNewest" 2023-04-09 20:34:56.524 - info: host.iobroker-prox Delete state "system.host.iobroker-prox.versions.nodeNewestNext" 2023-04-09 20:34:56.541 - info: host.iobroker-prox instance system.adapter.admin.0 started with pid 302 2023-04-09 20:34:56.543 - info: host.iobroker-prox Delete state "system.host.iobroker-prox.versions.npmCurrent" 2023-04-09 20:34:56.546 - info: host.iobroker-prox Delete state "system.host.iobroker-prox.versions.npmNewest" 2023-04-09 20:34:56.590 - info: host.iobroker-prox Delete state "system.host.iobroker-prox.versions.npmNewestNext" 2023-04-09 20:34:56.592 - info: host.iobroker-prox Some obsolete host states deleted. 2023-04-09 20:34:57.059 - info: admin.0 (302) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.15.0, js-controller: 4.0.24 2023-04-09 20:34:57.073 - info: admin.0 (302) requesting all states 2023-04-09 20:34:57.073 - info: admin.0 (302) requesting all objects 2023-04-09 20:34:57.210 - info: admin.0 (302) received all objects 2023-04-09 20:34:57.291 - info: admin.0 (302) Request actual repository... 2023-04-09 20:34:57.338 - info: admin.0 (302) http server listening on port 8081 2023-04-09 20:34:57.339 - info: admin.0 (302) Use link "http://localhost:8081" to configure. 2023-04-09 20:34:57.342 - info: admin.0 (302) socket.io server listening on port 8081 2023-04-09 20:34:57.395 - info: host.iobroker-prox Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-04-09 20:34:58.214 - info: admin.0 (302) Repository received successfully. 2023-04-09 20:35:00.517 - info: host.iobroker-prox instance system.adapter.discovery.0 started with pid 329 2023-04-09 20:35:00.952 - info: discovery.0 (329) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.15.0, js-controller: 4.0.24 2023-04-09 20:35:04.517 - info: host.iobroker-prox instance system.adapter.backitup.0 started with pid 344 2023-04-09 20:35:04.986 - info: backitup.0 (344) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0.24 2023-04-09 20:35:05.020 - info: backitup.0 (344) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-04-09 20:35:08.516 - info: host.iobroker-prox instance system.adapter.info.0 started with pid 359 2023-04-09 20:35:09.397 - info: info.0 (359) starting. Version 1.9.19 in /opt/iobroker/node_modules/iobroker.info, node: v18.15.0, js-controller: 4.0.24 2023-04-09 20:35:09.449 - info: info.0 (359) Reading/updating systemdata. 2023-04-09 20:35:09.809 - info: info.0 (359) cpu Temp res = {"main":41,"cores":[36,35,40,39],"max":41,"socket":[],"chipset":null} 2023-04-09 20:44:51.447 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:44:51.541 - info: admin.0 (302) failed connection to socket.io from ::ffff:192.168.178.88: Passport was not initialized 2023-04-09 20:44:58.825 - info: admin.0 (302) ==> Connected system.user.admin from ::ffff:192.168.178.88 2023-04-09 20:45:02.760 - info: admin.0 (302) ==> Connected system.user.admin from ::ffff:192.168.178.88 2023-04-09 20:45:15.043 - error: backitup.0 (344) Onedrive list error: TypeError: oneDriveAPI.items.download(...).pipe is not a function 2023-04-09 20:51:24.209 - info: admin.0 (302) <== Disconnect system.user.admin from ::ffff:192.168.178.88
-
-
@cbrocker sagte in 2 Fehler beim Backitup Restore:
@thomas-braun
das ist im alten iobrokerpi@iobroker:/opt/iobroker/backups $ file /opt/iobroker/backups/iobroker_2023_04_09-18_09_27_backupiobroker.tar.gz /opt/iobroker/backups/iobroker_2023_04_09-18_09_27_backupiobroker.tar.gz: gzip original size 77511680compressed data, from Unix,
original size 77511680
Zeige mal im Pi :
ls -lAh /opt/iobroker/backups
-
sorry, ich komme aus der Windows Welt, da braucht man für jeden Pups Adminrechte.
Was kann ein normaler User mehr als der root?
Ich habe 30 Jahre Windows-Erfahrung, aber erst 1 Jahr Linux-Erfahrung
-
@cbrocker sagte in 2 Fehler beim Backitup Restore:
Was kann ein normaler User mehr als der root?
Der kann sich nicht (so leicht) das System komplett zerbomben.
-
pi@iobroker:~ $ ls -lAh /opt/iobroker/backups total 69M drwxr-xr-x 2 root root 0 Apr 9 16:43 alt -rwxr-xr-x 1 root root 9.0K Apr 9 16:52 grafana_2023_04_09-16_52_04_backupiobroker.tar.gz -rwxr-xr-x 1 root root 9.0K Apr 9 18:10 grafana_2023_04_09-18_10_38_backupiobroker.tar.gz -rwxr-xr-x 1 root root 21M Apr 9 16:52 influxDB_2023_04_09-16_51_46_backupiobroker.tar.gz -rwxr-xr-x 1 root root 21M Apr 9 18:10 influxDB_2023_04_09-18_09_55_backupiobroker.tar.gz -rwxr-xr-x 1 root root 14M Apr 9 16:51 iobroker_2023_04_09-16_51_21_backupiobroker.tar.gz -rwxr-xr-x 1 root root 14M Apr 9 18:09 iobroker_2023_04_09-18_09_27_backupiobroker.tar.gz -rwxr-xr-x 1 root root 18K Apr 9 16:52 javascripts_2023_04_09-16_52_10_backupiobroker.tar.gz -rwxr-xr-x 1 root root 18K Apr 9 18:10 javascripts_2023_04_09-18_10_44_backupiobroker.tar.gz -rwxr-xr-x 1 root root 19K Apr 9 16:52 nodered.0_2023_04_09-16_52_10_backupiobroker.tar.gz -rwxr-xr-x 1 root root 19K Apr 9 18:10 nodered.0_2023_04_09-18_10_44_backupiobroker.tar.gz
-
@cbrocker was ist denn da jetzt so schwer ?
adduser <user> usermod -aG sudo <user>
ausloggen und über Terminal mit dem USER einloggen.
Dann musst halt viele Befehle mit sudo ausführen - was auch gut so ist !
edit: setzt natürlich voraus dass du vorher
apt install sudo
ausgeführt hast
-