Kein Start nach Backup möglich / Unraid Docker

[Marc Berg]

@bass-ti sagte in Kein Start nach Backup möglich / Unraid Docker:

Wenn der Docker gestartet wird, läuft alles laut Log sauber durch.
Die Oberfläche startet jedoch nicht.

Versuche mal ein

iob host this

Es könnte sein, dass es ein Problem mit dem Hostnamen gibt, wenn der Name im Backup vom jetzigen Hostnamen abweicht.

[Bass-Ti]

@dp20eic

root@fa845846d6ac:/opt/iobroker# iob diag
root@fa845846d6ac:/opt/iobroker# netstat -tulpe
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       User       Inode      PID/Program name    
tcp        0      0 127.0.0.11:37859        0.0.0.0:*               LISTEN      root       15054605   -                   
tcp        0      0 localhost:9000          0.0.0.0:*               LISTEN      iobroker   15063313   -                   
tcp        0      0 localhost:9001          0.0.0.0:*               LISTEN      iobroker   15063306   -                   
udp        0      0 127.0.0.11:41409        0.0.0.0:*                           root       15054604   -                   
root@fa845846d6ac:/opt/iobroker# 

root@fa845846d6ac:/opt/iobroker# iob host this
Cannot execute changes on running system. Stop iobroker first.
root@fa845846d6ac:/opt/iobroker# iobroker stop
iobroker controller daemon is not running
root@fa845846d6ac:/opt/iobroker# iobroker stop all
The adapter "admin.0" was stopped.
The adapter "backitup.0" was stopped.
root@fa845846d6ac:/opt/iobroker# iob host this
Cannot execute changes on running system. Stop iobroker first.
root@fa845846d6ac:/opt/iobroker# 

leider keinen erfolg

[Marc Berg]

@bass-ti sagte in Kein Start nach Backup möglich / Unraid Docker:

leider keinen erfolg
Cannot execute changes on running system. Stop iobroker first.

m on
iob host this
m off

iob start all

https://github.com/buanet/ioBroker.docker/issues/188

buanet created this issue in buanet/ioBroker.docker

closed After restore in container with new hostname - ioBroker not running/ admin not accessible #188

[Bass-Ti]

@marc-berg danke, da hat sich zumindest etwas getan.

--------------------------------------------------------------------------------
----- 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.

(Re)setting permissions (This might take a while! Please be patient!)... Done.

Fixing "sudo-bug" by replacing sudo with gosu... Done.

Checking Database connection... Done.

/opt/iobroker/node_modules/standard-as-callback/built/index.js:6
throw e;



Error: Connection is closed.

at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
at Readable.read (node:internal/streams/readable:496:12)
at resume_ (node:internal/streams/readable:999:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ScanStream instance at:

at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v18.17.1
/opt/iobroker/node_modules/standard-as-callback/built/index.js:6
throw e;



Error: Connection is closed.

at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
at Redis.scan (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
at ScanStream._read (/opt/iobroker/node_modules/ioredis/built/ScanStream.js:36:41)
at Readable.read (node:internal/streams/readable:496:12)
at resume_ (node:internal/streams/readable:999:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ScanStream instance at:

at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v18.17.1
There was a problem detecting the admin instance of your iobroker.
Make sure the ioBroker installation you use has an admin instance or try again with a fresh installation and restore your configuration.
For more details see https://docs.buanet.de/iobroker-docker-image/docs/#restore

This Script will exit now.
There was a problem detecting the admin instance of your iobroker.
Make sure the ioBroker installation you use has an admin instance or try again with a fresh installation and restore your configuration.
For more details see https://docs.buanet.de/iobroker-docker-image/docs/#restore

This Script will exit now.

[Bass-Ti]

@bass-ti ich habe den docker noch einmal neugestartet und zumindest scheint die oberfläche vom admin zu laufen. Muss erst einmal los und prüfe dann noch einmal später nach, danke erst einmal.

[Bass-Ti]

@bass-ti

Danke! iobroker ist jetzt wieder gestartet, leider hat die VIS wohl ein großes Problem.

[Marc Berg]

@bass-ti sagte in Kein Start nach Backup möglich / Unraid Docker:

leider hat die VIS wohl ein großes Problem.

Ja, ist ein bekanntes VIS Problem nach dem Restore. Suche mal hier im Forum, da wirst du schnell fündig.

[Bass-Ti]

@bass-ti

da stelle ich mich wohl etwas dümmlich an, beiträge finde ich einige. jedoch nur viel bla bla und keine lösung.

[Marc Berg]

@bass-ti

https://forum.iobroker.net/topic/67945/restore-auf-bookworm-vis-ohne-funktion/3?_=1694324500620

[warp735]

Erst den vis Adapter manuell installieren und ERST DANN das Backup starten. Hat mich damals auch einige Nerven gekostet

[Bass-Ti]

Danke euch! So hat jetzt auch alles wieder funktioniert.