Kein restore mit backitup [gelöst]
-
@christian-sandkaulen
iobroker logs --watchzeigt den Fortgang im Log File.
2021-08-16 15:43:23.925 - info: host.PI4 All instances are stopped. 2021-08-16 15:43:23.987 - info: host.PI4 terminated 2021-08-16 15:43:23.446 - info: host.PI4 instance system.adapter.mqtt.0 terminated with code null () 2021-08-16 15:43:23.575 - warn: host.PI4 instance system.adapter.ping.0 terminated due to SIGTERM 2021-08-16 15:43:23.576 - info: host.PI4 instance system.adapter.ping.0 terminated with code null () 2021-08-16 15:43:23.577 - warn: host.PI4 instance system.adapter.sonoff.0 terminated due to SIGTERM 2021-08-16 15:43:23.577 - info: host.PI4 instance system.adapter.sonoff.0 terminated with code null () 2021-08-16 15:43:23.765 - warn: host.PI4 instance system.adapter.logparser.0 terminated due to SIGTERM 2021-08-16 15:43:23.765 - info: host.PI4 instance system.adapter.logparser.0 terminated with code null () 2021-08-16 15:43:23.766 - warn: host.PI4 instance system.adapter.shelly.0 terminated due to SIGTERM 2021-08-16 15:43:23.766 - info: host.PI4 instance system.adapter.shelly.0 terminated with code null () 2021-08-16 15:43:23.854 - warn: host.PI4 instance system.adapter.zigbee.0 terminated due to SIGTERM 2021-08-16 15:43:23.855 - info: host.PI4 instance system.adapter.zigbee.0 terminated with code null () 2021-08-16 15:43:23.855 - warn: host.PI4 instance system.adapter.tankerkoenig.0 terminated due to SIGTERM 2021-08-16 15:43:23.856 - info: host.PI4 instance system.adapter.tankerkoenig.0 terminated with code null () 2021-08-16 15:43:23.924 - info: host.PI4 instance system.adapter.history.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-08-16 15:43:23.925 - info: host.PI4 All instances are stopped. 2021-08-16 15:43:23.987 - info: host.PI4 terminatedmüsste da nicht mehr stehen?
-
2021-08-16 15:43:23.925 - info: host.PI4 All instances are stopped. 2021-08-16 15:43:23.987 - info: host.PI4 terminated 2021-08-16 15:43:23.446 - info: host.PI4 instance system.adapter.mqtt.0 terminated with code null () 2021-08-16 15:43:23.575 - warn: host.PI4 instance system.adapter.ping.0 terminated due to SIGTERM 2021-08-16 15:43:23.576 - info: host.PI4 instance system.adapter.ping.0 terminated with code null () 2021-08-16 15:43:23.577 - warn: host.PI4 instance system.adapter.sonoff.0 terminated due to SIGTERM 2021-08-16 15:43:23.577 - info: host.PI4 instance system.adapter.sonoff.0 terminated with code null () 2021-08-16 15:43:23.765 - warn: host.PI4 instance system.adapter.logparser.0 terminated due to SIGTERM 2021-08-16 15:43:23.765 - info: host.PI4 instance system.adapter.logparser.0 terminated with code null () 2021-08-16 15:43:23.766 - warn: host.PI4 instance system.adapter.shelly.0 terminated due to SIGTERM 2021-08-16 15:43:23.766 - info: host.PI4 instance system.adapter.shelly.0 terminated with code null () 2021-08-16 15:43:23.854 - warn: host.PI4 instance system.adapter.zigbee.0 terminated due to SIGTERM 2021-08-16 15:43:23.855 - info: host.PI4 instance system.adapter.zigbee.0 terminated with code null () 2021-08-16 15:43:23.855 - warn: host.PI4 instance system.adapter.tankerkoenig.0 terminated due to SIGTERM 2021-08-16 15:43:23.856 - info: host.PI4 instance system.adapter.tankerkoenig.0 terminated with code null () 2021-08-16 15:43:23.924 - info: host.PI4 instance system.adapter.history.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-08-16 15:43:23.925 - info: host.PI4 All instances are stopped. 2021-08-16 15:43:23.987 - info: host.PI4 terminatedmüsste da nicht mehr stehen?
@christian-sandkaulen
Seit einer Stunde läuft das? Oder ist deine Zeitzone falsch?date && date -u -
@christian-sandkaulen
Seit einer Stunde läuft das? Oder ist deine Zeitzone falsch?date && date -u@thomas-braun said in Kein restore mit backitup:
date && date -u
ne seit einer stunde
Mo 16. Aug 16:44:45 CEST 2021 Mo 16. Aug 14:44:45 UTC 2021 -
@thomas-braun said in Kein restore mit backitup:
date && date -u
ne seit einer stunde
Mo 16. Aug 16:44:45 CEST 2021 Mo 16. Aug 14:44:45 UTC 2021@christian-sandkaulen
Das dürfte dann abgenippelt sein.
iobroker start Iobroker status which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs -
@christian-sandkaulen
Das dürfte dann abgenippelt sein.
iobroker start Iobroker status which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs@thomas-braun said in Kein restore mit backitup:
Iobroker status
iobroker is running on this host. Objects type: file States type: file-v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.22.1 v12.22.1 6.14.12 nodejs: Installiert: 12.22.1-1nodesource1 Installationskandidat: 12.22.1-1nodesource1 Versionstabelle: *** 12.22.1-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages -
@thomas-braun said in Kein restore mit backitup:
Iobroker status
iobroker is running on this host. Objects type: file States type: file-v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.22.1 v12.22.1 6.14.12 nodejs: Installiert: 12.22.1-1nodesource1 Installationskandidat: 12.22.1-1nodesource1 Versionstabelle: *** 12.22.1-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages@christian-sandkaulen
Damn bringst du jetzt erstmal dein Betriebssystem auf Stand:iobroker stop sudo apt update sudo apt dist-upgrade sudo reboot -
@thomas-braun said in Kein restore mit backitup:
Iobroker status
iobroker is running on this host. Objects type: file States type: file-v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.22.1 v12.22.1 6.14.12 nodejs: Installiert: 12.22.1-1nodesource1 Installationskandidat: 12.22.1-1nodesource1 Versionstabelle: *** 12.22.1-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages -
im backitup adapter ist jetzt das aufgetaucht
Started restore ... [DEBUG] [iobroker] Start ioBroker Restore ... [EXIT] 0 -
@christian-sandkaulen
Ist dein OS jetzt gepatcht? -
@christian-sandkaulen
Ist dein OS jetzt gepatcht?pi@PI4:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.22.5 v12.22.5 6.14.14 nodejs: Installiert: 12.22.5-1nodesource1 Installationskandidat: 12.22.5-1nodesource1 Versionstabelle: *** 12.22.5-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@PI4:~ $denke schon oder?
-
pi@PI4:~ $ which nodejs node npm && nodejs -v && node -v && npm -v && apt policy nodejs /usr/bin/nodejs /usr/bin/node /usr/bin/npm v12.22.5 v12.22.5 6.14.14 nodejs: Installiert: 12.22.5-1nodesource1 Installationskandidat: 12.22.5-1nodesource1 Versionstabelle: *** 12.22.5-1nodesource1 500 500 https://deb.nodesource.com/node_12.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u1 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages pi@PI4:~ $denke schon oder?
@christian-sandkaulen
Und wie ist jetzt der Status? Backup drin? -
@christian-sandkaulen
Und wie ist jetzt der Status? Backup drin? -
nein das bleibt immer noch hängen auch ein älteres, ein neues erstellen ging aber.
-
@christian-sandkaulen
Installier den Adapter nochmal. -
@christian-sandkaulen
Installier den Adapter nochmal. -
als zweite Instanz ?
@christian-sandkaulen
Nein, über den Adapter drüber.iobroker upgrade backitup@2.1.13 -
@christian-sandkaulen
Nein, über den Adapter drüber.iobroker upgrade backitup@2.1.13@thomas-braun said in Kein restore mit backitup:
iobroker upgrade backitup@2.1.13
pi@PI4:~ $ iobroker upgrade backitup@2.1.13 Would you like to reinstall version 2.1.13 of backitup now? [(y)es, (n)o]: y Update backitup from @2.1.13 to @2.1.13 host.PI4 Adapter "system.adapter.backitup.0" is stopped. NPM version: 6.14.14 npm install iobroker.backitup@2.1.13 --loglevel error --prefix "/opt/iobroker" ( System call)müsste da nicht mehr passsieren?
-
@thomas-braun said in Kein restore mit backitup:
iobroker upgrade backitup@2.1.13
pi@PI4:~ $ iobroker upgrade backitup@2.1.13 Would you like to reinstall version 2.1.13 of backitup now? [(y)es, (n)o]: y Update backitup from @2.1.13 to @2.1.13 host.PI4 Adapter "system.adapter.backitup.0" is stopped. NPM version: 6.14.14 npm install iobroker.backitup@2.1.13 --loglevel error --prefix "/opt/iobroker" ( System call)müsste da nicht mehr passsieren?
@christian-sandkaulen
upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.js index_m.js application/javascript upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript Adapter "backitup" updatedhat ewig gedauert.
-
@christian-sandkaulen
upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.js index_m.js application/javascript upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript Adapter "backitup" updatedhat ewig gedauert.
@christian-sandkaulen
Du bist zu ungeduldig.
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
610
Online32.7k
Benutzer82.6k
Themen1.3m
Beiträge