Restore läuft nicht weiter
-
@adamantium Im log sehe ich nichts auffälliges.
Und wenn du mit Browser auf die IP:8081 gehst kommt nichts?
Steht denn was im iobroker log:
cat /opt/iobroker/log/iobroker.current.log -
@adamantium sagte in Restore läuft nicht weiter:
und dann kommt nur die Summary.
nur wenn du das Summary startest.
-
@adamantium sagte in Restore läuft nicht weiter:
Docker: v8.0.0
host.dd14ecbc30a9 check instance "system.adapter.admin.0" for host "edfa9db59fd4"
Habe das schon zweimal mit dem Restore
pkill -u iobroker iobroker host thisdanach den Container neu starten
-
@wendy2702 said in Restore läuft nicht weiter:
@adamantium Im log sehe ich nichts auffälliges.
Und wenn du mit Browser auf die IP:8081 gehst kommt nichts?
Steht denn was im iobroker log:
cat /opt/iobroker/log/iobroker.current.logDas passiert:
[Marcel@Marcel ~]$ docker exec -i -t iobroker bash root@edfa9db59fd4:/opt/iobroker# cat /opt/iobroker/log/iobroker.current.log 2023-03-31 14:14:58.367 - info: host.edfa9db59fd4 iobroker.js-controller versio n 4.0.24 js-controller starting 2023-03-31 14:14:58.373 - info: host.edfa9db59fd4 Copyright (c) 2014-2022 bluef ox, 2014 hobbyquaker 2023-03-31 14:14:58.374 - info: host.edfa9db59fd4 hostname: edfa9db59fd4, node: v18.15.0 2023-03-31 14:14:58.375 - info: host.edfa9db59fd4 ip addresses: 192.168.1.49 2023-03-31 14:14:58.791 - info: host.edfa9db59fd4 connected to Objects and Stat es 2023-03-31 14:14:58.826 - info: host.edfa9db59fd4 Node.js version has changed f rom unknown to 18.15.0 2023-03-31 14:14:58.899 - info: host.edfa9db59fd4 added notifications configura tion of host 2023-03-31 14:14:59.182 - info: host.edfa9db59fd4 3 instances found 2023-03-31 14:14:59.191 - info: host.edfa9db59fd4 starting 3 instances 2023-03-31 14:14:59.243 - info: host.edfa9db59fd4 instance system.adapter.admin .0 started with pid 588 2023-03-31 14:14:59.530 - info: host.edfa9db59fd4 Successfully updated capabili ties "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-03-31 14:15:01.350 - info: admin.0 (588) starting. Version 6.3.5 in /opt/i obroker/node_modules/iobroker.admin, node: v18.15.0, js-controller: 4.0.24 2023-03-31 14:15:01.398 - info: admin.0 (588) requesting all states 2023-03-31 14:15:01.399 - info: admin.0 (588) requesting all objects 2023-03-31 14:15:01.596 - info: admin.0 (588) received all objects 2023-03-31 14:15:01.631 - info: admin.0 (588) Request actual repository... 2023-03-31 14:15:01.644 - info: host.edfa9db59fd4 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-03-31 14:15:01.651 - info: admin.0 (588) http server listening on port 808 1 2023-03-31 14:15:01.652 - info: admin.0 (588) Use link "http://localhost:8081" to configure. 2023-03-31 14:15:01.661 - info: admin.0 (588) socket.io server listening on por t 8081 2023-03-31 14:15:01.804 - warn: admin.0 (588) Repository cannot be read: Active repo - stable 2023-03-31 14:15:01.805 - warn: admin.0 (588) Active repository "stable" cannot be read 2023-03-31 14:15:03.215 - info: host.edfa9db59fd4 instance system.adapter.disco very.0 started with pid 603 2023-03-31 14:15:05.010 - info: discovery.0 (603) starting. Version 3.1.0 in /o pt/iobroker/node_modules/iobroker.discovery, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 14:15:07.401 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 630 2023-03-31 14:15:07.481 - info: admin.0 (588) Repository received successfully. 2023-03-31 14:15:09.494 - info: backitup.0 (630) starting. Version 2.5.12 in /o pt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0.2 4 2023-03-31 14:15:09.690 - info: backitup.0 (630) [iobroker] backup was activate d at 02:40 every 1 day(s) 2023-03-31 15:07:54.305 - info: admin.0 (588) ==> Connected system.user.admin f rom ::ffff:192.168.1.51 2023-03-31 15:08:51.640 - info: admin.0 (588) ==> Connected system.user.admin f rom ::ffff:192.168.1.51 2023-03-31 15:09:04.966 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 (force=false, process=true) 2023-03-31 15:09:04.975 - info: backitup.0 (630) Got terminate signal TERMINATE _YOURSELF 2023-03-31 15:09:04.977 - info: backitup.0 (630) cleaned everything up... 2023-03-31 15:09:04.978 - info: backitup.0 (630) terminating 2023-03-31 15:09:04.980 - info: backitup.0 (630) Terminated (ADAPTER_REQUESTED_ TERMINATION): Without reason 2023-03-31 15:09:05.015 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 send kill signal 2023-03-31 15:09:05.524 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:09:08.047 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 3338 2023-03-31 15:09:09.778 - info: backitup.0 (3338) starting. Version 2.5.12 in / opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 15:09:09.846 - info: backitup.0 (3338) Restarting Adapter because of changed Sentry settings 2023-03-31 15:09:09.847 - warn: backitup.0 (3338) Restart initiated 2023-03-31 15:09:09.849 - info: backitup.0 (3338) cleaned everything up... 2023-03-31 15:09:09.897 - info: backitup.0 (3338) terminating 2023-03-31 15:09:09.898 - info: backitup.0 (3338) Terminated (NO_ERROR): Withou t reason 2023-03-31 15:09:10.450 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 0 (NO_ERROR) 2023-03-31 15:09:10.450 - info: host.edfa9db59fd4 Restart adapter system.adapte r.backitup.0 because enabled 2023-03-31 15:09:27.084 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 3365 2023-03-31 15:09:28.707 - info: backitup.0 (3365) starting. Version 2.5.12 in / opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 15:09:28.854 - info: backitup.0 (3365) [iobroker] backup was activat ed at 02:40 every 1 day(s) 2023-03-31 15:09:30.646 - info: admin.0 (588) <== Disconnect system.user.admin from ::ffff:192.168.1.51 2023-03-31 15:09:34.037 - info: admin.0 (588) ==> Connected system.user.admin f rom ::ffff:192.168.1.51 2023-03-31 15:09:36.718 - error: backitup.0 (3365) FTP: Error: /backupDir: No s uch file or directory 2023-03-31 15:09:37.330 - error: backitup.0 (3365) FTP: Error: /backupDir: No s uch file or directory 2023-03-31 15:09:49.414 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 (force=false, process=true) 2023-03-31 15:09:49.419 - info: backitup.0 (3365) Got terminate signal TERMINAT E_YOURSELF 2023-03-31 15:09:49.421 - info: backitup.0 (3365) cleaned everything up... 2023-03-31 15:09:49.422 - info: backitup.0 (3365) terminating 2023-03-31 15:09:49.423 - info: backitup.0 (3365) Terminated (ADAPTER_REQUESTED _TERMINATION): Without reason 2023-03-31 15:09:49.458 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 send kill signal 2023-03-31 15:09:49.964 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:09:52.481 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 3405 2023-03-31 15:09:54.063 - info: backitup.0 (3405) starting. Version 2.5.12 in / opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 15:09:54.199 - info: backitup.0 (3405) [iobroker] backup was activat ed at 02:40 every 1 day(s) 2023-03-31 15:09:54.924 - error: backitup.0 (3405) FTP: Error: /backup_iobroker : No such file or directory 2023-03-31 15:10:10.325 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 (force=false, process=true) 2023-03-31 15:10:10.330 - info: backitup.0 (3405) Got terminate signal TERMINAT E_YOURSELF 2023-03-31 15:10:10.332 - info: backitup.0 (3405) cleaned everything up... 2023-03-31 15:10:10.333 - info: backitup.0 (3405) terminating 2023-03-31 15:10:10.334 - info: backitup.0 (3405) Terminated (ADAPTER_REQUESTED _TERMINATION): Without reason 2023-03-31 15:10:10.369 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 send kill signal 2023-03-31 15:10:10.876 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:10:13.002 - info: admin.0 (588) <== Disconnect system.user.admin from ::ffff:192.168.1.51 2023-03-31 15:10:13.393 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 3433 2023-03-31 15:10:14.908 - info: backitup.0 (3433) starting. Version 2.5.12 in / opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 15:10:15.028 - info: backitup.0 (3433) [iobroker] backup was activat ed at 02:40 every 1 day(s) 2023-03-31 15:10:15.743 - error: backitup.0 (3433) FTP: Error: /backup_iobroker /: No such file or directory 2023-03-31 15:10:17.465 - info: admin.0 (588) ==> Connected system.user.admin f rom ::ffff:192.168.1.51 2023-03-31 15:10:19.529 - error: backitup.0 (3433) FTP: Error: /backup_iobroker /: No such file or directory 2023-03-31 15:10:39.043 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 (force=false, process=true) 2023-03-31 15:10:39.047 - info: backitup.0 (3433) Got terminate signal TERMINAT E_YOURSELF 2023-03-31 15:10:39.048 - info: backitup.0 (3433) cleaned everything up... 2023-03-31 15:10:39.049 - info: backitup.0 (3433) terminating 2023-03-31 15:10:39.050 - info: backitup.0 (3433) Terminated (ADAPTER_REQUESTED _TERMINATION): Without reason 2023-03-31 15:10:39.086 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 send kill signal 2023-03-31 15:10:39.586 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:10:42.109 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 3472 2023-03-31 15:10:43.835 - info: backitup.0 (3472) starting. Version 2.5.12 in / opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 15:10:43.983 - info: backitup.0 (3472) [iobroker] backup was activat ed at 02:40 every 1 day(s) 2023-03-31 15:11:29.524 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 (force=false, process=true) 2023-03-31 15:11:29.529 - info: backitup.0 (3472) Got terminate signal TERMINAT E_YOURSELF 2023-03-31 15:11:29.531 - info: backitup.0 (3472) cleaned everything up... 2023-03-31 15:11:29.531 - info: backitup.0 (3472) terminating 2023-03-31 15:11:29.533 - info: backitup.0 (3472) Terminated (ADAPTER_REQUESTED _TERMINATION): Without reason 2023-03-31 15:11:29.568 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 send kill signal 2023-03-31 15:11:30.067 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:11:31.686 - info: admin.0 (588) <== Disconnect system.user.admin from ::ffff:192.168.1.51 2023-03-31 15:11:32.594 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 started with pid 3523 2023-03-31 15:11:34.107 - info: backitup.0 (3523) starting. Version 2.5.12 in / opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0. 24 2023-03-31 15:11:34.249 - info: backitup.0 (3523) [iobroker] backup was activat ed at 02:40 every 1 day(s) 2023-03-31 15:11:38.465 - info: admin.0 (588) ==> Connected system.user.admin f rom ::ffff:192.168.1.51 2023-03-31 15:12:20.313 - info: host.edfa9db59fd4 received SIGTERM 2023-03-31 15:12:20.315 - info: host.edfa9db59fd4 stopInstance system.adapter.a dmin.0 (force=false, process=true) 2023-03-31 15:12:20.315 - info: host.edfa9db59fd4 stopInstance system.adapter.d iscovery.0 (force=false, process=true) 2023-03-31 15:12:20.316 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 (force=false, process=true) 2023-03-31 15:12:20.322 - info: host.edfa9db59fd4 stopInstance system.adapter.a dmin.0 send kill signal 2023-03-31 15:12:20.322 - info: backitup.0 (3523) Got terminate signal TERMINAT E_YOURSELF 2023-03-31 15:12:20.323 - info: discovery.0 (603) Got terminate signal TERMINAT E_YOURSELF 2023-03-31 15:12:20.324 - info: host.edfa9db59fd4 stopInstance system.adapter.d iscovery.0 send kill signal 2023-03-31 15:12:20.325 - info: host.edfa9db59fd4 stopInstance system.adapter.b ackitup.0 send kill signal 2023-03-31 15:12:20.325 - info: admin.0 (588) Got terminate signal TERMINATE_YO URSELF 2023-03-31 15:12:20.325 - info: backitup.0 (3523) cleaned everything up... 2023-03-31 15:12:20.326 - info: backitup.0 (3523) terminating 2023-03-31 15:12:20.328 - info: backitup.0 (3523) Terminated (ADAPTER_REQUESTED _TERMINATION): Without reason 2023-03-31 15:12:20.328 - info: discovery.0 (603) terminating 2023-03-31 15:12:20.330 - info: discovery.0 (603) Terminated (ADAPTER_REQUESTED _TERMINATION): Without reason 2023-03-31 15:12:20.328 - info: admin.0 (588) terminating http server on port 8 081 2023-03-31 15:12:20.338 - info: admin.0 (588) terminating 2023-03-31 15:12:20.339 - info: admin.0 (588) Terminated (ADAPTER_REQUESTED_TER MINATION): Without reason 2023-03-31 15:12:20.873 - info: host.edfa9db59fd4 instance system.adapter.disco very.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:12:20.881 - info: host.edfa9db59fd4 instance system.adapter.backi tup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:12:20.923 - info: host.edfa9db59fd4 instance system.adapter.admin .0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-31 15:12:20.925 - info: host.edfa9db59fd4 All instances are stopped. 2023-03-31 15:12:21.141 - info: host.edfa9db59fd4 terminated 2023-03-31 15:26:48.156 - info: host.dd14ecbc30a9 iobroker.js-controller versio n 4.0.24 js-controller starting 2023-03-31 15:26:48.162 - info: host.dd14ecbc30a9 Copyright (c) 2014-2022 bluef ox, 2014 hobbyquaker 2023-03-31 15:26:48.163 - info: host.dd14ecbc30a9 hostname: dd14ecbc30a9, node: v18.15.0 2023-03-31 15:26:48.164 - info: host.dd14ecbc30a9 ip addresses: 192.168.1.49 2023-03-31 15:26:48.817 - info: host.dd14ecbc30a9 connected to Objects and Stat es 2023-03-31 15:26:48.842 - info: host.dd14ecbc30a9 added notifications configura tion of host 2023-03-31 15:26:49.199 - info: host.dd14ecbc30a9 Delete host system.host.edfa9 db59fd4 2023-03-31 15:26:49.249 - info: host.dd14ecbc30a9 Delete state "system.host.dd1 4ecbc30a9.versions.nodeCurrent" 2023-03-31 15:26:49.251 - info: host.dd14ecbc30a9 15 instances found 2023-03-31 15:26:49.266 - warn: host.dd14ecbc30a9 does not start any instances on this host 2023-03-31 15:26:49.343 - info: host.dd14ecbc30a9 Delete state "system.host.dd1 4ecbc30a9.versions.nodeNewest" 2023-03-31 15:26:49.396 - info: host.dd14ecbc30a9 Delete state "system.host.dd1 4ecbc30a9.versions.nodeNewestNext" 2023-03-31 15:26:49.449 - info: host.dd14ecbc30a9 Delete state "system.host.dd1 4ecbc30a9.versions.npmCurrent" 2023-03-31 15:26:49.500 - info: host.dd14ecbc30a9 Delete state "system.host.dd1 4ecbc30a9.versions.npmNewest" 2023-03-31 15:26:49.552 - info: host.dd14ecbc30a9 Delete state "system.host.dd1 4ecbc30a9.versions.npmNewestNext" 2023-03-31 15:26:49.603 - info: host.dd14ecbc30a9 Some obsolete host states del eted. 2023-03-31 15:48:40.806 - info: host.dd14ecbc30a9 received SIGINT 2023-03-31 15:48:40.860 - info: host.dd14ecbc30a9 terminated 2023-03-31 16:01:12.692 - info: host.dd14ecbc30a9 iobroker.js-controller versio n 4.0.24 js-controller starting 2023-03-31 16:01:12.697 - info: host.dd14ecbc30a9 Copyright (c) 2014-2022 bluef ox, 2014 hobbyquaker 2023-03-31 16:01:12.698 - info: host.dd14ecbc30a9 hostname: dd14ecbc30a9, node: v18.15.0 2023-03-31 16:01:12.699 - info: host.dd14ecbc30a9 ip addresses: 192.168.1.49 2023-03-31 16:01:13.348 - info: host.dd14ecbc30a9 connected to Objects and Stat es 2023-03-31 16:01:13.385 - info: host.dd14ecbc30a9 added notifications configura tion of host 2023-03-31 16:01:13.746 - info: host.dd14ecbc30a9 15 instances found 2023-03-31 16:01:13.758 - warn: host.dd14ecbc30a9 does not start any instances on this host 2023-03-31 16:59:01.051 - info: host.dd14ecbc30a9 iobroker.js-controller versio n 4.0.24 js-controller starting 2023-03-31 16:59:01.057 - info: host.dd14ecbc30a9 Copyright (c) 2014-2022 bluef ox, 2014 hobbyquaker 2023-03-31 16:59:01.057 - info: host.dd14ecbc30a9 hostname: dd14ecbc30a9, node: v18.15.0 2023-03-31 16:59:01.058 - info: host.dd14ecbc30a9 ip addresses: 192.168.1.49 2023-03-31 16:59:03.147 - error: host.dd14ecbc30a9-Server Cannot start inMem-ob jects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects. jsonl"! 2023-03-31 16:59:49.955 - info: host.dd14ecbc30a9 received SIGTERM 2023-03-31 16:59:49.996 - info: host.dd14ecbc30a9 terminated 2023-03-31 17:00:38.736 - info: host.dd14ecbc30a9 iobroker.js-controller versio n 4.0.24 js-controller starting 2023-03-31 17:00:38.743 - info: host.dd14ecbc30a9 Copyright (c) 2014-2022 bluef ox, 2014 hobbyquaker 2023-03-31 17:00:38.744 - info: host.dd14ecbc30a9 hostname: dd14ecbc30a9, node: v18.15.0 2023-03-31 17:00:38.744 - info: host.dd14ecbc30a9 ip addresses: 192.168.1.49 2023-03-31 17:00:39.460 - info: host.dd14ecbc30a9 connected to Objects and Stat es 2023-03-31 17:00:39.485 - info: host.dd14ecbc30a9 added notifications configura tion of host 2023-03-31 17:00:39.902 - info: host.dd14ecbc30a9 15 instances found 2023-03-31 17:00:39.914 - warn: host.dd14ecbc30a9 does not start any instances on this host root@edfa9db59fd4:/opt/iobroker# -
@adamantium sagte in Restore läuft nicht weiter:
2023-03-31 15:26:49.266 - warn: host.dd14ecbc30a9 does not start any instances on this host
-
@glasfaser said in Restore läuft nicht weiter:
@adamantium sagte in Restore läuft nicht weiter:
Docker: v8.0.0
host.dd14ecbc30a9 check instance "system.adapter.admin.0" for host "edfa9db59fd4"
Habe das schon zweimal mit dem Restore
pkill -u iobroker iobroker host thisdanach den Container neu starten
Die beiden Befehle per SSH?
-
Ja im Container bei ioBroker
-
@adamantium sagte in Restore läuft nicht weiter:
Der rattert schnell durch und dann kommt nur die Summary.
Im Terminal kann man auf der ersten Seite nach oben scrollen und zusätzlich liegt ein Log von iob diag im Home des iobrokers.
-
@glasfaser said in Restore läuft nicht weiter:
Ja im Container bei ioBroker
Da macht er gar nichts...als wenn es nicht beachtet wird.
-
@adamantium sagte in Restore läuft nicht weiter:
@glasfaser said in Restore läuft nicht weiter:
Ja im Container bei ioBroker
Da macht er gar nichts...als wenn es nicht beachtet wird.
??
Hier rein .. oder was machst du da
[Marcel@Marcel ~]$ docker exec -i -t iobroker bash root@edfa9db59fd4:/opt/iobroker# -
Theorie:
Bei jeder neuen Installation muss ich eine andere IP Adresse für den Container vergeben, da er sagt die alte wäre bereits belegt.
Heißt die Installation wo das Backup erstellt wurde hatte die 192.168.1.47...nun bin ich aber hinten bei der 1.49!
Kann es damit etwas zu tun haben?
-
@adamantium sagte in Restore läuft nicht weiter:
Kann es damit etwas zu tun haben?
Nein, Kurzfassung :
der Container HOST hat beim erstellen einen Namen X und dein Restore hat den Namen Y .
das passt nicht
daher :iobroker host this -
@glasfaser said in Restore läuft nicht weiter:
@adamantium sagte in Restore läuft nicht weiter:
@glasfaser said in Restore läuft nicht weiter:
Ja im Container bei ioBroker
Da macht er gar nichts...als wenn es nicht beachtet wird.
??
Hier rein .. oder was machst du da
[Marcel@Marcel ~]$ docker exec -i -t iobroker bash root@edfa9db59fd4:/opt/iobroker#Bin in dem root:
-
Ja , er hat doch schon alles gemacht ( changed ) !!
Jetzt den Container neu starten -
@glasfaser said in Restore läuft nicht weiter:
Ja , er hat doch schon alles gemacht ( changed ) !!
Jetzt den Container neu startenHabe ich gemacht, hängt aber an der gleichen Stell.
Nun steht im Log:
2023-03-31 17:16:20.646 - info: host.edfa9db59fd4 iobroker.js-controller version 4.0.24 js-controller starting 2023-03-31 17:16:20.651 - info: host.edfa9db59fd4 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-03-31 17:16:20.652 - info: host.edfa9db59fd4 hostname: edfa9db59fd4, node: v18.15.0 2023-03-31 17:16:20.653 - info: host.edfa9db59fd4 ip addresses: 192.168.1.49 2023-03-31 17:16:21.375 - info: host.edfa9db59fd4 connected to Objects and States 2023-03-31 17:16:21.413 - info: host.edfa9db59fd4 added notifications configuration of host 2023-03-31 17:16:21.418 - info: host.edfa9db59fd4 Node.js version has changed from unknown to 18.15.0 2023-03-31 17:16:21.479 - info: host.edfa9db59fd4 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-03-31 17:16:21.744 - info: host.edfa9db59fd4 Delete host system.host.edfa9db59fd4 2023-03-31 17:16:21.790 - info: host.edfa9db59fd4 15 instances found 2023-03-31 17:16:21.818 - info: host.edfa9db59fd4 starting 2 instances 2023-03-31 17:16:21.824 - warn: host.edfa9db59fd4 startInstance cannot find adapter "javascript@6.1.4". Try to install it... 1 attempt 2023-03-31 17:16:21.826 - info: host.edfa9db59fd4 iobroker install javascript@6.1.4 using installedFrom 2023-03-31 17:16:21.932 - info: host.edfa9db59fd4 instance system.adapter.admin.0 started with pid 174 2023-03-31 17:16:24.091 - info: admin.0 (174) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.15.0, js-controller: 4.0.24 2023-03-31 17:16:24.145 - info: admin.0 (174) requesting all states 2023-03-31 17:16:24.146 - info: admin.0 (174) requesting all objects 2023-03-31 17:16:24.648 - info: admin.0 (174) received all objects 2023-03-31 17:16:24.855 - info: admin.0 (174) http server listening on port 8081 2023-03-31 17:16:24.856 - info: admin.0 (174) Use link "http://localhost:8081" to configure. 2023-03-31 17:16:24.865 - info: admin.0 (174) socket.io server listening on port 8081 2023-03-31 17:16:25.071 - info: host.edfa9db59fd4 iobroker npm-install: NPM version: 9.5.0 2023-03-31 17:16:25.073 - info: host.edfa9db59fd4 iobroker npm-install: Installing iobroker.javascript@6.1.4... (System call) 2023-03-31 17:16:25.888 - info: host.edfa9db59fd4 instance system.adapter.backitup.0 started with pid 225 2023-03-31 17:16:27.713 - info: backitup.0 (225) starting. Version 2.5.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0.24 2023-03-31 17:16:27.932 - info: backitup.0 (225) [iobroker] backup was activated at 3:00 every 2 day(s) 2023-03-31 17:16:39.920 - warn: admin.0 (174) Cannot update rating: timeout of 15000ms exceeded 2023-03-31 17:17:25.230 - error: backitup.0 (225) Error: read ECONNRESET 2023-03-31 17:17:30.369 - warn: admin.0 (174) Cannot check node.js versions: Error: read ECONNRESET -
2023-03-31 17:16:25.073 - info: host.edfa9db59fd4 iobroker npm-install: Installing iobroker.javascript@6.1.4... (System call)
Wenn du ein Restore einspielst ... mußt du warten , denn die Adapter werden alle nachinstalliert
-
Aber er bleibt an gleicher Stelle stehen bzw. ist ein Error von backitup.
Lohnt es das System nochmal neu zu machen, dann das Backup zu restoren, die Befehle von dir und dann warten?
-
@adamantium sagte in Restore läuft nicht weiter:
Aber er bleibt an gleicher Stelle stehen bzw. ist ein Error von backitup.
so weit hab ich nicht runter gescrollt
ECONNRESET
sehr merkwürdig
Lohnt es das System nochmal neu zu machen, dann das Backup zu restoren, die Befehle von dir und dann warten?
Ja lohnt sich , ist ja noch nicht viel passiert !
-
Habe das System nochmal aufgesetzt und nun ging es
Nervig ist jetzt nur, dass die IP wieder eine andere ist. Muss eine Einstellung im Virtual Switch des QNAP sein.Vielen Dank für die Hilfe
