NEWS
Adapter: iobroker.backitup (stable Release)
-
Jo habe das manuell angestossen über die Seite STANDARD und Haken angekreuzt das SQL mitgemacht werden soll.
Auf der Seite von SQL habe ich schon sämtliche Einstellungen ausprobiert inkl unterschiedlich Ports (0, 3306, 3307 und leer). Immer das gleiche Ergebnise :-( Daten sind vom sql.0 Adapter übernommen
-
Hier meine Einstellung
backitup.0 2019-01-05 18:56:41.675 debug [minimal] exec: done backitup.0 2019-01-05 18:56:41.673 debug [minimal/umount] done backitup.0 2019-01-05 18:56:23.162 debug system.adapter.admin.0: logging false backitup.0 2019-01-05 18:56:23.162 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1546710983160,"q":0,"from":"system.adapter.admin.0","lc":1546710983160} backitup.0 2019-01-05 18:56:16.972 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"638246091":"xxxxxxxxx"} backitup.0 2019-01-05 18:56:16.970 debug redis pmessage messagebox.system.adapter.backitup.0 messagebox.system.adapter.backitup.0 {"command":"getTelegramUser","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":1 backitup.0 2019-01-05 18:55:46.977 debug system.adapter.admin.0: logging true backitup.0 2019-01-05 18:55:46.977 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1546710946975,"q":0,"from":"system.adapter.admin.0","lc":1546710946975} backitup.0 2019-01-05 18:55:41.669 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546710941667,"q":0,"from":"system.adapter.backitup.0","lc":1546710941667} backitup.0 2019-01-05 18:55:41.663 debug [minimal] exec: done backitup.0 2019-01-05 18:55:41.661 debug [minimal/redis] done backitup.0 2019-01-05 18:55:41.645 debug [minimal/mysql] MySql File deleted! backitup.0 2019-01-05 18:55:41.616 debug [minimal/umount] wait 60 seconds for umount! backitup.0 2019-01-05 18:55:41.614 debug [minimal/history] done backitup.0 2019-01-05 18:55:41.603 debug [minimal/telegram] done backitup.0 2019-01-05 18:55:41.603 debug sendTo "send" to system.adapter.telegram.0 from system.adapter.backitup.0 backitup.0 2019-01-05 18:55:41.601 debug [minimal/telegram] [minimal] used Telegram-Instance: telegram.0 backitup.0 2019-01-05 18:55:41.597 debug [minimal/clean] done backitup.0 2019-01-05 18:55:41.593 debug [minimal/cifs] done backitup.0 2019-01-05 18:55:41.588 debug [minimal/mysql] done backitup.0 2019-01-05 18:55:41.563 debug [minimal/mysql] done backitup.0 2019-01-05 18:55:41.504 debug [minimal/minimal] done backitup.0 2019-01-05 18:55:41.460 debug [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_01_05-18_55_36_backupiobroker.tar.gz backitup.0 2019-01-05 18:55:36.556 debug [minimal/mount] done backitup.0 2019-01-05 18:55:33.202 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":true,"ack":false,"ts":1546710933201,"q":0,"from":"system.adapter.admin.0","lc":1546710933201} backitup.0 2019-01-05 18:55:29.368 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"638246091":"Schecki_Homematic"} backitup.0 2019-01-05 18:55:29.367 debug redis pmessage messagebox.system.adapter.backitup.0 messagebox.system.adapter.backitup.0 {"command":"getTelegramUser","message":null,"from":"system.adapter.admin.0","callback":{"message":null,"id":1 backitup.0 2019-01-05 18:55:23.853 debug system.adapter.admin.0: logging false backitup.0 2019-01-05 18:55:23.853 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1546710923850,"q":0,"from":"system.adapter.admin.0","lc":1546710923850} -
So, man muss den PFAD eintragen und ich hatte noch zusaetzlich das Programm eingetragen.
Jedenfalls verstehe ich den Text so, wie er da steht - da gehört aber anscheinend nur der Pfad hin.
Nun rödelt er am backup rum !
Frage:
Warum kam keine Meldung im Log ? Kann du das noch einbauen oder nicht erforderlich ?
-
Jo, nach diesen Meldungen ist der Adapter neu gestartet :-( kannst du damit was anfangen ?
backitup.0 2019-01-05 20:06:31.445 debug [minimal] 10 00 01 */5 * * backitup.0 2019-01-05 20:06:31.444 info [minimal] backup was activated at 01:00 every 5 day(s) backitup.0 2019-01-05 20:06:31.402 error Error: spawn sudo umount ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19) at onErrorNT (internal/child_process.js:362:16) at _combinedTickCallback (internal backitup.0 2019-01-05 20:06:31.402 error uncaught exception: spawn sudo umount ENOENT backitup.0 2019-01-05 20:06:31.402 info starting. Version 1.0.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.15.0 backitup.0 2019-01-05 20:05:59.854 error Error: spawn EACCES at ChildProcess.spawn (internal/child_process.js:313:11) at exports.spawn (child_process.js:508:9) at WriteStream.stream.once.fd (/opt/iobroker/node_modules/iobroker.ba backitup.0 2019-01-05 20:05:59.853 error uncaught exception: spawn EACCES backitup.0 2019-01-05 20:05:59.825 debug [minimal/minimal] done backitup.0 2019-01-05 20:05:59.761 debug [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_01_05-20_05_54_backupiobroker.tar.gz backitup.0 2019-01-05 20:05:54.762 debug [minimal/mount] done -
Hallo,
neues Update gemacht, Adapter bleibt Rot Fehlerlog:
backitup.0 2019-01-06 09:18:08.763 info terminating backitup.0 2019-01-06 09:18:08.591 debug system.adapter.admin.0: logging false backitup.0 2019-01-06 09:18:08.251 error at tryOnImmediate (timers.js:768:5) backitup.0 2019-01-06 09:18:08.251 error at runCallback (timers.js:814:20) backitup.0 2019-01-06 09:18:08.251 error at Immediate.createInstancesObjects [as _onImmediate] (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:748:13) backitup.0 2019-01-06 09:18:08.251 error at C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:788:29 backitup.0 2019-01-06 09:18:08.251 error at initAdapter (C:\ioBroker\node_modules\iobroker.js-controller\lib\adapter.js:4990:18) backitup.0 2019-01-06 09:18:08.251 error at Adapter.emit (events.js:208:7) backitup.0 2019-01-06 09:18:08.251 error at emitNone (events.js:106:13) backitup.0 2019-01-06 09:18:08.251 error at Adapter.main (C:\ioBroker\node_modules\iobroker.backitup\main.js:555:5) backitup.0 2019-01-06 09:18:08.251 error at createBashScripts (C:\ioBroker\node_modules\iobroker.backitup\main.js:483:16) backitup.0 2019-01-06 09:18:08.251 error at Object.fs.unlinkSync (fs.js:1061:18) backitup.0 2019-01-06 09:18:08.251 error Error: ENOENT: no such file or directory, unlink 'C:\ioBroker\node_modules\iobroker.backitup\lib\stopIOB.bat' backitup.0 2019-01-06 09:18:08.251 error uncaught exception: ENOENT: no such file or directory, unlink 'C:\ioBroker\node_modules\iobroker.backitup\lib\stopIOB.bat' backitup.0 2019-01-06 09:18:08.251 info starting. Version 1.0.2 in C:/ioBroker/node_modules/iobroker.backitup, node: v8.15.0 backitup.0 2019-01-06 09:18:08.001 debug statesDB connected backitup.0 2019-01-06 09:18:07.986 debug objectDB connected -
Starte am besten dein iob und dein System mal neu.
Laut Log hat sich da irgendwas verabschiedet `
Habe ich alles schon mehrfach gemacht ! Bringt nichts.
Da es sich um mein Prod.-System handelt (ich habe noch kein Testsystem aufgesetzt) nehme ich den SQL jetzt raus und mache das direkt auf meinem NAS per Cronjob. Klappt auf Anhieb und tar-Datei ist 155MB groß.
Daher lasse ich es mal so jetzt. Wenn Testsystem aufgesetzt dann kann ich mal wieder weitertesten, okay ?
-
Bei mir wirft die neue Version leider auch Fehler:
host.orangepiplus2e 2019-01-06 09:40:45.971 info Restart adapter system.adapter.backitup.0 because enabled host.orangepiplus2e 2019-01-06 09:40:45.971 error instance system.adapter.backitup.0 terminated with code 0 (OK) host.orangepiplus2e 2019-01-06 09:40:45.971 error Caught by controller[0]: path: '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' } host.orangepiplus2e 2019-01-06 09:40:45.971 error Caught by controller[0]: syscall: 'unlink', host.orangepiplus2e 2019-01-06 09:40:45.970 error Caught by controller[0]: code: 'ENOENT', host.orangepiplus2e 2019-01-06 09:40:45.970 error Caught by controller[0]: errno: -2, host.orangepiplus2e 2019-01-06 09:40:45.970 error Caught by controller[0]: at tryOnImmediate (timers.js:768:5) host.orangepiplus2e 2019-01-06 09:40:45.970 error Caught by controller[0]: at runCallback (timers.js:814:20) host.orangepiplus2e 2019-01-06 09:40:45.969 error Caught by controller[0]: at Immediate.createInstancesObjects [as _onImmediate] (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:748:13) host.orangepiplus2e 2019-01-06 09:40:45.969 error Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:788:29 host.orangepiplus2e 2019-01-06 09:40:45.969 error Caught by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4990:18) host.orangepiplus2e 2019-01-06 09:40:45.969 error Caught by controller[0]: at Adapter.emit (events.js:208:7) host.orangepiplus2e 2019-01-06 09:40:45.969 error Caught by controller[0]: at emitNone (events.js:106:13) host.orangepiplus2e 2019-01-06 09:40:45.968 error Caught by controller[0]: at Adapter.main (/opt/iobroker/node_modules/iobroker.backitup/main.js:555:5) host.orangepiplus2e 2019-01-06 09:40:45.968 error Caught by controller[0]: at createBashScripts (/opt/iobroker/node_modules/iobroker.backitup/main.js:489:16) host.orangepiplus2e 2019-01-06 09:40:45.968 error Caught by controller[0]: at Object.fs.unlinkSync (fs.js:1061:18) host.orangepiplus2e 2019-01-06 09:40:45.967 error Caught by controller[0]: { Error: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' backitup.0 2019-01-06 09:40:45.448 error Error: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' at Object.fs.unlinkSync (fs.js:1061:18) at createBashScripts (/opt/iobroker/node_ backitup.0 2019-01-06 09:40:45.448 error uncaught exception: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' backitup.0 2019-01-06 09:40:45.447 info starting. Version 1.0.2 in /opt/iobroker/node_modules/iobroker.backitup, node: v8.12.0 -
auch hier sehr viele Fehler im Log und der Adapter geht immer wieder auf rot
host.raspberrypi 2019-01-06 09:58:40.435 error instance system.adapter.backitup.0 terminated with code 0 (OK) Caught 2019-01-06 09:58:40.435 error by controller[0]: path: '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' } Caught 2019-01-06 09:58:40.435 error by controller[0]: syscall: 'unlink', Caught 2019-01-06 09:58:40.435 error by controller[0]: code: 'ENOENT', Caught 2019-01-06 09:58:40.435 error by controller[0]: errno: -2, Caught 2019-01-06 09:58:40.435 error by controller[0]: at tryOnImmediate (timers.js:768:5) Caught 2019-01-06 09:58:40.435 error by controller[0]: at runCallback (timers.js:814:20) Caught 2019-01-06 09:58:40.434 error by controller[0]: at Immediate.createInstancesObjects [as _onImmediate] (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:748:13) Caught 2019-01-06 09:58:40.434 error by controller[0]: at /opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:788:29 Caught 2019-01-06 09:58:40.434 error by controller[0]: at initAdapter (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:4990:18) Caught 2019-01-06 09:58:40.434 error by controller[0]: at Adapter.emit (events.js:208:7) Caught 2019-01-06 09:58:40.434 error by controller[0]: at emitNone (events.js:106:13) Caught 2019-01-06 09:58:40.434 error by controller[0]: at Adapter.main (/opt/iobroker/node_modules/iobroker.backitup/main.js:555:5) Caught 2019-01-06 09:58:40.434 error by controller[0]: at createBashScripts (/opt/iobroker/node_modules/iobroker.backitup/main.js:489:16) Caught 2019-01-06 09:58:40.433 error by controller[0]: at Object.fs.unlinkSync (fs.js:1061:18) Caught 2019-01-06 09:58:40.433 error by controller[0]: { Error: ENOENT: no such file or directory, unlink '/opt/iobroker/node_modules/iobroker.backitup/lib/stopIOB.sh' -
Handelt es sich bei euch um eine Neuinstallation oder ein Update?
Denke da hat sich bei Update ein Fehler eingeschlichen
Gesendet von iPhone mit Tapatalk `
Update…...
817
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge