NEWS
Backup / Restore von Raspberry Pi auf Synology [gelöst]
-
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
iobroker list instances
+ system.adapter.admin.0 : admin : IoBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : IoBroker - enabled + system.adapter.discovery.0 : discovery : IoBroker - enabled + system.adapter.info.0 : info : IoBroker - enabled + instance is alive -
@wendy2702 said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx Und wie genau hast du das restore gemacht?
Weil davon steht ja nichts im log.
ich habe den restore über backitup angestoßen
-
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
iobroker list instances
+ system.adapter.admin.0 : admin : IoBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : IoBroker - enabled + system.adapter.discovery.0 : discovery : IoBroker - enabled + system.adapter.info.0 : info : IoBroker - enabled + instance is alive@zoxx Geht doch ;-)
dann hat backitup auch wirklich noch nichts gemacht.
Bitte ioBroker neu starten, backitup unter Instanzen im Expertenmodus auf Logstufe debug stellen, dann nochmal den restore anstoßen und das debug log posten
-
@zoxx Geht doch ;-)
dann hat backitup auch wirklich noch nichts gemacht.
Bitte ioBroker neu starten, backitup unter Instanzen im Expertenmodus auf Logstufe debug stellen, dann nochmal den restore anstoßen und das debug log posten
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx Geht doch ;-)
dann hat backitup auch wirklich noch nichts gemacht.
Bitte ioBroker neu starten, backitup unter Instanzen im Expertenmodus auf Logstufe debug stellen, dann nochmal den restore anstoßen und das debug log posten
backitup.0 2021-07-07 12:23:37.169 debug (629) sendTo "restore" to system.adapter.admin.0 from system.adapter.backitup.0 backitup.0 2021-07-07 12:23:37.125 debug (629) set chmod for "/opt/iobroker/backups" successfully backitup.0 2021-07-07 12:23:32.452 debug (629) sendTo "list" to system.adapter.admin.0 from system.adapter.backitup.0 backitup.0 2021-07-07 12:23:30.446 debug (629) Backup list be read ... backitup.0 2021-07-07 12:23:26.827 debug (629) telegram-instance: telegram.0 backitup.0 2021-07-07 12:23:25.157 debug (629) No backup file was found backitup.0 2021-07-07 12:23:25.079 info (629) [iobroker] backup was activated at 02:40 every 1 day(s) backitup.0 2021-07-07 12:23:24.934 info (629) starting. Version 2.1.13 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.22.1, js-controller: 3.2.16 backitup.0 2021-07-07 12:23:24.563 debug (629) Plugin sentry Initialize Plugin (enabled=true) backitup.0 2021-07-07 12:23:24.106 debug (629) statesDB connected backitup.0 2021-07-07 12:23:24.105 debug (629) States connected to redis: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:24.046 debug (629) States create User PubSub Client backitup.0 2021-07-07 12:23:24.043 debug (629) States create System PubSub Client backitup.0 2021-07-07 12:23:24.030 debug (629) Redis States: Use Redis connection: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:24.026 debug (629) objectDB connected backitup.0 2021-07-07 12:23:24.011 debug (629) Objects connected to redis: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:23.989 debug (629) Objects client initialize lua scripts backitup.0 2021-07-07 12:23:23.987 debug (629) Objects create User PubSub Client backitup.0 2021-07-07 12:23:23.985 debug (629) Objects create System PubSub Client backitup.0 2021-07-07 12:23:23.981 debug (629) Objects client ready ... initialize now backitup.0 2021-07-07 12:23:23.920 debug (629) Redis Objects: Use Redis connection: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:17.437 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.436 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.434 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.429 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.428 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.427 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.427 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.426 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.425 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.424 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.414 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.411 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.410 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.394 warn (614) redis get backitup.0.history.iobrokerLastTime, error - Connection is closed. backitup.0 2021-07-07 12:23:17.393 warn (614) redis get backitup.0.history.html, error - Connection is closed. backitup.0 2021-07-07 12:23:17.392 warn (614) redis get backitup.0.history.json, error - Connection is closed. backitup.0 2021-07-07 12:23:17.391 warn (614) redis get backitup.0.history.iobrokerSuccess, error - Connection is closed. backitup.0 2021-07-07 12:23:17.390 warn (614) redis get backitup.0.history.ccuSuccess, error - Connection is closed. backitup.0 2021-07-07 12:23:17.389 warn (614) redis get backitup.0.oneClick.ccu, error - Connection is closed. backitup.0 2021-07-07 12:23:17.388 warn (614) redis get backitup.0.oneClick.iobroker, error - Connection is closed. backitup.0 2021-07-07 12:23:17.388 warn (614) redis get backitup.0.history.ccuLastTime, error - Connection is closed. backitup.0 2021-07-07 12:23:17.383 debug (614) No backup file was found backitup.0 2021-07-07 12:23:17.309 info (614) [iobroker] backup was activated at 02:40 every 1 day(s) backitup.0 2021-07-07 12:23:17.168 info (614) starting. Version 2.1.13 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.22.1, js-controller: 3.2.16 backitup.0 2021-07-07 12:23:16.788 info (614) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason backitup.0 2021-07-07 12:23:16.787 debug (614) Plugin sentry destroyed backitup.0 2021-07-07 12:23:16.772 debug (614) statesDB connected backitup.0 2021-07-07 12:23:16.770 debug (614) States connected to redis: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:16.744 debug (614) States create User PubSub Client backitup.0 2021-07-07 12:23:16.742 debug (614) States create System PubSub Client backitup.0 2021-07-07 12:23:16.727 debug (614) Redis States: Use Redis connection: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:16.723 debug (614) objectDB connected backitup.0 2021-07-07 12:23:16.704 debug (614) Objects connected to redis: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:16.672 debug (614) Objects client initialize lua scripts backitup.0 2021-07-07 12:23:16.670 debug (614) Objects create User PubSub Client backitup.0 2021-07-07 12:23:16.668 debug (614) Objects create System PubSub Client backitup.0 2021-07-07 12:23:16.664 debug (614) Objects client ready ... initialize now backitup.0 2021-07-07 12:23:16.602 debug (614) Redis Objects: Use Redis connection: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:08.483 info (171) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason backitup.0 2021-07-07 12:23:08.480 info (171) terminating backitup.0 2021-07-07 12:23:08.478 info (171) cleaned everything up... backitup.0 2021-07-07 12:23:08.475 info (171) Got terminate signal TERMINATE_YOURSELF -
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx Geht doch ;-)
dann hat backitup auch wirklich noch nichts gemacht.
Bitte ioBroker neu starten, backitup unter Instanzen im Expertenmodus auf Logstufe debug stellen, dann nochmal den restore anstoßen und das debug log posten
backitup.0 2021-07-07 12:23:37.169 debug (629) sendTo "restore" to system.adapter.admin.0 from system.adapter.backitup.0 backitup.0 2021-07-07 12:23:37.125 debug (629) set chmod for "/opt/iobroker/backups" successfully backitup.0 2021-07-07 12:23:32.452 debug (629) sendTo "list" to system.adapter.admin.0 from system.adapter.backitup.0 backitup.0 2021-07-07 12:23:30.446 debug (629) Backup list be read ... backitup.0 2021-07-07 12:23:26.827 debug (629) telegram-instance: telegram.0 backitup.0 2021-07-07 12:23:25.157 debug (629) No backup file was found backitup.0 2021-07-07 12:23:25.079 info (629) [iobroker] backup was activated at 02:40 every 1 day(s) backitup.0 2021-07-07 12:23:24.934 info (629) starting. Version 2.1.13 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.22.1, js-controller: 3.2.16 backitup.0 2021-07-07 12:23:24.563 debug (629) Plugin sentry Initialize Plugin (enabled=true) backitup.0 2021-07-07 12:23:24.106 debug (629) statesDB connected backitup.0 2021-07-07 12:23:24.105 debug (629) States connected to redis: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:24.046 debug (629) States create User PubSub Client backitup.0 2021-07-07 12:23:24.043 debug (629) States create System PubSub Client backitup.0 2021-07-07 12:23:24.030 debug (629) Redis States: Use Redis connection: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:24.026 debug (629) objectDB connected backitup.0 2021-07-07 12:23:24.011 debug (629) Objects connected to redis: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:23.989 debug (629) Objects client initialize lua scripts backitup.0 2021-07-07 12:23:23.987 debug (629) Objects create User PubSub Client backitup.0 2021-07-07 12:23:23.985 debug (629) Objects create System PubSub Client backitup.0 2021-07-07 12:23:23.981 debug (629) Objects client ready ... initialize now backitup.0 2021-07-07 12:23:23.920 debug (629) Redis Objects: Use Redis connection: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:17.437 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.436 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.434 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.429 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.428 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.427 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.427 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.426 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.425 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.424 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.414 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.411 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.410 warn (614) get state error: Connection is closed. backitup.0 2021-07-07 12:23:17.394 warn (614) redis get backitup.0.history.iobrokerLastTime, error - Connection is closed. backitup.0 2021-07-07 12:23:17.393 warn (614) redis get backitup.0.history.html, error - Connection is closed. backitup.0 2021-07-07 12:23:17.392 warn (614) redis get backitup.0.history.json, error - Connection is closed. backitup.0 2021-07-07 12:23:17.391 warn (614) redis get backitup.0.history.iobrokerSuccess, error - Connection is closed. backitup.0 2021-07-07 12:23:17.390 warn (614) redis get backitup.0.history.ccuSuccess, error - Connection is closed. backitup.0 2021-07-07 12:23:17.389 warn (614) redis get backitup.0.oneClick.ccu, error - Connection is closed. backitup.0 2021-07-07 12:23:17.388 warn (614) redis get backitup.0.oneClick.iobroker, error - Connection is closed. backitup.0 2021-07-07 12:23:17.388 warn (614) redis get backitup.0.history.ccuLastTime, error - Connection is closed. backitup.0 2021-07-07 12:23:17.383 debug (614) No backup file was found backitup.0 2021-07-07 12:23:17.309 info (614) [iobroker] backup was activated at 02:40 every 1 day(s) backitup.0 2021-07-07 12:23:17.168 info (614) starting. Version 2.1.13 in /opt/iobroker/node_modules/iobroker.backitup, node: v12.22.1, js-controller: 3.2.16 backitup.0 2021-07-07 12:23:16.788 info (614) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason backitup.0 2021-07-07 12:23:16.787 debug (614) Plugin sentry destroyed backitup.0 2021-07-07 12:23:16.772 debug (614) statesDB connected backitup.0 2021-07-07 12:23:16.770 debug (614) States connected to redis: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:16.744 debug (614) States create User PubSub Client backitup.0 2021-07-07 12:23:16.742 debug (614) States create System PubSub Client backitup.0 2021-07-07 12:23:16.727 debug (614) Redis States: Use Redis connection: 127.0.0.1:9000 backitup.0 2021-07-07 12:23:16.723 debug (614) objectDB connected backitup.0 2021-07-07 12:23:16.704 debug (614) Objects connected to redis: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:16.672 debug (614) Objects client initialize lua scripts backitup.0 2021-07-07 12:23:16.670 debug (614) Objects create User PubSub Client backitup.0 2021-07-07 12:23:16.668 debug (614) Objects create System PubSub Client backitup.0 2021-07-07 12:23:16.664 debug (614) Objects client ready ... initialize now backitup.0 2021-07-07 12:23:16.602 debug (614) Redis Objects: Use Redis connection: 127.0.0.1:9001 backitup.0 2021-07-07 12:23:08.483 info (171) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason backitup.0 2021-07-07 12:23:08.480 info (171) terminating backitup.0 2021-07-07 12:23:08.478 info (171) cleaned everything up... backitup.0 2021-07-07 12:23:08.475 info (171) Got terminate signal TERMINATE_YOURSELF@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Redis Objects: Use Redis connection: 127.0.0.1:9001
was sagt
iobroker statusEDIT:
nee, scheint zu passenaber:
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
backitup.0 2021-07-07 12:23:17.383 debug (614) No backup file was found
also nochmal zum Anfang!
@wendy2702 sagte in Backup / Restore von Raspberry Pi auf Synology:
Und wie genau hast du das restore gemacht?
-
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Redis Objects: Use Redis connection: 127.0.0.1:9001
was sagt
iobroker statusEDIT:
nee, scheint zu passenaber:
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
backitup.0 2021-07-07 12:23:17.383 debug (614) No backup file was found
also nochmal zum Anfang!
@wendy2702 sagte in Backup / Restore von Raspberry Pi auf Synology:
Und wie genau hast du das restore gemacht?
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
iobroker status
iobroker is running on this host. Objects type: file States type: file -
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
iobroker status
iobroker is running on this host. Objects type: file States type: file@zoxx Danke - hab`s gerade editiert
-
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
iobroker status
iobroker is running on this host. Objects type: file States type: file@zoxx lief Redis auf dem RasPi?
-
@wendy2702 sagte in Backup / Restore von Raspberry Pi auf Synology:
sieht so aus.
genau!
@ZoXx
was sagt denn der RasPi beiiobroker status? -
@wendy2702 sagte in Backup / Restore von Raspberry Pi auf Synology:
sieht so aus.
genau!
@ZoXx
was sagt denn der RasPi beiiobroker status? -
@wendy2702 sagte in Backup / Restore von Raspberry Pi auf Synology:
sieht so aus.
genau!
@ZoXx
was sagt denn der RasPi beiiobroker status? -
@ZoXx
was sagt denn der RasPi beiiobroker status?iobroker is running on this host. Objects type: file States type: file@zoxx Danke!
Dann muss jetzt ein Docker-kundiger ran warum die Verbindung geschlossen wird
-
@zoxx Danke!
Dann muss jetzt ein Docker-kundiger ran warum die Verbindung geschlossen wird
-
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Problem ist jedoch, wenn ich ein Backup aus dem Raspberry Pi einspiele.
. Jedoch startet zwar der restore, allerdings passiert selbst nach ca. 2 Stunden nichts.
Nimm den Fußweg :
https://forum.iobroker.net/topic/46155/umzug-von-einem-docker-in-einen-anderen
-
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
aber auf dem Pi hattest du doch mit puTTY gearbeitet, dann muss das hier doch auch gehen.
Genau, da läuft das System aber direkt so installiert.
@homoran said in Backup / Restore von Raspberry Pi auf Synology:
kenne mich mit Docker nicht aus
Ich bin dort auch Neuling, muss mich in den Docker einloggen und dann schauen, Der meckert aber noch bei Synology immer, wenn ich da rein möchte.
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Der meckert aber noch bei Synology immer, wenn ich da rein möchte.
Welches Problem hast du noch , siehe hier ?
https://forum.iobroker.net/topic/30656/zugriff-auf-iobroker-nicht-mehr-möglich/12
-
@zoxx bin zwar kein dockerianer, aber hast du noch DSM6, oder schon DSM7 auf der syno?
bei der neuen 7er spinnt noch einiges rum. z.b. PLEX hat auch probleme damit.@da_woody said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx bin zwar kein dockerianer, aber hast du noch DSM6, oder schon DSM7 auf der syno?
bei der neuen 7er spinnt noch einiges rum. z.b. PLEX hat auch probleme damit.bin auf dem neuen 7er seit letzte Woche. Läuft bisher tatsächlich tadellos.
-
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Problem ist jedoch, wenn ich ein Backup aus dem Raspberry Pi einspiele.
. Jedoch startet zwar der restore, allerdings passiert selbst nach ca. 2 Stunden nichts.
Nimm den Fußweg :
https://forum.iobroker.net/topic/46155/umzug-von-einem-docker-in-einen-anderen
@glasfaser said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Problem ist jedoch, wenn ich ein Backup aus dem Raspberry Pi einspiele.
. Jedoch startet zwar der restore, allerdings passiert selbst nach ca. 2 Stunden nichts.
Nimm den Fußweg :
https://forum.iobroker.net/topic/46155/umzug-von-einem-docker-in-einen-anderen
habe es mal so angeschmissen. Ich berichte! :)
@glasfaser said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Der meckert aber noch bei Synology immer, wenn ich da rein möchte.
Welches Problem hast du noch , siehe hier ?
https://forum.iobroker.net/topic/30656/zugriff-auf-iobroker-nicht-mehr-möglich/12
Problem war eher, dass der Reverse Proxy angepasst werden musste, damit ich überhaupt Zugriff wieder erlange.
-
@glasfaser said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Problem ist jedoch, wenn ich ein Backup aus dem Raspberry Pi einspiele.
. Jedoch startet zwar der restore, allerdings passiert selbst nach ca. 2 Stunden nichts.
Nimm den Fußweg :
https://forum.iobroker.net/topic/46155/umzug-von-einem-docker-in-einen-anderen
habe es mal so angeschmissen. Ich berichte! :)
@glasfaser said in Backup / Restore von Raspberry Pi auf Synology:
@zoxx sagte in Backup / Restore von Raspberry Pi auf Synology:
Der meckert aber noch bei Synology immer, wenn ich da rein möchte.
Welches Problem hast du noch , siehe hier ?
https://forum.iobroker.net/topic/30656/zugriff-auf-iobroker-nicht-mehr-möglich/12
Problem war eher, dass der Reverse Proxy angepasst werden musste, damit ich überhaupt Zugriff wieder erlange.
@da_Woody backup ist durchgelaufen, kann jedoch den Container nicht mehr auflösen.
Folgende Fehlermeldung in Chrome: ERR_EMPTY_RESPONSEIch kopiere mal den Log:
2021-07-07 20:07:29.311 - [32minfo[39m: host.IoBroker received SIGTERM 2021-07-07 20:07:29.318 - [32minfo[39m: admin.0 (110) terminating http server on port 8081 2021-07-07 20:07:29.319 - [32minfo[39m: info.0 (152) cleaned everything up... 2021-07-07 20:07:29.332 - [32minfo[39m: backitup.0 (629) cleaned everything up... 2021-07-07 20:07:29.331 - [32minfo[39m: host.IoBroker stopInstance system.adapter.admin.0 (force=false, process=true) 2021-07-07 20:07:29.332 - [32minfo[39m: host.IoBroker stopInstance system.adapter.discovery.0 (force=false, process=true) 2021-07-07 20:07:29.334 - [32minfo[39m: host.IoBroker stopInstance system.adapter.info.0 (force=false, process=true) 2021-07-07 20:07:29.336 - [32minfo[39m: host.IoBroker stopInstance system.adapter.backitup.0 (force=false, process=true) 2021-07-07 20:07:29.352 - [32minfo[39m: admin.0 (110) Got terminate signal TERMINATE_YOURSELF 2021-07-07 20:07:29.355 - [32minfo[39m: info.0 (152) Got terminate signal TERMINATE_YOURSELF 2021-07-07 20:07:29.354 - [32minfo[39m: discovery.0 (125) Got terminate signal TERMINATE_YOURSELF 2021-07-07 20:07:29.356 - [32minfo[39m: backitup.0 (629) Got terminate signal TERMINATE_YOURSELF 2021-07-07 20:07:29.362 - [32minfo[39m: discovery.0 (125) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2021-07-07 20:07:29.363 - [32minfo[39m: host.IoBroker stopInstance system.adapter.admin.0 send kill signal 2021-07-07 20:07:29.364 - [32minfo[39m: info.0 (152) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2021-07-07 20:07:29.365 - [32minfo[39m: admin.0 (110) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2021-07-07 20:07:29.366 - [34mdebug[39m: backitup.0 (629) Plugin sentry destroyed 2021-07-07 20:07:29.367 - [32minfo[39m: backitup.0 (629) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2021-07-07 20:07:29.401 - [32minfo[39m: host.IoBroker stopInstance system.adapter.discovery.0 send kill signal 2021-07-07 20:07:29.402 - [32minfo[39m: host.IoBroker stopInstance system.adapter.info.0 send kill signal 2021-07-07 20:07:29.403 - [32minfo[39m: host.IoBroker stopInstance system.adapter.backitup.0 send kill signal 2021-07-07 20:07:30.224 - [32minfo[39m: host.IoBroker instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-07-07 20:07:30.275 - [32minfo[39m: host.IoBroker instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-07-07 20:07:30.278 - [32minfo[39m: host.IoBroker instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-07-07 20:07:30.279 - [32minfo[39m: host.IoBroker instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-07-07 20:07:30.280 - [32minfo[39m: host.IoBroker All instances are stopped. 2021-07-07 20:07:30.374 - [32minfo[39m: host.IoBroker terminated 2021-07-07 20:35:29.873 - [32minfo[39m: host.98f3f68508a4 iobroker.js-controller version 3.2.16 js-controller starting 2021-07-07 20:35:29.883 - [32minfo[39m: host.98f3f68508a4 Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-07-07 20:35:29.884 - [32minfo[39m: host.98f3f68508a4 hostname: 98f3f68508a4, node: v12.22.1 2021-07-07 20:35:29.886 - [32minfo[39m: host.98f3f68508a4 ip addresses: 172.17.0.6 2021-07-07 20:35:30.785 - [32minfo[39m: host.98f3f68508a4 connected to Objects and States 2021-07-07 20:35:30.901 - [32minfo[39m: host.98f3f68508a4 added notifications configuration of host 2021-07-07 20:35:31.880 - [32minfo[39m: host.98f3f68508a4 Delete host system.host.IoBroker 2021-07-07 20:35:31.981 - [32minfo[39m: host.98f3f68508a4 28 instances found 2021-07-07 20:35:32.016 - [33mwarn[39m: host.98f3f68508a4 does not start any instances on this host
Support us
568
Online32.4k
Benutzer81.5k
Themen1.3m
Beiträge