NEWS
[gelöst] Nach Stromausfall startet iobroker nicht mehr
ioBroker Allgemein
3
Beiträge
2
Kommentatoren
879
Aufrufe
3
Watching
-
Guten Morgen
Wir hatten heute Nacht ein schweres Gewitter mit Stromausfall.
Heute morgen habe ich bemerkt das IOBroker nicht durchstartet.IOBroker läuft bei mir auf einem Synology NAS.
Im Portainer-Log zu IOBroker steht folgendes
, ,------------------------------------------------------------ ,--------------- 2021-06-22 05:59:16 --------------- ,------------------------------------------------------------ , ,------------------------------------------------------------ ,----- Welcome to your ioBroker-container! ----- ,----- Startupscript is now running. ----- ,----- Please be patient! ----- ,------------------------------------------------------------ , ,------------------------------------------------------------ ,----- Debugging information ----- ,----- ----- ,----- System ----- ,----- arch: x86_64 ----- ,----- ----- ,----- Versions ----- ,----- image: v5.1.0 ----- ,----- node: v12.20.0 ----- ,----- npm: 6.14.8 ----- ,----- ----- ,----- 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. , ,The object system.adapter.admin.0 was not found! ,/opt/scripts/iobroker_startup.sh: Zeile 197: [: !=: Einstelliger (unärer) Operator erwartet. ,------------------------------------------------------------ ,----- 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 take a look at readme.md on Github! , ,------------------------------------------------------------ ,----- Step 5 of 5: ioBroker startup ----- ,------------------------------------------------------------ , ,Starting ioBroker...Nach IOBroker list instances
root@iobroker:/opt/iobroker# iobroker list instances Cannot read system.config: null (OK when migrating or restoring) Cannot find view "system" for search "host" + instance is alive root@iobroker:/opt/iobroker#root@iobroker:/opt/iobroker# tail -f /opt/iobroker/log/iobroker.current.log 2021-06-22 06:02:02.558 - info: host.iobroker iobroker _restart 2021-06-22 06:02:03.006 - info: host.iobroker iobroker Starting node restart.js 2021-06-22 06:44:50.403 - info: host.iobroker iobroker.js-controller version 3.2.16 js-controller starting 2021-06-22 06:44:50.407 - info: host.iobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-06-22 06:44:50.408 - info: host.iobroker hostname: iobroker, node: v12.20.0 2021-06-22 06:44:50.408 - info: host.iobroker ip addresses: 192.168.1.111 2003:db:6f1a:fe00:211:32ff:fe8e:cb86 fe80::211:32ff:fe8e:cb86 172.17.0.1 fe80::42:70ff:fe8c:e931 fe80::a43a:7ff:fe8c:59e8 2021-06-22 06:44:50.460 - info: host.iobroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 0.0.0.0:9001 2021-06-22 06:45:20.434 - error: host.iobroker No connection to databases possible, restart 2021-06-22 06:45:20.437 - info: host.iobroker iobroker _restart 2021-06-22 06:45:20.878 - info: host.iobroker iobroker Starting node restart.jswas kann ich jetzt tun um IOBoker wieder zu starten/retten
Gruß
HappyUser20 -
Guten Morgen
Wir hatten heute Nacht ein schweres Gewitter mit Stromausfall.
Heute morgen habe ich bemerkt das IOBroker nicht durchstartet.IOBroker läuft bei mir auf einem Synology NAS.
Im Portainer-Log zu IOBroker steht folgendes
, ,------------------------------------------------------------ ,--------------- 2021-06-22 05:59:16 --------------- ,------------------------------------------------------------ , ,------------------------------------------------------------ ,----- Welcome to your ioBroker-container! ----- ,----- Startupscript is now running. ----- ,----- Please be patient! ----- ,------------------------------------------------------------ , ,------------------------------------------------------------ ,----- Debugging information ----- ,----- ----- ,----- System ----- ,----- arch: x86_64 ----- ,----- ----- ,----- Versions ----- ,----- image: v5.1.0 ----- ,----- node: v12.20.0 ----- ,----- npm: 6.14.8 ----- ,----- ----- ,----- 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. , ,The object system.adapter.admin.0 was not found! ,/opt/scripts/iobroker_startup.sh: Zeile 197: [: !=: Einstelliger (unärer) Operator erwartet. ,------------------------------------------------------------ ,----- 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 take a look at readme.md on Github! , ,------------------------------------------------------------ ,----- Step 5 of 5: ioBroker startup ----- ,------------------------------------------------------------ , ,Starting ioBroker...Nach IOBroker list instances
root@iobroker:/opt/iobroker# iobroker list instances Cannot read system.config: null (OK when migrating or restoring) Cannot find view "system" for search "host" + instance is alive root@iobroker:/opt/iobroker#root@iobroker:/opt/iobroker# tail -f /opt/iobroker/log/iobroker.current.log 2021-06-22 06:02:02.558 - info: host.iobroker iobroker _restart 2021-06-22 06:02:03.006 - info: host.iobroker iobroker Starting node restart.js 2021-06-22 06:44:50.403 - info: host.iobroker iobroker.js-controller version 3.2.16 js-controller starting 2021-06-22 06:44:50.407 - info: host.iobroker Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-06-22 06:44:50.408 - info: host.iobroker hostname: iobroker, node: v12.20.0 2021-06-22 06:44:50.408 - info: host.iobroker ip addresses: 192.168.1.111 2003:db:6f1a:fe00:211:32ff:fe8e:cb86 fe80::211:32ff:fe8e:cb86 172.17.0.1 fe80::42:70ff:fe8c:e931 fe80::a43a:7ff:fe8c:59e8 2021-06-22 06:44:50.460 - info: host.iobroker-Server Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 0.0.0.0:9001 2021-06-22 06:45:20.434 - error: host.iobroker No connection to databases possible, restart 2021-06-22 06:45:20.437 - info: host.iobroker iobroker _restart 2021-06-22 06:45:20.878 - info: host.iobroker iobroker Starting node restart.jswas kann ich jetzt tun um IOBoker wieder zu starten/retten
Gruß
HappyUser20 -
697
Online32.6k
Benutzer82.2k
Themen1.3m
Beiträge