Gelöst: Restore in neuem Docker funktioniert nicht
-
Moin,
ich habe einen ioBroker der schon ziemlich lange problemlos läuft.
Der läuft in einem Docker Container (buanet) auf meinem Unraid Server.Nun muss ich aber mal ein Update machen....damit es keinen Ärger mit meiner Frau gibt dachte ich mir "Ist ja ganz einfach....alten Container beenden, neuen Container erstellen (anderer Name anderer Path), backup, einspielen, fertig"....tja nur kommt das neue System nicht wirklich an den start.
- Im alten Container lies sich das Backup Modul nicht installieren, also habe ich das Backup auf der Commandozeile erstellt.
- Einen neuen Container angelegt mit force Update um die letzte IOBroker version zu bekommen und ein leeres Verzeichnis wo nur das Backup drin ist gemappt.
- Das System startet, findet das Update, macht auch was....aber kommt nicht wirklich hoch
-------------------------------------------------------------------------------- ------------------------- 2022-10-19 12:22:01 ------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Welcome to your ioBroker-container! ----- ----- Startupscript is now running. ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: x86_64 ----- ----- hostname: 06603c0c1fdf ----- ----- ----- ----- Docker-Image ----- ----- image: v7.0.1 ----- ----- build: 2022-10-13T23:57:48+00:00 ----- ----- ----- ----- Versions ----- ----- node: v16.17.1 ----- ----- npm: 8.15.0 ----- ----- ----- ----- ENV ----- ----- SETGID: 16 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- Updating Linux packages on first run... dpkg-preconfigure: unable to re-open stdin: Preparing to unpack .../tzdata_2021a-1+deb11u7_all.deb ... Unpacking tzdata (2021a-1+deb11u7) over (2021a-1+deb11u6) ... Preparing to unpack .../libksba8_1.5.0-3+deb11u1_amd64.deb ... Unpacking libksba8:amd64 (1.5.0-3+deb11u1) over (1.5.0-3) ... Preparing to unpack .../linux-libc-dev_5.10.149-1_amd64.deb ... Unpacking linux-libc-dev:amd64 (5.10.149-1) over (5.10.140-1) ... Preparing to unpack .../nodejs_16.18.0-deb-1nodesource1_amd64.deb ... Unpacking nodejs (16.18.0-deb-1nodesource1) over (16.17.1-deb-1nodesource1) ... Setting up libksba8:amd64 (1.5.0-3+deb11u1) ... Setting up linux-libc-dev:amd64 (5.10.149-1) ... Setting up nodejs (16.18.0-deb-1nodesource1) ... Setting up tzdata (2021a-1+deb11u7) ... Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 19 10:22:41 UTC 2022. Universal Time is now: Wed Oct 19 10:22:41 UTC 2022. Run 'dpkg-reconfigure tzdata' if you wish to change it. Processing triggers for libc-bin (2.31-13+deb11u4) ... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done. Registering maintenance script as command... Done. Installing additional packages is set by ENV. Checking the following Packages: ... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done. Different UID and/ or GID is set by ENV. Changing UID to 1000 and GID to 16... usermod: no changes Done. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- IoBroker backup file detected in /opt/iobroker. Preparing restore... Done. Restoring ioBroker... Done. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!! IMPORTANT NOTE !!!!! !!!!! The startup 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. The object system.adapter.admin.0 was not found! /opt/scripts/iobroker_startup.sh: line 212: [: !=: unary operator expected -------------------------------------------------------------------------------- ----- 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... object system.meta.uuid created: 853f9384-d3be-430f-8d11-42c3de9fefa1 object system.user.admin createdIm restore.log steht
host.06603c0c1fdf Using backup file 2022_10_18-16_39_12_backupiobroker.tar.gz iobroker controller daemon is not running host.06603c0c1fdf OK. Removing current installation of iobroker.admin removed 22 packages in 1s 37 packages are looking for funding run `npm fund` for details Removing current installation of iobroker.backitup removed 124 packages in 1s 30 packages are looking for funding run `npm fund` for details Removing current installation of iobroker.discovery removed 45 packages in 843ms 18 packages are looking for funding run `npm fund` for details host.06603c0c1fdf Clear all objects and states... clean 97 objects... clean 20 states... host.06603c0c1fdf done. host.06603c0c1fdf Processed 0/7272 objects host.06603c0c1fdf Processed 200/7272 objects host.06603c0c1fdf Processed 400/7272 objects host.06603c0c1fdf Processed 600/7272 objects host.06603c0c1fdf Processed 800/7272 objects host.06603c0c1fdf Processed 1000/7272 objects host.06603c0c1fdf Processed 1200/7272 objects host.06603c0c1fdf Processed 1400/7272 objects host.06603c0c1fdf Processed 1600/7272 objects host.06603c0c1fdf Processed 1800/7272 objects host.06603c0c1fdf Processed 2000/7272 objects host.06603c0c1fdf Processed 2200/7272 objects host.06603c0c1fdf Processed 2400/7272 objects host.06603c0c1fdf Processed 2600/7272 objects host.06603c0c1fdf Processed 2800/7272 objects host.06603c0c1fdf Processed 3000/7272 objects host.06603c0c1fdf Processed 3200/7272 objects host.06603c0c1fdf Processed 3400/7272 objects host.06603c0c1fdf Processed 3600/7272 objects host.06603c0c1fdf Processed 3800/7272 objects host.06603c0c1fdf Processed 4000/7272 objects host.06603c0c1fdf Processed 4200/7272 objects host.06603c0c1fdf Processed 4400/7272 objects host.06603c0c1fdf Processed 4600/7272 objects host.06603c0c1fdf Processed 4800/7272 objects host.06603c0c1fdf Processed 5000/7272 objects host.06603c0c1fdf Processed 5200/7272 objects host.06603c0c1fdf Processed 5400/7272 objects host.06603c0c1fdf Processed 5600/7272 objects host.06603c0c1fdf Processed 5800/7272 objects host.06603c0c1fdf Processed 6000/7272 objects host.06603c0c1fdf Processed 6200/7272 objects host.06603c0c1fdf Processed 6400/7272 objects host.06603c0c1fdf Processed 6600/7272 objects host.06603c0c1fdf Processed 6800/7272 objects host.06603c0c1fdf Processed 7000/7272 objects host.06603c0c1fdf Processed 7200/7272 objects 7272 objects restored. host.06603c0c1fdf Processed 0/6289 states host.06603c0c1fdf Processed 200/6289 states host.06603c0c1fdf Processed 400/6289 states host.06603c0c1fdf Processed 600/6289 states host.06603c0c1fdf Processed 800/6289 states host.06603c0c1fdf Processed 1000/6289 states host.06603c0c1fdf Processed 1200/6289 states host.06603c0c1fdf Processed 1400/6289 states host.06603c0c1fdf Processed 1600/6289 states host.06603c0c1fdf Processed 1800/6289 states host.06603c0c1fdf Processed 2000/6289 states host.06603c0c1fdf Processed 2200/6289 states host.06603c0c1fdf Processed 2400/6289 states host.06603c0c1fdf Processed 2600/6289 states host.06603c0c1fdf Processed 2800/6289 states host.06603c0c1fdf Processed 3000/6289 states host.06603c0c1fdf Processed 3200/6289 states host.06603c0c1fdf Processed 3400/6289 states host.06603c0c1fdf Processed 3600/6289 states host.06603c0c1fdf Processed 3800/6289 states host.06603c0c1fdf Processed 4000/6289 states host.06603c0c1fdf Processed 4200/6289 states host.06603c0c1fdf Processed 4400/6289 states host.06603c0c1fdf Processed 4600/6289 states host.06603c0c1fdf Processed 4800/6289 states host.06603c0c1fdf Processed 5000/6289 states host.06603c0c1fdf Processed 5200/6289 states host.06603c0c1fdf Processed 5400/6289 states host.06603c0c1fdf Processed 5600/6289 states host.06603c0c1fdf Processed 5800/6289 states host.06603c0c1fdf Processed 6000/6289 states host.06603c0c1fdf Processed 6200/6289 states 6289 states restored. host.06603c0c1fdf Upload user file "vis.0/echo/vis-views.json host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/Erdgeschoss.jpg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/Erdgeschoss_dark.jpg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/control_building_2_s_all.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/control_building_2_s_dg.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/control_building_2_s_eg.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/control_building_2_s_kg.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/control_minus.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/control_plus.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/fts_window_1w.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/fts_window_1w_open.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/hot_chili.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_0.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_0.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_100.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_100.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_25.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_25.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_50.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_50.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_75.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/measure_battery_75.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/message_presence.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/message_presence_active.svg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/metal_background.jpg host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/moon.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/new-image.bmp host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/sun_.png host.06603c0c1fdf Upload user file "vis.0/main/EigeneDaten/thermometer_icon.png host.06603c0c1fdf Upload user file "vis.0/main/vis-user.css host.06603c0c1fdf Upload user file "vis.0/main/vis-views.json host.06603c0c1fdf object system.licenses created Reinstalling adapter "admin" from "iobroker.admin@4.2.1" added 105 packages in 6s 21 packages are looking for funding run `npm fund` for details System successfully restored!Die info/status Ausgabe:
# iobroker info Cannot read system.config: null (OK when migrating or restoring) Platform : docker os : linux Architecture : x64 CPUs : 8 Speed : 1968 MHz Model : Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz RAM : 19.6 GB System uptime : 240d. 00:30:10 Node.js : v16.18.0 time : 1666176225436 timeOffset : -120 NPM : v8.19.2 Disk size : 40.0 GiB Disk free : 14.5 GiB # iobroker status Cannot read system.config: null (OK when migrating or restoring) iobroker is running on this host. Objects type: file States type: fileund in dem status scheint auch nicht wirklich mehr was zu passieren.
Die einzigen Files welche sich ändern sind unter "iobroker-data" die states.json und states.json.bak Dateien.Im iobroker_startup.sh die line 212 ist
if [ $(bash iobroker object get system.adapter.admin.0 --pretty | grep -oP '(?<="host": ")[^"]*') != $(hostname) ] && [ "$multihost" != "slave" ] then echo "Hostname in ioBroker does not match the hostname of this container." echo -n "Updating hostname to " $(hostname)"... " bash iobroker host $(iobroker object get system.adapter.admin.0 --pretty | grep -oP '(?<="host": ")[^"]*') echo 'Done.' echo ' ' fiScheinbar habe ich keinen admin Adapter mehr.....und auch keine Config
Kann mir eventuell jemand helfen?
Was ich vermeiden möchte ist direkt in dem noch heilen Container was zu ändern.Ich habe auch schon versucht das Backup nachträglich über den BackupAdapter in das neue, leere, System einzuspielen....führt aber am ende zu dem gleichen Ergebnis.
LG
-
@skydream sagte in Restore in neuem Docker funktioniert nicht:
Kann mir eventuell jemand helfen?
ich versuche es mal mit dem Standardprocedere. mit Docker kenne ich mich nicht aus.
was kommt bei
iobroker list instances iobroker list adapters iobroker update -i -
@skydream sagte in Restore in neuem Docker funktioniert nicht:
Hostname in ioBroker does not match the hostname of this container
aaaah, anderer Hostname??
dann hilft ggf. noch
iobroker host this -
@skydream sagte in Restore in neuem Docker funktioniert nicht:
also habe ich das Backup auf der Commandozeile erstellt.
pkill -u iobroker iobroker host thisdann den Container neu starten
-
@skydream sagte in Restore in neuem Docker funktioniert nicht:
iobroker.admin@4.2.1
der ist aber schon ... sehr alt !
Wie alt ist denn das Backup oder warst du nie Up to Date !?
-
@glasfaser
Das Backup ist von gestern....
Aber das System....nun.....also.....das läuft halt und tut was es soll, also habe ich es auch nicht angefasst seit sehr langer Zeit.
Den Rest versuche ich gleich mal
-
# iobroker list instances Cannot read system.config: null (OK when migrating or restoring) + instance is alive # iobroker list adapters Cannot read system.config: null (OK when migrating or restoring) # -
@skydream sagte in Restore in neuem Docker funktioniert nicht:
@glasfaser
Das Backup ist von gestern....
also habe ich es auch nicht angefasst seit sehr langer Zeit.Also stimmt der Versionsstand vom ioBroker bzw. ist dann alles im alten Stand !?
Aber das System....nun.....also.....das läuft halt und tut was es soll,
Aud dauer wirst du damit nicht Glücklich !
-
# iobroker host this Cannot read system.config: null (OK when migrating or restoring) Cannot find view "system" for search "host" An unknown error occurred: Cannot find view "system" # -
@skydream sagte in Restore in neuem Docker funktioniert nicht:
iobroker host this
welche Meldung kam nach dieser Befehlseingabe !?
-
Deswegen will ich ja auch updaten und alles auf einen neuen stand bringen.
Nur ich mag das nicht im laufenden System mache....meine Frau Köpft mich wenn die ganzen kleine Gizmos im Hintergrund nicht mehr funktionieren. -
Ähhh....habe ich doch oben gepostet:
An unknown error occurred: Cannot find view "system"
-
@skydream sagte in Restore in neuem Docker funktioniert nicht:
Ähhh....habe ich doch oben gepostet:
Das sind Bruchstücke ... einer Ausgabe
Bitte immer die Ein/ und Ausgabe hier komplett posten !
Bitte nochmal
pkill -u iobroker iobroker host this -
# # # pkill -u iobroker # iobroker host this Cannot read system.config: null (OK when migrating or restoring) Cannot find view "system" for search "host" An unknown error occurred: Cannot find view "system" # # -
Setze den Container neu auf und dann das Backup rein .
dann nochmal die Befehle in der Konsole .
-
OK
Melde mich wenn ich soweit bin. -
So der Container ist ohne ein Backup Aufgesetzt und läuft. Ich kann mich anmelden und das System ist auf einem aktuell stand...denke ich:
# iobroker list instances + system.adapter.admin.0 : admin : 190f42507de6 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : 190f42507de6 - enabled + system.adapter.discovery.0 : discovery : 190f42507de6 - enabled + instance is alive # iobroker list adapters system.adapter.admin : admin - v6.2.22 system.adapter.backitup : backitup - v2.4.12 system.adapter.discovery : discovery - v3.0.3 #Nun habe ich das Backup aus dem alten system in das neue unter "backups" kopiert damit der Adapter es findet.
Jetzt spiele ich über das WebInterface/Backup dieses Backup ein
Ab hier ist die Adminoberfläche nicht mehr nutzbar...meine aber was gelesen zu haben das der BackupAdapter unter Docker das restart nicht hinbekommt. Da es auch kein Docker Konsole mehr gibt starte ich den Container neu.
Start Log
-------------------------------------------------------------------------------- ------------------------- 2022-10-19 14:06:59 ------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Welcome to your ioBroker-container! ----- ----- Startupscript is now running. ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: x86_64 ----- ----- hostname: 190f42507de6 ----- ----- ----- ----- Docker-Image ----- ----- image: v7.0.1 ----- ----- build: 2022-10-13T23:57:48+00:00 ----- ----- ----- ----- Versions ----- ----- node: v16.17.1 ----- ----- npm: 8.15.0 ----- ----- ----- ----- ENV ----- ----- SETGID: 16 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- Updating Linux packages on first run... dpkg-preconfigure: unable to re-open stdin: Preparing to unpack .../tzdata_2021a-1+deb11u7_all.deb ... Unpacking tzdata (2021a-1+deb11u7) over (2021a-1+deb11u6) ... Preparing to unpack .../libksba8_1.5.0-3+deb11u1_amd64.deb ... Unpacking libksba8:amd64 (1.5.0-3+deb11u1) over (1.5.0-3) ... Preparing to unpack .../linux-libc-dev_5.10.149-1_amd64.deb ... Unpacking linux-libc-dev:amd64 (5.10.149-1) over (5.10.140-1) ... Preparing to unpack .../nodejs_16.18.0-deb-1nodesource1_amd64.deb ... Unpacking nodejs (16.18.0-deb-1nodesource1) over (16.17.1-deb-1nodesource1) ... Setting up libksba8:amd64 (1.5.0-3+deb11u1) ... Setting up linux-libc-dev:amd64 (5.10.149-1) ... Setting up nodejs (16.18.0-deb-1nodesource1) ... Setting up tzdata (2021a-1+deb11u7) ... Current default time zone: 'Etc/UTC' Local time is now: Wed Oct 19 12:07:32 UTC 2022. Universal Time is now: Wed Oct 19 12:07:32 UTC 2022. Run 'dpkg-reconfigure tzdata' if you wish to change it. Processing triggers for libc-bin (2.31-13+deb11u4) ... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done. Registering maintenance script as command... Done. Installing additional packages is set by ENV. Checking the following Packages: ... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done. Different UID and/ or GID is set by ENV. Changing UID to 1000 and GID to 16... usermod: no changes Done. -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- There is no data detected in /opt/iobroker. Restoring initial ioBroker installation... Done. -------------------------------------------------------------------------------- ----- 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 190f42507de6... The host for instance "system.adapter.admin.0" was changed from "buildkitsandbox" to "190f42507de6". The host for instance "system.adapter.discovery.0" was changed from "buildkitsandbox" to "190f42507de6". The host for instance "system.adapter.backitup.0" was changed from "buildkitsandbox" to "190f42507de6". 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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... host.190f42507de6 check instance "system.adapter.admin.0" for host "190f42507de6" host.190f42507de6 check instance "system.adapter.discovery.0" for host "190f42507de6" host.190f42507de6 check instance "system.adapter.backitup.0" for host "190f42507de6" object system.meta.uuid created: 684eff08-04b2-4af5-ba30-ea56a7b62c9a ================================== > LOG REDIRECT system.adapter.admin.0 => true [system.adapter.admin.0.logging] Send diag info: {"uuid":"684eff08-04b2-4af5-ba30-ea56a7b62c9a","language":"de","country":"Germany","hosts":[{"version":"4.0.23","platform":"Javascript/Node.js","type":"linux"}],"node":"v16.18.0","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.2.22","platform":"Javascript/Node.js"},"discovery":{"version":"3.0.3","platform":"Javascript/Node.js"},"backitup":{"version":"2.4.12","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz","cpus":8,"mem":21090963456,"ostype":"Linux","city":"Garbsen"} ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] Terminated Recived termination signal (SIGTERM). Shutting down ioBroker... -------------------------------------------------------------------------------- ------------------------- 2022-10-19 14:30:00 ------------------------- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Welcome to your ioBroker-container! ----- ----- Startupscript is now running. ----- ----- Please be patient! ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Debugging information ----- ----- ----- ----- System ----- ----- arch: x86_64 ----- ----- hostname: 190f42507de6 ----- ----- ----- ----- Docker-Image ----- ----- image: v7.0.1 ----- ----- build: 2022-10-13T23:57:48+00:00 ----- ----- ----- ----- Versions ----- ----- node: v16.18.0 ----- ----- npm: 8.19.2 ----- ----- ----- ----- ENV ----- ----- SETGID: 16 ----- ----- SETUID: 1000 ----- -------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ----- Step 1 of 5: Preparing container ----- -------------------------------------------------------------------------------- This is not the first run of this container. Skipping first run preparation. Installing additional packages is set by ENV. Checking the following Packages: ... Reading package lists... Building dependency tree... Reading state information... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Done. -------------------------------------------------------------------------------- ----- 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 see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/). -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... host.3b1886e597ab check instance "system.adapter.admin.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.mqtt.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.tr-064.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.daswetter.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.influxdb.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.web.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-colorpicker.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-history.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-timeandweather.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-players.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.javascript.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-hqwidgets.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.sayit.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-weather.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.ical.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.find-my-iphone.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-jqui-mfd.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-fancyswitch.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.alexa2.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.iot.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.cloud.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.hm-rpc.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.simple-api.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.sonoff.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.mihome-vacuum.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.scenes.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.milight.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.info.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.hm-rpc.1" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.vis-materialdesign.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.hm-rpc.2" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.phantomjs.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.zigbee.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.homeconnect.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.squeezeboxrpc.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.kodi.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.jarvis.0" for host "190f42507de6" host.3b1886e597ab check instance "system.adapter.pushsafer.0" for host "190f42507de6"Das sieht schonmal anders aus..
# iobroker list instances system.adapter.admin.0 : admin : 190f42507de6 - enabled, port: 8881, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : 190f42507de6 - disabled system.adapter.cloud.0 : cloud : 190f42507de6 - disabled system.adapter.daswetter.0 : daswetter : 190f42507de6 - disabled system.adapter.find-my-iphone.0 : find-my-iphone : 190f42507de6 - disabled system.adapter.flot.0 : flot : 190f42507de6 - disabled system.adapter.hm-rpc.0 : hm-rpc : 190f42507de6 - disabled, port: 20100 system.adapter.hm-rpc.1 : hm-rpc : 190f42507de6 - disabled, port: 20101 system.adapter.hm-rpc.2 : hm-rpc : 190f42507de6 - disabled, port: 20102 system.adapter.homeconnect.0 : homeconnect : 190f42507de6 - disabled system.adapter.ical.0 : ical : 190f42507de6 - disabled system.adapter.icons-material-png.0 : icons-material-png : 190f42507de6 - disabled system.adapter.icons-material-svg.0 : icons-material-svg : 190f42507de6 - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : 190f42507de6 - disabled system.adapter.icons-ultimate-png.0 : icons-ultimate-png : 190f42507de6 - disabled system.adapter.influxdb.0 : influxdb : 190f42507de6 - disabled, port: 8086 system.adapter.info.0 : info : 190f42507de6 - disabled system.adapter.iot.0 : iot : 190f42507de6 - disabled system.adapter.jarvis.0 : jarvis : 190f42507de6 - disabled system.adapter.javascript.0 : javascript : 190f42507de6 - disabled system.adapter.kodi.0 : kodi : 190f42507de6 - disabled, port: 9090 system.adapter.mihome-vacuum.0 : mihome-vacuum : 190f42507de6 - disabled, port: 54321 system.adapter.milight.0 : milight : 190f42507de6 - disabled, port: 5987 system.adapter.mqtt.0 : mqtt : 190f42507de6 - disabled, port: 1883, bind: 0.0.0.0 system.adapter.phantomjs.0 : phantomjs : 190f42507de6 - disabled system.adapter.pushsafer.0 : pushsafer : 190f42507de6 - disabled system.adapter.sayit.0 : sayit : 190f42507de6 - disabled, port: 0 system.adapter.scenes.0 : scenes : 190f42507de6 - disabled system.adapter.simple-api.0 : simple-api : 190f42507de6 - disabled, port: 8887, bind: 0.0.0.0, run as: admin system.adapter.sonoff.0 : sonoff : 190f42507de6 - disabled, port: 1885, bind: 0.0.0.0 system.adapter.squeezeboxrpc.0 : squeezeboxrpc : 190f42507de6 - disabled, port: 9000 system.adapter.tr-064.0 : tr-064 : 190f42507de6 - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : 190f42507de6 - disabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : 190f42507de6 - disabled system.adapter.vis-history.0 : vis-history : 190f42507de6 - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : 190f42507de6 - disabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : 190f42507de6 - disabled system.adapter.vis-materialdesign.0 : vis-materialdesign : 190f42507de6 - disabled system.adapter.vis-players.0 : vis-players : 190f42507de6 - disabled system.adapter.vis-timeandweather.0 : vis-timeandweather : 190f42507de6 - disabled system.adapter.vis-weather.0 : vis-weather : 190f42507de6 - disabled system.adapter.vis.0 : vis : 190f42507de6 - disabled system.adapter.web.0 : web : 190f42507de6 - disabled, port: 8882, bind: 0.0.0.0, run as: admin system.adapter.zigbee.0 : zigbee : 190f42507de6 - disabled, port: /dev/ttyUSB0 + instance is alive # ^C #Er hat auch erkannt das der Admin Port wie vorher auf 8881 liegt
und die Adapter:# # iobroker list adapters system.adapter.admin : admin - v4.2.1 system.adapter.alexa2 : alexa2 - v3.8.1 system.adapter.cloud : cloud - v3.0.2 system.adapter.daswetter : daswetter - v3.0.4 system.adapter.discovery : discovery - v2.2.2 system.adapter.find-my-iphone : find-my-iphone - v0.2.15 system.adapter.flot : flot - v1.10.7 system.adapter.hm-rpc : hm-rpc - v1.12.10 system.adapter.homeconnect : homeconnect - v0.0.30 system.adapter.ical : ical - v1.7.0 system.adapter.icons-material-png : icons-material-png - v0.1.0 system.adapter.icons-material-svg : icons-material-svg - v0.1.0 system.adapter.icons-mfd-svg : icons-mfd-svg - v1.1.0 system.adapter.icons-ultimate-png : icons-ultimate-png - v1.0.1 system.adapter.influxdb : influxdb - v1.9.4 system.adapter.info : info - v1.5.6 system.adapter.iot : iot - v1.8.16 system.adapter.jarvis : jarvis - v3.0.11 system.adapter.javascript : javascript - v4.3.4 system.adapter.kodi : kodi - v2.0.4 system.adapter.lightify : lightify - v0.2.16 system.adapter.mihome-vacuum : mihome-vacuum - v2.0.9 system.adapter.milight : milight - v0.3.6 system.adapter.mqtt : mqtt - v2.4.0 system.adapter.phantomjs : phantomjs - v1.1.2 system.adapter.pushsafer : pushsafer - v1.0.3 system.adapter.sayit : sayit - v1.8.2 system.adapter.scenes : scenes - v1.1.0 system.adapter.simple-api : simple-api - v2.4.5 system.adapter.sonoff : sonoff - v2.4.0 system.adapter.squeezeboxrpc : squeezeboxrpc - v1.0.0 system.adapter.terminal : terminal - v0.1.2 system.adapter.tr-064 : tr-064 - v4.2.14 system.adapter.tr-064-community : tr-064-community - v1.1.0 system.adapter.tradfri : tradfri - v1.5.4 system.adapter.vis : vis - v1.3.8 system.adapter.vis-colorpicker : vis-colorpicker - v1.2.0 system.adapter.vis-fancyswitch : vis-fancyswitch - v1.1.0 system.adapter.vis-history : vis-history - v1.0.0 system.adapter.vis-hqwidgets : vis-hqwidgets - v1.1.4 system.adapter.vis-jqui-mfd : vis-jqui-mfd - v1.0.12 system.adapter.vis-materialdesign : vis-materialdesign - v0.2.61 system.adapter.vis-players : vis-players - v0.1.5 system.adapter.vis-timeandweather : vis-timeandweather - v1.1.7 system.adapter.vis-weather : vis-weather - v2.5.2 system.adapter.web : web - v3.3.0 system.adapter.zigbee : zigbee - v1.5.6Nur ich komme nicht auf das Admin interface.....
Weder direkt über die Dockerinterne IP
172.17.0.4:8881
172.17.0.4:8081
noch über die Gemappte des Server
192.168.1.1:8881aber er läuft...sagt er...
# iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonlDas iobroker log:
root@nas:/mnt/cache/appdata/iobroker/Update/log# more iobroker.current.log 2022-10-19 14:08:17.661 - info: host.190f42507de6 iobroker.js-controller version 4.0.23 js-controller starting 2022-10-19 14:08:17.663 - info: host.190f42507de6 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2022-10-19 14:08:17.663 - info: host.190f42507de6 hostname: 190f42507de6, node: v16.18.0 2022-10-19 14:08:17.664 - info: host.190f42507de6 ip addresses: 172.17.0.4 2022-10-19 14:08:17.922 - info: host.190f42507de6 connected to Objects and States 2022-10-19 14:08:17.932 - info: host.190f42507de6 Node.js version has changed from unknown to 16.18.0 2022-10-19 14:08:17.961 - info: host.190f42507de6 added notifications configuration of host 2022-10-19 14:08:18.093 - info: host.190f42507de6 3 instances found 2022-10-19 14:08:18.096 - info: host.190f42507de6 starting 3 instances 2022-10-19 14:08:18.113 - info: host.190f42507de6 instance system.adapter.admin.0 started with pid 861 2022-10-19 14:08:18.228 - info: host.190f42507de6 Created UUID: 684eff08-04b2-4af5-ba30-ea56a7b62c9a 2022-10-19 14:08:18.263 - info: host.190f42507de6 Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2022-10-19 14:08:18.724 - info: admin.0 (861) starting. Version 6.2.22 in /opt/iobroker/node_modules/iobroker.admin, node: v16.18.0, js-controller: 4.0.23 2022-10-19 14:08:18.740 - info: admin.0 (861) requesting all states 2022-10-19 14:08:18.741 - info: admin.0 (861) requesting all objects 2022-10-19 14:08:18.773 - info: admin.0 (861) received all objects 2022-10-19 14:08:18.782 - info: admin.0 (861) Request actual repository... 2022-10-19 14:08:18.787 - info: host.190f42507de6 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2022-10-19 14:08:18.830 - info: admin.0 (861) http server listening on port 8081 2022-10-19 14:08:18.830 - info: admin.0 (861) Use link "http://localhost:8081" to configure. 2022-10-19 14:08:18.833 - info: admin.0 (861) socket.io server listening on port 8081 2022-10-19 14:08:18.922 - warn: admin.0 (861) Repository cannot be read: Active repo - stable 2022-10-19 14:08:18.923 - warn: admin.0 (861) Active repository "stable" cannot be read 2022-10-19 14:08:19.923 - info: admin.0 (861) Repository received successfully. 2022-10-19 14:08:22.106 - info: host.190f42507de6 instance system.adapter.discovery.0 started with pid 889 2022-10-19 14:08:22.606 - info: discovery.0 (889) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.discovery, node: v16.18.0, js-controller: 4.0.23 2022-10-19 14:08:26.106 - info: host.190f42507de6 instance system.adapter.backitup.0 started with pid 904 2022-10-19 14:08:26.670 - info: backitup.0 (904) starting. Version 2.4.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v16.18.0, js-controller: 4.0.23 2022-10-19 14:08:26.692 - info: backitup.0 (904) [iobroker] backup was activated at 02:40 every 1 day(s) 2022-10-19 14:10:22.254 - info: admin.0 (861) ==> Connected system.user.admin from ::ffff:192.168.1.118 2022-10-19 14:16:59.018 - info: admin.0 (861) ==> Connected system.user.admin from ::ffff:192.168.1.118 2022-10-19 14:18:43.956 - info: admin.0 (861) <== Disconnect system.user.admin from ::ffff:192.168.1.118 2022-10-19 14:18:47.019 - info: admin.0 (861) ==> Connected system.user.admin from ::ffff:192.168.1.118 2022-10-19 14:21:32.396 - info: admin.0 (861) <== Disconnect system.user.admin from ::ffff:192.168.1.118 2022-10-19 14:21:39.167 - info: admin.0 (861) ==> Connected system.user.admin from ::ffff:192.168.1.118 2022-10-19 14:23:19.930 - info: host.190f42507de6 received SIGTERM 2022-10-19 14:23:19.932 - info: host.190f42507de6 stopInstance system.adapter.admin.0 (force=false, process=true) 2022-10-19 14:23:19.932 - info: host.190f42507de6 stopInstance system.adapter.discovery.0 (force=false, process=true) 2022-10-19 14:23:19.933 - info: host.190f42507de6 stopInstance system.adapter.backitup.0 (force=false, process=true) 2022-10-19 14:23:19.935 - info: admin.0 (861) Got terminate signal TERMINATE_YOURSELF 2022-10-19 14:23:19.936 - info: host.190f42507de6 stopInstance system.adapter.admin.0 send kill signal 2022-10-19 14:23:19.936 - info: host.190f42507de6 stopInstance system.adapter.discovery.0 send kill signal 2022-10-19 14:23:19.936 - info: discovery.0 (889) Got terminate signal TERMINATE_YOURSELF 2022-10-19 14:23:19.936 - info: backitup.0 (904) Got terminate signal TERMINATE_YOURSELF 2022-10-19 14:23:19.936 - info: host.190f42507de6 stopInstance system.adapter.backitup.0 send kill signal 2022-10-19 14:23:19.936 - info: admin.0 (861) terminating http server on port 8081 2022-10-19 14:23:19.937 - info: admin.0 (861) terminating 2022-10-19 14:23:19.937 - info: admin.0 (861) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2022-10-19 14:23:19.937 - info: discovery.0 (889) terminating 2022-10-19 14:23:19.937 - info: discovery.0 (889) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2022-10-19 14:23:19.937 - info: backitup.0 (904) cleaned everything up... 2022-10-19 14:23:19.937 - info: backitup.0 (904) terminating 2022-10-19 14:23:19.938 - info: backitup.0 (904) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2022-10-19 14:23:20.458 - info: host.190f42507de6 instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2022-10-19 14:23:20.498 - info: host.190f42507de6 instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2022-10-19 14:23:20.500 - info: host.190f42507de6 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2022-10-19 14:23:20.500 - info: host.190f42507de6 All instances are stopped. 2022-10-19 14:23:20.546 - info: host.190f42507de6 terminated 2022-10-19 14:30:17.047 - info: host.3b1886e597ab iobroker.js-controller version 4.0.23 js-controller starting 2022-10-19 14:30:17.050 - info: host.3b1886e597ab Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2022-10-19 14:30:17.050 - info: host.3b1886e597ab hostname: 3b1886e597ab, node: v16.18.0 2022-10-19 14:30:17.050 - info: host.3b1886e597ab ip addresses: 172.17.0.4 2022-10-19 14:30:17.340 - info: host.3b1886e597ab Sets unsupported 2022-10-19 14:30:17.609 - info: host.3b1886e597ab connected to Objects and States 2022-10-19 14:30:17.624 - info: host.3b1886e597ab added notifications configuration of host 2022-10-19 14:30:17.626 - info: host.3b1886e597ab Node.js version has changed from unknown to 16.18.0 2022-10-19 14:30:17.739 - info: host.3b1886e597ab Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node 2022-10-19 14:30:17.917 - info: host.3b1886e597ab Delete host system.host.190f42507de6 2022-10-19 14:30:17.953 - info: host.3b1886e597ab 44 instances found 2022-10-19 14:30:17.960 - warn: host.3b1886e597ab does not start any instances on this hostDie letzte Zeile:
host.3b1886e597ab does not start any instances on this host
Ist der Patient noch zu retten?
-
@skydream sagte in Restore in neuem Docker funktioniert nicht:
host.3b1886e597ab does not start any instances on this host
was ist jetzt dein host?
hier steht ein anderer
@skydream sagte in Restore in neuem Docker funktioniert nicht:
system.adapter.admin.0 : admin : 190f42507de6 - enabled, port: 8881, bind: 0.0.0.0, run as: admin
-
Also der Hostname ist
# hostname 190f42507de6wenn du das mit host meinst.
Vermutlich ist die 3b1886e597ab der aus dem Backup?
-
@skydream sagte in Restore in neuem Docker funktioniert nicht:
Vermutlich ist die 3b1886e597ab der aus dem Backup?
sag du es mir! ich kenne die Namen deiner Hosts nicht.
