NEWS
Backup aus älterer Version einspielen
Installation
54
Beiträge
4
Kommentatoren
4.4k
Aufrufe
2
Watching
-
Dann muss ich doch jetzt nur eine Docker Instanz aufsetzten, wo nodejs 14.x drauf läuft oder ?
@firefighter166 sagte in Backup aus älterer Version einspielen:
Dann muss ich doch jetzt nur eine Docker Instanz aufsetzten, wo nodejs 14.x drauf läuft oder ?
Insofern war das mit dem Docker-Image 7.x genau richtig, denn dort läuft Node.js 14. Ich hätte es wohl auch so gemacht.
Versuch noch mal bei einem leeren Verzeichnis zu starten. Und (wie schon anfangs erwähnt) das komplette Docker-Log aus der Console hier rein.
-
@firefighter166 sagte in Backup aus älterer Version einspielen:
Dann muss ich doch jetzt nur eine Docker Instanz aufsetzten, wo nodejs 14.x drauf läuft oder ?
Insofern war das mit dem Docker-Image 7.x genau richtig, denn dort läuft Node.js 14. Ich hätte es wohl auch so gemacht.
Versuch noch mal bei einem leeren Verzeichnis zu starten. Und (wie schon anfangs erwähnt) das komplette Docker-Log aus der Console hier rein.
wie gewünscht der Docker Log
-------------------------------------------------------------------------------- ------------------------- 2023-12-07 13:56:53 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: 51ebd490ef3f ----- ----- ----- ----- Version Information ----- ----- image: v7.2.0 ----- ----- build: 2023-02-10T23:45:25+00:00 ----- ----- node: v16.20.2 ----- ----- npm: 8.19.4 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- This is not the first run of this container. Skipping first run preparation. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo with gosu... Done. Hostname in ioBroker matches the hostname of this container. No action required. -------------------------------------------------------------------------------- ----- 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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### host.51ebd490ef3f check instance "system.adapter.admin.0" for host "51ebd490ef3f" host.51ebd490ef3f check instance "system.adapter.discovery.0" for host "51ebd490ef3f" host.51ebd490ef3f check instance "system.adapter.backitup.0" for host "51ebd490ef3f" Send diag info: {"uuid":"95b5c97c-816b-475b-9b4d-29c6637fe84f","language":"de","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.20.2","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.5.12","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"AMD GX-424CC SOC with Radeon(TM) R5E Graphics","cpus":4,"mem":15734272000,"ostype":"Linux","city":""} ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] -
wie gewünscht der Docker Log
-------------------------------------------------------------------------------- ------------------------- 2023-12-07 13:56:53 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: 51ebd490ef3f ----- ----- ----- ----- Version Information ----- ----- image: v7.2.0 ----- ----- build: 2023-02-10T23:45:25+00:00 ----- ----- node: v16.20.2 ----- ----- npm: 8.19.4 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- This is not the first run of this container. Skipping first run preparation. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo with gosu... Done. Hostname in ioBroker matches the hostname of this container. No action required. -------------------------------------------------------------------------------- ----- 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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### host.51ebd490ef3f check instance "system.adapter.admin.0" for host "51ebd490ef3f" host.51ebd490ef3f check instance "system.adapter.discovery.0" for host "51ebd490ef3f" host.51ebd490ef3f check instance "system.adapter.backitup.0" for host "51ebd490ef3f" Send diag info: {"uuid":"95b5c97c-816b-475b-9b4d-29c6637fe84f","language":"de","country":"","hosts":[{"version":"4.0.24","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.20.2","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.3.5","platform":"Javascript/Node.js"},"discovery":{"version":"3.1.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.5.12","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"AMD GX-424CC SOC with Radeon(TM) R5E Graphics","cpus":4,"mem":15734272000,"ostype":"Linux","city":""} ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]@firefighter166 sagte in Backup aus älterer Version einspielen:
wie gewünscht der Docker Log
Da ist jetzt aber Node 16 drin. Dann müsstest du noch mal in den Release Notes wühlen, mit welchem Image die 14 mitkam.
-
@firefighter166 sagte in Backup aus älterer Version einspielen:
wie gewünscht der Docker Log
Da ist jetzt aber Node 16 drin. Dann müsstest du noch mal in den Release Notes wühlen, mit welchem Image die 14 mitkam.
ich bin jetzt nochmal auf die Docker-Image 6.0 zurück gegangen und jetzt müsste es mit Node.js 14x passen oder?
-------------------------------------------------------------------------------- ------------------------- 2023-12-07 14:19:06 ------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Welcome to your ioBroker-container! ----- ----- Startupscript is now running. ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: x86_64 ----- ----- ----- ----- Docker-Image ----- ----- image: v6.0.0 ----- ----- build: 2022-02-25T23:46:04+00:00 ----- ----- ----- ----- Versions ----- ----- node: v14.21.3 ----- ----- npm: 6.14.18 ----- ----- ----- ----- 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. -------------------------------------------------------------------------------- ----- 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... host.3b2fadb26f50 check instance "system.adapter.admin.0" for host "3b2fadb26f50" host.3b2fadb26f50 check instance "system.adapter.discovery.0" for host "3b2fadb26f50" host.3b2fadb26f50 check instance "system.adapter.backitup.0" for host "3b2fadb26f50" ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] -
ich bin jetzt nochmal auf die Docker-Image 6.0 zurück gegangen und jetzt müsste es mit Node.js 14x passen oder?
-------------------------------------------------------------------------------- ------------------------- 2023-12-07 14:19:06 ------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Welcome to your ioBroker-container! ----- ----- Startupscript is now running. ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: x86_64 ----- ----- ----- ----- Docker-Image ----- ----- image: v6.0.0 ----- ----- build: 2022-02-25T23:46:04+00:00 ----- ----- ----- ----- Versions ----- ----- node: v14.21.3 ----- ----- npm: 6.14.18 ----- ----- ----- ----- 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. -------------------------------------------------------------------------------- ----- 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... host.3b2fadb26f50 check instance "system.adapter.admin.0" for host "3b2fadb26f50" host.3b2fadb26f50 check instance "system.adapter.discovery.0" for host "3b2fadb26f50" host.3b2fadb26f50 check instance "system.adapter.backitup.0" for host "3b2fadb26f50" ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging]@firefighter166
sieht gut aus, versuch dein Glück. -
@firefighter166
sieht gut aus, versuch dein Glück.ich habe jetzt nochmal auf die Docker Version 7 umgeschwenkt, da ich eine neuere Backupdatei gefunden haben.
installedVersion ist hier 4.0.23
Die Backup Datei lässt sich auch einspielen nur beim Container Neustart hängt er sich dann auf.
-------------------------------------------------------------------------------- ------------------------- 2023-12-07 14:54:41 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: 5e92feb257f9 ----- ----- ----- ----- Version Information ----- ----- image: v7.2.0 ----- ----- build: 2023-02-10T23:45:25+00:00 ----- ----- node: v16.20.2 ----- ----- npm: 8.19.4 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- This is not the first run of this container. Skipping first run preparation. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo with gosu... Done. Hostname in ioBroker matches the hostname of this container. No action required. -------------------------------------------------------------------------------- ----- 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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### ================================== > LOG REDIRECT system.adapter.admin.0 => true [starting] host.iobroker-1 check instance "system.adapter.admin.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.history.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.influxdb.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.influxdb.1" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.javascript.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.node-red.0" for host "slavestrom" host.iobroker-1 check instance "system.adapter.telegram.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.alexa2.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.alexa2.1" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.hm-rega.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.hm-rpc.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.hue.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.modbus.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.mqtt.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.smartmeter.0" for host "slavestrom" host.iobroker-1 check instance "system.adapter.sonoff.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.sonos.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.sony-bravia.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.discovery.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.backitup.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.daswetter.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.device-reminder.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.echarts.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.energymanager.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.fritzdect.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.fronius.1" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.habpanel.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.info.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.kecontact.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.pvforecast.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.smartgarden.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.vis.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.web.0" for host "5e92feb257f9" -
ich habe jetzt nochmal auf die Docker Version 7 umgeschwenkt, da ich eine neuere Backupdatei gefunden haben.
installedVersion ist hier 4.0.23
Die Backup Datei lässt sich auch einspielen nur beim Container Neustart hängt er sich dann auf.
-------------------------------------------------------------------------------- ------------------------- 2023-12-07 14:54:41 ------------------------- -------------------------------------------------------------------------------- ----- ----- ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- ----- ----- ----- Welcome to your ioBroker Docker container! ----- ----- Startupscript is now running! ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- System Information ----- ----- arch: x86_64 ----- ----- hostname: 5e92feb257f9 ----- ----- ----- ----- Version Information ----- ----- image: v7.2.0 ----- ----- build: 2023-02-10T23:45:25+00:00 ----- ----- node: v16.20.2 ----- ----- npm: 8.19.4 ----- ----- ----- ----- Environment Variables ----- ----- SETGID: 1000 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- This is not the first run of this container. Skipping first run preparation. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- Existing installation of ioBroker detected in "/opt/iobroker". -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)setting permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo with gosu... Done. Hostname in ioBroker matches the hostname of this container. No action required. -------------------------------------------------------------------------------- ----- 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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### ================================== > LOG REDIRECT system.adapter.admin.0 => true [starting] host.iobroker-1 check instance "system.adapter.admin.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.history.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.influxdb.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.influxdb.1" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.javascript.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.node-red.0" for host "slavestrom" host.iobroker-1 check instance "system.adapter.telegram.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.alexa2.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.alexa2.1" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.hm-rega.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.hm-rpc.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.hue.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.modbus.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.mqtt.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.smartmeter.0" for host "slavestrom" host.iobroker-1 check instance "system.adapter.sonoff.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.sonos.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.sony-bravia.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.discovery.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.backitup.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.daswetter.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.device-reminder.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.echarts.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.energymanager.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.fritzdect.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.fronius.1" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.habpanel.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.info.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.kecontact.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.pvforecast.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.smartgarden.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.vis.0" for host "5e92feb257f9" host.iobroker-1 check instance "system.adapter.web.0" for host "5e92feb257f9"@firefighter166
Ja, so ganz ohne Fehlermeldung ...Versuch mal folgendes:
In den Container gehen und
iob fix pkill -u iobroker iob host thisNeustart des Containers.
-
@firefighter166
Ja, so ganz ohne Fehlermeldung ...Versuch mal folgendes:
In den Container gehen und
iob fix pkill -u iobroker iob host thisNeustart des Containers.
Keine Chance der Container bleibt an der selben Stelle hängen.
-
Keine Chance der Container bleibt an der selben Stelle hängen.
@firefighter166 sagte in Backup aus älterer Version einspielen:
Keine Chance der Container bleibt an der selben Stelle hängen.
Der Container-/Hostname ist jetzt scheinbar ein anderer als in der Sicherung.
host.iobroker-1 check instance "system.adapter.web.0" for host "5e92feb257f9"
Benenne den mal wie vorher (also "iobroker-1"), und dann nochmal mit leerem Ordner starten.
-
@firefighter166 sagte in Backup aus älterer Version einspielen:
Keine Chance der Container bleibt an der selben Stelle hängen.
Der Container-/Hostname ist jetzt scheinbar ein anderer als in der Sicherung.
host.iobroker-1 check instance "system.adapter.web.0" for host "5e92feb257f9"
Benenne den mal wie vorher (also "iobroker-1"), und dann nochmal mit leerem Ordner starten.
@marc-berg said in Backup aus älterer Version einspielen:
Benenne den mal wie vorher (also "iobroker-1"), und dann nochmal mit leerem Ordner starten.
Wie beschrieben habe ich den Container Namen auf iobroker-1 angepasst, was auch hier nicht zum Erfolg geführt hat. Der Container bleibt immer wieder an der selben Stelle hängen. Habe es jetzt auch mal mit einer Backup Datei versucht die nur zwei Tage älter ist, keine Chance.
-
@marc-berg said in Backup aus älterer Version einspielen:
Benenne den mal wie vorher (also "iobroker-1"), und dann nochmal mit leerem Ordner starten.
Wie beschrieben habe ich den Container Namen auf iobroker-1 angepasst, was auch hier nicht zum Erfolg geführt hat. Der Container bleibt immer wieder an der selben Stelle hängen. Habe es jetzt auch mal mit einer Backup Datei versucht die nur zwei Tage älter ist, keine Chance.
@firefighter166 sagte in Backup aus älterer Version einspielen:
keine Chance.
so ganz ohne Fehlermeldungen ist das jetzt Fischen im Trüben. Wie sieht es denn im Ordner /iobroker/log aus?
-
@firefighter166 sagte in Backup aus älterer Version einspielen:
keine Chance.
so ganz ohne Fehlermeldungen ist das jetzt Fischen im Trüben. Wie sieht es denn im Ordner /iobroker/log aus?
@marc-berg said in Backup aus älterer Version einspielen:
so ganz ohne Fehlermeldungen ist das jetzt Fischen im Trüben. Wie sieht es denn im Ordner /iobroker/log aus?
Welchen Ordner muss ich denn leeren, damit ich den Container erneute starten kann?
Hier ist mal der Log:
2023-12-08 09:48:33.700 - [32minfo[39m: host.db4cbef0bc80 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 09:48:33.706 - [32minfo[39m: host.db4cbef0bc80 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 09:48:33.707 - [32minfo[39m: host.db4cbef0bc80 hostname: db4cbef0bc80, node: v16.20.2 2023-12-08 09:48:33.708 - [32minfo[39m: host.db4cbef0bc80 ip addresses: 10.0.1.126 2023-12-08 09:48:33.957 - [32minfo[39m: host.db4cbef0bc80 connected to Objects and States 2023-12-08 09:48:33.994 - [32minfo[39m: host.db4cbef0bc80 Node.js version has changed from unknown to 16.20.2 2023-12-08 09:48:34.033 - [32minfo[39m: host.db4cbef0bc80 added notifications configuration of host 2023-12-08 09:48:34.251 - [32minfo[39m: host.db4cbef0bc80 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-12-08 09:48:34.289 - [32minfo[39m: host.db4cbef0bc80 3 instances found 2023-12-08 09:48:34.299 - [32minfo[39m: host.db4cbef0bc80 starting 3 instances 2023-12-08 09:48:34.360 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.admin.0 started with pid 2206 2023-12-08 09:48:34.553 - [32minfo[39m: host.db4cbef0bc80 Created UUID: ee7c0d0e-d418-4da2-bc87-b8432405ee7b 2023-12-08 09:48:36.403 - [32minfo[39m: admin.0 (2206) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v16.20.2, js-controller: 4.0.24 2023-12-08 09:48:36.460 - [32minfo[39m: admin.0 (2206) requesting all states 2023-12-08 09:48:36.461 - [32minfo[39m: admin.0 (2206) requesting all objects 2023-12-08 09:48:36.562 - [32minfo[39m: admin.0 (2206) received all objects 2023-12-08 09:48:36.599 - [32minfo[39m: admin.0 (2206) Request actual repository... 2023-12-08 09:48:36.622 - [32minfo[39m: host.db4cbef0bc80 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-12-08 09:48:36.711 - [32minfo[39m: admin.0 (2206) http server listening on port 8081 2023-12-08 09:48:36.712 - [32minfo[39m: admin.0 (2206) Use link "http://localhost:8081" to configure. 2023-12-08 09:48:36.720 - [32minfo[39m: admin.0 (2206) socket.io server listening on port 8081 2023-12-08 09:48:36.782 - [33mwarn[39m: admin.0 (2206) Repository cannot be read: Active repo - stable 2023-12-08 09:48:36.783 - [33mwarn[39m: admin.0 (2206) Active repository "stable" cannot be read 2023-12-08 09:48:36.802 - [31merror[39m: admin.0 (2206) Cannot update news: TypeError: newNews.forEach is not a function 2023-12-08 09:48:39.179 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.discovery.0 started with pid 2233 2023-12-08 09:48:39.381 - [32minfo[39m: admin.0 (2206) Repository received successfully. 2023-12-08 09:48:40.900 - [32minfo[39m: discovery.0 (2233) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.20.2, js-controller: 4.0.24 2023-12-08 09:48:42.335 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.backitup.0 started with pid 2248 2023-12-08 09:48:44.139 - [32minfo[39m: backitup.0 (2248) starting. Version 2.5.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.20.2, js-controller: 4.0.24 2023-12-08 09:48:44.262 - [32minfo[39m: backitup.0 (2248) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-12-08 09:51:09.032 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:51:10.922 - [32minfo[39m: admin.0 (2206) <== Disconnect system.user.admin from ::ffff:10.0.2.171 admin 2023-12-08 09:51:19.847 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:52:35.912 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:52:38.526 - [32minfo[39m: admin.0 (2206) <== Disconnect system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:52:54.495 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:53:52.048 - [32minfo[39m: host.db4cbef0bc80 received SIGTERM 2023-12-08 09:53:52.053 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.admin.0 (force=false, process=true) 2023-12-08 09:53:52.054 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.discovery.0 (force=false, process=true) 2023-12-08 09:53:52.054 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-12-08 09:53:52.065 - [32minfo[39m: admin.0 (2206) Got terminate signal TERMINATE_YOURSELF 2023-12-08 09:53:52.065 - [32minfo[39m: discovery.0 (2233) Got terminate signal TERMINATE_YOURSELF 2023-12-08 09:53:52.069 - [32minfo[39m: backitup.0 (2248) Got terminate signal TERMINATE_YOURSELF 2023-12-08 09:53:52.066 - [32minfo[39m: admin.0 (2206) terminating http server on port 8081 2023-12-08 09:53:52.070 - [32minfo[39m: admin.0 (2206) terminating 2023-12-08 09:53:52.072 - [32minfo[39m: admin.0 (2206) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-08 09:53:52.067 - [32minfo[39m: discovery.0 (2233) terminating 2023-12-08 09:53:52.078 - [32minfo[39m: discovery.0 (2233) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-08 09:53:52.085 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.admin.0 send kill signal 2023-12-08 09:53:52.071 - [32minfo[39m: backitup.0 (2248) cleaned everything up... 2023-12-08 09:53:52.082 - [32minfo[39m: backitup.0 (2248) terminating 2023-12-08 09:53:52.083 - [32minfo[39m: backitup.0 (2248) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-08 09:53:52.088 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.discovery.0 send kill signal 2023-12-08 09:53:52.090 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.backitup.0 send kill signal 2023-12-08 09:53:52.683 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-08 09:53:52.684 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-08 09:53:52.685 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-08 09:53:52.685 - [32minfo[39m: host.db4cbef0bc80 All instances are stopped. 2023-12-08 09:53:52.879 - [32minfo[39m: host.db4cbef0bc80 terminated 2023-12-08 09:55:57.094 - [32minfo[39m: host.iobroker-1 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 09:55:57.101 - [32minfo[39m: host.iobroker-1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 09:55:57.102 - [32minfo[39m: host.iobroker-1 hostname: iobroker-1, node: v16.20.2 2023-12-08 09:55:57.103 - [32minfo[39m: host.iobroker-1 ip addresses: 10.0.1.126 2023-12-08 09:55:58.041 - [33mwarn[39m: host.iobroker-1-Server Objects 10.0.1.65:42936 Error from InMemDB: Error: Unknown Script 2023-12-08 09:55:58.670 - [32minfo[39m: host.iobroker-1 connected to Objects and States 2023-12-08 09:55:58.727 - [32minfo[39m: host.iobroker-1 added notifications configuration of host 2023-12-08 09:55:58.742 - [32minfo[39m: host.iobroker-1 Node.js version has changed from 14.20.0 to 16.20.2 2023-12-08 09:55:58.932 - [32minfo[39m: host.iobroker-1 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-12-08 09:56:00.160 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.nodeCurrent" 2023-12-08 09:56:00.163 - [32minfo[39m: host.iobroker-1 34 instances found 2023-12-08 09:56:00.182 - [33mwarn[39m: host.iobroker-1 does not start any instances on this host 2023-12-08 09:56:00.218 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.nodeNewest" 2023-12-08 09:56:00.228 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.nodeNewestNext" 2023-12-08 09:56:00.238 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.npmCurrent" 2023-12-08 09:56:00.247 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.npmNewest" 2023-12-08 09:56:00.298 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.npmNewestNext" 2023-12-08 09:56:00.309 - [32minfo[39m: host.iobroker-1 Some obsolete host states deleted. 2023-12-08 10:01:31.417 - [32minfo[39m: host.iobroker-1 received SIGTERM 2023-12-08 10:01:31.460 - [32minfo[39m: host.iobroker-1 terminated 2023-12-08 10:02:12.098 - [32minfo[39m: host.iobroker-1 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 10:02:12.104 - [32minfo[39m: host.iobroker-1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 10:02:12.105 - [32minfo[39m: host.iobroker-1 hostname: iobroker-1, node: v16.20.2 2023-12-08 10:02:12.106 - [32minfo[39m: host.iobroker-1 ip addresses: 10.0.1.126 2023-12-08 10:02:13.373 - [32minfo[39m: host.iobroker-1 connected to Objects and States 2023-12-08 10:02:13.424 - [32minfo[39m: host.iobroker-1 added notifications configuration of host 2023-12-08 10:02:14.131 - [32minfo[39m: host.iobroker-1 34 instances found 2023-12-08 10:02:14.150 - [33mwarn[39m: host.iobroker-1 does not start any instances on this host 2023-12-08 10:10:19.617 - [32minfo[39m: host.iobroker-1 received SIGTERM 2023-12-08 10:10:19.661 - [32minfo[39m: host.iobroker-1 terminated 2023-12-08 10:11:04.261 - [32minfo[39m: host.iobroker-1 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 10:11:04.270 - [32minfo[39m: host.iobroker-1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 10:11:04.271 - [32minfo[39m: host.iobroker-1 hostname: iobroker-1, node: v16.20.2 2023-12-08 10:11:04.272 - [32minfo[39m: host.iobroker-1 ip addresses: 10.0.1.126 2023-12-08 10:11:05.632 - [32minfo[39m: host.iobroker-1 connected to Objects and States 2023-12-08 10:11:05.688 - [32minfo[39m: host.iobroker-1 added notifications configuration of host 2023-12-08 10:11:06.486 - [32minfo[39m: host.iobroker-1 34 instances found 2023-12-08 10:11:06.505 - [33mwarn[39m: host.iobroker-1 does not start any instances on this host -
@marc-berg said in Backup aus älterer Version einspielen:
so ganz ohne Fehlermeldungen ist das jetzt Fischen im Trüben. Wie sieht es denn im Ordner /iobroker/log aus?
Welchen Ordner muss ich denn leeren, damit ich den Container erneute starten kann?
Hier ist mal der Log:
2023-12-08 09:48:33.700 - [32minfo[39m: host.db4cbef0bc80 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 09:48:33.706 - [32minfo[39m: host.db4cbef0bc80 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 09:48:33.707 - [32minfo[39m: host.db4cbef0bc80 hostname: db4cbef0bc80, node: v16.20.2 2023-12-08 09:48:33.708 - [32minfo[39m: host.db4cbef0bc80 ip addresses: 10.0.1.126 2023-12-08 09:48:33.957 - [32minfo[39m: host.db4cbef0bc80 connected to Objects and States 2023-12-08 09:48:33.994 - [32minfo[39m: host.db4cbef0bc80 Node.js version has changed from unknown to 16.20.2 2023-12-08 09:48:34.033 - [32minfo[39m: host.db4cbef0bc80 added notifications configuration of host 2023-12-08 09:48:34.251 - [32minfo[39m: host.db4cbef0bc80 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-12-08 09:48:34.289 - [32minfo[39m: host.db4cbef0bc80 3 instances found 2023-12-08 09:48:34.299 - [32minfo[39m: host.db4cbef0bc80 starting 3 instances 2023-12-08 09:48:34.360 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.admin.0 started with pid 2206 2023-12-08 09:48:34.553 - [32minfo[39m: host.db4cbef0bc80 Created UUID: ee7c0d0e-d418-4da2-bc87-b8432405ee7b 2023-12-08 09:48:36.403 - [32minfo[39m: admin.0 (2206) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v16.20.2, js-controller: 4.0.24 2023-12-08 09:48:36.460 - [32minfo[39m: admin.0 (2206) requesting all states 2023-12-08 09:48:36.461 - [32minfo[39m: admin.0 (2206) requesting all objects 2023-12-08 09:48:36.562 - [32minfo[39m: admin.0 (2206) received all objects 2023-12-08 09:48:36.599 - [32minfo[39m: admin.0 (2206) Request actual repository... 2023-12-08 09:48:36.622 - [32minfo[39m: host.db4cbef0bc80 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-12-08 09:48:36.711 - [32minfo[39m: admin.0 (2206) http server listening on port 8081 2023-12-08 09:48:36.712 - [32minfo[39m: admin.0 (2206) Use link "http://localhost:8081" to configure. 2023-12-08 09:48:36.720 - [32minfo[39m: admin.0 (2206) socket.io server listening on port 8081 2023-12-08 09:48:36.782 - [33mwarn[39m: admin.0 (2206) Repository cannot be read: Active repo - stable 2023-12-08 09:48:36.783 - [33mwarn[39m: admin.0 (2206) Active repository "stable" cannot be read 2023-12-08 09:48:36.802 - [31merror[39m: admin.0 (2206) Cannot update news: TypeError: newNews.forEach is not a function 2023-12-08 09:48:39.179 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.discovery.0 started with pid 2233 2023-12-08 09:48:39.381 - [32minfo[39m: admin.0 (2206) Repository received successfully. 2023-12-08 09:48:40.900 - [32minfo[39m: discovery.0 (2233) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.20.2, js-controller: 4.0.24 2023-12-08 09:48:42.335 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.backitup.0 started with pid 2248 2023-12-08 09:48:44.139 - [32minfo[39m: backitup.0 (2248) starting. Version 2.5.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.20.2, js-controller: 4.0.24 2023-12-08 09:48:44.262 - [32minfo[39m: backitup.0 (2248) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-12-08 09:51:09.032 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:51:10.922 - [32minfo[39m: admin.0 (2206) <== Disconnect system.user.admin from ::ffff:10.0.2.171 admin 2023-12-08 09:51:19.847 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:52:35.912 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:52:38.526 - [32minfo[39m: admin.0 (2206) <== Disconnect system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:52:54.495 - [32minfo[39m: admin.0 (2206) ==> Connected system.user.admin from ::ffff:10.0.2.171 2023-12-08 09:53:52.048 - [32minfo[39m: host.db4cbef0bc80 received SIGTERM 2023-12-08 09:53:52.053 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.admin.0 (force=false, process=true) 2023-12-08 09:53:52.054 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.discovery.0 (force=false, process=true) 2023-12-08 09:53:52.054 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-12-08 09:53:52.065 - [32minfo[39m: admin.0 (2206) Got terminate signal TERMINATE_YOURSELF 2023-12-08 09:53:52.065 - [32minfo[39m: discovery.0 (2233) Got terminate signal TERMINATE_YOURSELF 2023-12-08 09:53:52.069 - [32minfo[39m: backitup.0 (2248) Got terminate signal TERMINATE_YOURSELF 2023-12-08 09:53:52.066 - [32minfo[39m: admin.0 (2206) terminating http server on port 8081 2023-12-08 09:53:52.070 - [32minfo[39m: admin.0 (2206) terminating 2023-12-08 09:53:52.072 - [32minfo[39m: admin.0 (2206) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-08 09:53:52.067 - [32minfo[39m: discovery.0 (2233) terminating 2023-12-08 09:53:52.078 - [32minfo[39m: discovery.0 (2233) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-08 09:53:52.085 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.admin.0 send kill signal 2023-12-08 09:53:52.071 - [32minfo[39m: backitup.0 (2248) cleaned everything up... 2023-12-08 09:53:52.082 - [32minfo[39m: backitup.0 (2248) terminating 2023-12-08 09:53:52.083 - [32minfo[39m: backitup.0 (2248) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-08 09:53:52.088 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.discovery.0 send kill signal 2023-12-08 09:53:52.090 - [32minfo[39m: host.db4cbef0bc80 stopInstance system.adapter.backitup.0 send kill signal 2023-12-08 09:53:52.683 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-08 09:53:52.684 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-08 09:53:52.685 - [32minfo[39m: host.db4cbef0bc80 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-08 09:53:52.685 - [32minfo[39m: host.db4cbef0bc80 All instances are stopped. 2023-12-08 09:53:52.879 - [32minfo[39m: host.db4cbef0bc80 terminated 2023-12-08 09:55:57.094 - [32minfo[39m: host.iobroker-1 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 09:55:57.101 - [32minfo[39m: host.iobroker-1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 09:55:57.102 - [32minfo[39m: host.iobroker-1 hostname: iobroker-1, node: v16.20.2 2023-12-08 09:55:57.103 - [32minfo[39m: host.iobroker-1 ip addresses: 10.0.1.126 2023-12-08 09:55:58.041 - [33mwarn[39m: host.iobroker-1-Server Objects 10.0.1.65:42936 Error from InMemDB: Error: Unknown Script 2023-12-08 09:55:58.670 - [32minfo[39m: host.iobroker-1 connected to Objects and States 2023-12-08 09:55:58.727 - [32minfo[39m: host.iobroker-1 added notifications configuration of host 2023-12-08 09:55:58.742 - [32minfo[39m: host.iobroker-1 Node.js version has changed from 14.20.0 to 16.20.2 2023-12-08 09:55:58.932 - [32minfo[39m: host.iobroker-1 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2023-12-08 09:56:00.160 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.nodeCurrent" 2023-12-08 09:56:00.163 - [32minfo[39m: host.iobroker-1 34 instances found 2023-12-08 09:56:00.182 - [33mwarn[39m: host.iobroker-1 does not start any instances on this host 2023-12-08 09:56:00.218 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.nodeNewest" 2023-12-08 09:56:00.228 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.nodeNewestNext" 2023-12-08 09:56:00.238 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.npmCurrent" 2023-12-08 09:56:00.247 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.npmNewest" 2023-12-08 09:56:00.298 - [32minfo[39m: host.iobroker-1 Delete state "system.host.iobroker-1.versions.npmNewestNext" 2023-12-08 09:56:00.309 - [32minfo[39m: host.iobroker-1 Some obsolete host states deleted. 2023-12-08 10:01:31.417 - [32minfo[39m: host.iobroker-1 received SIGTERM 2023-12-08 10:01:31.460 - [32minfo[39m: host.iobroker-1 terminated 2023-12-08 10:02:12.098 - [32minfo[39m: host.iobroker-1 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 10:02:12.104 - [32minfo[39m: host.iobroker-1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 10:02:12.105 - [32minfo[39m: host.iobroker-1 hostname: iobroker-1, node: v16.20.2 2023-12-08 10:02:12.106 - [32minfo[39m: host.iobroker-1 ip addresses: 10.0.1.126 2023-12-08 10:02:13.373 - [32minfo[39m: host.iobroker-1 connected to Objects and States 2023-12-08 10:02:13.424 - [32minfo[39m: host.iobroker-1 added notifications configuration of host 2023-12-08 10:02:14.131 - [32minfo[39m: host.iobroker-1 34 instances found 2023-12-08 10:02:14.150 - [33mwarn[39m: host.iobroker-1 does not start any instances on this host 2023-12-08 10:10:19.617 - [32minfo[39m: host.iobroker-1 received SIGTERM 2023-12-08 10:10:19.661 - [32minfo[39m: host.iobroker-1 terminated 2023-12-08 10:11:04.261 - [32minfo[39m: host.iobroker-1 iobroker.js-controller version 4.0.24 js-controller starting 2023-12-08 10:11:04.270 - [32minfo[39m: host.iobroker-1 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-12-08 10:11:04.271 - [32minfo[39m: host.iobroker-1 hostname: iobroker-1, node: v16.20.2 2023-12-08 10:11:04.272 - [32minfo[39m: host.iobroker-1 ip addresses: 10.0.1.126 2023-12-08 10:11:05.632 - [32minfo[39m: host.iobroker-1 connected to Objects and States 2023-12-08 10:11:05.688 - [32minfo[39m: host.iobroker-1 added notifications configuration of host 2023-12-08 10:11:06.486 - [32minfo[39m: host.iobroker-1 34 instances found 2023-12-08 10:11:06.505 - [33mwarn[39m: host.iobroker-1 does not start any instances on this host@firefighter166 sagte in Backup aus älterer Version einspielen:
host.db4cbef0bc80 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
Ich sehe da immer noch den Hostnamen "db4cbef0bc80". Wie erstellst du den Container, und was hat der Befehl von oben
iob host thisausgegeben?
-
Also den Hostname bekomme ich ja von der Container Station vorgegeben ist die ID. Ich habe jetzt mal den oberen Befehlt ausgeführt und hier das Ergebnis.
# iob fix library: loaded Library version=2023-10-13 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-10-13 ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48,4 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB] Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4.586 B] Get:5 http://deb.debian.org/debian bullseye/main amd64 Packages [8.062 kB] Get:6 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages [776 B] Get:7 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [260 kB] Get:8 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [17,7 kB] Fetched 8.553 kB in 4s (2.130 kB/s) Reading package lists... Done Docker detected! If you have any adapters that need the CAP_NET_ADMIN capability, you need to start the docker container with the option --cap-add=NET_ADMIN and manually add that capability to node ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... This system does not support setting default permissions. Do not use npm to manually install adapters unless you know what you are doing! ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Cannot compress states.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! at JsonlDB.open (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:78:17) Compressing /opt/iobroker/iobroker-data/objects.jsonl Cannot compress objects.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! at JsonlDB.open (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:93:17) No relevant JSONL files found to compress, skip ========================================================================== Checking autostart (5/5) ========================================================================== Unsupported init system, cannot enable autostart! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== # pkill -u iobroker # iob host this Cannot use this command in multihost! iobroker host this Initialize current host Options: --help Show help [boolean] # -
Also den Hostname bekomme ich ja von der Container Station vorgegeben ist die ID. Ich habe jetzt mal den oberen Befehlt ausgeführt und hier das Ergebnis.
# iob fix library: loaded Library version=2023-10-13 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-10-13 ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48,4 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB] Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4.586 B] Get:5 http://deb.debian.org/debian bullseye/main amd64 Packages [8.062 kB] Get:6 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages [776 B] Get:7 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [260 kB] Get:8 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [17,7 kB] Fetched 8.553 kB in 4s (2.130 kB/s) Reading package lists... Done Docker detected! If you have any adapters that need the CAP_NET_ADMIN capability, you need to start the docker container with the option --cap-add=NET_ADMIN and manually add that capability to node ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... This system does not support setting default permissions. Do not use npm to manually install adapters unless you know what you are doing! ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Cannot compress states.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/states.jsonl"! at JsonlDB.open (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:78:17) Compressing /opt/iobroker/iobroker-data/objects.jsonl Cannot compress objects.jsonl: Error: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"! at JsonlDB.open (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@alcalzone/jsonl-db/build/lib/db.js:185:19) at async compressDB (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:37:9) at async main (/opt/iobroker/.npm/_npx/36bee06d4228a674/node_modules/@iobroker/jsonltool/index.js:93:17) No relevant JSONL files found to compress, skip ========================================================================== Checking autostart (5/5) ========================================================================== Unsupported init system, cannot enable autostart! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== # pkill -u iobroker # iob host this Cannot use this command in multihost! iobroker host this Initialize current host Options: --help Show help [boolean] #@firefighter166 sagte in Backup aus älterer Version einspielen:
Also den Hostname bekomme ich ja von der Container Station vorgegeben ist die ID
Ich kenne die Containerstation nicht, aber das Internet sagt mir:
Um einen Containernamen in der QNAP Container Station zu vergeben, können Sie die folgenden Schritte befolgen:
- Wechseln Sie im Menü zu Container.
- Klicken Sie auf Erstellen. Das Fenster “Container erstellen” wird geöffnet.
- Wählen Sie ein Image aus.
- Klicken Sie auf Weiter.
- Geben Sie einen Containernamen an, der 2-64 Zeichen enthält, mit einem Buchstaben oder einer Zahl beginnt und nur die folgenden Zeichen enthält:
Gültige Zeichen: A-Z , a-z , 0-9
Gültige Sonderzeichen: Bindestrich (-) , Unterstrich (_) oder Punkt (.)1
-
@firefighter166 sagte in Backup aus älterer Version einspielen:
Also den Hostname bekomme ich ja von der Container Station vorgegeben ist die ID
Ich kenne die Containerstation nicht, aber das Internet sagt mir:
Um einen Containernamen in der QNAP Container Station zu vergeben, können Sie die folgenden Schritte befolgen:
- Wechseln Sie im Menü zu Container.
- Klicken Sie auf Erstellen. Das Fenster “Container erstellen” wird geöffnet.
- Wählen Sie ein Image aus.
- Klicken Sie auf Weiter.
- Geben Sie einen Containernamen an, der 2-64 Zeichen enthält, mit einem Buchstaben oder einer Zahl beginnt und nur die folgenden Zeichen enthält:
Gültige Zeichen: A-Z , a-z , 0-9
Gültige Sonderzeichen: Bindestrich (-) , Unterstrich (_) oder Punkt (.)1
Sorry habe mich wohl falsch ausgedrückt das mit dem Hostnamen kann ich natürlich selbst bestimmt der lautet aktuell iobroker-1. Was ich nicht vorgeben kann, ist die Container ID.
-
Sorry habe mich wohl falsch ausgedrückt das mit dem Hostnamen kann ich natürlich selbst bestimmt der lautet aktuell iobroker-1. Was ich nicht vorgeben kann, ist die Container ID.
-
-
jetzt habe ich das gefunden mit dem Hostnamen und den muss ich mir jetzt aus dem Backup suchen, wenn ich es richtig verstanden habe.
-
jetzt habe ich das gefunden mit dem Hostnamen und den muss ich mir jetzt aus dem Backup suchen, wenn ich es richtig verstanden habe.
@firefighter166 sagte in Backup aus älterer Version einspielen:
jetzt habe ich das gefunden mit dem Hostnamen und den muss ich mir jetzt aus dem Backup suchen, wenn ich es richtig verstanden habe.
Genau, wie ich das jetzt sehe, hast du den Namen immer leer gelassen, dann wird wohl die ID vergeben. Stattdessen sollte da der alte Name rein. Müsste "iobroker-1" sein.
Support us
735
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge