ioBroker nicht erreichbar nach Stromausfall
Verfasst: Fr Okt 22, 2021 5:23 pm
Hallo zusammen
heute gab es bei uns einen kurzen stromausfall und seit dem komme ich nicht mehr auf den iobroker (Docker) hab den TW neugestartet und den Container zusätzlich neu gestartet, leider ohne erfolg.
Kennt jemand so ein Problem und hat ggf eine Lösung?
Wenn ich ein Backup des TW von gestern wiederherstelle sind dann die Container auch auf dem Stand von gestern wieder verfügbar?
Im LOG des ioBroker Containers bekomme ich folgendes angezeigt:
------------------------------------------------------------
--------------- 2021-10-22 15:42:49 ---------------
------------------------------------------------------------
------------------------------------------------------------
----- 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.22.1 -----
----- npm: 6.14.12 -----
----- -----
----- 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...
doc.rows is not iterable
TypeError: doc.rows is not iterable
at Object.getInstancesOrderedByStartPrio (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js27)
object system.meta.uuid cannot be updated: Error: DB closed
object system.user.admin created
heute gab es bei uns einen kurzen stromausfall und seit dem komme ich nicht mehr auf den iobroker (Docker) hab den TW neugestartet und den Container zusätzlich neu gestartet, leider ohne erfolg.
Kennt jemand so ein Problem und hat ggf eine Lösung?
Wenn ich ein Backup des TW von gestern wiederherstelle sind dann die Container auch auf dem Stand von gestern wieder verfügbar?
Im LOG des ioBroker Containers bekomme ich folgendes angezeigt:
------------------------------------------------------------
--------------- 2021-10-22 15:42:49 ---------------
------------------------------------------------------------
------------------------------------------------------------
----- 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.22.1 -----
----- npm: 6.14.12 -----
----- -----
----- 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...
doc.rows is not iterable
TypeError: doc.rows is not iterable
at Object.getInstancesOrderedByStartPrio (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js27)
object system.meta.uuid cannot be updated: Error: DB closed
object system.user.admin created