Adapter: iobroker.backitup (stable Release)
-
so hier erstmal das Log; sind auf jedenfall error drin:
2019-01-05 08:43:15.732 - [34mdebug[39m: backitup.0 [minimal/mount] done 2019-01-05 08:43:21.901 - [34mdebug[39m: backitup.0 [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_01_05-08_43_15_backupiobroker.tar.gz 2019-01-05 08:43:21.970 - [34mdebug[39m: backitup.0 [minimal/minimal] done 2019-01-05 08:43:21.996 - [34mdebug[39m: backitup.0 [minimal/mysql] [IGNORED] Error: spawn mysqldump ENOENT 2019-01-05 08:43:22.013 - [34mdebug[39m: backitup.0 [minimal/mysql] done 2019-01-05 08:43:22.036 - [34mdebug[39m: backitup.0 [minimal/cifs] done 2019-01-05 08:43:22.051 - [34mdebug[39m: backitup.0 [minimal/clean] Backup files not deleted from /opt/iobroker/backups because some errors. 2019-01-05 08:43:22.051 - [34mdebug[39m: backitup.0 [minimal/clean] done 2019-01-05 08:43:22.057 - [34mdebug[39m: backitup.0 [minimal/mysql] done 2019-01-05 08:43:22.064 - [34mdebug[39m: backitup.0 [minimal/telegram] [minimal] used Telegram-Instance: telegram.0 2019-01-05 08:43:22.067 - [34mdebug[39m: backitup.0 sendTo "send" to system.adapter.telegram.0 from system.adapter.backitup.0 2019-01-05 08:43:22.067 - [34mdebug[39m: backitup.0 [minimal/telegram] done 2019-01-05 08:43:22.072 - [34mdebug[39m: backitup.0 [minimal/mysql] MySql File deleted! 2019-01-05 08:43:22.079 - [34mdebug[39m: backitup.0 [minimal/umount] wait 60 seconds for umount! 2019-01-05 08:43:22.085 - [34mdebug[39m: backitup.0 [minimal/history] done 2019-01-05 08:43:22.086 - [34mdebug[39m: backitup.0 [minimal] exec: done 2019-01-05 08:43:22.094 - [34mdebug[39m: backitup.0 redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546674202093,"q":0,"from":"system.adapter.backitup.0","lc":1546674202093} 2019-01-05 08:43:22.134 - [34mdebug[39m: backitup.0 [minimal/redis] done 2019-01-05 08:43:22.135 - [34mdebug[39m: backitup.0 [minimal] exec: done 2019-01-05 08:43:22.140 - [34mdebug[39m: backitup.0 redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546674202138,"q":0,"from":"system.adapter.backitup.0","lc":1546674202093} 2019-01-05 08:44:22.147 - [34mdebug[39m: backitup.0 [minimal/umount] done 2019-01-05 08:44:22.148 - [34mdebug[39m: backitup.0 [minimal] exec: done 2019-01-05 08:44:22.153 - [34mdebug[39m: backitup.0 redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546674262151,"q":0,"from":"system.adapter.backitup.0","lc":1546674202093} -
die Installation von
apt-get install mysql-client
war die Lösung `
Das hier hat die Lösung gebracht ! Zumindest ist der Fehler weg und alles läuft sauber durch –> oder nicht ? mysql.tar.gz ist immer noch sehr klein
backitup.0 2019-01-05 09:45:34.911 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546677934908,"q":0,"from":"system.adapter.backitup.0","lc":1546677874890} backitup.0 2019-01-05 09:45:34.910 debug [minimal] exec: done backitup.0 2019-01-05 09:45:34.909 debug [minimal/umount] done host.ioBdebian 2019-01-05 09:45:10.805 info instance system.adapter.daswetter.0 terminated with code 0 (OK) daswetter.0 2019-01-05 09:45:01.308 info starting. Version 2.5.0 in /opt/iobroker/node_modules/iobroker.daswetter, node: v8.15.0 host.ioBdebian 2019-01-05 09:45:00.024 info instance system.adapter.daswetter.0 started with pid 1810 backitup.0 2019-01-05 09:44:39.905 debug system.adapter.admin.0: logging true backitup.0 2019-01-05 09:44:39.904 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":true,"ack":true,"ts":1546677879900,"q":0,"from":"system.adapter.admin.0","lc":1546677879900} backitup.0 2019-01-05 09:44:34.963 debug [minimal/mysql] MySql File deleted! backitup.0 2019-01-05 09:44:34.891 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546677874890,"q":0,"from":"system.adapter.backitup.0","lc":1546677874890} backitup.0 2019-01-05 09:44:34.888 debug [minimal] exec: done backitup.0 2019-01-05 09:44:34.885 debug [minimal/redis] done backitup.0 2019-01-05 09:44:34.846 debug [minimal/umount] wait 60 seconds for umount! backitup.0 2019-01-05 09:44:34.844 debug [minimal/history] done backitup.0 2019-01-05 09:44:34.831 debug [minimal/telegram] done backitup.0 2019-01-05 09:44:34.830 debug sendTo "send" to system.adapter.telegram.0 from system.adapter.backitup.0 backitup.0 2019-01-05 09:44:34.828 debug [minimal/telegram] [minimal] used Telegram-Instance: telegram.0 backitup.0 2019-01-05 09:44:34.823 debug [minimal/clean] done backitup.0 2019-01-05 09:44:34.819 debug [minimal/cifs] done backitup.0 2019-01-05 09:44:34.814 debug [minimal/mysql] done backitup.0 2019-01-05 09:44:34.774 debug [minimal/mysql] done backitup.0 2019-01-05 09:44:34.674 debug [minimal/minimal] done backitup.0 2019-01-05 09:44:34.561 debug [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_01_05-09_44_29_backupiobroker.tar.gz backitup.0 2019-01-05 09:44:29.848 debug [minimal/mount] done backitup.0 2019-01-05 09:44:25.496 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":true,"ack":false,"ts":1546677865495,"q":0,"from":"system.adapter.admin.0","lc":1546677865495} backitup.0 2019-01-05 09:44:22.157 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"638246091":"Schecki_Homematic"} backitup.0 2019-01-05 09:44:22.154 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 09:43:48.300 debug system.adapter.admin.0: logging false backitup.0 2019-01-05 09:43:48.298 debug redis pmessage io.*.logging io.system.adapter.admin.0.logging {"val":false,"ack":true,"ts":1546677828296,"q":0,"from":"system.adapter.admin.0","lc":1546677828296} -
Wie gesagt … öffne das backup und schaue nach.
Alles andere ist Glaskugel schauen ...
Gesendet von iPhone mit Tapatalk
-
Musste dafür an den Win-Rechner. Also das mysql file ist leer. Das wurde also nicht erstellt - kein Wunder bei 1Kb Größe.
Im Log ist aber auch keine Meldung gewesen.
Debug File sieht sauber aus aber SQL dump wird nicht gemacht
backitup.0 2019-01-05 12:56:51.107 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546689411103,"q":0,"from":"system.adapter.backitup.0","lc":1546689351091} backitup.0 2019-01-05 12:56:51.104 debug [minimal] exec: done backitup.0 2019-01-05 12:56:51.104 debug [minimal/umount] done backitup.0 2019-01-05 12:55:51.093 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":false,"ack":true,"ts":1546689351091,"q":0,"from":"system.adapter.backitup.0","lc":1546689351091} backitup.0 2019-01-05 12:55:51.088 debug [minimal] exec: done backitup.0 2019-01-05 12:55:51.086 debug [minimal/redis] done backitup.0 2019-01-05 12:55:51.041 debug [minimal/umount] wait 60 seconds for umount! backitup.0 2019-01-05 12:55:51.038 debug [minimal/history] done backitup.0 2019-01-05 12:55:51.031 debug [minimal/mysql] MySql File deleted! backitup.0 2019-01-05 12:55:51.020 debug [minimal/telegram] done backitup.0 2019-01-05 12:55:51.019 debug sendTo "send" to system.adapter.telegram.0 from system.adapter.backitup.0 backitup.0 2019-01-05 12:55:51.017 debug [minimal/telegram] [minimal] used Telegram-Instance: telegram.0 backitup.0 2019-01-05 12:55:51.009 debug [minimal/clean] done backitup.0 2019-01-05 12:55:51.004 debug [minimal/cifs] done backitup.0 2019-01-05 12:55:50.995 debug [minimal/mysql] done backitup.0 2019-01-05 12:55:50.899 debug [minimal/mysql] done backitup.0 2019-01-05 12:55:50.840 debug [minimal/minimal] done backitup.0 2019-01-05 12:55:50.774 debug [minimal/minimal] Backup created: /opt/iobroker/backups/minimal_2019_01_05-12_55_45_backupiobroker.tar.gz backitup.0 2019-01-05 12:55:45.829 debug [minimal/mount] done backitup.0 2019-01-05 12:55:41.309 debug redis pmessage io.backitup.0.oneClick.* io.backitup.0.oneClick.minimal {"val":true,"ack":false,"ts":1546689341308,"q":0,"from":"system.adapter.admin.0","lc":1546689341308} backitup.0 2019-01-05 12:55:38.285 debug sendTo "getTelegramUser" to system.adapter.admin.0 from system.adapter.backitup.0: {"638246091":"Schecki_Homematic"} backitup.0 2019-01-05 12:55:38.280 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":4 -
Schaue mal genau rein.
Da liegt ein File drin mit dem Dateinamen „.“ (Punkt)
Die kannst du im Editor öffnen
Gesendet von iPhone mit Tapatalk
-
Puh, jetzt hab ichs entpacken können und meine AUGENESA hen gar nicht das "_" File
Hier das Ergebnis was auch immer mir das sagen soll:
-- MySQL dump 10.16 Distrib 10.1.37-MariaDB, for debian-linux-gnu (x86_64) -- -- Host: 192.168.40.11 Database: iobroker -- ------------------------------------------------------ -- Server version 5.1.73 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8mb4 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;Zur Info: Ich habe mal per sqldump auf dem NAS direkt ein backup angestossen. Datei ist 155MB gross und nicht 1kB
-
Wie hast das manuell gemacht?
Nur die iobroker Datenbank oder alles
Prüfe deine Daten in der backitup config auch noch einmal
Vor allem den Port
Gesendet von iPhone mit Tapatalk
-
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 -
zeige mal bitte deine Einstellung für mysql
-
Ab sofort ist die Version 1.0.2 im github und latest verfügbar.
1.0.2 (05.01.2019)
(simatec) Fix start/stop for new iobroker-Installer
-
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} -
Hast du mal probiert den Hostname statt der IP Adresse zu nehmen?
Wo liegt deine mysqldump?
Gib mal zum testen den Pfad mit ein
-
Weder der Name noch der Pfad bringt was
Warte mal ich glaub ich habs !
-
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 ?
-
zu früh gefreut ?
seit (fast) einer Stunde dieses Bild
-
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 -
Was liegt jetzt auf dem NAS?
Hat er etwas erstellt?
Gesendet von iPhone mit Tapatalk
-
Bitte schön
-
Starte am besten dein iob und dein System mal neu.
Laut Log hat sich da irgendwas verabschiedet
Gesendet von iPhone mit Tapatalk
-
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
