Adapter: iobroker.backitup (stable Release)

Segway

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

simatec

Schaue mal genau rein.

Da liegt ein File drin mit dem Dateinamen „.“ (Punkt)

Die kannst du im Editor öffnen

Gesendet von iPhone mit Tapatalk

Segway

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

simatec

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

Segway

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

simatec

zeige mal bitte deine Einstellung für mysql

simatec

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

Segway

Hier meine Einstellung

1043_bildschirmfoto_2019-01-05_um_18.56.23.png

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}

simatec

Hast du mal probiert den Hostname statt der IP Adresse zu nehmen?

Wo liegt deine mysqldump?

Gib mal zum testen den Pfad mit ein

Segway

Weder der Name noch der Pfad bringt was

Warte mal ich glaub ich habs !

Segway

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 ?

Segway

zu früh gefreut ?

seit (fast) einer Stunde dieses Bild

1043_bildschirmfoto_2019-01-05_um_19.59.19.png

Segway

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

simatec

Was liegt jetzt auf dem NAS?

Hat er etwas erstellt?

Gesendet von iPhone mit Tapatalk

Segway

Bitte schön

1043_bildschirmfoto_2019-01-05_um_20.40.37.png

simatec

Starte am besten dein iob und dein System mal neu.

Laut Log hat sich da irgendwas verabschiedet

Gesendet von iPhone mit Tapatalk

sigi234

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

Segway

~~@simatec:~~

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 ?

Merlin123

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

Jan1

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'

NEWS

Adapter: iobroker.backitup (stable Release)

Support us

1.0k
Online

31.1k
Users

78.2k
Topics

1.2m
Posts

NEWS

Adapter: iobroker.backitup (stable Release)

Support us

1.0kOnline

31.1kUsers

78.2kTopics

1.2mPosts

1.0k
Online

31.1k
Users

78.2k
Topics

1.2m
Posts