wie beschrieben habe ich in das Volume eine backupdatei gelegt und den container gestartet.
Leider bricht der restore ab (sudo bug???)
Was könnte ich noch versuchen?
docker log
--------------------------------------------------------------------------------
------------------------- 2022-01-18 16:28:11 -------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Welcome to your ioBroker-container! -----
----- Startupscript is now running. -----
----- Please be patient! -----
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Debugging information -----
----- -----
----- System -----
----- arch: armv7l -----
----- -----
----- Docker-Image -----
----- image: v6.0.0 -----
----- build: 2021-12-17T03:48:21+00:00 -----
----- -----
----- Versions -----
----- node: v14.18.3 -----
----- npm: 6.14.15 -----
----- -----
----- ENV -----
----- SETGID: 1000 -----
----- SETUID: 1000 -----
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Step 1 of 5: Preparing container -----
--------------------------------------------------------------------------------
Nothing to do here.
--------------------------------------------------------------------------------
----- Step 2 of 5: Detecting ioBroker installation -----
--------------------------------------------------------------------------------
IoBroker backup file detected in /opt/iobroker.
Preparing restore...
Done.
Restoring ioBroker...
Done.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!! IMPORTANT NOTE !!!!!
!!!!! The sartup script restored iobroker from a backup file. !!!!!
!!!!! Check /opt/iobroker/log/restore.log to see if restore was successful. !!!!!
!!!!! When ioBroker now starts it will reinstall all Adapters automatically. !!!!!
!!!!! This might be take a looooong time! Please be patient! !!!!!
!!!!! You can view installation process by taking a look at ioBroker log. !!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--------------------------------------------------------------------------------
----- 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.
Hostname in ioBroker does not match the hostname of this container.
Updating hostname to iobroker...
The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "iobroker".
The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "iobroker".
The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "iobroker".
Done.
--------------------------------------------------------------------------------
----- 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...
[/s]
/opt/iobroker/log/restore.log
host.iobroker Using backup file iobroker_2022_01_18-02_00_10_produktivsystem_backupiobroker.tar.gz
iobroker controller daemon is not running
host.iobroker OK.
<--- Last few GCs --->
[85:0x3995a50] 12391 ms: Scavenge 13.5 (16.8) -> 12.0 (16.8) MB, 4.8 / 0.0 ms (average mu = 0.996, current mu = 0.986) task
[85:0x3995a50] 12519 ms: Scavenge 13.7 (16.8) -> 12.2 (17.3) MB, 3.1 / 0.0 ms (average mu = 0.996, current mu = 0.986) task
[85:0x3995a50] 14372 ms: Mark-sweep 124.4 (129.2) -> 122.6 (129.2) MB, 65.9 / 0.0 ms (average mu = 0.992, current mu = 0.990) external memory pressure scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory
iobroker: line 6: 84 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@"
wie beschrieben habe ich in das Volume eine backupdatei gelegt und den container gestartet.
Leider bricht der restore ab (sudo bug???)
Was könnte ich noch versuchen?
docker log
--------------------------------------------------------------------------------
------------------------- 2022-01-18 16:28:11 -------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Welcome to your ioBroker-container! -----
----- Startupscript is now running. -----
----- Please be patient! -----
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Debugging information -----
----- -----
----- System -----
----- arch: armv7l -----
----- -----
----- Docker-Image -----
----- image: v6.0.0 -----
----- build: 2021-12-17T03:48:21+00:00 -----
----- -----
----- Versions -----
----- node: v14.18.3 -----
----- npm: 6.14.15 -----
----- -----
----- ENV -----
----- SETGID: 1000 -----
----- SETUID: 1000 -----
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Step 1 of 5: Preparing container -----
--------------------------------------------------------------------------------
Nothing to do here.
--------------------------------------------------------------------------------
----- Step 2 of 5: Detecting ioBroker installation -----
--------------------------------------------------------------------------------
IoBroker backup file detected in /opt/iobroker.
Preparing restore...
Done.
Restoring ioBroker...
Done.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!! IMPORTANT NOTE !!!!!
!!!!! The sartup script restored iobroker from a backup file. !!!!!
!!!!! Check /opt/iobroker/log/restore.log to see if restore was successful. !!!!!
!!!!! When ioBroker now starts it will reinstall all Adapters automatically. !!!!!
!!!!! This might be take a looooong time! Please be patient! !!!!!
!!!!! You can view installation process by taking a look at ioBroker log. !!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
--------------------------------------------------------------------------------
----- 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.
Hostname in ioBroker does not match the hostname of this container.
Updating hostname to iobroker...
The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "iobroker".
The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "iobroker".
The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "iobroker".
Done.
--------------------------------------------------------------------------------
----- 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...
[/s]
/opt/iobroker/log/restore.log
host.iobroker Using backup file iobroker_2022_01_18-02_00_10_produktivsystem_backupiobroker.tar.gz
iobroker controller daemon is not running
host.iobroker OK.
<--- Last few GCs --->
[85:0x3995a50] 12391 ms: Scavenge 13.5 (16.8) -> 12.0 (16.8) MB, 4.8 / 0.0 ms (average mu = 0.996, current mu = 0.986) task
[85:0x3995a50] 12519 ms: Scavenge 13.7 (16.8) -> 12.2 (17.3) MB, 3.1 / 0.0 ms (average mu = 0.996, current mu = 0.986) task
[85:0x3995a50] 14372 ms: Mark-sweep 124.4 (129.2) -> 122.6 (129.2) MB, 65.9 / 0.0 ms (average mu = 0.992, current mu = 0.990) external memory pressure scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: MarkCompactCollector: young object promotion failed Allocation failed - JavaScript heap out of memory
iobroker: line 6: 84 Aborted sudo -H -u iobroker node /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js "$@"
@homoran
war schon dabei.
hat sich überschnitten. Sorry!!
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
