Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[habi989]

@homoran

Hi, sorry das walnatürlich nicht meine Absicht.

Ich habe das Log nun gesäubert und alle anderen Warnungen etc. herausgelöscht. Hier nun was der Backitup Adapter meldet.

2022-02-02 09:49:41.089  - error: host.raspberrypi uncaught exception: Array buffer allocation failed
2022-02-02 09:49:42.635  - error: backitup.0 (25330) States database error: read ECONNRESET
2022-02-02 09:49:42.660  - info: backitup.0 (25330) cleaned everything up...
2022-02-02 09:49:42.635  - error: backitup.0 (25330) States database error: read ECONNRESET
2022-02-02 09:49:42.660  - info: backitup.0 (25330) cleaned everything up...
2022-02-02 09:49:44.171  - info: backitup.0 (25330) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-02-02 09:49:44.171  - info: backitup.0 (25330) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-02-02 09:49:47.653  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.655  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.657  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.660  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.663  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.664  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.667  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.669  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.670  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.672  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.674  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.676  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.677  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.679  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.680  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.681  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.683  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.699  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.707  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.708  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.709  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.710  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.711  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.712  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.713  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.716  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.718  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.720  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.721  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.653  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.655  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.657  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.660  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.663  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.664  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.667  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.669  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.670  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.672  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.674  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.676  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.677  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.679  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.680  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.681  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.683  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.698  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.699  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.707  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.708  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.709  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.710  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.711  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.712  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.713  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.716  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.717  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.718  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.719  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.720  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:49:47.721  - warn: backitup.0 (25330) get state error: DB closed
2022-02-02 09:50:53.250  - error: backitup.0 (10769) backitup.0 already running
2022-02-02 09:50:53.255  - warn: backitup.0 (10769) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-02-02 09:50:53.250  - error: backitup.0 (10769) backitup.0 already running
2022-02-02 09:50:53.255  - warn: backitup.0 (10769) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2022-02-02 09:51:25.869  - info: backitup.0 (10871) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
2022-02-02 09:51:25.933  - info: backitup.0 (10871) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-02-02 09:51:25.869  - info: backitup.0 (10871) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
2022-02-02 09:51:25.933  - info: backitup.0 (10871) [iobroker] backup was activated at 02:40 every 1 day(s)

[Homoran]

@habi989 sagte in Backitup Mount Error Synology NAS:

Hier nun was der Backitup Adapter meldet.

das ist immer noch kein debug-log!
hast du die Instanz auch auf Logstufe debug gestellt?

Bin mal am PC und habe deinen letzten Riesen-log mal etwas gekürzt.

Dabei habe ich eine Zeile gesehen, die mich stutzig macht:

@habi989 sagte in Backitup Mount Error Synology NAS:

warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4:

hast du etwa tausende MB an Videos im Backup?

[habi989]

@homoran

ach jetzt habe ich kapiert was du mir sagen wolltest. So habe es auf debug gestellt. so wie ich das sehe findet er kein backup?

2022-02-02 13:56:53.835  - debug: backitup.0 (22002) Redis Objects: Use Redis connection: 127.0.0.1:9001
2022-02-02 13:56:53.934  - debug: backitup.0 (22002) Objects client ready ... initialize now
2022-02-02 13:56:53.937  - debug: backitup.0 (22002) Objects create System PubSub Client
2022-02-02 13:56:53.939  - debug: backitup.0 (22002) Objects create User PubSub Client
2022-02-02 13:56:53.941  - debug: backitup.0 (22002) Objects client initialize lua scripts
2022-02-02 13:56:53.956  - debug: backitup.0 (22002) Objects connected to redis: 127.0.0.1:9001
2022-02-02 13:56:53.965  - debug: backitup.0 (22002) objectDB connected
2022-02-02 13:56:53.967  - debug: backitup.0 (22002) Redis States: Use Redis connection: 127.0.0.1:9000
2022-02-02 13:56:53.976  - debug: backitup.0 (22002) States create System PubSub Client
2022-02-02 13:56:53.978  - debug: backitup.0 (22002) States create User PubSub Client
2022-02-02 13:56:53.988  - debug: backitup.0 (22002) States connected to redis: 127.0.0.1:9000
2022-02-02 13:56:53.989  - debug: backitup.0 (22002) statesDB connected
2022-02-02 13:56:54.283  - debug: backitup.0 (22002) Plugin sentry Initialize Plugin (enabled=true)
2022-02-02 13:56:54.495  - info: backitup.0 (22002) starting. Version 2.2.3 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.18.3, js-controller: 3.3.22
2022-02-02 13:56:54.540  - debug: backitup.0 (22002) Backitup has recognized a linux system
2022-02-02 13:56:54.646  - debug: backitup.0 (22002) [iobroker] 10 40 02 */1 * * 
2022-02-02 13:56:54.668  - debug: backitup.0 (22002) noserverino option: true
2022-02-02 13:56:54.669  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
2022-02-02 13:56:54.745  - debug: backitup.0 (22002) first mount attempt with smb option failed. try next mount attempt without smb option ...
2022-02-02 13:56:54.746  - debug: backitup.0 (22002) cifs-mount command: "sudo mount -t cifs -o username=backitup,password=****,noserverino,rw,file_mode=0777,dir_mode=0777 //192.168.178.2Backupio/iobroker /opt/iobroker/backups"
2022-02-02 13:56:54.833  - debug: backitup.0 (22002) mount successfully completed
2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
2022-02-02 13:56:56.843  - debug: backitup.0 (22002) No backup file was found
2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
2022-02-02 13:57:04.585  - debug: backitup.0 (22002) mount activ... umount in 2 Seconds!!
2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed
2022-02-02 13:57:06.685  - debug: backitup.0 (22002) umount successfully completed

[habi989]

@homoran

Hi,

ja die Video der Ring werden auf der sd karte abgelegt... etwa 20gb ohne jetzt genau nachzusehen...

[Homoran]

@habi989 sagte in Backitup Mount Error Synology NAS:

so wie ich das sehe findet er kein backup?

was hast du denn gemacht, damit er danach sucht?

Hast du dazu noch eine Antwort?

@homoran sagte in Backitup Mount Error Synology NAS:

Dabei habe ich eine Zeile gesehen, die mich stutzig macht:
@habi989 sagte in Backitup Mount Error Synology NAS:

warn: host.raspberrypi-Server Cannot read file ring.0 / doorbell_86292617/livestream86292617_1638876876746.mp4:

hast du etwa tausende MB an Videos im Backup?

[Glasfaser]

@habi989

Zeige mal die Ausgabe von :

du -hs /opt/iobroker/iobroker-data/files/*

[Thomas Braun]

@habi989 sagte in Backitup Mount Error Synology NAS:

192.168.178.2Backupio/iobroker

Da fehlt ein /
Zeigmal die Pfad in den Einstellungen für das NAS.
Ist das eine FritzBox da?

Die 20GB Hollywood-Filme dürften dir das Genick brechen, wenn die Backup-Pfad liegen.

[habi989]

@glasfaser

pi@raspberrypi:/opt/iobroker $ du -hs /opt/iobroker/iobroker-data/files/*
252K	/opt/iobroker/iobroker-data/files/admin.admin
1.2M	/opt/iobroker/iobroker-data/files/alexa2.admin
368K	/opt/iobroker/iobroker-data/files/backitup.admin
4.9M	/opt/iobroker/iobroker-data/files/daswetter.admin
640K	/opt/iobroker/iobroker-data/files/discovery.admin
100K	/opt/iobroker/iobroker-data/files/dwd.admin
28K	/opt/iobroker/iobroker-data/files/fullybrowser.admin
52K	/opt/iobroker/iobroker-data/files/gruenbeck.admin
88K	/opt/iobroker/iobroker-data/files/ical.admin
20M	/opt/iobroker/iobroker-data/files/icons-icons8
12K	/opt/iobroker/iobroker-data/files/icons-icons8.admin
16K	/opt/iobroker/iobroker-data/files/icons-mfd-png.admin
6.8M	/opt/iobroker/iobroker-data/files/icons-ultimate-png
20K	/opt/iobroker/iobroker-data/files/icons-ultimate-png.admin
27M	/opt/iobroker/iobroker-data/files/javascript.admin
124K	/opt/iobroker/iobroker-data/files/ping.admin
5.1G	/opt/iobroker/iobroker-data/files/ring.0
40K	/opt/iobroker/iobroker-data/files/ring.admin
204K	/opt/iobroker/iobroker-data/files/shelly.admin
48K	/opt/iobroker/iobroker-data/files/sonos.admin
176K	/opt/iobroker/iobroker-data/files/synology.admin
76K	/opt/iobroker/iobroker-data/files/tr-064.admin
216K	/opt/iobroker/iobroker-data/files/trashschedule.admin
15M	/opt/iobroker/iobroker-data/files/vis
8.8M	/opt/iobroker/iobroker-data/files/vis.0
48K	/opt/iobroker/iobroker-data/files/vis.admin
24K	/opt/iobroker/iobroker-data/files/vis-hqwidgets.admin
12K	/opt/iobroker/iobroker-data/files/vis-jqui-mfd.admin
36K	/opt/iobroker/iobroker-data/files/vis-metro.admin
68K	/opt/iobroker/iobroker-data/files/vis-players.admin
20K	/opt/iobroker/iobroker-data/files/vis-timeandweather.admin
36K	/opt/iobroker/iobroker-data/files/vis-weather.admin
7.9M	/opt/iobroker/iobroker-data/files/web
9.4M	/opt/iobroker/iobroker-data/files/web.admin
88K	/opt/iobroker/iobroker-data/files/whatsapp-cmb.admin

[habi989]

@thomas-braun

meinst du diese Pfade?

[Thomas Braun]

@habi989
Ja, für die Optik: Setz da ein / an den Anfang.
Und wenn das NAS nicht gerade direkt auf der FritzBox läuft nimm den Haken bei 'noserverino' raus.

[Homoran]

@habi989 sagte in Backitup Mount Error Synology NAS:

5.1G /opt/iobroker/iobroker-data/files/ring.0

5 GiG Videos. Da bleibt das Backup hängen

[habi989]

@homoran

kann ich das irgendwo konfigurieren, damit das einfach nicht mit in das Backup genommen wird?

[Homoran]

@habi989 sagte in Backitup Mount Error Synology NAS:

@homoran

kann ich das irgendwo konfigurieren, damit das einfach nicht mit in das Backup genommen wird?

keine Ahnung, ich nutze klingling nicht

[OstfrieseUnterwegs]

@habi989 sagte in Backitup Mount Error Synology NAS:

@homoran

kann ich das irgendwo konfigurieren, damit das einfach nicht mit in das Backup genommen wird?

In backitup Adapter kann man nichts ausschließen, da musst Du schon selber per Script aufräumen und/oder archivieren. Vlt kann auch der ring Adapter altes Zeugs weglöschen?

[Homoran]

@ostfrieseunterwegs sagte in Backitup Mount Error Synology NAS:

In backitup Adapter kann man nichts ausschließen,

ich glaube auch nicht, dass @habi989 das meinte. Sondern eher, ob man im Klingling-Adapter einen anderen Speicherpfad für die Videos einstellen kann (wie z.B. /home/iobroker), der nicht gesichert wird.

[habi989]

@homoran

okay, ich versuche gerade die Dateien in dem Verzeichnis zu löschen: Hierzu eine Frage:

Das Verzeichnis ist das folgende

/opt/iobroker/iobroker-data/ring_0/snapshot

ich möchte alle Dateien mit der Endung .mp4 löschen.

Kann mir jemand sagen, welchen Befehl ich dazu eingeben muss?

find /opt/iobroker/iobroker-data/ring_0/snapshot -exec rm *.mp4

wäre das richtig?

[Thomas Braun]

@habi989 sagte in Backitup Mount Error Synology NAS:

/opt/iobroker/iobroker-data/ring_0/snapshot

sudo -u iobroker rm /opt/iobroker/iobroker-data/ring_0/snapshot/*.mp4

[habi989]

@thomas-braun @Homoran @Glasfaser

So, nachdem ich nun den Ordner mit den Videos gelöscht habe, hat das Backup auf die NAS endlich funktioniert!

Ich danke euch für eure Hilfe und Geduld!! Vielen, vielen Dank und einen schönen Abend!

[Homoran]

@habi989 sagte in Backitup Mount Error Synology NAS:

hat das Backup auf die NAS endlich funktioniert!

klar doch - der Ballast von 5GB war ja weg.
ein übliches Backup liegt max. im niedrigen 2stelligen MB-Bereich