Weihnachtsangebot 2025! 🎄

[dan11hh]

Moin Zusammen!
Ich hatte gestern den Elektriker da und infolgedessen war meine Synology DS218+ öfter stromlos. Leider funktionierte ioBroker nicht mehr. Der Host auf 8081 war offenbar nicht offen. Gut, ich hab ja ein Backup. Also die letzte Buanet Version als Docker Image runtergeladen um eine saubere Installation zu haben und dann mit dem Backup Adapter das Backup zurückspielen. Dachte ich zumindest. Leider startet auch die frisch installierte Buanet Version keinen Host.

Das Protokoll sieht eigentlich ganz ok aus, oder?
Fehlermeldung bei Eingabe von "iobroker start" übrigens:

iobroker controller daemon failed to start: 24

Jemand eine Idee? Mir ist irgendwie auch unklar wo/wie er die alte Version noch entdeckt.

                                                                                                                                                                                                                                            

--------------------------------------------------------------------------------
-------------------------     2022-03-19 14:14:19      -------------------------
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                 Welcome to your ioBroker-container!                  -----
-----                    Startupscript is now running.                     -----
-----                          Please be patient!                          -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                        Debugging information                         -----
-----                                                                      -----
-----                                System                                -----
-----                    arch:                x86_64                       -----
-----                    hostname:            ioBroker                     -----
-----                                                                      -----
-----                             Docker-Image                             -----
-----                    image:               v6.1.0                       -----
-----                    build:               2022-03-14T07:29:48+00:00    -----
-----                                                                      -----
-----                               Versions                               -----
-----                    node:                v14.19.0                     -----
-----                    npm:                 6.14.16                      -----
-----                                                                      -----
-----                                 ENV                                  -----
-----                    SETGID:              1000                         -----
-----                    SETUID:              1000                         -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                  Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
Updating Linux packages on first run...
Preconfiguring packages ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 32069 files and directories currently installed.)
Preparing to unpack .../libssl1.1_1.1.1k-1+deb11u2_amd64.deb ...
Unpacking libssl1.1:amd64 (1.1.1k-1+deb11u2) over (1.1.1k-1+deb11u1) ...
Setting up libssl1.1:amd64 (1.1.1k-1+deb11u2) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 32069 files and directories currently installed.)
Preparing to unpack .../nodejs_14.19.1-deb-1nodesource1_amd64.deb ...
Unpacking nodejs (14.19.1-deb-1nodesource1) over (14.19.0-deb-1nodesource1) ...
Preparing to unpack .../openssl_1.1.1k-1+deb11u2_amd64.deb ...
Unpacking openssl (1.1.1k-1+deb11u2) over (1.1.1k-1+deb11u1) ...
Setting up nodejs (14.19.1-deb-1nodesource1) ...
Setting up openssl (1.1.1k-1+deb11u2) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 66%

Reading package lists... 97%

Reading package lists... 97%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... 85%

Building dependency tree... Done

Reading state information... 0% 

Reading state information... 0%

Reading state information... Done

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 0%

Reading package lists... 65%

Reading package lists... 97%

Reading package lists... 97%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... 99%

Reading package lists... Done

Building dependency tree... 0%

Building dependency tree... 0%

Building dependency tree... 50%

Building dependency tree... 50%

Building dependency tree... 87%

Building dependency tree... Done

Reading state information... 0% 

Reading state information... 0%

Reading state information... Done

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Done.
 
Registering maintenance script as command...
Done.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in /opt/iobroker.
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)Setting folder permissions (This might take a while! Please be patient!)...
Done.
 
Fixing "sudo-bug" by replacing sudo in iobroker with gosu...
Done.
 
Hostname in ioBroker does not match the hostname of this container.
Updating hostname to  ioBroker...
The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "ioBroker".
The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "ioBroker".
The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "ioBroker".
Done.
 
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------
 
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
 
--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------
 
Starting ioBroker...
 
host.ioBroker check instance "system.adapter.admin.0" for host "ioBroker"
host.ioBroker check instance "system.adapter.discovery.0" for host "ioBroker"
host.ioBroker check instance "system.adapter.backitup.0" for host "ioBroker"
object system.meta.uuid created: dc8cc982-64f3-4937-9171-944e6012218f

[dan11hh]

@dan11hh Ok. Jetzt habe ich das Backup zurückspielen können. Soweit so gut. Jetzt habe ich aber offenbar eine anderes "Docker" Problem.
Die Ports bzw. Adressen sind nicht erreichbar für einige Adapter. Woran könnte das liegen? DANKE!!!!

host.ioBroker
2022-03-19 16:24:37.800	info	Restart adapter system.adapter.hm-rpc.2 because enabled
host.ioBroker
2022-03-19 16:24:37.800	error	instance system.adapter.hm-rpc.2 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2022-03-19 16:24:37.800	error	Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:83:21)
host.ioBroker
2022-03-19 16:24:37.796	error	Caught by controller[0]: at doListen (net.js:1516:7)
host.ioBroker
2022-03-19 16:24:37.795	error	Caught by controller[0]: at listenInCluster (net.js:1379:12)
host.ioBroker
2022-03-19 16:24:37.795	error	Caught by controller[0]: at Server.setupListenHandle [as _listen2] (net.js:1314:21)
host.ioBroker
2022-03-19 16:24:37.795	error	Caught by controller[0]: Error: listen EADDRNOTAVAIL: address not available 192.168.179.111:12001
host.ioBroker
2022-03-19 16:24:37.728	info	Restart adapter system.adapter.hm-rpc.5 because enabled
host.ioBroker
2022-03-19 16:24:37.728	error	instance system.adapter.hm-rpc.5 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2022-03-19 16:24:37.727	error	Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:83:21)
host.ioBroker
2022-03-19 16:24:37.727	error	Caught by controller[0]: at doListen (net.js:1516:7)
host.ioBroker
2022-03-19 16:24:37.727	error	Caught by controller[0]: at listenInCluster (net.js:1379:12)
host.ioBroker
2022-03-19 16:24:37.727	error	Caught by controller[0]: at Server.setupListenHandle [as _listen2] (net.js:1314:21)
host.ioBroker
2022-03-19 16:24:37.727	error	Caught by controller[0]: Error: listen EADDRNOTAVAIL: address not available 192.168.179.111:2001
host.ioBroker
2022-03-19 16:24:37.325	info	Restart adapter system.adapter.hm-rpc.3 because enabled
host.ioBroker
2022-03-19 16:24:37.325	error	instance system.adapter.hm-rpc.3 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2022-03-19 16:24:37.325	error	Caught by controller[0]: at processTicksAndRejections (internal/process/task_queues.js:83:21)
host.ioBroker
2022-03-19 16:24:37.324	error	Caught by controller[0]: at doListen (net.js:1516:7)
host.ioBroker
2022-03-19 16:24:37.324	error	Caught by controller[0]: at listenInCluster (net.js:1379:12)
host.ioBroker
2022-03-19 16:24:37.324	error	Caught by controller[0]: at Server.setupListenHandle [as _listen2] (net.js:1314:21)
host.ioBroker
2022-03-19 16:24:37.324	error	Caught by controller[0]: Error: listen EADDRNOTAVAIL: address not available 192.168.179.111:12010

hm-rpc.2
2022-03-19 16:24:37.146	error	Exception-Code: EADDRNOTAVAIL: listen EADDRNOTAVAIL: address not available 192.168.179.111:12001

hm-rpc.2
2022-03-19 16:24:37.145	error	Error: listen EADDRNOTAVAIL: address not available 192.168.179.111:12001 at Server.setupListenHandle [as _listen2] (net.js:1314:21) at listenInCluster (net.js:1379:12) at doListen (net.js:1516:7) at processTicksAndRejections (internal/process/task_queues.js:83:21)

hm-rpc.2
2022-03-19 16:24:37.145	error	uncaught exception: listen EADDRNOTAVAIL: address not available 192.168.179.111:12001

hm-rpc.5
2022-03-19 16:24:37.108	error	Exception-Code: EADDRNOTAVAIL: listen EADDRNOTAVAIL: address not available 192.168.179.111:2001

hm-rpc.5
2022-03-19 16:24:37.108	error	Error: listen EADDRNOTAVAIL: address not available 192.168.179.111:2001 at Server.setupListenHandle [as _listen2] (net.js:1314:21) at listenInCluster (net.js:1379:12) at doListen (net.js:1516:7) at processTicksAndRejections (internal/process/task_queues.js:83:21)

hm-rpc.5
2022-03-19 16:24:37.106	error	uncaught exception: listen EADDRNOTAVAIL: address not available 192.168.179.111:2001

hm-rpc.2
2022-03-19 16:24:37.144	error	Address 192.168.179.111 not available, maybe your HOST IP has changed due to migration

[Thomas Braun]

@dan11hh sagte in Probleme beim Backup zurückspielen:

address not available 192.168.179.111

Was ist/war denn das für ein System?

[dan11hh]

@thomas-braun
Moin Thomas! Danke für Deine Hilfe.
Das ist die Diskstation IP, also das Gerät auf dem Docker und dadrunter die ioBroker Installation läuft.

[wendy2702]

Musst du die Ports nicht erneut Freigeben wenn du einen neuen Docker einrichtest?

[dan11hh]

@wendy2702
Ja schon, aber eigentlich nur die die vom außen erreichbar sein sollen. Also zum Beispiel 8081.

[wendy2702]

@dan11hh Sicher?

Ich meinen mich an Threads erinnern zu können wo auch die HM Ports geöffnet werden mussten.

[dan11hh]

@wendy2702

Letztlich lag es daran, dass ich wohl in hmrpc eine Callback Adresse eintragen musste. Hatte ich initial auch nicht gemacht. Jetzt ist hmrpc wieder grün. freu Danke für die Hilfe!

[wendy2702]

@dan11hh sagte in Probleme beim Backup zurückspielen:

Callback Adresse eintragen musste

Welche musstest du denn eintragen?

Die vom Container oder die vom Interface?

[Ein ehemaliger Benutzer]

Moin zusammen,

ich möchte mich hier mal einklinken. Ich bekomme mein Backup ebenfalls nicht geladen.

Worum genau geht es: Ich bin von meinem Raspi 4 mit 2GB RAM auf einen Raspi 4 mit 8GB RAM umgezogen. Vorher habe ich mit Hilfe des Backup Adapters ein Backup auf mein Google Drive Konto gemacht.

Auf dem neuen sowie alten Raspi läuft DietPi. Der Unterschied ist allerdings das ich mir nun Docker + Portainer installiert habe und der 8GB Raspi ja bekanntlich unter der 64bit Version läuft, der 2GB Raspi nutzt 32bit.

Jedenfalls habe ich soweit alles erfolgreich installiert und wollte nun das Backup einspielen. Das Update startet, aber nach einiger Zeit kann ich im Container Log sehen, dass der Startup Prozess "zu hängen scheint". Auch habe ich im Log folgendes entdeckt:

Recived termination signal (SIGTERM).
Shutting down ioBroker...

Ich muss dazu sagen, dass das mein erstes Mal mit Docker / Portainer ist. Ich bitte um ein wenig Nachsicht :expressionless: .

Hier mal der komplette Log, beginnend mit dem Start des Einspielens.

================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]
Terminated
 
Recived termination signal (SIGTERM).
Shutting down ioBroker...
 
--------------------------------------------------------------------------------
-------------------------     2022-03-29 23:26:23      -------------------------
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                 Welcome to your ioBroker-container!                  -----
-----                    Startupscript is now running.                     -----
-----                          Please be patient!                          -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                        Debugging information                         -----
-----                                                                      -----
-----                                System                                -----
-----                    arch:                aarch64                      -----
-----                    hostname:            c82beff765d8                 -----
-----                                                                      -----
-----                             Docker-Image                             -----
-----                    image:               v6.1.0                       -----
-----                    build:               2022-03-14T07:29:48+00:00    -----
-----                                                                      -----
-----                               Versions                               -----
-----                    node:                v14.19.1                     -----
-----                    npm:                 6.14.16                      -----
-----                                                                      -----
-----                                 ENV                                  -----
-----                    SETGID:              1000                         -----
-----                    SETUID:              1000                         -----
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
-----                  Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
Nothing to do here.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in /opt/iobroker.
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)Setting folder permissions (This might take a while! Please be patient!)...
Done.
 
Fixing "sudo-bug" by replacing sudo in iobroker with gosu...
Done.
 
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------
 
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
 
--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------
 
Starting ioBroker...
 
================================== > LOG REDIRECT system.adapter.admin.0 => true [starting]
host.RaspberryPi check instance "system.adapter.admin.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.javascript.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.scenes.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.alexa2.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.mihome-vacuum.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.rpi2.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.tr-064.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.backitup.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.deconz.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.iot.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.nuki.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.sony-bravia.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.whatsapp-cmb.0" for host "c82beff765d8"
host.RaspberryPi check instance "system.adapter.yahka.0" for host "c82beff765d8"

Wie gesagt. Ab Schritt 5/5 befindet sich der iobroker in einem "Loop". Ich versuche es bereits seit Stunden mit Hilfe von Google selber zu lösen aber es führt zu nichts. Ist hier vielleicht das Problem, dass das Backup auf der 32bit Version erstellen worden ist? Oder dass das Backup vorher aus einem Nicht Docker System erstellt wurde und ich es nun im Docker betreiben möchte? Keine Ahnung. Meine Frau hängt mir jedenfalls bereits in den Ohren weil jetzt natürlich gar nichts mehr geht. Heizung, Licht etc.

Auch hatte ich im Verdacht das der iobroker Prozess einfach nicht starten will. Allerdings bringt ein "iobroker start" nur folgende Fehlermeldung:

root@c82beff765d8:/opt/iobroker# iobroker start
Starting iobroker controller daemon...
iobroker controller daemon failed to start:  24
An unknown error occurred: Error: 24

Auch ein restart des Containers hilft nicht. Hier bleibt der Restart auch bei Schritt 5/5 hängen. Die iobroker WebUI ist nun jedenfalls nicht mehr aufrufbar denn "Safari kann keine Verbindung zum Server aufbauen".

Ich hoffe es ist noch irgendwie zu retten.

Gruß