Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Betatester für Backitup 2.0.0 gesucht

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Betatester für Backitup 2.0.0 gesucht

    This topic has been deleted. Only users with topic management privileges can see it.
    • amg_666
      amg_666 @Homoran last edited by amg_666

      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] 0
      

      Der 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 (???)

      Dr. Bakterius 1 Reply Last reply Reply Quote 0
      • ostseereiter
        ostseereiter last edited by

        @simatec
        habe auch installiert sieht erst mal ganz gut aus mal sehen ob ich was finde.

        1 Reply Last reply Reply Quote 0
        • Dr. Bakterius
          Dr. Bakterius Most Active @amg_666 last edited by

          @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 1 Reply Last reply Reply Quote 0
          • amg_666
            amg_666 @Dr. Bakterius last edited by

            @dr-bakterius siehe mein edit oben. Das ist der Pfad der im Standard vorbelegt war, sollte man natürlich ändern...

            Fenriswolf 1 Reply Last reply Reply Quote 0
            • Fenriswolf
              Fenriswolf @amg_666 last edited by

              @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
              
              
              simatec 1 Reply Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active last edited by crunchip

                habe es auch mal getestet, funktioniert soweit, bis auf folgendes

                [DEBUG] [jarvis] - Jarvis Backup cannot created. Please install a Jarvis version >= 2.2.0
                

                6cf9447f-8de2-4511-9fd6-8b557ce63403-grafik.png

                was mir noch auffällt

                [DEBUG] [iobroker] - host.IoBroker 53511 states saved
                
                [DEBUG] [iobroker] - host.IoBroker 42968 objects saved
                

                68f025ed-6916-4fe8-96c5-182370fa14ca-grafik.png

                simatec 1 Reply Last reply Reply Quote 0
                • simatec
                  simatec Developer Most Active @Fenriswolf last edited by

                  @fenriswolf
                  Bitte poste mal den kompletten debug Log und dein Config

                  Fenriswolf R 2 Replies Last reply Reply Quote 0
                  • simatec
                    simatec Developer Most Active @crunchip last edited by

                    @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 Thomas Braun 2 Replies Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @simatec last edited by

                      @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 sein

                      simatec 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @simatec last edited by Thomas Braun

                        @simatec

                        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
                        
                        simatec 2 Replies Last reply Reply Quote 0
                        • simatec
                          simatec Developer Most Active @Thomas Braun last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • simatec
                            simatec Developer Most Active @Thomas Braun last edited by

                            @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 2 Replies Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @simatec last edited by

                              @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.

                              1 Reply Last reply Reply Quote 0
                              • Fenriswolf
                                Fenriswolf @simatec last edited by

                                @simatec sagte in Betatester für Backitup 2.0.0 gesucht:

                                @fenriswolf
                                Bitte poste mal den kompletten debug Log und dein Config

                                Aber 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
                                
                                ![Bildschirmfoto 2021-02-02 um 06.42.10.png](/assets/uploads/files/1612244831143-bildschirmfoto-2021-02-02-um-06.42.10.png) 
                                

                                Bildschirmfoto 2021-02-02 um 06.42.31.png

                                simatec 1 Reply Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @simatec last edited by

                                  @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 1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active @Fenriswolf last edited by

                                    @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 1 Reply Last reply Reply Quote 0
                                    • Fenriswolf
                                      Fenriswolf @simatec last edited by

                                      @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

                                      system.adapter.backitup.0.json

                                      simatec Fenriswolf 2 Replies Last reply Reply Quote 0
                                      • simatec
                                        simatec Developer Most Active @Thomas Braun last edited by simatec

                                        @thomas-braun

                                        Konnte auf meinen Testsystemen auch keine Auffälligkeiten feststellen.

                                        2021-02-02 07:53:10.266 - debug: backitup.0 (11148) Backup has started ...
                                        2021-02-02 07:53:10.271 - silly: backitup.0 (11148) States user redis pmessage io.backitup.0.oneClick.*/io.backitup.0.oneClick.iobroker:{"val":true,"ack":true,"ts":1612248790268,"q":0,"from":"system.adapter.backitup.0","user":"system.user.admin","lc":1612248790268}
                                        2021-02-02 07:53:20.360 - debug: backitup.0 (11148) [iobroker/mount] mount successfully completed
                                        2021-02-02 07:53:20.364 - debug: backitup.0 (11148) [iobroker/mount] done
                                        2021-02-02 07:53:22.159 - debug: backitup.0 (11148) [iobroker/iobroker] host.iobroker-dev 1628 states saved
                                        2021-02-02 07:53:22.187 - debug: backitup.0 (11148) [iobroker/iobroker] host.iobroker-dev 2019 objects saved
                                        2021-02-02 07:53:24.567 - debug: backitup.0 (11148) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2021_02_02-07_53_20_dev_backupiobroker.tar.gz
                                        2021-02-02 07:53:28.491 - debug: backitup.0 (11148) [iobroker/iobroker] done
                                        2021-02-02 07:53:29.095 - debug: backitup.0 (11148) [iobroker/redis] Start Redis Backup ...
                                        2021-02-02 07:53:42.294 - debug: backitup.0 (11148) [iobroker/redis] Packed 35MB so far...
                                        2021-02-02 07:53:51.363 - debug: backitup.0 (11148) [iobroker/redis] Packed 60MB so far...
                                        2021-02-02 07:53:58.532 - debug: backitup.0 (11148) [iobroker/redis] done
                                        2021-02-02 07:53:58.843 - debug: backitup.0 (11148) [iobroker/zigbee] found zigbee database: zigbee.0,zigbee.1
                                        2021-02-02 07:53:58.844 - debug: backitup.0 (11148) [iobroker/zigbee] done
                                        2021-02-02 07:53:58.997 - debug: backitup.0 (11148) [iobroker/grafana] Start Grafana Backup ...
                                        2021-02-02 07:54:01.549 - debug: backitup.0 (11148) [iobroker/grafana] Created grafana_tmp directory
                                        2021-02-02 07:54:01.571 - debug: backitup.0 (11148) [iobroker/grafana] Created dashboard directory
                                        2021-02-02 07:54:01.594 - debug: backitup.0 (11148) [iobroker/grafana] Created dashboards_manually_restore directory
                                        2021-02-02 07:54:01.616 - debug: backitup.0 (11148) [iobroker/grafana] Created datasource directory
                                        2021-02-02 07:54:01.618 - debug: backitup.0 (11148) [iobroker/grafana] start Grafana request ...
                                        2021-02-02 07:54:01.675 - debug: backitup.0 (11148) [iobroker/grafana] Grafana is available ... Status: 200
                                        2021-02-02 07:54:02.461 - debug: backitup.0 (11148) [iobroker/grafana] found Dashboard: conronastatistik
                                        2021-02-02 07:54:02.468 - debug: backitup.0 (11148) [iobroker/grafana] found Dashboard: wetterbedingungen
                                        2021-02-02 07:54:02.475 - debug: backitup.0 (11148) [iobroker/grafana] found Dashboard: gestorben
                                        2021-02-02 07:54:02.477 - debug: backitup.0 (11148) [iobroker/grafana] start Grafana backup compress ...
                                        2021-02-02 07:54:02.665 - debug: backitup.0 (11148) [iobroker/grafana] Backup created: /opt/iobroker/backups/grafana_2021_02_02-07_54_02_backupiobroker.tar.gz
                                        2021-02-02 07:54:02.666 - debug: backitup.0 (11148) [iobroker/grafana] Try deleting the Grafana tmp directory: "/opt/iobroker/backups/grafana_tmp"
                                        2021-02-02 07:54:02.825 - debug: backitup.0 (11148) [iobroker/grafana] Grafana tmp directory "/opt/iobroker/backups/grafana_tmp" successfully deleted
                                        2021-02-02 07:54:02.827 - debug: backitup.0 (11148) [iobroker/grafana] done
                                        2021-02-02 07:54:02.980 - debug: backitup.0 (11148) [iobroker/jarvis] found Jarvis Instance: 0
                                        2021-02-02 07:54:02.981 - debug: backitup.0 (11148) [iobroker/jarvis] start Jarvis Backup for Instance 0...
                                        2021-02-02 07:54:02.983 - debug: backitup.0 (11148) [iobroker/jarvis] found Jarvis Instance: 1
                                        2021-02-02 07:54:02.984 - debug: backitup.0 (11148) [iobroker/jarvis] start Jarvis Backup for Instance 1...
                                        2021-02-02 07:54:03.012 - debug: backitup.0 (11148) [iobroker/jarvis] Backup created: /opt/iobroker/backups/jarvis.1_2021_02_02-07_54_02_backupiobroker.tar.gz
                                        2021-02-02 07:54:03.013 - debug: backitup.0 (11148) [iobroker/jarvis] done
                                        2021-02-02 07:54:03.022 - debug: backitup.0 (11148) [iobroker/jarvis] Backup created: /opt/iobroker/backups/jarvis.0_2021_02_02-07_54_02_backupiobroker.tar.gz
                                        2021-02-02 07:54:03.370 - debug: backitup.0 (11148) [iobroker/javascripts] done
                                        2021-02-02 07:54:03.674 - debug: backitup.0 (11148) [iobroker/cifs] done
                                        2021-02-02 07:54:04.134 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy iobroker_2021_02_02-07_53_20_dev_backupiobroker.tar.gz...
                                        2021-02-02 07:54:23.922 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy redis_2021_02_02-07_53_29_backupiobroker.tar.gz...
                                        2021-02-02 08:00:55.893 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy zigbee.0_2021_02_02-07_53_58_backupiobroker.tar.gz...
                                        2021-02-02 08:00:58.562 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy zigbee.1_2021_02_02-07_53_58_backupiobroker.tar.gz...
                                        2021-02-02 08:01:02.062 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy grafana_2021_02_02-07_54_02_backupiobroker.tar.gz...
                                        2021-02-02 08:01:04.738 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy jarvis.0_2021_02_02-07_54_02_backupiobroker.tar.gz...
                                        2021-02-02 08:01:07.211 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy jarvis.1_2021_02_02-07_54_02_backupiobroker.tar.gz...
                                        2021-02-02 08:01:09.619 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: Copy javascripts_2021_02_02-07_54_03_backupiobroker.tar.gz...
                                        2021-02-02 08:01:14.733 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: delete iobroker_2020_12_07-16_09_20_dev_backupiobroker.tar.gz
                                        2021-02-02 08:01:15.598 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: delete redis_2020_12_07-16_09_25_backupiobroker.tar.gz
                                        2021-02-02 08:01:16.267 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: delete zigbee.0_2020_09_28-12_46_25_backupiobroker.tar.gz
                                        2021-02-02 08:01:16.955 - debug: backitup.0 (11148) [iobroker/googledrive] Google Drive: delete zigbee.1_2020_09_28-12_46_25_backupiobroker.tar.gz
                                        2021-02-02 08:01:17.669 - debug: backitup.0 (11148) [iobroker/googledrive] done
                                        2021-02-02 08:01:17.838 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/iobroker_2021_01_31-17_03_20_dev_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.267 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/redis_2021_01_31-17_03_29_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.324 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/zigbee.0_2021_01_31-17_03_59_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.356 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/zigbee.1_2021_01_31-17_03_59_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.390 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/grafana_2021_01_31-17_04_02_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.423 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/jarvis.1_2021_01_31-17_04_03_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.456 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/jarvis.0_2021_01_31-17_04_03_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.491 - debug: backitup.0 (11148) [iobroker/clean] delete /opt/iobroker/backups/javascripts_2021_01_31-17_04_04_backupiobroker.tar.gz
                                        2021-02-02 08:01:21.517 - debug: backitup.0 (11148) [iobroker/clean] done
                                        2021-02-02 08:01:21.679 - debug: backitup.0 (11148) [iobroker/email] done
                                        2021-02-02 08:01:22.289 - debug: backitup.0 (11148) [iobroker/historyHTML] new history html values created
                                        2021-02-02 08:01:22.291 - debug: backitup.0 (11148) [iobroker/historyHTML] done
                                        2021-02-02 08:01:22.452 - debug: backitup.0 (11148) [iobroker/historyJSON] new history json values created
                                        2021-02-02 08:01:22.453 - debug: backitup.0 (11148) [iobroker/historyJSON] done
                                        2021-02-02 08:01:22.632 - debug: backitup.0 (11148) [iobroker/umount] mount activ... umount in 60 Seconds!!
                                        2021-02-02 08:02:22.761 - debug: backitup.0 (11148) [iobroker/umount] umount successfully completed
                                        2021-02-02 08:02:22.764 - debug: backitup.0 (11148) [iobroker/umount] done
                                        2021-02-02 08:02:22.916 - debug: backitup.0 (11148) [iobroker] exec: done
                                        
                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • simatec
                                          simatec Developer Most Active @Fenriswolf last edited by

                                          @fenriswolf
                                          Die Antwort liegt hier
                                          Die interne IP Adresse ist nicht zertifiziert.
                                          Konnte das auch auf meinem Testsystem nachstellen.

                                          backitup.0	2021-02-02 08:23:47.157	error	at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:687:12)
                                          backitup.0	2021-02-02 08:23:47.157	error	at TLSSocket._finishInit (_tls_wrap.js:917:8)
                                          backitup.0	2021-02-02 08:23:47.157	error	at TLSSocket.emit (events.js:310:20)
                                          backitup.0	2021-02-02 08:23:47.157	error	at TLSSocket.onConnectSecure (_tls_wrap.js:1484:27)
                                          backitup.0	2021-02-02 08:23:47.157	error	at Object.checkServerIdentity (tls.js:288:12)
                                          backitup.0	2021-02-02 08:23:47.157	error	(11312) Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: IP: 192.168.123.43 is not in the cert's list:
                                          backitup.0	2021-02-02 08:23:47.156	error	(11312) unhandled promise rejection: Hostname/IP does not match certificate's altnames: IP: 192.168.123.43 is not in the cert's list:
                                          Unhandled	2021-02-02 08:23:47.155	error	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().
                                          

                                          Hier muss ein eindeutiger Hostname verwendet werden, dem du auch über Lets Entcrypt in deiner Nextcloud dementsprechend zulässt.

                                          Den fehlerlog werde ich in der nächsten beta noch etwas besser abfangen, aber dein Problem selbst kann ich nicht beheben.
                                          Nimm keine interne IP für den Zugriff auf deine Nextcloud. Selbst Chrome, Firefox und Co meckern da

                                          1 Reply Last reply Reply Quote 0
                                          • Agria4800
                                            Agria4800 @Homoran last edited by

                                            @homoran sagte in Betatester für Backitup 2.0.0 gesucht:

                                            @agria4800 sagte in Betatester für Backitup 2.0.0 gesucht:

                                            Ich weiß, ist nicht zwingend notwendig, aber statt des ganzen System nur speziell die Vis Projekte zu sichern fände ich super

                                            Wie meinst du das?
                                            in dem "normalen" iobroker backup sind auch bereits die Vis-Projekte in den jeweiligen vis-views.json enthalten.
                                            Und ich würde mich nicht wundern, wenn das dort die größten Dateien sind.

                                            Du kannst das Backup mit einem entzipper öffnen und die Projekte rauskopieren.

                                            Was wäre deine Wunsch-Option?

                                            Ja, wäre nur eine Wunschoption!

                                            Gerade für Leute mit wenig Erfahrung in Vis wäre es hilfreich, schnell und unkompliziert ihr Projekt wieder herstellen zu können.
                                            Ich selbst habe keine Probleme und handhabe das so wie von dir beschrieben...
                                            Toll fände ich auch die Möglichkeit zu haben, bei einem Backup nur ausgewählte Projekte mit zu sichern und nicht immer alle.. ich habe ca 20 In meiner Sammlung, die ich zwar ab und an brauche, aber nicht immer aktuell halten muss und somit auch nicht mit sichern müsste...
                                            Vielleicht ist es ja kein großer Aufwand das in den Backitup Adapter zu integrieren

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            839
                                            Online

                                            31.8k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            32
                                            293
                                            31965
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo