Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Test Adapter ioBroker.backitup v3.0.x

    NEWS

    • js-controller Lucy (Version 7.0) jetzt im Stable Repository

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    Test Adapter ioBroker.backitup v3.0.x

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

      @Homoran
      Mir ist da eben was aufgefallen.
      Der Ordner backups im IOBroker Verzeichnis wird beim Backup erstellen an gemeckert. Ich habe mir dann das mal angesehen und der ist nicht mehr vorhanden. Also von Hand angelegt und jetzt wirds seltsam, in der Konsole kann ich ihn sehen:

      root@Beelink:/opt/iobroker# ls
backups                       iob            node_modules
CHANGELOG_FIXER_LINUX.md      iobroker       package.json
CHANGELOG_INSTALLER_LINUX.md  iobroker-data  package-lock.json
fix_installation.sh           lib            README.md
install                       LICENSE        reinstall.js

      in FileZilla nicht:
      6dbb4f64-ea60-418e-a8e8-8ef5c73b01cf-grafik.png
      und wenn ich den Fixer laufen lasse, dann kommt auch ne Fehlermeldung genau zu dem Ordner:

      Created /etc/sudoers.d/iobroker
Fixing directory permissions...
chown: Zugriff auf '/opt/iobroker/backups' nicht möglich: Der Rechner ist nicht aktiv
This system does not support setting default permissions.
Do not use npm to manually install adapters unless you know what you are doing!

      Was ist denn da los?

      Die Backups werden aber korrekt angelegt:
      bacefc41-b02a-4233-80e7-847435f28d06-grafik.png

      Log vom Backup:

      Gestartet...
[DEBUG] [mount] - mount activ... umount is started before mount!!
[DEBUG] [mount] - done
[DEBUG] [iobroker] - host.Beelink 6477 states saved

[DEBUG] [iobroker] - host.Beelink 4684 objects saved

[DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2019_12_15-10_46_41_BeeLink_backupiobroker.tar.gz

[DEBUG] [iobroker] - done
[ERROR] [historyDB] - [IGNORED] No source for compress!
[DEBUG] [zigbee] - done
[DEBUG] [cifs] - done
[ERROR] [clean] - Backup files not deleted from /opt/iobroker/backups because some errors.
[DEBUG] [clean] - done
[DEBUG] [history] - backitup.0.history.html
[DEBUG] [umount] - mount activ... umount in 60 Seconds!!
[DEBUG] [umount] - done
[EXIT] 0
      simatec 1 Reply Last reply Reply Quote 0
      • simatec
        simatec Developer Most Active @Jan1 last edited by

        @Jan1
        Ich gehe davon aus, dass dein mount aktiv war.
        Da der mount auf den Ordner backups geht, kann der Fixer da keine Rechte auf dem NAS setzen.
        Schalte mal History Backup aus.
        Du hast keinen Pfad vergeben, somit bekommst du die Fehlermeldung und das Backup läuft nicht sauber durch

        J 1 Reply Last reply Reply Quote 1
        • J
          Jan1 @simatec last edited by

          @simatec
          Bingo, hatte den Haken bei History gesetzt und den Pfad nicht zugewiesen (übersehen). Jetzt läuft das wunderbar:

          Gestartet...
[DEBUG] [mount] - mount activ... umount is started before mount!!
[DEBUG] [mount] - done
[DEBUG] [iobroker] - host.Beelink 6480 states saved

[DEBUG] [iobroker] - host.Beelink 4716 objects saved

[DEBUG] [iobroker] - Backup created: /opt/iobroker/backups/iobroker_2019_12_15-12_33_22_BeeLink_backupiobroker.tar.gz

[DEBUG] [iobroker] - done
[DEBUG] [historyDB] - done
[DEBUG] [zigbee] - done
[DEBUG] [cifs] - done
[DEBUG] [clean] - done
[DEBUG] [history] - backitup.0.history.html
[DEBUG] [umount] - mount activ... umount in 60 Seconds!!
[DEBUG] [umount] - done
[EXIT] 0
          simatec 1 Reply Last reply Reply Quote 0
          • simatec
            simatec Developer Most Active @Jan1 last edited by

            @Jan1
            Sehr gut ... kleiner Tipp noch.
            Wenn du beim manuellen Backup alle Debugmeldungen haben willst, kannst du in den Haupteinstellungen von backitup debug aktivieren und bekommst somit die volle Ausgabe aller Daten

            vauvau07 Glasfaser J 3 Replies Last reply Reply Quote 0
            • vauvau07
              vauvau07 @simatec last edited by

              @simatec
              mit backitup bin ich von Anfang an dabei, einfach Super.
              auf einem Testsystem mit neustem Adapterstand habe ich jetzt auch backitup 1.3.3
              Auch bei mir iobroker rödelt sich zu tode und nichts passiert.
              Das Popup bleibt leer, bzw ich sehe nur Backup gestartet, das war's

              host.iobroker2	2019-12-15 13:16:10.216	error	Caught by controller[0]: at processImmediate (timers.js:658:5)
host.iobroker2	2019-12-15 13:16:10.216	error	Caught by controller[0]: at tryOnImmediate (timers.js:676:5)
host.iobroker2	2019-12-15 13:16:10.216	error	Caught by controller[0]: at runCallback (timers.js:705:18)
host.iobroker2	2019-12-15 13:16:10.216	error	Caught by controller[0]: at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4749:38)
host.iobroker2	2019-12-15 13:16:10.215	error	Caught by controller[0]: at Adapter.emit (events.js:198:13)
host.iobroker2	2019-12-15 13:16:10.215	error	Caught by controller[0]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.backitup/main.js:67:17)
host.iobroker2	2019-12-15 13:16:10.215	error	Caught by controller[0]: at startBackup (/opt/iobroker/node_modules/iobroker.backitup/main.js:44:9)
host.iobroker2	2019-12-15 13:16:10.215	error	Caught by controller[0]: at executeScripts (/opt/iobroker/node_modules/iobroker.backitup/lib/execute.js:176:37)
host.iobroker2	2019-12-15 13:16:10.215	error	Caught by controller[0]: TypeError: Cannot read property 'dropbox' of null
backitup.0	2019-12-15 13:16:09.694	info	(1376) Terminated (NO_ERROR): Without reason
backitup.0	2019-12-15 13:16:09.693	info	(1376) terminating
backitup.0	2019-12-15 13:16:09.188	error	at processImmediate (timers.js:658:5)
backitup.0	2019-12-15 13:16:09.188	error	at tryOnImmediate (timers.js:676:5)
backitup.0	2019-12-15 13:16:09.188	error	at runCallback (timers.js:705:18)
backitup.0	2019-12-15 13:16:09.188	error	at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4749:38)
backitup.0	2019-12-15 13:16:09.188	error	at Adapter.emit (events.js:198:13)
backitup.0	2019-12-15 13:16:09.188	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.backitup/main.js:67:17)
backitup.0	2019-12-15 13:16:09.188	error	at startBackup (/opt/iobroker/node_modules/iobroker.backitup/main.js:44:9)
backitup.0	2019-12-15 13:16:09.188	error	at executeScripts (/opt/iobroker/node_modules/iobroker.backitup/lib/execute.js:176:37)
backitup.0	2019-12-15 13:16:09.188	error	(1376) TypeError: Cannot read property 'dropbox' of null
backitup.0	2019-12-15 13:16:09.188	error	(1376) uncaught exception: Cannot read property 'dropbox' of null
javascript.0	2019-12-15 13:16:00.221	info	(20087) script.js.Klima___Energie.UWZ: [{"object":"{\"center\":\"UWZ\",\"areaID\":\"UWZDE26129\",\"dtgEnd\":1576436400,\"areaType\":\"UWZCODE\",\"dtgStart\":1576393200,\"payload\":{\"translationsLong
backitup.0	2019-12-15 13:15:58.899	debug	(1376) mount activ... umount in 2 Seconds!!
backitup.0	2019-12-15 13:15:48.908	debug	(1376) [iobroker] 10 00 01 */1 * *
backitup.0	2019-12-15 13:15:48.897	info	(1376) [iobroker] backup was activated at 01:00 every 1 day(s)
backitup.0	2019-12-15 13:15:48.865	info	(1376) starting. Version 1.3.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v10.17.0
backitup.0	2019-12-15 13:15:47.971	debug	(1376) States connected to redis: 127.0.0.1:9000
backitup.0	2019-12-15 13:15:47.919	debug	(1376) statesDB connected
backitup.0	2019-12-15 13:15:47.918	debug	(1376) States create PubSub Client
backitup.0	2019-12-15 13:15:47.913	debug	(1376) Objects connected to redis: 127.0.0.1:9001
backitup.0	2019-12-15 13:15:47.911	debug	(1376) Redis States: Use Redis connection: 127.0.0.1:9000
backitup.0	2019-12-15 13:15:47.910	debug	(1376) objectDB connected
backitup.0	2019-12-15 13:15:47.903	debug	(1376) Objects client initialize lua scripts
backitup.0	2019-12-15 13:15:47.903	debug	(1376) Objects create PubSub Client
backitup.0	2019-12-15 13:15:47.901	debug	(1376) Objects client ready ... initialize now
backitup.0	2019-12-15 13:15:47.879	debug	(1376) Redis Objects: Use Redis connection: 127.0.0.1:9001
              simatec 2 Replies Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @simatec last edited by

                @simatec

                Zur Info für dich !!

                Gleicher Fehler wie bei @vauvau07
                auch hier Link Text

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

                  @simatec sagte in Test Adapter Backitup v1.3.x:

                  @Jan1
                  Sehr gut ... kleiner Tipp noch.
                  Wenn du beim manuellen Backup alle Debugmeldungen haben willst, kannst du in den Haupteinstellungen von backitup debug aktivieren und bekommst somit die volle Ausgabe aller Daten

                  Gut zu wissen, aber ich bin heil froh, dass es nur noch so wenig ist und man hier auch schnell sieht, wo es ein Problem gegeben hat. Gefällt mir sehr gut.

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

                    @vauvau07 und @Glasfaser
                    Danke für den Log.
                    Fehler ist bereits gefunden und wird gefixt.

                    Eine Frage aber dazu. Nutzt ihr die Dropbox in backitup oder hattet ihr diese Option noch nie aktiviert?

                    vauvau07 Glasfaser 2 Replies Last reply Reply Quote 0
                    • vauvau07
                      vauvau07 @simatec last edited by

                      @simatec
                      ich hatte Dropbox noch nie aktiviert

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

                        @vauvau07
                        Danke dann kann ich den Fehler besser reproduzieren

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

                          @simatec
                          Ich nutze kein Dropbox und habe auch keine Probleme 😉

                          Ich habe nur den Fehler an dir weiter gegeben bzw. gemeldet von den anderen Usern !!!!!

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

                            @Glasfaser
                            Ahh jetzt sehe ich es.
                            Hast du bei Version 1.3.3 den Error nicht?

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

                              @simatec

                              Nein .. kein Error Meldung oder sonstige Fehler !

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

                                @vauvau07
                                Kannst du bitte mal die Version 1.3.4 vom Github installieren und testen, ob der Fehler behoben ist?
                                Ich kann den Fehler leider nicht nachstellen, habe aber eine Vermutung.

                                Habe das in Version 1.3.4 auf Github gefixt.

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

                                  @simatec
                                  leider für mich das gleiche Ergebnis mit 1.3.4

                                  backitup.0	2019-12-15 16:39:20.461	debug	(10481) mount activ... umount in 2 Seconds!!
backitup.0	2019-12-15 16:39:10.473	debug	(10481) [iobroker] 10 00 01 */1 * *
backitup.0	2019-12-15 16:39:10.461	info	(10481) [iobroker] backup was activated at 01:00 every 1 day(s)
backitup.0	2019-12-15 16:39:10.426	info	(10481) starting. Version 1.3.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v10.17.0
host.iobroker2	2019-12-15 16:39:07.972	info	instance system.adapter.backitup.0 started with pid 10481
javascript.0	2019-12-15 16:39:00.175	info	(20087) script.js.Klima___Energie.UWZ: [{"object":"{\"center\":\"UWZ\",\"areaID\":\"UWZDE26129\",\"dtgEnd\":1576436400,\"areaType\":\"UWZCODE\",\"dtgStart\":1576393200,\"payload\":{\"translationsLong
host.iobroker2	2019-12-15 16:38:37.953	info	Restart adapter system.adapter.backitup.0 because enabled
host.iobroker2	2019-12-15 16:38:37.953	info	instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at processImmediate (timers.js:658:5)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at tryOnImmediate (timers.js:676:5)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at runCallback (timers.js:705:18)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4749:38)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at Adapter.emit (events.js:198:13)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.backitup/main.js:67:17)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at startBackup (/opt/iobroker/node_modules/iobroker.backitup/main.js:44:9)
host.iobroker2	2019-12-15 16:38:37.953	error	Caught by controller[0]: at executeScripts (/opt/iobroker/node_modules/iobroker.backitup/lib/execute.js:176:37)
host.iobroker2	2019-12-15 16:38:37.952	error	Caught by controller[0]: TypeError: Cannot read property 'dropbox' of null
backitup.0	2019-12-15 16:38:37.433	info	(8223) Terminated (NO_ERROR): Without reason
backitup.0	2019-12-15 16:38:37.432	info	(8223) terminating
backitup.0	2019-12-15 16:38:36.927	error	at processImmediate (timers.js:658:5)
backitup.0	2019-12-15 16:38:36.927	error	at tryOnImmediate (timers.js:676:5)
backitup.0	2019-12-15 16:38:36.927	error	at runCallback (timers.js:705:18)
backitup.0	2019-12-15 16:38:36.927	error	at Immediate.setImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4749:38)
backitup.0	2019-12-15 16:38:36.927	error	at Adapter.emit (events.js:198:13)
backitup.0	2019-12-15 16:38:36.927	error	at Adapter.adapter.on (/opt/iobroker/node_modules/iobroker.backitup/main.js:67:17)
backitup.0	2019-12-15 16:38:36.927	error	at startBackup (/opt/iobroker/node_modules/iobroker.backitup/main.js:44:9)
backitup.0	2019-12-15 16:38:36.927	error	at executeScripts (/opt/iobroker/node_modules/iobroker.backitup/lib/execute.js:176:37)
backitup.0	2019-12-15 16:38:36.927	error	(8223) TypeError: Cannot read property 'dropbox' of null
backitup.0	2019-12-15 16:38:36.927	error	(8223) uncaught exception: Cannot read property 'dropbox' of null
javascript.0	2019-12-15 16:38:00.202	info	(20087) script.js.Klima___Energie.UWZ: [{"object":"{\"center\":\"UWZ\",\"areaID\":\"UWZDE26129\",\"dtgEnd\":1576436400,\"areaType\":\"UWZCODE\",\"dtgStart\":1576393200,\"payload\":{\"translationsLong
host.iobroker2	2019-12-15 16:37:59.032	info	iobroker exit 0
host.iobroker2	2019-12-15 16:37:57.896	info	iobroker upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png
host.iobroker2	2019-12-15 16:37:57.841	info	iobroker upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/de/translations.json i18n/de/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.787	info	iobroker upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/en/translations.json i18n/en/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.733	info	iobroker upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/es/translations.json i18n/es/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.678	info	iobroker upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.624	info	iobroker upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/it/translations.json i18n/it/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.571	info	iobroker upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.513	info	iobroker upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.458	info	iobroker upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.403	info	iobroker upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
host.iobroker2	2019-12-15 16:37:57.347	info	iobroker upload [10] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html
host.iobroker2	2019-12-15 16:37:57.292	info	iobroker upload [11] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html
host.iobroker2	2019-12-15 16:37:57.206	info	iobroker upload [12] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript
host.iobroker2	2019-12-15 16:37:56.257	info	iobroker upload backitup
backitup.0	2019-12-15 16:37:37.163	debug	(8223) mount activ... umount in 2 Seconds!!
backitup.0	2019-12-15 16:37:27.175	debug	(8223) [iobroker] 10 00 01 */1 * *
backitup.0	2019-12-15 16:37:27.163	info	(8223) [iobroker] backup was activated at 01:00 every 1 day(s)
backitup.0	2019-12-15 16:37:27.131	info	(8223) starting. Version 1.3.4 in /opt/iobroker/node_modules/iobroker.backitup, node: v10.17.0
backitup.0	2019-12-15 16:37:25.955	debug	(8223) States connected to redis: 127.0.0.1:9000
backitup.0	2019-12-15 16:37:25.901	debug	(8223) statesDB connected
backitup.0	2019-12-15 16:37:25.900	debug	(8223) States create PubSub Client
backitup.0	2019-12-15 16:37:25.886	debug	(8223) Redis States: Use Redis connection: 127.0.0.1:9000
backitup.0	2019-12-15 16:37:25.883	debug	(8223) objectDB connected
backitup.0	2019-12-15 16:37:25.876	debug	(8223) Objects connected to redis: 127.0.0.1:9001
backitup.0	2019-12-15 16:37:25.847	debug	(8223) Objects client initialize lua scripts
backitup.0	2019-12-15 16:37:25.846	debug	(8223) Objects create PubSub Client
backitup.0	2019-12-15 16:37:25.834	debug	(8223) Objects client ready ... initialize now
backitup.0	2019-12-15 16:37:25.703	debug	(8223) Redis Objects: Use Redis connection: 127.0.0.1:9001
                                  simatec 1 Reply Last reply Reply Quote 0
                                  • simatec
                                    simatec Developer Most Active @vauvau07 last edited by

                                    @vauvau07
                                    Mach mal bitte nochmal einen Upload und Neustart des Adapters

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

                                      @simatec
                                      ich habe mir angewöhnt bei jedem Adapter mit neuer Version dies zu machen,
                                      also leider keine Änderung gleiche Fehlermeldung

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

                                        @vauvau07
                                        Ich habe dir mal eine PN geschickt ...

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

                                          @simatec
                                          backitup2.PNG

                                          version 1.3.2 alles i.o.

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

                                            @vauvau07
                                            Diese Funktion gab es in Version 1.3.2 noch nicht ... habe dir nochmal ne PN geschickt.
                                            Jetzt sollte der Fehler gefixt sein

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.7k
                                            Online

                                            30.5k
                                            Users

                                            76.8k
                                            Topics

                                            1.2m
                                            Posts

                                            backitup backitup backup ccu history mysql redis restore restore backup
                                            167
                                            2691
                                            711952
                                            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