NEWS
Betatester für Backitup 2.0.0 gesucht
-
@lobomau sagte in Betatester für Backitup 2.0.0 gesucht:
Andererseits war das auch nicht schlecht den Adapter nur auf dem slave laufen zu lasten, um den host zu entlasten.
Aber auf dem slave ist bei korrekter Multihost Konfiguration ja nichts.
Die gesamte Administartion befindet sich auf dem Master@homoran ok. Aber für mein Verständnis ein Beispiel: der Pi3-slave bekommt eine neue SD mit frischem ioBroker drauf. Dann
a) eigenes backup: müsste er dann nicht auch gleich die richtige slave-Einstellung mitbekommen und fertig?
b) der host macht die Backups. Nun ist der neue frische Pi3-slave aber noch gar nicht auf slave Betrieb eingestellt!? Klar, kann ich dann auch machen... aber ist dann auch ein Schritt extra, den ich machen muss und wo ich vielleicht was falsch machen kann? Bei a) müsste doch alles klappen?Host: NUC8i3 mit Proxmox:
- ioBroker CT Debian 13, npm 10.9.3, nodejs 22.20.0
- Slave: Pi4
-
@lobomau sagte in Betatester für Backitup 2.0.0 gesucht:
Andererseits war das auch nicht schlecht den Adapter nur auf dem slave laufen zu lasten, um den host zu entlasten.
Aber auf dem slave ist bei korrekter Multihost Konfiguration ja nichts.
Die gesamte Administartion befindet sich auf dem Master@homoran sagte in Betatester für Backitup 2.0.0 gesucht:
@lobomau sagte in Betatester für Backitup 2.0.0 gesucht:
Andererseits war das auch nicht schlecht den Adapter nur auf dem slave laufen zu lasten, um den host zu entlasten.
Aber auf dem slave ist bei korrekter Multihost Konfiguration ja nichts.
Die gesamte Administartion befindet sich auf dem MasterGar nichts? Die Adapter werden doch auf den jeweiligen Geräten installiert... jedensfalls sieht es im log danach aus. Und wozu habe ich ein slave, wenn da nichts drauf laufen würde?
-
@homoran ok. Aber für mein Verständnis ein Beispiel: der Pi3-slave bekommt eine neue SD mit frischem ioBroker drauf. Dann
a) eigenes backup: müsste er dann nicht auch gleich die richtige slave-Einstellung mitbekommen und fertig?
b) der host macht die Backups. Nun ist der neue frische Pi3-slave aber noch gar nicht auf slave Betrieb eingestellt!? Klar, kann ich dann auch machen... aber ist dann auch ein Schritt extra, den ich machen muss und wo ich vielleicht was falsch machen kann? Bei a) müsste doch alles klappen?@lobomau sagte in Betatester für Backitup 2.0.0 gesucht:
eigenes backup: müsste er dann nicht auch gleich die richtige slave-Einstellung mitbekommen und fertig?
ich weiß gar nicht, was passiert wenn die Instanz auf dem slave installiert ist.
in der iobroker setup custom wird ja alles auf den Master umgeleitet
Da müsste @simatec was zu sagen.kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@lobomau sagte in Betatester für Backitup 2.0.0 gesucht:
eigenes backup: müsste er dann nicht auch gleich die richtige slave-Einstellung mitbekommen und fertig?
ich weiß gar nicht, was passiert wenn die Instanz auf dem slave installiert ist.
in der iobroker setup custom wird ja alles auf den Master umgeleitet
Da müsste @simatec was zu sagen.Edit: aaaargh, das ist der Defaultpfad im neuen Reiter javascript backup, hätt ich auch gleich merken können.
Also neues Fazit: Adapter 2.0.0 läuft soweit bei mir.Hallo,
kurze Frage: Ich hab den Adpater installiert (System 3*Raspi3b) und habe im backitup Adapter jetzt noch angeklickt, dass er Javascript mit sichern soll (neben homematic ccu, und zigbee). Gesichert wird auf einen FTP Server.
Sicherung ergibt:
Started iobroker ... [DEBUG] [iobroker] - host.iomaster 14107 states saved [DEBUG] [iobroker] - host.iomaster 15880 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-18_19_27_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [zigbee] - found zigbee database: zigbee.0 [DEBUG] [zigbee] - done [DEBUG] [javascripts] - javascript directory "/media/usb/scripts" not found [DEBUG] [javascripts] - done [DEBUG] [ftp] - FTP connected. [DEBUG] [ftp] - Send iobroker_2021_02_01-18_19_27_backupiobroker.tar.gz [DEBUG] [ftp] - Send zigbee.0_2021_02_01-18_20_15_backupiobroker.tar.gz [DEBUG] [ftp] - Send javascripts_2021_02_01-18_20_15_backupiobroker.tar.gz [ERROR] [ftp] - File "/opt/iobroker/backups/javascripts_2021_02_01-18_20_15_backupiobroker.tar.gz" not found [DEBUG] [ftp] - done [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [EXIT] 0Der Fehler in Zeile 14 "...backupiobroker... not found" tritt auch bei der alten Version des backitup bei mir sporadisch auf, da bin ich noch dran.
Aber woher kommt die Meldung in Zeile 8 /media/usb/scripts not found? Ich sichere doch nichts auf USB (???)iobroker auf proxmox container
-
@simatec
habe auch installiert sieht erst mal ganz gut aus mal sehen ob ich was finde. -
Edit: aaaargh, das ist der Defaultpfad im neuen Reiter javascript backup, hätt ich auch gleich merken können.
Also neues Fazit: Adapter 2.0.0 läuft soweit bei mir.Hallo,
kurze Frage: Ich hab den Adpater installiert (System 3*Raspi3b) und habe im backitup Adapter jetzt noch angeklickt, dass er Javascript mit sichern soll (neben homematic ccu, und zigbee). Gesichert wird auf einen FTP Server.
Sicherung ergibt:
Started iobroker ... [DEBUG] [iobroker] - host.iomaster 14107 states saved [DEBUG] [iobroker] - host.iomaster 15880 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-18_19_27_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [zigbee] - found zigbee database: zigbee.0 [DEBUG] [zigbee] - done [DEBUG] [javascripts] - javascript directory "/media/usb/scripts" not found [DEBUG] [javascripts] - done [DEBUG] [ftp] - FTP connected. [DEBUG] [ftp] - Send iobroker_2021_02_01-18_19_27_backupiobroker.tar.gz [DEBUG] [ftp] - Send zigbee.0_2021_02_01-18_20_15_backupiobroker.tar.gz [DEBUG] [ftp] - Send javascripts_2021_02_01-18_20_15_backupiobroker.tar.gz [ERROR] [ftp] - File "/opt/iobroker/backups/javascripts_2021_02_01-18_20_15_backupiobroker.tar.gz" not found [DEBUG] [ftp] - done [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [EXIT] 0Der Fehler in Zeile 14 "...backupiobroker... not found" tritt auch bei der alten Version des backitup bei mir sporadisch auf, da bin ich noch dran.
Aber woher kommt die Meldung in Zeile 8 /media/usb/scripts not found? Ich sichere doch nichts auf USB (???)@amg_666 sagte in Betatester für Backitup 2.0.0 gesucht:
Aber woher kommt die Meldung in Zeile 8 /media/usb/scripts not found?
Sieht nach einem mount-Pfad aus.
-
@amg_666 sagte in Betatester für Backitup 2.0.0 gesucht:
Aber woher kommt die Meldung in Zeile 8 /media/usb/scripts not found?
Sieht nach einem mount-Pfad aus.
-
@dr-bakterius siehe mein edit oben. Das ist der Pfad der im Standard vorbelegt war, sollte man natürlich ändern...
@simatec
Habe auch deinen neuen Adapter direkt mal installiert und probiert. Bekomme aber noch Fehler im Logbuch.
So wie es aussieht, scheint es vom WebDav zu kommen. Wollte auf einen seperaten Raspi bei mir sichern auf dem Nextcloud läuft.backitup.0 2021-02-01 19:55:19.148 debug (4282) mount successfully completed backitup.0 2021-02-01 19:55:19.133 warn (4282) Terminated (UNCAUGHT_EXCEPTION): Without reason backitup.0 2021-02-01 19:55:19.132 debug (4282) Plugin sentry destroyed backitup.0 2021-02-01 19:55:19.131 info (4282) terminating backitup.0 2021-02-01 19:55:19.130 info (4282) cleaned everything up... backitup.0 2021-02-01 19:55:19.102 error (4282) Exception-Code: DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate backitup.0 2021-02-01 19:55:19.101 error (4282) Error: self signed certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at TLSS backitup.0 2021-02-01 19:55:19.101 error (4282) unhandled promise rejection: self signed certificate backitup.0 2021-02-01 19:55:19.100 error (4282) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). backitup.0 2021-02-01 19:55:18.820 info (4282) [ccu] backup was activated at 01:30 every 2 day(s) backitup.0 2021-02-01 19:55:18.807 info (4282) [iobroker] backup was activated at 02:00 every 1 day(s) backitup.0 2021-02-01 19:55:18.730 info (4282) starting. Version 2.0.0-beta.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.20.1, js-controller: 3.2.12Press any key to continue or any other to quit
-
habe es auch mal getestet, funktioniert soweit, bis auf folgendes
[DEBUG] [jarvis] - Jarvis Backup cannot created. Please install a Jarvis version >= 2.2.0
was mir noch auffällt
[DEBUG] [iobroker] - host.IoBroker 53511 states saved [DEBUG] [iobroker] - host.IoBroker 42968 objects saved
umgestiegen von Proxmox auf Unraid
-
@simatec
Habe auch deinen neuen Adapter direkt mal installiert und probiert. Bekomme aber noch Fehler im Logbuch.
So wie es aussieht, scheint es vom WebDav zu kommen. Wollte auf einen seperaten Raspi bei mir sichern auf dem Nextcloud läuft.backitup.0 2021-02-01 19:55:19.148 debug (4282) mount successfully completed backitup.0 2021-02-01 19:55:19.133 warn (4282) Terminated (UNCAUGHT_EXCEPTION): Without reason backitup.0 2021-02-01 19:55:19.132 debug (4282) Plugin sentry destroyed backitup.0 2021-02-01 19:55:19.131 info (4282) terminating backitup.0 2021-02-01 19:55:19.130 info (4282) cleaned everything up... backitup.0 2021-02-01 19:55:19.102 error (4282) Exception-Code: DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate backitup.0 2021-02-01 19:55:19.101 error (4282) Error: self signed certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at TLSS backitup.0 2021-02-01 19:55:19.101 error (4282) unhandled promise rejection: self signed certificate backitup.0 2021-02-01 19:55:19.100 error (4282) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). backitup.0 2021-02-01 19:55:18.820 info (4282) [ccu] backup was activated at 01:30 every 2 day(s) backitup.0 2021-02-01 19:55:18.807 info (4282) [iobroker] backup was activated at 02:00 every 1 day(s) backitup.0 2021-02-01 19:55:18.730 info (4282) starting. Version 2.0.0-beta.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.20.1, js-controller: 3.2.12@fenriswolf
Bitte poste mal den kompletten debug Log und dein Config -
habe es auch mal getestet, funktioniert soweit, bis auf folgendes
[DEBUG] [jarvis] - Jarvis Backup cannot created. Please install a Jarvis version >= 2.2.0was mir noch auffällt
[DEBUG] [iobroker] - host.IoBroker 53511 states saved [DEBUG] [iobroker] - host.IoBroker 42968 objects saved@crunchip
Jarvis muss in Version >= 2.2.0 installiert sein.
Also die aktuelle Beta nehmen.
Grund hierfür ist, dass jarvis und backitup sich ab Version 2.2.0 auf diese Backupstruktur geeinigt haben.Die States passen so. Es sind auch Systeminterne States dabei. Eventuell mal Experten Einstellungen im Objektbaum aktivieren, dann sollten die Zahl passen
-
@crunchip
Jarvis muss in Version >= 2.2.0 installiert sein.
Also die aktuelle Beta nehmen.
Grund hierfür ist, dass jarvis und backitup sich ab Version 2.2.0 auf diese Backupstruktur geeinigt haben.Die States passen so. Es sind auch Systeminterne States dabei. Eventuell mal Experten Einstellungen im Objektbaum aktivieren, dann sollten die Zahl passen
@simatec
ok, >=v2.2.0 ist ja installiert gewesen, war nur nicht die aktuelle beta, daher etwas irreführend
Experten Modus ändert nichts an Zahlen, dann wird wohl der Rest Systeminterne States seinumgestiegen von Proxmox auf Unraid
-
@crunchip
Jarvis muss in Version >= 2.2.0 installiert sein.
Also die aktuelle Beta nehmen.
Grund hierfür ist, dass jarvis und backitup sich ab Version 2.2.0 auf diese Backupstruktur geeinigt haben.Die States passen so. Es sind auch Systeminterne States dabei. Eventuell mal Experten Einstellungen im Objektbaum aktivieren, dann sollten die Zahl passen
Hab jetzt auch mal installiert.
Started iobroker ... [DEBUG] [mount] - first mount attempt with smb option failed. try next mount attempt without smb option ... [ERROR] [mount] - [undefined Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.42/FRITZ.NAS/iobroker_backups /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) [ERROR] [mount] - [IGNORED] Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.42/FRITZ.NAS/iobroker_backups /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) [DEBUG] [iobroker] - host.raspberrypi 3667 states saved [DEBUG] [iobroker] - host.raspberrypi 4442 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [redis] - Start Redis Backup ... [DEBUG] [redis] - done [DEBUG] [cifs] - done [DEBUG] [googledrive] - Google Drive: Copy iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz'Mit den gleichen Einstellungen hat das in 1.8.5 immer wunderbar funktioniert.
In dmesg finde ich auf auf einmal viele Einträge dazu. Die ersten paar Zeilen waren das nächtliche automatisierte Backup in den letzten Nächten:
[ 69.266841] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [ 1082.685761] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [23613.674561] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [110015.201171] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [196416.931959] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [282818.708390] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355129.727389] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/iobroker_backups [355139.776479] CIFS VFS: Error connecting to socket. Aborting operation. [355139.776499] CIFS VFS: cifs_mount failed w/return code = -2 [355139.851154] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/iobroker_backups [355139.851264] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [355149.936718] CIFS VFS: Error connecting to socket. Aborting operation. [355149.936740] CIFS VFS: cifs_mount failed w/return code = -2 [355262.162504] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355320.577457] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355332.600034] CIFS VFS: bogus file nlink value 0 [355332.605856] CIFS VFS: bogus file nlink value 0 [355333.114350] CIFS VFS: bogus file nlink value 0 [355333.127420] CIFS VFS: bogus file nlink value 0 [355663.236274] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355663.395131] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355663.395215] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [355909.277648] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355923.282396] CIFS VFS: bogus file nlink value 0 [355923.290974] CIFS VFS: bogus file nlink value 0 [355923.820181] CIFS VFS: bogus file nlink value 0 [355923.833061] CIFS VFS: bogus file nlink value 0 [356150.682616] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356150.778504] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356150.778566] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356253.906657] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356254.004691] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356254.004751] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356505.859671] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356505.956918] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356505.956997] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356518.314935] CIFS VFS: bogus file nlink value 0 [356518.320970] CIFS VFS: bogus file nlink value 0 [356518.894873] CIFS VFS: bogus file nlink value 0 [356518.912211] CIFS VFS: bogus file nlink value 0[Edit:] Backup auf das NAS/FritzBox funktioniert nun, allerdings wird das Backup nicht nach Google Drive geschoben.
Schaut so aus:
Started iobroker ... [DEBUG] [mount] - mount successfully completed [DEBUG] [mount] - done [DEBUG] [iobroker] - host.raspberrypi 3667 states saved [DEBUG] [iobroker] - host.raspberrypi 4442 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [redis] - Start Redis Backup ... [DEBUG] [redis] - done [DEBUG] [cifs] - done [DEBUG] [googledrive] - Google Drive: Copy iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz' [ERROR] [googledrive] - Google Drive: Error: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 408 (Request Timeout)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>408.</b> <ins>That’s an error.</ins> <p>Your client has taken too long to issue its request. <ins>That’s all we know.</ins> [DEBUG] [googledrive] - Google Drive: Copy redis_2021_02_01-23_02_05_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/redis_2021_02_01-23_02_05_backupiobroker.tar.gz' [ERROR] [googledrive] - Google Drive: Error: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 408 (Request Timeout)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>408.</b> <ins>That’s an error.</ins> <p>Your client has taken too long to issue its request. <ins>That’s all we know.</ins> [DEBUG] [googledrive] - done [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [DEBUG] [umount] - mount activ... umount in 60 Seconds!! [DEBUG] [umount] - umount successfully completed [DEBUG] [umount] - done -
Hab jetzt auch mal installiert.
Started iobroker ... [DEBUG] [mount] - first mount attempt with smb option failed. try next mount attempt without smb option ... [ERROR] [mount] - [undefined Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.42/FRITZ.NAS/iobroker_backups /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) [ERROR] [mount] - [IGNORED] Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.42/FRITZ.NAS/iobroker_backups /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) [DEBUG] [iobroker] - host.raspberrypi 3667 states saved [DEBUG] [iobroker] - host.raspberrypi 4442 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [redis] - Start Redis Backup ... [DEBUG] [redis] - done [DEBUG] [cifs] - done [DEBUG] [googledrive] - Google Drive: Copy iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz'Mit den gleichen Einstellungen hat das in 1.8.5 immer wunderbar funktioniert.
In dmesg finde ich auf auf einmal viele Einträge dazu. Die ersten paar Zeilen waren das nächtliche automatisierte Backup in den letzten Nächten:
[ 69.266841] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [ 1082.685761] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [23613.674561] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [110015.201171] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [196416.931959] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [282818.708390] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355129.727389] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/iobroker_backups [355139.776479] CIFS VFS: Error connecting to socket. Aborting operation. [355139.776499] CIFS VFS: cifs_mount failed w/return code = -2 [355139.851154] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/iobroker_backups [355139.851264] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [355149.936718] CIFS VFS: Error connecting to socket. Aborting operation. [355149.936740] CIFS VFS: cifs_mount failed w/return code = -2 [355262.162504] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355320.577457] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355332.600034] CIFS VFS: bogus file nlink value 0 [355332.605856] CIFS VFS: bogus file nlink value 0 [355333.114350] CIFS VFS: bogus file nlink value 0 [355333.127420] CIFS VFS: bogus file nlink value 0 [355663.236274] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355663.395131] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355663.395215] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [355909.277648] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355923.282396] CIFS VFS: bogus file nlink value 0 [355923.290974] CIFS VFS: bogus file nlink value 0 [355923.820181] CIFS VFS: bogus file nlink value 0 [355923.833061] CIFS VFS: bogus file nlink value 0 [356150.682616] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356150.778504] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356150.778566] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356253.906657] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356254.004691] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356254.004751] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356505.859671] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356505.956918] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356505.956997] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356518.314935] CIFS VFS: bogus file nlink value 0 [356518.320970] CIFS VFS: bogus file nlink value 0 [356518.894873] CIFS VFS: bogus file nlink value 0 [356518.912211] CIFS VFS: bogus file nlink value 0[Edit:] Backup auf das NAS/FritzBox funktioniert nun, allerdings wird das Backup nicht nach Google Drive geschoben.
Schaut so aus:
Started iobroker ... [DEBUG] [mount] - mount successfully completed [DEBUG] [mount] - done [DEBUG] [iobroker] - host.raspberrypi 3667 states saved [DEBUG] [iobroker] - host.raspberrypi 4442 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [redis] - Start Redis Backup ... [DEBUG] [redis] - done [DEBUG] [cifs] - done [DEBUG] [googledrive] - Google Drive: Copy iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz' [ERROR] [googledrive] - Google Drive: Error: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 408 (Request Timeout)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>408.</b> <ins>That’s an error.</ins> <p>Your client has taken too long to issue its request. <ins>That’s all we know.</ins> [DEBUG] [googledrive] - Google Drive: Copy redis_2021_02_01-23_02_05_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/redis_2021_02_01-23_02_05_backupiobroker.tar.gz' [ERROR] [googledrive] - Google Drive: Error: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 408 (Request Timeout)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>408.</b> <ins>That’s an error.</ins> <p>Your client has taken too long to issue its request. <ins>That’s all we know.</ins> [DEBUG] [googledrive] - done [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [DEBUG] [umount] - mount activ... umount in 60 Seconds!! [DEBUG] [umount] - umount successfully completed [DEBUG] [umount] - done@thomas-braun
Das muss ich mir morgen mal in Ruhe anschauen und testen. Bis auf die aktuelle dependencies hat sich an Google Drive seit der Version 1.8.5 nix geändert. -
Hab jetzt auch mal installiert.
Started iobroker ... [DEBUG] [mount] - first mount attempt with smb option failed. try next mount attempt without smb option ... [ERROR] [mount] - [undefined Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.42/FRITZ.NAS/iobroker_backups /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) [ERROR] [mount] - [IGNORED] Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,rw,file_mode=0777,dir_mode=0777 //192.168.0.42/FRITZ.NAS/iobroker_backups /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) [DEBUG] [iobroker] - host.raspberrypi 3667 states saved [DEBUG] [iobroker] - host.raspberrypi 4442 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [redis] - Start Redis Backup ... [DEBUG] [redis] - done [DEBUG] [cifs] - done [DEBUG] [googledrive] - Google Drive: Copy iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/iobroker_2021_02_01-22_50_26_backupiobroker.tar.gz'Mit den gleichen Einstellungen hat das in 1.8.5 immer wunderbar funktioniert.
In dmesg finde ich auf auf einmal viele Einträge dazu. Die ersten paar Zeilen waren das nächtliche automatisierte Backup in den letzten Nächten:
[ 69.266841] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [ 1082.685761] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [23613.674561] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [110015.201171] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [196416.931959] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [282818.708390] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355129.727389] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/iobroker_backups [355139.776479] CIFS VFS: Error connecting to socket. Aborting operation. [355139.776499] CIFS VFS: cifs_mount failed w/return code = -2 [355139.851154] CIFS: Attempting to mount //192.168.178.1/FRITZ.NAS/iobroker_backups [355139.851264] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [355149.936718] CIFS VFS: Error connecting to socket. Aborting operation. [355149.936740] CIFS VFS: cifs_mount failed w/return code = -2 [355262.162504] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355320.577457] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355332.600034] CIFS VFS: bogus file nlink value 0 [355332.605856] CIFS VFS: bogus file nlink value 0 [355333.114350] CIFS VFS: bogus file nlink value 0 [355333.127420] CIFS VFS: bogus file nlink value 0 [355663.236274] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355663.395131] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355663.395215] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [355909.277648] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [355923.282396] CIFS VFS: bogus file nlink value 0 [355923.290974] CIFS VFS: bogus file nlink value 0 [355923.820181] CIFS VFS: bogus file nlink value 0 [355923.833061] CIFS VFS: bogus file nlink value 0 [356150.682616] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356150.778504] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356150.778566] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356253.906657] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356254.004691] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356254.004751] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356505.859671] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356505.956918] CIFS: Attempting to mount //192.168.0.42/FRITZ.NAS/iobroker_backups [356505.956997] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [356518.314935] CIFS VFS: bogus file nlink value 0 [356518.320970] CIFS VFS: bogus file nlink value 0 [356518.894873] CIFS VFS: bogus file nlink value 0 [356518.912211] CIFS VFS: bogus file nlink value 0[Edit:] Backup auf das NAS/FritzBox funktioniert nun, allerdings wird das Backup nicht nach Google Drive geschoben.
Schaut so aus:
Started iobroker ... [DEBUG] [mount] - mount successfully completed [DEBUG] [mount] - done [DEBUG] [iobroker] - host.raspberrypi 3667 states saved [DEBUG] [iobroker] - host.raspberrypi 4442 objects saved [DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz [DEBUG] [iobroker] - done [DEBUG] [redis] - Start Redis Backup ... [DEBUG] [redis] - done [DEBUG] [cifs] - done [DEBUG] [googledrive] - Google Drive: Copy iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/iobroker_2021_02_01-23_01_54_backupiobroker.tar.gz' [ERROR] [googledrive] - Google Drive: Error: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 408 (Request Timeout)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>408.</b> <ins>That’s an error.</ins> <p>Your client has taken too long to issue its request. <ins>That’s all we know.</ins> [DEBUG] [googledrive] - Google Drive: Copy redis_2021_02_01-23_02_05_backupiobroker.tar.gz... [ERROR] [googledrive] - Google Drive: Error: Unknown system error -116: Unknown system error -116, open '/opt/iobroker/backups/redis_2021_02_01-23_02_05_backupiobroker.tar.gz' [ERROR] [googledrive] - Google Drive: Error: <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 408 (Request Timeout)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>408.</b> <ins>That’s an error.</ins> <p>Your client has taken too long to issue its request. <ins>That’s all we know.</ins> [DEBUG] [googledrive] - done [DEBUG] [clean] - done [DEBUG] [historyHTML] - new history html values created [DEBUG] [historyHTML] - done [DEBUG] [historyJSON] - new history json values created [DEBUG] [historyJSON] - done [DEBUG] [umount] - mount activ... umount in 60 Seconds!! [DEBUG] [umount] - umount successfully completed [DEBUG] [umount] - done@thomas-braun
Kannst du dein NAS nochmal bitte nach den Rechten checken. So wie ich den Log deute, kann für den Upload auf GoogleDrive nicht auf die BackupFiles zugegriffen werden.Ist aktuell nur ne Vermutung und ich werde das morgen mal nachstellen
-
@thomas-braun
Kannst du dein NAS nochmal bitte nach den Rechten checken. So wie ich den Log deute, kann für den Upload auf GoogleDrive nicht auf die BackupFiles zugegriffen werden.Ist aktuell nur ne Vermutung und ich werde das morgen mal nachstellen
@simatec
Ich hatte jetzt auch wie besprochen aus zwei Instanzen eine gemacht.
Neu ist jetzt, dass zuerst Freigabe aus der Fritzbox gemountet wird, das Backup angelegt wird und dann auch ins Google Drive geschoben werden soll.
Bislang waren das ja einzelne Vorgänge in eigenen Instanzen.
Ich wüsste jetzt auch gar nicht wie ich dem Google Drive Rechte auf dem FritzNAS einrichten könnte. Oder andersrum. -
@fenriswolf
Bitte poste mal den kompletten debug Log und dein Config@simatec sagte in Betatester für Backitup 2.0.0 gesucht:
@fenriswolf
Bitte poste mal den kompletten debug Log und dein ConfigAber gerne doch ....
backitup.0 2021-02-02 06:45:28.244 warn (9308) Terminated (UNCAUGHT_EXCEPTION): Without reason backitup.0 2021-02-02 06:45:28.244 debug (9308) Plugin sentry destroyed backitup.0 2021-02-02 06:45:28.243 info (9308) terminating backitup.0 2021-02-02 06:45:28.242 info (9308) cleaned everything up... backitup.0 2021-02-02 06:45:28.193 error (9308) Exception-Code: DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate backitup.0 2021-02-02 06:45:28.193 error (9308) Error: self signed certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at TLSS backitup.0 2021-02-02 06:45:28.190 error (9308) unhandled promise rejection: self signed certificate backitup.0 2021-02-02 06:45:28.189 error (9308) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). backitup.0 2021-02-02 06:45:28.126 debug (9308) first mount attempt with smb option failed. try next mount attempt without smb option ... backitup.0 2021-02-02 06:45:27.841 debug (9308) [ccu] 10 30 01 */2 * * backitup.0 2021-02-02 06:45:27.837 info (9308) [ccu] backup was activated at 01:30 every 2 day(s) backitup.0 2021-02-02 06:45:27.836 debug (9308) [iobroker] 10 00 02 */1 * * backitup.0 2021-02-02 06:45:27.821 info (9308) [iobroker] backup was activated at 02:00 every 1 day(s) backitup.0 2021-02-02 06:45:27.739 info (9308) starting. Version 2.0.0-beta.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.20.1, js-controller: 3.2.12 backitup.0 2021-02-02 06:45:27.490 debug (9308) Plugin sentry Initialize Plugin (enabled=true) backitup.0 2021-02-02 06:44:52.856 warn (8256) Terminated (UNCAUGHT_EXCEPTION): Without reason backitup.0 2021-02-02 06:44:52.856 debug (8256) Plugin sentry destroyed backitup.0 2021-02-02 06:44:52.855 info (8256) terminating backitup.0 2021-02-02 06:44:52.854 info (8256) cleaned everything up... backitup.0 2021-02-02 06:44:52.827 error (8256) Exception-Code: DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate backitup.0 2021-02-02 06:44:52.826 error (8256) Error: self signed certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at TLSS backitup.0 2021-02-02 06:44:52.826 error (8256) unhandled promise rejection: self signed certificate backitup.0 2021-02-02 06:44:52.825 error (8256) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). backitup.0 2021-02-02 06:44:52.752 debug (8256) mount successfully completed backitup.0 2021-02-02 06:44:52.426 debug (8256) [ccu] 10 30 01 */2 * * backitup.0 2021-02-02 06:44:52.421 info (8256) [ccu] backup was activated at 01:30 every 2 day(s) backitup.0 2021-02-02 06:44:52.420 debug (8256) [iobroker] 10 00 02 */1 * * backitup.0 2021-02-02 06:44:52.407 info (8256) [iobroker] backup was activated at 02:00 every 1 day(s) backitup.0 2021-02-02 06:44:52.329 info (8256) starting. Version 2.0.0-beta.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.20.1, js-controller: 3.2.12 
Press any key to continue or any other to quit
-
@thomas-braun
Kannst du dein NAS nochmal bitte nach den Rechten checken. So wie ich den Log deute, kann für den Upload auf GoogleDrive nicht auf die BackupFiles zugegriffen werden.Ist aktuell nur ne Vermutung und ich werde das morgen mal nachstellen
@simatec sagte in Betatester für Backitup 2.0.0 gesucht:
Ist aktuell nur ne Vermutung und ich werde das morgen mal nachstellen
Hat sich wohl erledigt. Das automatische Nacht-Backup ist durchgelaufen. War wohl irgendwie Schluckauf bei Google Drive.
-
@simatec sagte in Betatester für Backitup 2.0.0 gesucht:
@fenriswolf
Bitte poste mal den kompletten debug Log und dein ConfigAber gerne doch ....
backitup.0 2021-02-02 06:45:28.244 warn (9308) Terminated (UNCAUGHT_EXCEPTION): Without reason backitup.0 2021-02-02 06:45:28.244 debug (9308) Plugin sentry destroyed backitup.0 2021-02-02 06:45:28.243 info (9308) terminating backitup.0 2021-02-02 06:45:28.242 info (9308) cleaned everything up... backitup.0 2021-02-02 06:45:28.193 error (9308) Exception-Code: DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate backitup.0 2021-02-02 06:45:28.193 error (9308) Error: self signed certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at TLSS backitup.0 2021-02-02 06:45:28.190 error (9308) unhandled promise rejection: self signed certificate backitup.0 2021-02-02 06:45:28.189 error (9308) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). backitup.0 2021-02-02 06:45:28.126 debug (9308) first mount attempt with smb option failed. try next mount attempt without smb option ... backitup.0 2021-02-02 06:45:27.841 debug (9308) [ccu] 10 30 01 */2 * * backitup.0 2021-02-02 06:45:27.837 info (9308) [ccu] backup was activated at 01:30 every 2 day(s) backitup.0 2021-02-02 06:45:27.836 debug (9308) [iobroker] 10 00 02 */1 * * backitup.0 2021-02-02 06:45:27.821 info (9308) [iobroker] backup was activated at 02:00 every 1 day(s) backitup.0 2021-02-02 06:45:27.739 info (9308) starting. Version 2.0.0-beta.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.20.1, js-controller: 3.2.12 backitup.0 2021-02-02 06:45:27.490 debug (9308) Plugin sentry Initialize Plugin (enabled=true) backitup.0 2021-02-02 06:44:52.856 warn (8256) Terminated (UNCAUGHT_EXCEPTION): Without reason backitup.0 2021-02-02 06:44:52.856 debug (8256) Plugin sentry destroyed backitup.0 2021-02-02 06:44:52.855 info (8256) terminating backitup.0 2021-02-02 06:44:52.854 info (8256) cleaned everything up... backitup.0 2021-02-02 06:44:52.827 error (8256) Exception-Code: DEPTH_ZERO_SELF_SIGNED_CERT: self signed certificate backitup.0 2021-02-02 06:44:52.826 error (8256) Error: self signed certificate at TLSSocket.onConnectSecure (_tls_wrap.js:1502:34) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at TLSS backitup.0 2021-02-02 06:44:52.826 error (8256) unhandled promise rejection: self signed certificate backitup.0 2021-02-02 06:44:52.825 error (8256) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). backitup.0 2021-02-02 06:44:52.752 debug (8256) mount successfully completed backitup.0 2021-02-02 06:44:52.426 debug (8256) [ccu] 10 30 01 */2 * * backitup.0 2021-02-02 06:44:52.421 info (8256) [ccu] backup was activated at 01:30 every 2 day(s) backitup.0 2021-02-02 06:44:52.420 debug (8256) [iobroker] 10 00 02 */1 * * backitup.0 2021-02-02 06:44:52.407 info (8256) [iobroker] backup was activated at 02:00 every 1 day(s) backitup.0 2021-02-02 06:44:52.329 info (8256) starting. Version 2.0.0-beta.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.20.1, js-controller: 3.2.12 @fenriswolf
Dein Screenshot reicht leider nicht. Dort sehe ich nur die Haupteinstellungen. Lade mir mal über die Pfeiltasten deine Config runter und poste sie hier. Passwörter und Keys natürlich dann mit ein paar Sternchen versehen ... ;-) -
@fenriswolf
Dein Screenshot reicht leider nicht. Dort sehe ich nur die Haupteinstellungen. Lade mir mal über die Pfeiltasten deine Config runter und poste sie hier. Passwörter und Keys natürlich dann mit ein paar Sternchen versehen ... ;-)@simatec sagte in Betatester für Backitup 2.0.0 gesucht:
@fenriswolf
Dein Screenshot reicht leider nicht. Dort sehe ich nur die Haupteinstellungen. Lade mir mal über die Pfeiltasten deine Config runter und poste sie hier. Passwörter und Keys natürlich dann mit ein paar Sternchen versehen ... ;-)gerne
Press any key to continue or any other to quit
Support us
652
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge