Monatsrückblick Januar/Februar 2026 ist online!

[OliverIO]

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Ich nutze Portainer für das Teminal

Kenne ich nicht, kenne nur Portainer als Web oberfläche
hast du im Portainer unter stacks einen Eintrag?

[Happyuser20]

@OliverIO sagte in IOB im Docker Startet nicht mehr!!!:

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Ich nutze Portainer für das Teminal

Kenne ich nicht, kenne nur Portainer als Web oberfläche
hast du im Portainer unter stacks einen Eintrag?

Über Portainer die Exec Console meine ich )

Müssen die richtigen angaben in der "iobroker.json" zwischen den Zeile 32 - 52 stehen?
iobroker.json

Unter Stacks habe ich nichts im Portainer

[OliverIO]

@Happyuser20

Das ist schwer zu lesen.
Nach welcher Beschreibung hast du das erstellt?

Ich empfehle dir, auf Docker Compose umzustellen.
Das nennt sich bei Container stacks.
Ist aber 1:1 identisch.
Das ist viel einfacher zu pflegen und zu erweitern
Alle Informationen sind leicht lesbar
https://docs.buanet.de/de/iobroker-docker-image/docs/#starten-per-docker-compose

Die wahrscheinlichste Lösung hab ich ja geschrieben
Aber ohne die lesbaren Detailformationen mit der Container gestartet wird, ist es ein wenig raten

[Happyuser20]

Die iobroker Jason habe ich nicht erstellt.
Die habe ich nur geöffnet und eben die Multihost einstellungen, falls das die sind, gefunden.

[Happyuser20]

IOB läuft ja in einem Docker Container auf einer Synology NAS.
Ist Docker-Compose wieder was anderes?

[Happyuser20]

Da ich hier nicht weitergekommen bin habe ich mich entschlossen, IoBroker im container neu zu installieren
Das war einfach und schnell erledigt.
Nun wollte ich eine Backitup Datei wieder herstellen. (habe täglich ein Backup des Iobrokers und der History daten erstellt und auf dem Nas gespeichert)
Wenn ich nun über Backitup auf der neuinstallation dei Backup-Datei einspielen will, tut sich nichts.

Im Protokoll steht nur das

[Homoran]

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Im Protokoll steht nur das

dann stell den Filter mal nicht suf warn

bitte nie Screenshots vom log!
immer als Text in code-tags posten!

Darf dein container in die Welt telefonieren?

[Happyuser20]

Ich denke schon das er telefonieren kann.
Ich habe den IOBroker mit Docker Compose von Buanet installiert.
Es erscheint nach der Neuinstallation auch die Admin Oberfläche, dann wollte ich eine Backup Datei (von gestern) hochladen.

Ab dann tut sich nichts mehr.

[Homoran]

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Ab dann tut sich nichts mehr.

zeig doch mal was!
so ist alles Kaffeesatzleserei!

sagte in IOB im Docker Startet nicht mehr!!!:

stell den Filter mal nicht auf warn

und zeig das log!

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

dann wollte ich eine Backup Datei (von gestern) hochladen.

oder hast du?
wenn doch, wie?

und nur durch das hochladen hängt es jetzt?
oder doch bereits den Restore gestartet???

und nichts im debug-log zu sehen?

[Happyuser20]

@Homoran sagte in IOB im Docker Startet nicht mehr!!!:

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Ab dann tut sich nichts mehr.

zeig doch mal was!
so ist alles Kaffeesatzleserei!

sagte in IOB im Docker Startet nicht mehr!!!:

stell den Filter mal nicht auf warn

und zeig das log!

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

dann wollte ich eine Backup Datei (von gestern) hochladen.

oder hast du?
wenn doch, wie?

und nur durch das hochladen hängt es jetzt?
oder doch bereits den Restore gestartet???

und nichts im debug-log zu sehen?

Ich ziehe hier die Backupdatei rein

Drücke auf "Backup Upload" und dann passiert nichts mehr.

2026-03-22 15:32:44.360 - info: host.iobroker iobroker.js-controller version 7.0.7 js-controller starting
2026-03-22 15:32:44.365 - info: host.iobroker Copyright (c) 2014-2024 bluefox, 2014 hobbyquaker
2026-03-22 15:32:44.366 - info: host.iobroker hostname: iobroker, node: v22.22.1
2026-03-22 15:32:44.367 - info: host.iobroker ip addresses: 172.18.0.2
2026-03-22 15:32:44.735 - info: host.iobroker connected to Objects and States
2026-03-22 15:32:44.770 - info: host.iobroker Node.js version has changed from unknown to 22.22.1
2026-03-22 15:32:44.794 - info: host.iobroker added notifications configuration of host
2026-03-22 15:32:45.204 - info: host.iobroker Delete host system.host.iobroker
2026-03-22 15:32:45.213 - warn: host.iobroker Error while trying to update capabilities after detecting new Node.js version: Command failed: sudo setcap cap_net_bind_service,cap_net_raw+epi /usr/bin/node
Failed to set capabilities on file '/usr/bin/node': Operation not supported
2026-03-22 15:32:45.275 - info: host.iobroker 3 instances found
2026-03-22 15:32:45.283 - info: host.iobroker starting 3 instances
2026-03-22 15:32:45.346 - info: host.iobroker instance system.adapter.admin.0 in version "7.7.22" started with pid 198
2026-03-22 15:32:48.708 - info: admin.0 (198) starting. Version 7.7.22 in /opt/iobroker/node_modules/iobroker.admin, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:32:48.743 - info: admin.0 (198) requesting all objects
2026-03-22 15:32:48.888 - info: admin.0 (198) received all objects
2026-03-22 15:32:48.949 - info: admin.0 (198) Request actual repository...
2026-03-22 15:32:48.977 - info: admin.0 (198) socket.io server listening on port 8081
2026-03-22 15:32:48.981 - info: admin.0 (198) http server listening on port 8081
2026-03-22 15:32:48.981 - info: admin.0 (198) Use link "http://127.0.0.1:8081" to configure.
2026-03-22 15:32:49.040 - info: host.iobroker Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
2026-03-22 15:32:49.381 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.13" started with pid 243
2026-03-22 15:32:49.395 - warn: admin.0 (198) Repository cannot be read: Active repo - stable
2026-03-22 15:32:49.511 - warn: admin.0 (198) Active repository "stable" cannot be read
2026-03-22 15:32:52.579 - info: admin.0 (198) Repository received successfully.
2026-03-22 15:32:53.769 - info: host.iobroker instance system.adapter.discovery.0 in version "5.0.0" started with pid 266
2026-03-22 15:32:54.549 - info: backitup.0 (243) starting. Version 3.3.13 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:32:54.743 - info: backitup.0 (243) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 15:32:56.198 - info: discovery.0 (266) starting. Version 5.0.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:35:18.664 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:36:04.984 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 admin
2026-03-22 15:36:05.395 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:36:07.945 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:38:13.974 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:38:25.153 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:38:37.580 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:39:06.743 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 15:39:06.748 - info: backitup.0 (243) Got terminate signal TERMINATE_YOURSELF
2026-03-22 15:39:06.750 - info: backitup.0 (243) cleaned everything up...
2026-03-22 15:39:06.751 - info: backitup.0 (243) terminating
2026-03-22 15:39:06.752 - info: backitup.0 (243) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 15:39:06.788 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 15:39:07.254 - info: backitup.0 (243) terminating
2026-03-22 15:39:07.359 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 15:39:10.121 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:39:10.703 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.13" started with pid 598
2026-03-22 15:39:12.808 - info: backitup.0 (598) starting. Version 3.3.13 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:39:12.913 - info: backitup.0 (598) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 15:39:48.397 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:40:15.587 - info: host.iobroker iobroker upgrade backitup@3.3.14 --debug
2026-03-22 15:40:17.712 - info: host.iobroker iobroker Update backitup from @3.3.13 to @3.3.14
2026-03-22 15:40:17.728 - info: host.iobroker iobroker host.iobroker Adapter "system.adapter.backitup.0" is stopped.
2026-03-22 15:40:17.768 - info: host.iobroker "system.adapter.backitup.0" disabled
2026-03-22 15:40:17.769 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 15:40:17.796 - info: backitup.0 (598) Got terminate signal TERMINATE_YOURSELF
2026-03-22 15:40:17.797 - info: backitup.0 (598) cleaned everything up...
2026-03-22 15:40:17.801 - info: backitup.0 (598) terminating
2026-03-22 15:40:17.802 - info: backitup.0 (598) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 15:40:17.825 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 15:40:18.060 - info: host.iobroker iobroker NPM version: 10.9.4
2026-03-22 15:40:18.061 - info: host.iobroker iobroker Installing iobroker.backitup@3.3.14... (System call)
2026-03-22 15:40:18.304 - info: backitup.0 (598) terminating
2026-03-22 15:40:18.343 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 15:40:26.485 - info: host.iobroker iobroker changed 2 packages in 8s
2026-03-22 15:40:26.487 - info: host.iobroker iobroker 102 packages are looking for funding run `npm fund` for details
2026-03-22 15:40:32.478 - info: host.iobroker iobroker Updating objects from io-package.json for adapter "backitup" with version "3.3.14"
2026-03-22 15:40:32.523 - info: host.iobroker iobroker Update "system.adapter.backitup.0"
2026-03-22 15:40:33.170 - info: host.iobroker iobroker upload [91] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/asset-manifest.json asset-manifest.json application/json
2026-03-22 15:40:33.184 - info: host.iobroker iobroker upload [90] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/assets/ccu-DJclZqBW.png assets/ccu-DJclZqBW.png image/png
2026-03-22 15:40:33.634 - info: host.iobroker iobroker upload [80] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/custom/assets/Components-UGyi-iSQ.js custom/assets/Components-UGyi-iSQ.js application/javascript
2026-03-22 15:40:33.688 - info: host.iobroker iobroker upload [70] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/custom/assets/createSvgIcon-B6mnt2Dk.js custom/assets/createSvgIcon-B6mnt2Dk.js application/javascript
2026-03-22 15:40:33.773 - info: host.iobroker iobroker upload [60] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/custom/assets/index-C4bVJG3o.js custom/assets/index-C4bVJG3o.js application/javascript
2026-03-22 15:40:34.063 - info: host.iobroker iobroker upload [50] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/custom/assets/virtualExposes-BiWMrXLv.js custom/assets/virtualExposes-BiWMrXLv.js application/javascript
2026-03-22 15:40:34.128 - info: host.iobroker iobroker upload [40] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/custom/i18n/pt.json custom/i18n/pt.json application/json
2026-03-22 15:40:34.181 - info: host.iobroker iobroker upload [30] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/history.jsonConfig.json5 history.jsonConfig.json5 application/json5
2026-03-22 15:40:34.234 - info: host.iobroker iobroker upload [20] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/uk/translations.json i18n/uk/translations.json application/json
2026-03-22 15:40:34.243 - info: host.iobroker iobroker upload [19] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
2026-03-22 15:40:34.252 - info: host.iobroker iobroker upload [18] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/influxdb.jsonConfig.json5 influxdb.jsonConfig.json5 application/json5
2026-03-22 15:40:34.260 - info: host.iobroker iobroker upload [17] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/iob.jsonConfig.json5 iob.jsonConfig.json5 application/json5
2026-03-22 15:40:34.270 - info: host.iobroker iobroker upload [16] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/jsonConfig.json5 jsonConfig.json5 application/json5
2026-03-22 15:40:34.278 - info: host.iobroker iobroker upload [15] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/main.jsonConfig.json5 main.jsonConfig.json5 application/json5
2026-03-22 15:40:34.286 - info: host.iobroker iobroker upload [14] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/manifest.json manifest.json application/json
2026-03-22 15:40:34.296 - info: host.iobroker iobroker upload [13] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/mysql.jsonConfig.json5 mysql.jsonConfig.json5 application/json5
2026-03-22 15:40:34.304 - info: host.iobroker iobroker upload [12] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/notifications.jsonConfig.json5 notifications.jsonConfig.json5 application/json5
2026-03-22 15:40:34.313 - info: host.iobroker iobroker upload [11] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/onedrive.jsonConfig.json5 onedrive.jsonConfig.json5 application/json5
2026-03-22 15:40:34.321 - info: host.iobroker iobroker upload [10] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/pgsql.jsonConfig.json5 pgsql.jsonConfig.json5 application/json5
2026-03-22 15:40:34.331 - info: host.iobroker iobroker upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/redis.jsonConfig.json5 redis.jsonConfig.json5 application/json5
2026-03-22 15:40:34.338 - info: host.iobroker iobroker upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/restore.jsonConfig.json5 restore.jsonConfig.json5 application/json5
2026-03-22 15:40:34.346 - info: host.iobroker iobroker upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/sqlite.jsonConfig.json5 sqlite.jsonConfig.json5 application/json5
2026-03-22 15:40:34.354 - info: host.iobroker iobroker upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css
2026-03-22 15:40:34.363 - info: host.iobroker iobroker upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.css tab_m.css text/css
2026-03-22 15:40:34.373 - info: host.iobroker iobroker upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html
2026-03-22 15:40:34.383 - info: host.iobroker iobroker upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript
2026-03-22 15:40:34.392 - info: host.iobroker iobroker upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/webdav.jsonConfig.json5 webdav.jsonConfig.json5 application/json5
2026-03-22 15:40:34.400 - info: host.iobroker iobroker upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript
2026-03-22 15:40:34.409 - info: host.iobroker iobroker upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/zigbee2mqtt.jsonConfig.json5 zigbee2mqtt.jsonConfig.json5 application/json5
2026-03-22 15:40:34.419 - info: host.iobroker iobroker host.iobroker Adapter "system.adapter.backitup.0" is started
2026-03-22 15:40:34.436 - info: host.iobroker "system.adapter.backitup.0" enabled
2026-03-22 15:40:34.718 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 861
2026-03-22 15:40:35.470 - info: host.iobroker iobroker exit 0
2026-03-22 15:40:36.886 - info: backitup.0 (861) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:40:36.962 - info: backitup.0 (861) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 15:40:41.599 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:42:04.135 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:42:51.734 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:45:22.769 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:45:45.855 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:48:49.692 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:55:51.741 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:55:54.372 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 15:56:11.312 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 15:56:11.316 - info: backitup.0 (861) Got terminate signal TERMINATE_YOURSELF
2026-03-22 15:56:11.318 - info: backitup.0 (861) cleaned everything up...
2026-03-22 15:56:11.319 - info: backitup.0 (861) terminating
2026-03-22 15:56:11.321 - info: backitup.0 (861) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 15:56:11.355 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 15:56:11.822 - info: backitup.0 (861) terminating
2026-03-22 15:56:11.859 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 15:56:15.162 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 1649
2026-03-22 15:56:17.387 - info: backitup.0 (1649) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:56:17.468 - info: backitup.0 (1649) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 15:56:18.449 - error: backitup.0 (1649) Error: Command failed: sudo mount :/sharename/backupDir /opt/iobroker/backups
mount.nfs: Failed to resolve server : Name or service not known
2026-03-22 15:58:23.550 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 15:58:23.557 - info: backitup.0 (1649) Got terminate signal TERMINATE_YOURSELF
2026-03-22 15:58:23.558 - info: backitup.0 (1649) cleaned everything up...
2026-03-22 15:58:23.559 - info: backitup.0 (1649) terminating
2026-03-22 15:58:23.561 - info: backitup.0 (1649) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 15:58:23.604 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 15:58:24.062 - info: backitup.0 (1649) terminating
2026-03-22 15:58:24.100 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 15:58:27.446 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 1766
2026-03-22 15:58:29.638 - info: backitup.0 (1766) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:58:29.758 - info: backitup.0 (1766) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 15:59:17.423 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 15:59:17.428 - info: backitup.0 (1766) Got terminate signal TERMINATE_YOURSELF
2026-03-22 15:59:17.430 - info: backitup.0 (1766) cleaned everything up...
2026-03-22 15:59:17.431 - info: backitup.0 (1766) terminating
2026-03-22 15:59:17.433 - info: backitup.0 (1766) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 15:59:17.466 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 15:59:17.934 - info: backitup.0 (1766) terminating
2026-03-22 15:59:17.966 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 15:59:21.306 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 1831
2026-03-22 15:59:23.378 - info: backitup.0 (1831) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 15:59:23.467 - info: backitup.0 (1831) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 15:59:24.627 - error: backitup.0 (1831) FTP: Error: /Daten/Backups/iobroker: No such file or directory.
2026-03-22 15:59:27.623 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 15:59:28.290 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 16:04:03.121 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:04:03.126 - info: backitup.0 (1831) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:04:03.128 - info: backitup.0 (1831) cleaned everything up...
2026-03-22 16:04:03.129 - info: backitup.0 (1831) terminating
2026-03-22 16:04:03.131 - info: backitup.0 (1831) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:04:03.164 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:04:03.632 - info: backitup.0 (1831) terminating
2026-03-22 16:04:03.667 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:04:06.993 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2079
2026-03-22 16:04:09.033 - info: backitup.0 (2079) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:04:09.107 - info: backitup.0 (2079) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:04:09.929 - error: backitup.0 (2079) FTP: Error: /Daten/Backups/iobroker: No such file or directory.
2026-03-22 16:08:45.081 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:08:45.084 - info: backitup.0 (2079) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:08:45.086 - info: backitup.0 (2079) cleaned everything up...
2026-03-22 16:08:45.087 - info: backitup.0 (2079) terminating
2026-03-22 16:08:45.088 - info: backitup.0 (2079) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:08:45.123 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:08:45.589 - info: backitup.0 (2079) terminating
2026-03-22 16:08:45.622 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:08:48.960 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2326
2026-03-22 16:08:51.195 - info: backitup.0 (2326) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:08:51.275 - info: backitup.0 (2326) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:08:52.160 - error: backitup.0 (2326) FTP: Error: /Daten/Backups/iobroker: No such file or directory.
2026-03-22 16:09:01.252 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 16:09:02.515 - error: backitup.0 (2326) Error: Command failed: sudo mount 192.168.1.111:/sharename/backupDir /opt/iobroker/backups
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: access denied by server while mounting 192.168.1.111:/sharename/backupDir
2026-03-22 16:09:16.618 - error: backitup.0 (2326) Error: Command failed: sudo mount 192.168.1.111:/sharename/backupDir /opt/iobroker/backups
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: access denied by server while mounting 192.168.1.111:/sharename/backupDir
2026-03-22 16:09:26.005 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 16:10:17.382 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:10:17.389 - info: backitup.0 (2326) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:10:17.390 - info: backitup.0 (2326) cleaned everything up...
2026-03-22 16:10:17.391 - info: backitup.0 (2326) terminating
2026-03-22 16:10:17.393 - info: backitup.0 (2326) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:10:17.424 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:10:17.894 - info: backitup.0 (2326) terminating
2026-03-22 16:10:17.934 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:10:21.286 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2430
2026-03-22 16:10:23.318 - info: backitup.0 (2430) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:10:23.404 - info: backitup.0 (2430) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:10:24.170 - error: backitup.0 (2430) Error: Command failed: mount -t cifs -o username=Chef,password=****,rw,forceuid,uid=iobroker,forcegid,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.1.111/sharename/backupDir /opt/iobroker/backups
Unable to apply new capability set.
2026-03-22 16:10:24.223 - error: backitup.0 (2430) FTP: Error: /Daten/Backups/iobroker: No such file or directory.
2026-03-22 16:10:46.141 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:10:46.147 - info: backitup.0 (2430) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:10:46.148 - info: backitup.0 (2430) cleaned everything up...
2026-03-22 16:10:46.149 - info: backitup.0 (2430) terminating
2026-03-22 16:10:46.151 - info: backitup.0 (2430) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:10:46.189 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:10:46.653 - info: backitup.0 (2430) terminating
2026-03-22 16:10:46.692 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:10:50.039 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2476
2026-03-22 16:10:52.123 - info: backitup.0 (2476) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:10:52.245 - info: backitup.0 (2476) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:10:53.181 - error: backitup.0 (2476) FTP: Error: /Daten/Backups/iobroker: No such file or directory.
2026-03-22 16:11:52.833 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:11:52.838 - info: backitup.0 (2476) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:11:52.840 - info: backitup.0 (2476) cleaned everything up...
2026-03-22 16:11:52.841 - info: backitup.0 (2476) terminating
2026-03-22 16:11:52.842 - info: backitup.0 (2476) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:11:52.876 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:11:53.345 - info: backitup.0 (2476) terminating
2026-03-22 16:11:53.401 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:11:56.744 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2540
2026-03-22 16:11:58.843 - info: backitup.0 (2540) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:11:58.930 - info: backitup.0 (2540) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:11:59.789 - error: backitup.0 (2540) FTP: Error: /volume1/Daten/Backups/iobroker: No such file or directory.
2026-03-22 16:13:43.423 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:13:43.429 - info: backitup.0 (2540) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:13:43.431 - info: backitup.0 (2540) cleaned everything up...
2026-03-22 16:13:43.432 - info: backitup.0 (2540) terminating
2026-03-22 16:13:43.433 - info: backitup.0 (2540) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:13:43.467 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:13:43.934 - info: backitup.0 (2540) terminating
2026-03-22 16:13:43.977 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:13:47.318 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2640
2026-03-22 16:13:49.545 - info: backitup.0 (2640) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:13:49.639 - info: backitup.0 (2640) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:13:50.478 - error: backitup.0 (2640) FTP: Error: /OldNo7NAS/Daten/Backups/: No such file or directory.
2026-03-22 16:14:11.686 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:14:11.691 - info: backitup.0 (2640) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:14:11.693 - info: backitup.0 (2640) cleaned everything up...
2026-03-22 16:14:11.694 - info: backitup.0 (2640) terminating
2026-03-22 16:14:11.696 - info: backitup.0 (2640) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:14:11.731 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:14:12.197 - info: backitup.0 (2640) terminating
2026-03-22 16:14:12.248 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:14:15.593 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2680
2026-03-22 16:14:17.705 - info: backitup.0 (2680) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:14:17.792 - info: backitup.0 (2680) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:14:18.688 - error: backitup.0 (2680) FTP: Error: /OldNo7NAS/Daten/Backups/: No such file or directory.
2026-03-22 16:15:20.325 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:15:20.332 - info: backitup.0 (2680) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:15:20.334 - info: backitup.0 (2680) cleaned everything up...
2026-03-22 16:15:20.335 - info: backitup.0 (2680) terminating
2026-03-22 16:15:20.336 - info: backitup.0 (2680) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:15:20.378 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:15:20.838 - info: backitup.0 (2680) terminating
2026-03-22 16:15:20.890 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:15:24.231 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2757
2026-03-22 16:15:26.196 - info: backitup.0 (2757) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:15:26.289 - info: backitup.0 (2757) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:15:27.124 - error: backitup.0 (2757) FTP: Error: /192.168.1.111/Daten/Backups/: No such file or directory.
2026-03-22 16:19:40.634 - info: host.iobroker stopInstance system.adapter.backitup.0 (force=false, process=true)
2026-03-22 16:19:40.638 - info: backitup.0 (2757) Got terminate signal TERMINATE_YOURSELF
2026-03-22 16:19:40.639 - info: backitup.0 (2757) cleaned everything up...
2026-03-22 16:19:40.640 - info: backitup.0 (2757) terminating
2026-03-22 16:19:40.642 - info: backitup.0 (2757) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2026-03-22 16:19:40.676 - info: host.iobroker stopInstance system.adapter.backitup.0 send kill signal
2026-03-22 16:19:41.143 - info: backitup.0 (2757) terminating
2026-03-22 16:19:41.176 - info: host.iobroker instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2026-03-22 16:19:44.523 - info: host.iobroker instance system.adapter.backitup.0 in version "3.3.14" started with pid 2981
2026-03-22 16:19:46.641 - info: backitup.0 (2981) starting. Version 3.3.14 in /opt/iobroker/node_modules/iobroker.backitup, node: v22.22.1, js-controller: 7.0.7
2026-03-22 16:19:46.727 - info: backitup.0 (2981) [iobroker] backup will be activated at 02:48 every 1 day(s)
2026-03-22 16:19:47.595 - error: backitup.0 (2981) FTP: Error: //Oldno7NAS/Daten/Backups/: No such file or directory.
2026-03-22 16:20:47.261 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 16:21:19.879 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup
2026-03-22 16:21:29.614 - info: admin.0 (198) ==> Connected system.user.admin from ::ffff:172.18.0.1
2026-03-22 16:24:50.076 - info: admin.0 (198) <== Disconnect system.user.admin from ::ffff:172.18.0.1 backitup

Die Warnungen vom Backup Adapter, kommen vom rumspielen mit dem Pfad zum NAS via FTP. Klappt auch nicht. Heute ist igendwie der Wurm drin bei mir.

[Homoran]

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

FTP: Error: //Oldno7NAS/Daten/Backups/: No such file or directory

und?
stimmt das?

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

kommen vom rumspielen mit dem Pfad zum NAS via FTP

und wie sind die Einstellungen?

ein debug-log ist das aber auch nicht

[Happyuser20]

@Homoran sagte in IOB im Docker Startet nicht mehr!!!:

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

FTP: Error: //Oldno7NAS/Daten/Backups/: No such file or directory

und?
stimmt das?

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

kommen vom rumspielen mit dem Pfad zum NAS via FTP

und wie sind die Einstellungen?

ein debug-log ist das aber auch nicht

Ich bin jetzt ein wenig weiter weiter gekommen, die Freude war nur kurz.

[Homoran]

@Happyuser20 was kam denn dabei raus?

[Happyuser20]

Er kämpft gerade noch, das dauert noch eine weile bis er durch ist.

[Homoran]

wovon redest du?
Im letzten Screenshot war doch eine Aufgabe!

Was kam dabei raus, als du das gemacht hast?

Hast du das:
https://forum.iobroker.net/topic/51555/hinweise-für-gute-forenbeiträge

jemals gelesen?

[Happyuser20]

Sorry, ich bin ein wenig durcheinander, ein wenig Panik ist dabei!
Evtl. sollte ich ein wenig riger werden

Nach dem letzten Screenshot habe ich den Container neu gestartet.
Und jetzt installiert er alle Adapter nach und nach, sieht zumindest so aus.

Das war wohl wieder falsch ;)

[Homoran]

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Und jetzt installiert er alle Adapter nach und nach, sieht zumindest so aus

dann diesmal WARTEN und nicht stören!

[Happyuser20]

Guten Morgen
Er ist jetzt durch, einige Adapter funktionieren nicht mehr. Auch nach löschen und Neuinstallation funktioniert die VIS nicht mehr. Seite ist nicht erreichbar.
Aber ich muss alles noch mal neu machen. Ich habe vergessen den USB Port der Synology durchzureichen.

Noch eine andere Frage zum Thema. Mein MQTT-Server kann auch keine Verbindung zu den Devices aufbauen oder umgekehrt. Muss ich den Port von MQTT auch durchreichen?

Gruß
HappyUser20

[Homoran]

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Ich habe vergessen den USB Port der Synology durchzureichen.

Deswegen sind mir Container jeder Art zu kompliziert

@Happyuser20 sagte in IOB im Docker Startet nicht mehr!!!:

Muss ich den Port von MQTT auch durchreichen?

sehr wahrscheinlich! Das müsstest du wahrscheinlich besser wissen als ich.

[haselchen]

@Happyuser20

Als was hast Du den Container installiert?
Ich hoffe als Host.
Ansonsten wird das hier ausarten mit Hilfestellungen.
Bei Bridge musste alle Ports manuell freigeben.