UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Basti81]

@glasfaser das ist leider alles was ich im Log sehe nachdem ich den Restore gemacht habe (iobroker restore 0) und anschließen iob start:

2023-05-07 22:14:16.115  - info: host.iobrokerpi iobroker.js-controller version 4.0.24 js-controller starting
2023-05-07 22:14:16.117  - info: host.iobrokerpi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2023-05-07 22:14:16.117  - info: host.iobrokerpi hostname: iobrokerpi, node: v18.16.0
2023-05-07 22:14:16.118  - info: host.iobrokerpi ip addresses: 192.168.178.100 2003:e5:f749:200:9209:d0ff:fe32:ee4 fe80::9209:d0ff:fe32:ee4 172.18.0.1 fe80::42:61ff:fed4:5012 172.17.0.1 fe80::42:78ff:fe4d:9345 fe80::ccac:35ff:fe52:594a fe80::4819:c2ff:fee1:e247 fe80::301e:e6ff:feec:9aa2
2023-05-07 22:14:46.125  - error: host.iobrokerpi No connection to databases possible, restart
2023-05-07 22:14:46.129  - info: host.iobrokerpi iobroker _restart
2023-05-07 22:14:46.506  - info: host.iobrokerpi iobroker Starting node restart.js
2023-05-07 22:14:46.979  - info: host.iobrokerpi received SIGTERM
2023-05-07 22:14:46.992  - warn: host.iobrokerpi get state error: Connection is closed.
2023-05-07 22:14:46.993  - info: host.iobrokerpi terminated
2023-05-07 22:14:53.436  - info: host.iobrokerpi iobroker.js-controller version 4.0.24 js-controller starting
2023-05-07 22:14:53.439  - info: host.iobrokerpi Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2023-05-07 22:14:53.439  - info: host.iobrokerpi hostname: iobrokerpi, node: v18.16.0
2023-05-07 22:14:53.439  - info: host.iobrokerpi ip addresses: 192.168.178.100 2003:e5:f749:200:9209:d0ff:fe32:ee4 fe80::9209:d0ff:fe32:ee4 172.18.0.1 fe80::42:61ff:fed4:5012 172.17.0.1 fe80::42:78ff:fe4d:9345 fe80::ccac:35ff:fe52:594a fe80::4819:c2ff:fee1:e247 fe80::301e:e6ff:feec:9aa2

Das wiederholt sich dann...

Restore war aber erfolgreich lt. shell:

Reinstalling adapter "admin" from "iobroker.admin@6.3.5"                                              
                                                                                                      
added 80 packages in 8s                                                                               
                                                                                                      
20 packages are looking for funding                                                                   
  run `npm fund` for details                                                                          
Reinstalling adapter "backitup" from "iobroker.backitup@2.6.19"                                       
                                                                                                      
added 94 packages in 9s                                                                               
                                                                                                      
33 packages are looking for funding                                                                   
  run `npm fund` for details                                                                          
System successfully restored! 

[Glasfaser]

@basti81 sagte in Migration Pi4 > Synology Docker:

iobroker restore 0

Warum nicht über den Adapter Backitup !?

[Homoran]

@basti81 sagte in Migration Pi4 > Synology Docker:

Restore war aber erfolgreich lt. shell:

nein, nur die Konfigurationsdateien wurden erfolgreich wieder hergestellt.
Anhand derer wird dann das gesamte System neu gebaut, was je nach Hardware und Umfang auch gerne mal 1h dauern jann.
In dieser Zeit darf nichts am System verändert werden damit es nicht zu einer Störungvder Prozesse und damit ggf. zu einem undefinierten Zustand kommt.

[Basti81]

@glasfaser hatte ich auch versucht mit dem gleichen Ergebnis nur dann startet das System autom. durch und ich komme gar nicht mehr an den Container ran per ssh da er andauernd von selbst neu startet (wahrscheinlich wegen des Startup bash scripts von buanet.

[Glasfaser]

@Basti81

Zeige das DSM Log !

@glasfaser sagte in Migration Pi4 > Synology Docker:
@basti81 sagte in Migration Pi4 > Synology Docker:

Das steht im DSM Container Protokoll

Please check your configuration and try again.

Zeige mal von Anfang an das Log !

[Basti81]

@homoran nach dem restore mit Backitup startet der Container durch. Dann sehe ich im Protokoll folgendes:

--------------------------------------
-----                   Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
This is not the first run of this container. Skipping first run preparation.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in "/opt/iobroker".
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
Checking Database connection... Failed.
Please check your configuration and try again.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
 
This Script will exit now.

[Glasfaser]

@basti81 sagte in Migration Pi4 > Synology Docker:

Dann sehe ich im Protokoll folgendes:

Der Anfang fehlt .

Zeige mal eine DEBUG Ausgabe :

Eintrag in Environment Variables ( ENV )

DEBUG:               true

und dann das Log hier posten

[Basti81]

@glasfaser ah ok, anbei das Log:

--------------------------------------------------
-----                   Step 1 of 5: Preparing container                   -----
--------------------------------------------------------------------------------
 
This is not the first run of this container. Skipping first run preparation.
 
--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------
 
Existing installation of ioBroker detected in "/opt/iobroker".
 
--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
[DEBUG] Checking multihost settings... 
[DEBUG] No multihost settings detected.
[DEBUG] Done.
 
[DEBUG] Checking custom objects db settings... 
[DEBUG] No custom objects db settings detected.
[DEBUG] Done.
 
[DEBUG] Checking custom states db settings... 
[DEBUG] No custom states db settings detected.
[DEBUG] Done.
 
Checking Database connection... Failed.
[DEBUG] Error message: 
[DEBUG] No connection to states 0.0.0.0:6379[redis]
Please check your configuration and try again.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
 
[DEBUG] Debug mode prevents the container from exiting on errors.
[DEBUG] This enables you to investigate or fix your issue on the command line.
[DEBUG] If you want to stop or restart your container you have to do it manually.
[DEBUG] IoBroker is not running!

[Glasfaser]

@basti81 sagte in Migration Pi4 > Synology Docker:

[DEBUG] No connection to states 0.0.0.0:6379[redis]

Redis:

Hast du das so auf der Pi !?

[Basti81]

@glasfaser auf dem Pi:

pi@iobrokerpi:~ $ sudo redis-server -v
Redis server v=5.0.14 sha=00000000:0 malloc=libc bits=32 build=ddd3b1f304a7d4d5

In dem Container:

root@iobrokerpi:/opt/iobroker# redis-server -v                                                        
bash: redis-server: command not found

[Glasfaser]

@basti81

https://github.com/buanet/ioBroker.docker/issues/136#issuecomment-710220772

[Basti81]

@glasfaser den Container habe ich über die GUI aktiviert und das gibt es nur diese ENV:

[Glasfaser]

@basti81 sagte in Migration Pi4 > Synology Docker:

das gibt es nur diese ENV:

Ja das ist der Standart ,

extras siehe hier unter :

Configuration via environment variables

https://hub.docker.com/r/buanet/iobroker

[Basti81]

@glasfaser wir kommen der Sache näher :-)

-------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
[DEBUG] Checking multihost settings... 
[DEBUG] No multihost settings detected.
[DEBUG] Done.
 
Configuring custom objects db...
IOB_OBJECTSDB_TYPE is available and value meets detected ioBroker installation.
IOB_OBJECTSDB_HOST is available and value meets detected ioBroker installation.
IOB_OBJECTSDB_PORT is available and value meets detected ioBroker installation.
Done.
 
Configuring custom states db...
IOB_STATESDB_TYPE is available and value meets detected ioBroker installation.
IOB_STATESDB_HOST is available and value meets detected ioBroker installation.
IOB_STATESDB_PORT is available but value is different from detected ioBroker installation.
Setting port of states db to "9000"... Done.
Done.
 
Checking Database connection... Failed.
[DEBUG] Error message: 
[DEBUG] No connection to objects 127.0.0.1:9001[redis]
Please check your configuration and try again.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
 
[DEBUG] Debug mode prevents the container from exiting on errors.
[DEBUG] This enables you to investigate or fix your issue on the command line.
[DEBUG] If you want to stop or restart your container you have to do it manually.
[DEBUG] IoBroker is not running!

[Glasfaser]

@basti81 sagte in Migration Pi4 > Synology Docker:

No connection to objects 127.0.0.1:9001[redis]

Warum 9001

@basti81 sagte in Migration Pi4 > Synology Docker:
[DEBUG] No connection to states 0.0.0.0:6379[redis]

[Glasfaser]

@basti81

zu Redis auch :

https://smarthome.buanet.de/2020/12/iobroker-docker-container-mit-redis-db-verbinden/

[Basti81]

@glasfaser hab jetzt den 6379 versucht und ich bekomme den gleichen Fehler:

-----------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------
 
(Re)setting permissions (This might take a while! Please be patient!)... Done.
 
Fixing "sudo-bug" by replacing sudo with gosu... Done.
 
[DEBUG] Checking multihost settings... 
[DEBUG] No multihost settings detected.
[DEBUG] Done.
 
Configuring custom objects db...
IOB_OBJECTSDB_TYPE is available and value meets detected ioBroker installation.
IOB_OBJECTSDB_HOST is available and value meets detected ioBroker installation.
IOB_OBJECTSDB_PORT is available but value is different from detected ioBroker installation.
Setting port of objects db to "6379"... Done.
Done.
 
Configuring custom states db...
IOB_STATESDB_TYPE is available and value meets detected ioBroker installation.
IOB_STATESDB_HOST is available and value meets detected ioBroker installation.
IOB_STATESDB_PORT is available but value is different from detected ioBroker installation.
Setting port of states db to "6379"... Done.
Done.
 
Checking Database connection... Failed.
[DEBUG] Error message: 
[DEBUG] No connection to objects 127.0.0.1:6379[redis]
Please check your configuration and try again.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs).
 
[DEBUG] Debug mode prevents the container from exiting on errors.
[DEBUG] This enables you to investigate or fix your issue on the command line.
[DEBUG] If you want to stop or restart your container you have to do it manually.
[DEBUG] IoBroker is not running!

Soll ich mal:
apt-get install redis-sentinel

im Container ausführen? Mich wundert das hier im Container:

root@iobrokerpi:/opt/iobroker# redis-server -v                                                        
bash: redis-server: command not found

[Glasfaser]

@basti81 sagte in Migration Pi4 > Synology Docker:

im Container ausführen?

kannst du machen ... aber beim nächsten Image wechsel ist er weg !

siehe meinen Link , da ist redis seperat als Container !

[Basti81]

@glasfaser danke dir. Habe die Container sauber neu aufgesetzt wie hier erläutert:
https://smarthome.buanet.de/2020/12/iobroker-docker-container-mit-redis-db-verbinden/

Alles läuft nun wie es soll und der Restore hat geklappt da die redis Verbindung von Anfang an funktionierte. Bridged Network war hier der Schlüssel. Mit Host network hat es nicht geklappt.

Danke dir!!!