Wiederherstellung nach Neuinstallation Backitup Probleme
-
Dann dürfte das Backup gar nicht reinkommen. Hier hakelt es aber an der Beta-Version, die lässt sich offenbar im Moment nicht frisch installieren.
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Bisher bin ich eigentlich sehr gut gefahren mit dem Latest Repo.
passt nicht zu
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Da ich mit meinem aktuellen ioBroker Probleme habe
Und dann wieder latest und auch noch einen Container.
Hast du dich inzwischen mit den Eigenheiten eines Containers erfolgreich auseinandergesetzt und weisst wie man diese Problematiken löst? -
@thomas-braun sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Dann dürfte das Backup gar nicht reinkommen
ich meinte eher, falls er cifs im backitup eingerichtet hatte und durchs backup ja zurück spielt, aber die cifs utils noch gar nicht auf dem frischen System installiert hat.
-
@homoran sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Hast du dich inzwischen mit den Eigenheiten eines Containers erfolgreich auseinandergesetzt und weisst wie man diese Problematiken löst?
dazu kommt bestimmt ein Folge Thread, wie bekomme ich mein zigbee durchgereicht/zum laufen
-
@crunchip sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
wie bekomme ich mein zigbee durchgereicht
es reicht ja erst einmal: wie bekomme ich meinen mount durchgereicht
-
@homoran said in Wiederherstellung nach Neuinstallation Backitup Probleme:
Hast du dich inzwischen mit den Eigenheiten eines Containers erfolgreich auseinandergesetzt und weisst wie man diese Problematiken löst?
Also das sollte hiermit funktionieren.
Ich hatte auch Debmatic über einen LXC laufen mit durchgereichtem Modul. Ganz so fremd sind mir die LXC nicht auch ext. HDD mounten ist kein Problem, das war alles auf der alten Hardware so.
Fakt ist ja das jetzt der Backitup in Schleife Fehler in die Log schreibt, zwar nicht mehr von der VIS aber sobald der Backitup startet kommen ja die Meldungen vom Host.
Ich wollte jetzt mal schauen ob eine neue Basis Installation mit anschließendem Restore die Fehler mit dem Ram immer noch auftreten.
Und wie gesagt, vor dem ganzen Updaten von nodejs und dem Umzug lief ja alles stabil, ich hatte mit dem System und den Adaptern keine Problem. Also wollte ich nun noch mal eine saubere Install starten und dann drauf aufbauen.
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Ich wollte jetzt mal schauen ob eine neue Basis Installation mit anschließendem Restore die Fehler mit dem Ram immer noch auftreten.
mag sein, das falls erfolgreich, zwar ein sauberes system hast, dein Problem aber zu 99,8% von deinen Scripten kommt
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
vor dem ganzen Updaten
das mag sein, jedoch müssen einige Scripte für die folgenden version wie Js-controller, node, admin, etc... eben angepasst werden. Oder willst du dann alles ohne Updates weiter laufen lassen
-
@crunchip Ich hab jetzt mal alles ohne Scripte restored um zu schauen ob auch die Fehler mit dem weatherunderground, daswetter und Co wieder auftauchen. Des weiteren hatte er ja auch Probleme mit dem Zigbee Adapter obwohl die States sauber rein kamen, nach Rebuild war die Meldung zwar weck, aber dann muss doch beim upgrade auf nodejs 14 irgendwas schief gelaufen sein.
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Rebuild war die Meldung zwar weck, aber dann muss doch beim upgrade auf nodejs 14 irgendwas schief gelaufen sein
nö, ist bekannt beim zigbee
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
ch hab jetzt mal alles ohne Scripte restored
wie hast du das denn geschafft?
Die Skripte sind in den Tiefen des Backups enthalten. -
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
Zigbee Adapter obwohl die States sauber rein kamen, nach Rebuild war die Meldung zwar weck, aber dann muss doch beim upgrade auf nodejs 14 irgendwas schief gelaufen sein.
Der zigbee-Adapter muss nach einem node-Upgrade immer gegen die neue Version gebaut werden. Da läuft nix schief, das ist so.
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
aber dann muss doch beim upgrade auf nodejs 14 irgendwas schief gelaufen sein.
ich weiß nicht warum du dich immer noch an diese krude Theorie klammerst.
Deine Problem kommen von deinen Skripten -
@homoran said in Wiederherstellung nach Neuinstallation Backitup Probleme:
wie hast du das denn geschafft?
Die Skripte sind in den Tiefen des Backups enthalten.Ups, indem ich Quatsch erzähle. Ich war der Meinung die konnte man separat einspielen... Ich komm gar nicht mehr klar, wenn man den ganzen Tag an der Kiste sitzt und versucht das ganze wieder stabil zum laufen zu bekommen.
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
versucht das ganze wieder stabil zum laufen zu bekommen.
Mit dem Beta-Repo bekommst du das schon qua Definition nicht 'stabil'.
-
@d3ltoroxp sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
separat einspiele
separat sichern
-
Guten Morgen,
ich möchte gerne von meinem PI auf Proxmox umziehen.
Leider funtioniert aber die Wiederherstellung nicht. Ich auch nicht den Fehler.Habe nun mal die bei LOG beigefügt, vielleicht kann mir ja jemand helfen.
Es werden einfach nicht die Adapter nach wiederherstellung installiert.[DEBUG] [iobroker] Start ioBroker Restore ... [DEBUG] [iobroker] iobroker controller daemon is not running [DEBUG] [iobroker] host.iobroker2 OK. [DEBUG] [iobroker] Removing current installation of iobroker.admin [DEBUG] [iobroker] removed 24 packages in 2s [DEBUG] [iobroker] 44 packages are looking for funding [DEBUG] [iobroker] run `npm fund` for details [DEBUG] [iobroker] Removing current installation of iobroker.backitup [DEBUG] [iobroker] removed 147 packages in 2s [DEBUG] [iobroker] 25 packages are looking for funding [DEBUG] [iobroker] run `npm fund` for details [DEBUG] [iobroker] Removing current installation of iobroker.discovery [DEBUG] [iobroker] removed 43 packages in 1s [DEBUG] [iobroker] 13 packages are looking for funding [DEBUG] [iobroker] run `npm fund` for details [DEBUG] [iobroker] host.iobroker2 Clear all objects and states... [DEBUG] [iobroker] clean 142 objects... [DEBUG] [iobroker] clean 100 states... [DEBUG] [iobroker] host.iobroker2 done. [DEBUG] [iobroker] host.iobroker2 Processed 0/143 objects [DEBUG] [iobroker] 143 objects restored. [DEBUG] [iobroker] host.iobroker2 Processed 0/102 states [DEBUG] [iobroker] 102 states restored. [DEBUG] [iobroker] Reinstalling adapter "admin" from "iobroker.admin@6.3.5" [DEBUG] [iobroker] added 80 packages in 9s [DEBUG] [iobroker] 20 packages are looking for funding [DEBUG] [iobroker] run `npm fund` for details [DEBUG] [iobroker] Reinstalling adapter "backitup" from "iobroker.backitup@2.6.16" [DEBUG] [iobroker] added 94 packages in 9s [DEBUG] [iobroker] 33 packages are looking for funding [DEBUG] [iobroker] run `npm fund` for details [DEBUG] [iobroker] Forced restore - executing setup ... [DEBUG] [iobroker] System successfully restored! [DEBUG] [iobroker] ioBroker Restore completed successfully [EXIT] 0 **** Restore completed successfully!! ****2023-05-01 04:01:40.484 - info: admin.0 (11928) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 04:02:00.485 - info: admin.0 (11928) <== Disconnect system.user.admin from ::ffff:192.168.2.55 admin 2023-05-01 04:02:26.204 - info: admin.0 (11928) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 04:11:28.396 - info: admin.0 (11928) <== Disconnect system.user.admin from ::ffff:192.168.2.55 admin 2023-05-01 04:17:36.077 - info: admin.0 (11928) terminating http server on port 8081 2023-05-01 04:17:36.081 - info: backitup.0 (11970) cleaned everything up... 2023-05-01 04:17:36.100 - info: host.iobroker2 received SIGTERM 2023-05-01 04:17:36.105 - info: host.iobroker2 stopInstance system.adapter.admin.0 (force=false, process=true) 2023-05-01 04:17:36.105 - info: host.iobroker2 stopInstance system.adapter.discovery.0 (force=false, process=true) 2023-05-01 04:17:36.105 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 04:17:36.130 - info: admin.0 (11928) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 04:17:36.130 - info: discovery.0 (11955) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 04:17:36.140 - info: admin.0 (11928) Got terminate signal TERMINATE_YOURSELF 2023-05-01 04:17:36.141 - info: backitup.0 (11970) Got terminate signal TERMINATE_YOURSELF 2023-05-01 04:17:36.142 - info: discovery.0 (11955) Got terminate signal TERMINATE_YOURSELF 2023-05-01 04:17:36.147 - info: host.iobroker2 stopInstance system.adapter.admin.0 send kill signal 2023-05-01 04:17:36.147 - info: host.iobroker2 stopInstance system.adapter.discovery.0 send kill signal 2023-05-01 04:17:36.147 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 04:17:36.188 - info: backitup.0 (11970) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 04:17:36.671 - info: host.iobroker2 instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 04:17:36.705 - info: host.iobroker2 instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 04:17:36.748 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 04:17:36.748 - info: host.iobroker2 All instances are stopped. 2023-05-01 04:17:36.919 - info: host.iobroker2 terminated 2023-05-01 06:17:43.958 - info: host.iobroker2 iobroker.js-controller version 4.0.24 js-controller starting 2023-05-01 06:17:43.961 - info: host.iobroker2 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-01 06:17:43.961 - info: host.iobroker2 hostname: iobroker2, node: v18.16.0 2023-05-01 06:17:43.961 - info: host.iobroker2 ip addresses: 192.168.2.116 fe80::84aa:d6ff:febe:cccc 2023-05-01 06:17:44.463 - info: host.iobroker2 connected to Objects and States 2023-05-01 06:17:44.473 - info: host.iobroker2 added notifications configuration of host 2023-05-01 06:17:44.762 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeCurrent" 2023-05-01 06:17:44.765 - info: host.iobroker2 3 instances found 2023-05-01 06:17:44.782 - info: host.iobroker2 starting 3 instances 2023-05-01 06:17:44.819 - info: host.iobroker2 instance system.adapter.admin.0 started with pid 333 2023-05-01 06:17:44.846 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewest" 2023-05-01 06:17:44.849 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewestNext" 2023-05-01 06:17:44.854 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmCurrent" 2023-05-01 06:17:44.867 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewest" 2023-05-01 06:17:44.870 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewestNext" 2023-05-01 06:17:44.879 - info: host.iobroker2 Some obsolete host states deleted. 2023-05-01 06:17:45.867 - info: admin.0 (333) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:17:45.890 - info: admin.0 (333) requesting all states 2023-05-01 06:17:45.890 - info: admin.0 (333) requesting all objects 2023-05-01 06:17:46.231 - info: admin.0 (333) received all objects 2023-05-01 06:17:46.419 - info: admin.0 (333) Request actual repository... 2023-05-01 06:17:46.467 - info: admin.0 (333) http server listening on port 8081 2023-05-01 06:17:46.468 - info: admin.0 (333) Use link "http://localhost:8081" to configure. 2023-05-01 06:17:46.471 - info: admin.0 (333) socket.io server listening on port 8081 2023-05-01 06:17:46.715 - info: host.iobroker2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-05-01 06:17:48.522 - info: admin.0 (333) Repository received successfully. 2023-05-01 06:17:48.805 - info: host.iobroker2 instance system.adapter.discovery.0 started with pid 360 2023-05-01 06:17:49.584 - info: discovery.0 (360) starting. Version 3.1.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:17:52.800 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 375 2023-05-01 06:17:53.734 - info: backitup.0 (375) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:17:53.803 - info: backitup.0 (375) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-05-01 06:23:49.870 - info: admin.0 (333) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:23:52.453 - info: admin.0 (333) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:25:13.760 - info: host.iobroker2 received SIGTERM 2023-05-01 06:25:13.764 - info: admin.0 (333) terminating http server on port 8081 2023-05-01 06:25:13.769 - info: backitup.0 (375) cleaned everything up... 2023-05-01 06:25:13.762 - info: host.iobroker2 stopInstance system.adapter.admin.0 (force=false, process=true) 2023-05-01 06:25:13.763 - info: host.iobroker2 stopInstance system.adapter.discovery.0 (force=false, process=true) 2023-05-01 06:25:13.763 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:25:13.789 - info: discovery.0 (360) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:25:13.790 - info: admin.0 (333) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:25:13.791 - info: backitup.0 (375) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:25:13.799 - info: discovery.0 (360) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 06:25:13.803 - info: admin.0 (333) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 06:25:13.804 - info: host.iobroker2 stopInstance system.adapter.admin.0 send kill signal 2023-05-01 06:25:13.806 - info: host.iobroker2 stopInstance system.adapter.discovery.0 send kill signal 2023-05-01 06:25:13.806 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:25:13.848 - info: backitup.0 (375) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 06:25:14.335 - info: host.iobroker2 instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 06:25:14.367 - info: host.iobroker2 instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 06:25:14.408 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 06:25:14.408 - info: host.iobroker2 All instances are stopped. 2023-05-01 06:25:14.588 - info: host.iobroker2 terminated 2023-05-01 06:26:55.621 - info: host.iobroker2 iobroker.js-controller version 4.0.24 js-controller starting 2023-05-01 06:26:55.624 - info: host.iobroker2 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-01 06:26:55.625 - info: host.iobroker2 hostname: iobroker2, node: v18.16.0 2023-05-01 06:26:55.625 - info: host.iobroker2 ip addresses: 192.168.2.116 2001:9e8:2546:de00:84aa:d6ff:febe:cccc fe80::84aa:d6ff:febe:cccc 2023-05-01 06:26:56.153 - info: host.iobroker2 connected to Objects and States 2023-05-01 06:26:56.162 - info: host.iobroker2 added notifications configuration of host 2023-05-01 06:26:56.341 - info: host.iobroker2 Delete host system.host.iobroker2 2023-05-01 06:26:56.394 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeCurrent" 2023-05-01 06:26:56.397 - info: host.iobroker2 3 instances found 2023-05-01 06:26:56.400 - info: host.iobroker2 starting 2 instances 2023-05-01 06:26:56.402 - warn: host.iobroker2 startInstance cannot find adapter "discovery@3.1.0". Try to install it... 1 attempt 2023-05-01 06:26:56.403 - info: host.iobroker2 iobroker install discovery@3.1.0 using installedVersion 2023-05-01 06:26:56.430 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewest" 2023-05-01 06:26:56.526 - info: host.iobroker2 instance system.adapter.admin.0 started with pid 612 2023-05-01 06:26:56.529 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewestNext" 2023-05-01 06:26:56.578 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmCurrent" 2023-05-01 06:26:56.626 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewest" 2023-05-01 06:26:56.670 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewestNext" 2023-05-01 06:26:56.718 - info: host.iobroker2 Some obsolete host states deleted. 2023-05-01 06:26:58.432 - info: admin.0 (612) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:26:58.494 - info: admin.0 (612) requesting all states 2023-05-01 06:26:58.503 - info: admin.0 (612) requesting all objects 2023-05-01 06:26:59.092 - info: admin.0 (612) received all objects 2023-05-01 06:26:59.363 - info: admin.0 (612) Request actual repository... 2023-05-01 06:26:59.419 - info: admin.0 (612) http server listening on port 8081 2023-05-01 06:26:59.427 - info: admin.0 (612) Use link "http://localhost:8081" to configure. 2023-05-01 06:26:59.431 - info: admin.0 (612) socket.io server listening on port 8081 2023-05-01 06:26:59.794 - info: host.iobroker2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-05-01 06:26:59.900 - info: host.iobroker2 iobroker npm-install: NPM version: 9.5.1Installing iobroker.discovery@3.1.0... (System call) 2023-05-01 06:27:00.447 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 658 2023-05-01 06:27:03.174 - info: admin.0 (612) Repository received successfully. 2023-05-01 06:27:03.519 - info: backitup.0 (658) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:27:03.671 - info: backitup.0 (658) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-05-01 06:27:09.863 - info: host.iobroker2 iobroker npm-install: added 40 packages in 8s 2023-05-01 06:27:09.865 - info: host.iobroker2 iobroker npm-install: 2023-05-01 06:27:09.866 - info: host.iobroker2 iobroker npm-install: 45 packages are looking for funding 2023-05-01 06:27:09.868 - info: host.iobroker2 iobroker npm-install: run `npm fund` for details 2023-05-01 06:27:09.892 - info: host.iobroker2 iobroker npm-install: host.iobroker2 install adapter discovery@3.1.0 2023-05-01 06:27:09.906 - info: host.iobroker2 iobroker npm-install: upload [6] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png 2023-05-01 06:27:09.922 - info: host.iobroker2 iobroker npm-install: upload [5] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index.html index.html text/html 2023-05-01 06:27:09.927 - info: host.iobroker2 iobroker npm-install: upload [4] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index_m.html index_m.html text/html 2023-05-01 06:27:09.931 - info: host.iobroker2 iobroker npm-install: upload [3] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings.html settings.html text/html 2023-05-01 06:27:09.935 - info: host.iobroker2 iobroker npm-install: upload [2] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html 2023-05-01 06:27:09.939 - info: host.iobroker2 iobroker npm-install: upload [1] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/translateTools.js translateTools.js application/javascript 2023-05-01 06:27:09.943 - info: host.iobroker2 iobroker npm-install: upload [0] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript 2023-05-01 06:27:09.959 - info: host.iobroker2 iobroker npm-install: host.iobroker2 object system.adapter.discovery created/updated 2023-05-01 06:27:09.968 - info: host.iobroker2 iobroker npm-install: Update "system.adapter.discovery.0" 2023-05-01 06:27:10.990 - info: host.iobroker2 iobroker npm-install: exit 0 2023-05-01 06:27:13.919 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:27:14.860 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:27:17.937 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:30:17.530 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:30:17.532 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 admin 2023-05-01 06:30:17.835 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:30:17.948 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:32:03.487 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:32:09.157 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:49:11.753 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:49:31.006 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:52:21.337 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:52:21.339 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 admin 2023-05-01 06:52:21.834 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:52:21.869 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:52:41.999 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:52:50.990 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:53:40.590 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:53:40.595 - info: backitup.0 (658) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:53:40.596 - info: backitup.0 (658) cleaned everything up... 2023-05-01 06:53:40.596 - info: backitup.0 (658) terminating 2023-05-01 06:53:40.597 - info: backitup.0 (658) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-05-01 06:53:40.636 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:53:41.119 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-01 06:53:43.657 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 792 2023-05-01 06:53:44.513 - info: backitup.0 (792) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:53:44.584 - info: backitup.0 (792) [iobroker] backup was activated at 02:00 every 2 day(s) 2023-05-01 06:53:44.619 - info: backitup.0 (792) [ccu] backup was activated at 01:30 every 3 day(s) 2023-05-01 06:53:45.637 - error: backitup.0 (792) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:53:56.672 - error: backitup.0 (792) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:53:56.676 - error: backitup.0 (792) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:54:46.961 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:54:47.056 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:55:13.051 - info: admin.0 (612) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:55:16.660 - info: admin.0 (612) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:55:22.729 - error: backitup.0 (792) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:55:33.821 - error: backitup.0 (792) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:55:42.278 - info: host.iobroker2 received SIGTERM 2023-05-01 06:55:42.280 - info: admin.0 (612) terminating http server on port 8081 2023-05-01 06:55:42.283 - info: backitup.0 (792) cleaned everything up... 2023-05-01 06:55:42.279 - info: host.iobroker2 stopInstance system.adapter.admin.0 (force=false, process=true) 2023-05-01 06:55:42.284 - info: host.iobroker2 stopInstance system.adapter.discovery.0 (force=false, process=false) 2023-05-01 06:55:42.284 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:55:42.293 - info: backitup.0 (792) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:55:42.295 - info: admin.0 (612) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:55:42.293 - info: host.iobroker2 stopInstance system.adapter.admin.0 send kill signal 2023-05-01 06:55:42.297 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:55:42.299 - info: admin.0 (612) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 06:55:42.340 - info: backitup.0 (792) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-05-01 06:55:42.823 - info: host.iobroker2 instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 06:55:42.860 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2023-05-01 06:55:42.860 - info: host.iobroker2 All instances are stopped. 2023-05-01 06:55:42.906 - info: host.iobroker2 terminated 2023-05-01 06:56:38.466 - info: host.iobroker2 iobroker.js-controller version 4.0.24 js-controller starting 2023-05-01 06:56:38.469 - info: host.iobroker2 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-01 06:56:38.469 - info: host.iobroker2 hostname: iobroker2, node: v18.16.0 2023-05-01 06:56:38.470 - info: host.iobroker2 ip addresses: 192.168.2.116 2001:9e8:2546:de00:84aa:d6ff:febe:cccc fe80::84aa:d6ff:febe:cccc 2023-05-01 06:56:39.085 - info: host.iobroker2 connected to Objects and States 2023-05-01 06:56:39.095 - info: host.iobroker2 added notifications configuration of host 2023-05-01 06:56:39.277 - info: host.iobroker2 Delete host system.host.iobroker2 2023-05-01 06:56:39.333 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeCurrent" 2023-05-01 06:56:39.336 - info: host.iobroker2 3 instances found 2023-05-01 06:56:39.339 - info: host.iobroker2 starting 2 instances 2023-05-01 06:56:39.341 - warn: host.iobroker2 startInstance cannot find adapter "discovery@3.1.0". Try to install it... 1 attempt 2023-05-01 06:56:39.342 - info: host.iobroker2 iobroker install discovery@3.1.0 using installedVersion 2023-05-01 06:56:39.368 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewest" 2023-05-01 06:56:39.479 - info: host.iobroker2 instance system.adapter.admin.0 started with pid 995 2023-05-01 06:56:39.481 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewestNext" 2023-05-01 06:56:39.526 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmCurrent" 2023-05-01 06:56:39.571 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewest" 2023-05-01 06:56:39.661 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewestNext" 2023-05-01 06:56:39.705 - info: host.iobroker2 Some obsolete host states deleted. 2023-05-01 06:56:41.389 - info: admin.0 (995) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:56:41.424 - info: admin.0 (995) requesting all states 2023-05-01 06:56:41.424 - info: admin.0 (995) requesting all objects 2023-05-01 06:56:42.121 - info: admin.0 (995) received all objects 2023-05-01 06:56:42.407 - info: admin.0 (995) Request actual repository... 2023-05-01 06:56:42.454 - info: admin.0 (995) http server listening on port 8081 2023-05-01 06:56:42.455 - info: admin.0 (995) Use link "http://localhost:8081" to configure. 2023-05-01 06:56:42.458 - info: admin.0 (995) socket.io server listening on port 8081 2023-05-01 06:56:42.641 - info: admin.0 (995) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:56:42.929 - info: host.iobroker2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-05-01 06:56:43.050 - info: host.iobroker2 iobroker npm-install: NPM version: 9.5.1Installing iobroker.discovery@3.1.0... (System call) 2023-05-01 06:56:43.379 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 1041 2023-05-01 06:56:45.696 - info: admin.0 (995) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:56:46.728 - info: admin.0 (995) Repository received successfully. 2023-05-01 06:56:47.273 - info: backitup.0 (1041) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:56:47.523 - info: backitup.0 (1041) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-05-01 06:56:53.466 - info: host.iobroker2 iobroker npm-install: added 40 packages in 9s 2023-05-01 06:56:53.469 - info: host.iobroker2 iobroker npm-install: 2023-05-01 06:56:53.470 - info: host.iobroker2 iobroker npm-install: 45 packages are looking for funding 2023-05-01 06:56:53.472 - info: host.iobroker2 iobroker npm-install: run `npm fund` for details 2023-05-01 06:56:53.496 - info: host.iobroker2 iobroker npm-install: host.iobroker2 install adapter discovery@3.1.0 2023-05-01 06:56:53.510 - info: host.iobroker2 iobroker npm-install: upload [6] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png 2023-05-01 06:56:53.528 - info: host.iobroker2 iobroker npm-install: upload [5] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index.html index.html text/html 2023-05-01 06:56:53.533 - info: host.iobroker2 iobroker npm-install: upload [4] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index_m.html index_m.html text/html 2023-05-01 06:56:53.538 - info: host.iobroker2 iobroker npm-install: upload [3] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings.html settings.html text/html 2023-05-01 06:56:53.542 - info: host.iobroker2 iobroker npm-install: upload [2] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html 2023-05-01 06:56:53.547 - info: host.iobroker2 iobroker npm-install: upload [1] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/translateTools.js translateTools.js application/javascript 2023-05-01 06:56:53.551 - info: host.iobroker2 iobroker npm-install: upload [0] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript 2023-05-01 06:56:53.568 - info: host.iobroker2 iobroker npm-install: host.iobroker2 object system.adapter.discovery created/updated 2023-05-01 06:56:53.582 - info: host.iobroker2 iobroker npm-install: Update "system.adapter.discovery.0" 2023-05-01 06:56:54.606 - info: host.iobroker2 iobroker npm-install: exit 0 2023-05-01 06:57:05.893 - info: admin.0 (995) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:57:15.949 - info: admin.0 (995) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:58:50.203 - info: host.iobroker2 iobroker upgrade backitup@2.6.19 2023-05-01 06:58:51.168 - info: host.iobroker2 iobroker Update backitup from @2.6.16 to @2.6.19 2023-05-01 06:58:51.223 - info: host.iobroker2 iobroker host.iobroker2 Adapter "system.adapter.backitup.0" is stopped. 2023-05-01 06:58:51.229 - info: host.iobroker2 "system.adapter.backitup.0" disabled 2023-05-01 06:58:51.231 - info: backitup.0 (1041) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:58:51.232 - info: backitup.0 (1041) cleaned everything up... 2023-05-01 06:58:51.232 - info: backitup.0 (1041) terminating 2023-05-01 06:58:51.233 - info: backitup.0 (1041) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-05-01 06:58:51.230 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:58:51.272 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:58:51.768 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-01 06:58:51.867 - info: host.iobroker2 iobroker NPM version: 9.5.1Installing iobroker.backitup@2.6.19... (System call) 2023-05-01 06:58:55.254 - info: host.iobroker2 iobroker changed 2 packages in 3s 2023-05-01 06:58:55.256 - info: host.iobroker2 iobroker 2023-05-01 06:58:55.258 - info: host.iobroker2 iobroker 45 packages are looking for funding 2023-05-01 06:58:55.261 - info: host.iobroker2 iobroker run `npm fund` for details 2023-05-01 06:58:55.306 - info: host.iobroker2 iobroker Update "system.adapter.backitup.0" 2023-05-01 06:58:55.327 - info: host.iobroker2 iobroker upload [21] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript 2023-05-01 06:58:55.341 - info: host.iobroker2 iobroker upload [20] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png 2023-05-01 06:58:55.346 - info: host.iobroker2 iobroker upload [19] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml 2023-05-01 06:58:55.351 - info: host.iobroker2 iobroker upload [18] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/de/translations.json i18n/de/translations.json application/json 2023-05-01 06:58:55.361 - info: host.iobroker2 iobroker upload [17] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/en/translations.json i18n/en/translations.json application/json 2023-05-01 06:58:55.366 - info: host.iobroker2 iobroker upload [16] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/es/translations.json i18n/es/translations.json application/json 2023-05-01 06:58:55.372 - info: host.iobroker2 iobroker upload [15] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/fr/translations.json i18n/fr/translations.json application/json 2023-05-01 06:58:55.383 - info: host.iobroker2 iobroker upload [14] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/it/translations.json i18n/it/translations.json application/json 2023-05-01 06:58:55.388 - info: host.iobroker2 iobroker upload [13] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/nl/translations.json i18n/nl/translations.json application/json 2023-05-01 06:58:55.394 - info: host.iobroker2 iobroker upload [12] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/pl/translations.json i18n/pl/translations.json application/json 2023-05-01 06:58:55.399 - info: host.iobroker2 iobroker upload [11] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/pt/translations.json i18n/pt/translations.json application/json 2023-05-01 06:58:55.406 - info: host.iobroker2 iobroker upload [10] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/ru/translations.json i18n/ru/translations.json application/json 2023-05-01 06:58:55.411 - info: host.iobroker2 iobroker upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/uk/translations.json i18n/uk/translations.json application/json 2023-05-01 06:58:55.416 - info: host.iobroker2 iobroker upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json 2023-05-01 06:58:55.421 - info: host.iobroker2 iobroker upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html 2023-05-01 06:58:55.427 - info: host.iobroker2 iobroker upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html 2023-05-01 06:58:55.432 - info: host.iobroker2 iobroker upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.js index_m.js application/javascript 2023-05-01 06:58:55.437 - info: host.iobroker2 iobroker upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css 2023-05-01 06:58:55.441 - info: host.iobroker2 iobroker upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.css tab_m.css text/css 2023-05-01 06:58:55.445 - info: host.iobroker2 iobroker upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html 2023-05-01 06:58:55.450 - info: host.iobroker2 iobroker upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript 2023-05-01 06:58:55.455 - info: host.iobroker2 iobroker upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript 2023-05-01 06:58:55.460 - info: host.iobroker2 iobroker host.iobroker2 Adapter "system.adapter.backitup.0" is started 2023-05-01 06:58:55.469 - info: host.iobroker2 "system.adapter.backitup.0" enabled 2023-05-01 06:58:55.538 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 1114 2023-05-01 06:58:56.386 - info: backitup.0 (1114) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:58:56.458 - info: backitup.0 (1114) [iobroker] backup will be activated at 02:40 every 1 day(s) 2023-05-01 06:58:56.487 - info: host.iobroker2 iobroker exit 0 2023-05-01 06:59:08.050 - info: admin.0 (995) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:59:18.947 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:59:18.950 - info: backitup.0 (1114) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:59:18.950 - info: backitup.0 (1114) cleaned everything up... 2023-05-01 06:59:18.951 - info: backitup.0 (1114) terminating 2023-05-01 06:59:18.951 - info: backitup.0 (1114) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-05-01 06:59:18.992 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:59:19.469 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-01 06:59:22.004 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 1129 2023-05-01 06:59:22.865 - info: backitup.0 (1129) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:59:22.956 - info: backitup.0 (1129) [iobroker] backup will be activated at 02:40 every 1 day(s) 2023-05-01 06:59:31.007 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:59:31.009 - info: backitup.0 (1129) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:59:31.010 - info: backitup.0 (1129) cleaned everything up... 2023-05-01 06:59:31.010 - info: backitup.0 (1129) terminating 2023-05-01 06:59:31.011 - info: backitup.0 (1129) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-05-01 06:59:31.056 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:59:31.318 - info: admin.0 (995) <== Disconnect system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:59:31.539 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-01 06:59:33.419 - info: admin.0 (995) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 06:59:34.070 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 1144 2023-05-01 06:59:34.914 - info: backitup.0 (1144) starting. Version 2.6.19 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 06:59:34.981 - info: backitup.0 (1144) [iobroker] backup will be activated at 02:00 every 2 day(s) 2023-05-01 06:59:35.014 - info: backitup.0 (1144) [ccu] backup will be activated at 01:30 every 3 day(s) 2023-05-01 06:59:35.444 - error: backitup.0 (1144) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:59:39.816 - error: backitup.0 (1144) Error: Command failed: sudo mount -t cifs -o username=backup,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.2.159/home/backup/iobroker/standard /opt/iobroker/backups mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-05-01 06:59:49.811 - info: host.iobroker2 received SIGTERM 2023-05-01 06:59:49.816 - info: backitup.0 (1144) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:59:49.820 - info: admin.0 (995) Got terminate signal TERMINATE_YOURSELF 2023-05-01 06:59:49.816 - info: backitup.0 (1144) cleaned everything up... 2023-05-01 06:59:49.817 - info: backitup.0 (1144) terminating 2023-05-01 06:59:49.817 - info: backitup.0 (1144) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-05-01 06:59:49.812 - info: host.iobroker2 stopInstance system.adapter.admin.0 (force=false, process=true) 2023-05-01 06:59:49.812 - info: host.iobroker2 stopInstance system.adapter.discovery.0 (force=false, process=false) 2023-05-01 06:59:49.812 - info: host.iobroker2 stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-05-01 06:59:49.814 - info: host.iobroker2 stopInstance system.adapter.admin.0 send kill signal 2023-05-01 06:59:49.814 - info: host.iobroker2 stopInstance system.adapter.backitup.0 send kill signal 2023-05-01 06:59:49.821 - info: admin.0 (995) terminating http server on port 8081 2023-05-01 06:59:49.822 - info: admin.0 (995) terminating 2023-05-01 06:59:49.823 - info: admin.0 (995) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-05-01 06:59:50.345 - info: host.iobroker2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-01 06:59:50.362 - info: host.iobroker2 instance system.adapter.admin.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-05-01 06:59:50.362 - info: host.iobroker2 All instances are stopped. 2023-05-01 06:59:50.425 - info: host.iobroker2 terminated 2023-05-01 07:00:34.445 - info: host.iobroker2 iobroker.js-controller version 4.0.24 js-controller starting 2023-05-01 07:00:34.448 - info: host.iobroker2 Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker 2023-05-01 07:00:34.449 - info: host.iobroker2 hostname: iobroker2, node: v18.16.0 2023-05-01 07:00:34.449 - info: host.iobroker2 ip addresses: 192.168.2.116 2001:9e8:2546:de00:84aa:d6ff:febe:cccc fe80::84aa:d6ff:febe:cccc 2023-05-01 07:00:35.143 - info: host.iobroker2 connected to Objects and States 2023-05-01 07:00:35.153 - info: host.iobroker2 added notifications configuration of host 2023-05-01 07:00:35.340 - info: host.iobroker2 Delete host system.host.iobroker2 2023-05-01 07:00:35.393 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeCurrent" 2023-05-01 07:00:35.396 - info: host.iobroker2 3 instances found 2023-05-01 07:00:35.399 - info: host.iobroker2 starting 2 instances 2023-05-01 07:00:35.401 - warn: host.iobroker2 startInstance cannot find adapter "discovery@3.1.0". Try to install it... 1 attempt 2023-05-01 07:00:35.402 - info: host.iobroker2 iobroker install discovery@3.1.0 using installedVersion 2023-05-01 07:00:35.429 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewest" 2023-05-01 07:00:35.526 - info: host.iobroker2 instance system.adapter.admin.0 started with pid 1316 2023-05-01 07:00:35.528 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.nodeNewestNext" 2023-05-01 07:00:35.578 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmCurrent" 2023-05-01 07:00:35.622 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewest" 2023-05-01 07:00:35.674 - info: host.iobroker2 Delete state "system.host.iobroker2.versions.npmNewestNext" 2023-05-01 07:00:35.719 - info: host.iobroker2 Some obsolete host states deleted. 2023-05-01 07:00:37.436 - info: admin.0 (1316) starting. Version 6.3.5 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.0, js-controller: 4.0.24 2023-05-01 07:00:37.474 - info: admin.0 (1316) requesting all states 2023-05-01 07:00:37.474 - info: admin.0 (1316) requesting all objects 2023-05-01 07:00:38.107 - info: admin.0 (1316) received all objects 2023-05-01 07:00:38.420 - info: admin.0 (1316) Request actual repository... 2023-05-01 07:00:38.494 - info: admin.0 (1316) http server listening on port 8081 2023-05-01 07:00:38.495 - info: admin.0 (1316) Use link "http://localhost:8081" to configure. 2023-05-01 07:00:38.499 - info: admin.0 (1316) socket.io server listening on port 8081 2023-05-01 07:00:38.955 - info: host.iobroker2 Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-05-01 07:00:38.977 - info: host.iobroker2 iobroker npm-install: NPM version: 9.5.1Installing iobroker.discovery@3.1.0... (System call) 2023-05-01 07:00:39.451 - info: host.iobroker2 instance system.adapter.backitup.0 started with pid 1362 2023-05-01 07:00:42.150 - info: admin.0 (1316) Repository received successfully. 2023-05-01 07:00:42.482 - info: backitup.0 (1362) starting. Version 2.6.16 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.16.0, js-controller: 4.0.24 2023-05-01 07:00:42.710 - info: backitup.0 (1362) [iobroker] backup was activated at 02:40 every 1 day(s) 2023-05-01 07:00:44.585 - info: host.iobroker2 iobroker npm-install: added 40 packages in 4s 2023-05-01 07:00:44.587 - info: host.iobroker2 iobroker npm-install: 2023-05-01 07:00:44.589 - info: host.iobroker2 iobroker npm-install: 45 packages are looking for funding 2023-05-01 07:00:44.590 - info: host.iobroker2 iobroker npm-install: run `npm fund` for details 2023-05-01 07:00:44.614 - info: host.iobroker2 iobroker npm-install: host.iobroker2 install adapter discovery@3.1.0 2023-05-01 07:00:44.630 - info: host.iobroker2 iobroker npm-install: upload [6] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/discovery.png discovery.png image/png 2023-05-01 07:00:44.647 - info: host.iobroker2 iobroker npm-install: upload [5] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index.html index.html text/html 2023-05-01 07:00:44.652 - info: host.iobroker2 iobroker npm-install: upload [4] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/index_m.html index_m.html text/html 2023-05-01 07:00:44.657 - info: host.iobroker2 iobroker npm-install: upload [3] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings.html settings.html text/html 2023-05-01 07:00:44.661 - info: host.iobroker2 iobroker npm-install: upload [2] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/settings_m.html settings_m.html text/html 2023-05-01 07:00:44.665 - info: host.iobroker2 iobroker npm-install: upload [1] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/translateTools.js translateTools.js application/javascript 2023-05-01 07:00:44.669 - info: host.iobroker2 iobroker npm-install: upload [0] discovery.admin /opt/iobroker/node_modules/iobroker.discovery/admin/words.js words.js application/javascript 2023-05-01 07:00:44.685 - info: host.iobroker2 iobroker npm-install: host.iobroker2 object system.adapter.discovery created/updated 2023-05-01 07:00:44.694 - info: host.iobroker2 iobroker npm-install: Update "system.adapter.discovery.0" 2023-05-01 07:00:45.720 - info: host.iobroker2 iobroker npm-install: exit 0 2023-05-01 07:00:48.235 - info: admin.0 (1316) ==> Connected system.user.admin from ::ffff:192.168.2.55 2023-05-01 07:00:49.507 - info: admin.0 (1316) ==> Connected system.user.admin from ::ffff:192.168.2.55Ich würde mich freuen, wenn mir jemand helfen kann.
Viele Grüße -
cifs-utils installiert?
-
@thomas-braun sagte in Wiederherstellung nach Neuinstallation Backitup Probleme:
cifs-utils
nein, habe ich noch nicht
wie ist denn der richtige Befehl? -
sudo apt update apt policy cifs-utilsWenn das nicht installiert ist:
sudo apt install cifs-utils -
@thomas-braun
Hat leider nichts geändert. Hast du vielleicht noch eine Idee?
