NEWS
Adapter: iobroker.backitup (stable Release)
-
Das erste error was kommt beudeutet keinen Zugang oder ? `
Nimm am besten mal ein FTP Client wie z.B. Filezilla und probier dich mit den Daten auf dem FTP einzuloggen.
Ich gehe davon aus, dass dein Pfad mit dem # nicht stimmen kann
Gesendet von iPhone mit Tapatalk
-
Wenn ich diese Adresse ohen # eingebe komme ich nicht auf die Nas seite.
Das gebe ich in die adresszeile vom Broweser ein und komme dann zum Login:
fritz.box/nas/#/files/Generic-FlashDisk-01
Host: 192.168.178.1
Der Pfad Lautet:
/nas/#/files/Generic-FlashDisk-01
Edit:
Ich komme über Filezilla auf die NAS mit den Login Daten
-
Tja, nun war es soweit. von 0.4.2 auf die ganze neue Version installiert und leider geht das backup manuell ausgelöst jetzt nicht mehr. Was soll mir die Meldung sagen ? Nas ist bereits neu gestartet
Gestartet... [DEBUG] [mount] start with {"mountType":"CIFS","type":"storage","source":"Local","mount":"192.168.40.11","fileDir":"/opt/iobroker/node_modules/iobroker.backitup","wakeOnLAN":false,"macAd":"20:DE:20:DE:20:DE","smb":"vers=1.0","sudo":true,"deleteOldBackup":true,"ownDir":true,"bkpType":"Minimal","dir":"/Daten/Daten/iobroker/Standard","dirMinimal":"/Daten/Daten/iobroker/Standard","dirTotal":"/Daten/Daten/iobroker/Komplett","user":"xxxxx","pass":"****"} [ERROR] [mount] - [undefined 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=xxxxxx,password=xxxxxx,rw,file_mode=0777,dir_mode=0777 //192.168.40.11/Daten/Daten/iobroker/Standard /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) -
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} -
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 -
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
-
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
387
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge