Test Adapter ioBroker.backitup v3.0.x
-
@ichderarnd sagte in Test Adapter ioBroker.backitup v2.8.x:
Habe dann das fix-skript nochmal laufen lassen und die 18.18.1 installiert.
Zeig mal bitte die vollständige Ausgabe davon.
-
Sieht gut aus bei mir:
iobroker@iobroker:~ $ type -p nodejs node npm npx corepack && nodejs -v && node -v && npm -v && npx -v && corepack -v /usr/bin/nodejs /usr/bin/node /usr/bin/npm /usr/bin/npx /usr/bin/corepack v18.18.1 v18.18.1 9.8.1 9.8.1 0.19.0Backitup Debug:
2023-10-10 23:00:10.051 - debug: backitup.0 (1018) The local storage check was completed successfully. On the host "iobroker" are currently 24051 MB free space available! 2023-10-10 23:00:10.170 - debug: backitup.0 (1018) Backup has started ... 2023-10-10 23:00:20.173 - debug: backitup.0 (1018) [iobroker/mount] noserverino option: false 2023-10-10 23:00:20.175 - debug: backitup.0 (1018) [iobroker/mount] cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.5/Backup_IoBroker/Backup /opt/iobroker/backups" 2023-10-10 23:00:20.373 - debug: backitup.0 (1018) [iobroker/mount] mount successfully completed 2023-10-10 23:00:20.377 - debug: backitup.0 (1018) [iobroker/mount] done 2023-10-10 23:00:23.711 - debug: backitup.0 (1018) [iobroker/iobroker] host.iobroker 3070 states saved 2023-10-10 23:00:27.682 - debug: backitup.0 (1018) [iobroker/iobroker] host.iobroker 3596 objects saved 2023-10-10 23:00:32.053 - debug: backitup.0 (1018) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2023_10_10-23_00_20_backupiobroker.tar.gz 2023-10-10 23:00:33.540 - debug: backitup.0 (1018) [iobroker/iobroker] done 2023-10-10 23:00:34.448 - debug: backitup.0 (1018) [iobroker/historyDB] compress from historyDB started ... 2023-10-10 23:00:40.687 - debug: backitup.0 (1018) [iobroker/historyDB] Backup created: /opt/iobroker/backups/historyDB_2023_10_10-23_00_34_backupiobroker.tar.gz 2023-10-10 23:00:40.690 - debug: backitup.0 (1018) [iobroker/historyDB] done 2023-10-10 23:00:41.615 - debug: backitup.0 (1018) [iobroker/javascripts] Created javascript_tmp directory: "/opt/iobroker/backups/tmpScripts" 2023-10-10 23:00:41.729 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: VAR_Wochenverbrauch 2023-10-10 23:00:41.730 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: VAR_Monatsverbrauch 2023-10-10 23:00:41.732 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: VAR_Tagesverbrauch 2023-10-10 23:00:41.733 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Verbrauchsmessung_Shellys 2023-10-10 23:00:41.733 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Schaltung_openDTU 2023-10-10 23:00:41.734 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Notabschaltung___Alarm 2023-10-10 23:00:41.735 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: An-_Abschaltung_Solar 2023-10-10 23:00:41.737 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: VAR_Realtime_Untertägig 2023-10-10 23:00:41.737 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Akku_Balancing 2023-10-10 23:00:41.738 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Luftentfeuchter 2023-10-10 23:00:41.739 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Raspberry_PI 2023-10-10 23:00:41.739 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: OpenDTU 2023-10-10 23:00:41.740 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: HM_WR_Keller 2023-10-10 23:00:41.740 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Akkuladung_100 2023-10-10 23:00:41.742 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: VAR_Jahresverbrauch 2023-10-10 23:00:41.742 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: TEST 2023-10-10 23:00:41.743 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: Test_Hama 2023-10-10 23:00:41.744 - debug: backitup.0 (1018) [iobroker/javascripts] found Script: HM_WR_Garage 2023-10-10 23:00:41.867 - debug: backitup.0 (1018) [iobroker/javascripts] Try deleting the Javascript tmp directory: "/opt/iobroker/backups/tmpScripts" 2023-10-10 23:00:41.886 - debug: backitup.0 (1018) [iobroker/javascripts] Javascript tmp directory "/opt/iobroker/backups/tmpScripts" successfully deleted 2023-10-10 23:00:41.887 - debug: backitup.0 (1018) [iobroker/javascripts] Backup created: /opt/iobroker/backups/javascripts_2023_10_10-23_00_41_backupiobroker.tar.gz 2023-10-10 23:00:41.887 - debug: backitup.0 (1018) [iobroker/javascripts] done 2023-10-10 23:00:42.640 - debug: backitup.0 (1018) [iobroker/cifs] used copy path: /Backup_IoBroker/Backup 2023-10-10 23:00:42.641 - debug: backitup.0 (1018) [iobroker/cifs] done 2023-10-10 23:00:43.259 - debug: backitup.0 (1018) [iobroker/clean] delete /opt/iobroker/backups/iobroker_2023_10_05-23_27_16_backupiobroker.tar.gz 2023-10-10 23:00:43.276 - debug: backitup.0 (1018) [iobroker/clean] delete /opt/iobroker/backups/historyDB_2023_10_05-23_27_35_backupiobroker.tar.gz 2023-10-10 23:00:43.292 - debug: backitup.0 (1018) [iobroker/clean] delete /opt/iobroker/backups/javascripts_2023_10_05-23_27_40_backupiobroker.tar.gz 2023-10-10 23:00:43.296 - debug: backitup.0 (1018) [iobroker/clean] done 2023-10-10 23:00:44.528 - debug: backitup.0 (1018) [iobroker/historyHTML] new history html values created 2023-10-10 23:00:44.580 - debug: backitup.0 (1018) [iobroker/historyHTML] done 2023-10-10 23:00:44.747 - debug: backitup.0 (1018) [iobroker/historyJSON] new history json values created 2023-10-10 23:00:44.748 - debug: backitup.0 (1018) [iobroker/historyJSON] done 2023-10-10 23:00:44.929 - debug: backitup.0 (1018) [iobroker/umount] mount activ, umount is started ... 2023-10-10 23:00:49.980 - debug: backitup.0 (1018) [iobroker/umount] umount successfully completed 2023-10-10 23:00:49.981 - debug: backitup.0 (1018) [iobroker/umount] done 2023-10-10 23:00:50.133 - debug: backitup.0 (1018) [iobroker] exec: doneIch werds nochmal 1-2 Tage beobachten aber sieht schonmal deutlich besser aus als mit der 18.18.0
-
@ichderarnd sagte in Test Adapter ioBroker.backitup v2.8.x:
Merkwürdig.
Mit einer schiefen Installation ist da gar nix merkwürdig. Höchstens verbesserungswürdig.
-
Der erste Lauf für die nodejs 16 war schon aus dem History Buffer raus. Hier der zweite Aufruf mit Update auf die 18.18.1:
ioBroker nodejs fixer 2023-10-09 Recommended nodejs-version is: 18.18.1 Checking your installation now. Please be patient! Your current setup is: /usr/bin/nodejs v16.20.2 /usr/bin/node v16.20.2 /usr/bin/npm 8.19.4 /usr/bin/npx 8.19.4 /usr/bin/corepack 0.17.0 We found these nodejs versions available for installation: nodejs: Installed: 16.20.2-deb-1nodesource1 Candidate: 16.20.2-deb-1nodesource1 Version table: *** 16.20.2-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages Nothing to do - Your installation is using the correct paths. You are running nodejs v16.20.2. Do you want to install recommended version 18.18.1? Press <y> to continue or any other key to quit Trying to fix your installation now. Please be patient. Waiting for ioBroker to shut down - Give me a minute... ############################################################ *** These repos are active on your system: Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB] Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:3 https://apt.pivccu.de/piVCCU testing InRelease [13.6 kB] Get:4 http://archive.raspberrypi.org/debian buster/main armhf Packages [400 kB] Get:5 http://raspbian.raspberrypi.org/raspbian buster/non-free Sources [139 kB] Get:6 https://apt.pivccu.de/piVCCU testing/main armhf Packages [13.8 kB] Get:7 http://raspbian.raspberrypi.org/raspbian buster/main Sources [11.4 MB] Get:8 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB] Get:9 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Packages [110 kB] Fetched 25.1 MB in 11s (2383 kB/s) Reading package lists... Done *** Installing ca-certificates, curl and gnupg, just in case they are missing. *** Creating new /etc/apt/sources.list.d/nodesource.list and pinning source deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main Package: nodejs Pin: origin deb.nodesource.com Pin-Priority: 1001 *** These repos are active after the adjustments: Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 http://archive.raspberrypi.org/debian buster InRelease Hit:3 https://apt.pivccu.de/piVCCU testing InRelease Get:4 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB] Get:5 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages [5529 B] Fetched 17.7 kB in 1s (13.3 kB/s) Reading package lists... Done Installing the recommended nodejs version now! Extracting templates from packages: 100% (Reading database ... 266527 files and directories currently installed.) Preparing to unpack .../ncurses-bin_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking ncurses-bin (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Setting up ncurses-bin (6.1+20181013-2+deb10u4) ... (Reading database ... 266527 files and directories currently installed.) Preparing to unpack .../ncurses-base_6.1+20181013-2+deb10u4_all.deb ... Unpacking ncurses-base (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Setting up ncurses-base (6.1+20181013-2+deb10u4) ... (Reading database ... 266527 files and directories currently installed.) Preparing to unpack .../0-python2.7-dev_2.7.16-2+deb10u3_armhf.deb ... Unpacking python2.7-dev (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../1-libpython2.7-dev_2.7.16-2+deb10u3_armhf.deb ... Unpacking libpython2.7-dev:armhf (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../2-libpython2.7_2.7.16-2+deb10u3_armhf.deb ... Unpacking libpython2.7:armhf (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../3-python2.7_2.7.16-2+deb10u3_armhf.deb ... Unpacking python2.7 (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../4-libpython2.7-stdlib_2.7.16-2+deb10u3_armhf.deb ... Unpacking libpython2.7-stdlib:armhf (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../5-python2.7-minimal_2.7.16-2+deb10u3_armhf.deb ... Unpacking python2.7-minimal (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../6-libpython2.7-minimal_2.7.16-2+deb10u3_armhf.deb ... Unpacking libpython2.7-minimal:armhf (2.7.16-2+deb10u3) over (2.7.16-2+deb10u2) ... Preparing to unpack .../7-libncurses6_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking libncurses6:armhf (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Preparing to unpack .../8-libtinfo6_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking libtinfo6:armhf (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Setting up libtinfo6:armhf (6.1+20181013-2+deb10u4) ... (Reading database ... 266527 files and directories currently installed.) Preparing to unpack .../libncursesw6_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking libncursesw6:armhf (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Setting up libncursesw6:armhf (6.1+20181013-2+deb10u4) ... (Reading database ... 266527 files and directories currently installed.) Preparing to unpack .../00-vim-tiny_2%3a8.1.0875-5+deb10u6_armhf.deb ... Unpacking vim-tiny (2:8.1.0875-5+deb10u6) over (2:8.1.0875-5+deb10u5) ... Preparing to unpack .../01-xxd_2%3a8.1.0875-5+deb10u6_armhf.deb ... Unpacking xxd (2:8.1.0875-5+deb10u6) over (2:8.1.0875-5+deb10u5) ... Preparing to unpack .../02-vim-common_2%3a8.1.0875-5+deb10u6_all.deb ... Unpacking vim-common (2:8.1.0875-5+deb10u6) over (2:8.1.0875-5+deb10u5) ... Preparing to unpack .../03-ncurses-term_6.1+20181013-2+deb10u4_all.deb ... Unpacking ncurses-term (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Preparing to unpack .../04-ghostscript_9.27~dfsg-2+deb10u9_armhf.deb ... Unpacking ghostscript (9.27~dfsg-2+deb10u9) over (9.27~dfsg-2+deb10u8) ... Preparing to unpack .../05-libgs9_9.27~dfsg-2+deb10u9_armhf.deb ... Unpacking libgs9:armhf (9.27~dfsg-2+deb10u9) over (9.27~dfsg-2+deb10u8) ... Preparing to unpack .../06-libgs9-common_9.27~dfsg-2+deb10u9_all.deb ... Unpacking libgs9-common (9.27~dfsg-2+deb10u9) over (9.27~dfsg-2+deb10u8) ... Preparing to unpack .../07-libdw1_0.176-1.1+deb10u1_armhf.deb ... Unpacking libdw1:armhf (0.176-1.1+deb10u1) over (0.176-1.1) ... Preparing to unpack .../08-libelf1_0.176-1.1+deb10u1_armhf.deb ... Unpacking libelf1:armhf (0.176-1.1+deb10u1) over (0.176-1.1) ... Preparing to unpack .../09-libflac-dev_1.3.2-3+deb10u3_armhf.deb ... Unpacking libflac-dev:armhf (1.3.2-3+deb10u3) over (1.3.2-3+deb10u2) ... Preparing to unpack .../10-libflac8_1.3.2-3+deb10u3_armhf.deb ... Unpacking libflac8:armhf (1.3.2-3+deb10u3) over (1.3.2-3+deb10u2) ... Preparing to unpack .../11-libncursesw5_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking libncursesw5:armhf (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Preparing to unpack .../12-libncurses5_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking libncurses5:armhf (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Preparing to unpack .../13-libtinfo5_6.1+20181013-2+deb10u4_armhf.deb ... Unpacking libtinfo5:armhf (6.1+20181013-2+deb10u4) over (6.1+20181013-2+deb10u3) ... Preparing to unpack .../14-libpq-dev_11.21-0+deb10u2_armhf.deb ... Unpacking libpq-dev (11.21-0+deb10u2) over (11.19-0+deb10u1) ... Preparing to unpack .../15-libpq5_11.21-0+deb10u2_armhf.deb ... Unpacking libpq5:armhf (11.21-0+deb10u2) over (11.19-0+deb10u1) ... Preparing to unpack .../16-libvpx-dev_1.7.0-3+deb10u2_armhf.deb ... Unpacking libvpx-dev:armhf (1.7.0-3+deb10u2) over (1.7.0-3+deb10u1) ... Preparing to unpack .../17-libvpx5_1.7.0-3+deb10u2_armhf.deb ... Unpacking libvpx5:armhf (1.7.0-3+deb10u2) over (1.7.0-3+deb10u1) ... Preparing to unpack .../18-libwebp-dev_0.6.1-2+deb10u3_armhf.deb ... Unpacking libwebp-dev:armhf (0.6.1-2+deb10u3) over (0.6.1-2+deb10u2) ... Preparing to unpack .../19-libwebp6_0.6.1-2+deb10u3_armhf.deb ... Unpacking libwebp6:armhf (0.6.1-2+deb10u3) over (0.6.1-2+deb10u2) ... Preparing to unpack .../20-libwebpmux3_0.6.1-2+deb10u3_armhf.deb ... Unpacking libwebpmux3:armhf (0.6.1-2+deb10u3) over (0.6.1-2+deb10u2) ... Preparing to unpack .../21-libwebpdemux2_0.6.1-2+deb10u3_armhf.deb ... Unpacking libwebpdemux2:armhf (0.6.1-2+deb10u3) over (0.6.1-2+deb10u2) ... Preparing to unpack .../22-libx11-dev_2%3a1.6.7-1+deb10u4_armhf.deb ... Unpacking libx11-dev:armhf (2:1.6.7-1+deb10u4) over (2:1.6.7-1+deb10u3) ... Preparing to unpack .../23-libx11-data_2%3a1.6.7-1+deb10u4_all.deb ... Unpacking libx11-data (2:1.6.7-1+deb10u4) over (2:1.6.7-1+deb10u3) ... Preparing to unpack .../24-libx11-6_2%3a1.6.7-1+deb10u4_armhf.deb ... Unpacking libx11-6:armhf (2:1.6.7-1+deb10u4) over (2:1.6.7-1+deb10u3) ... Preparing to unpack .../25-libx11-xcb-dev_2%3a1.6.7-1+deb10u4_armhf.deb ... Unpacking libx11-xcb-dev:armhf (2:1.6.7-1+deb10u4) over (2:1.6.7-1+deb10u3) ... Preparing to unpack .../26-libx11-xcb1_2%3a1.6.7-1+deb10u4_armhf.deb ... Unpacking libx11-xcb1:armhf (2:1.6.7-1+deb10u4) over (2:1.6.7-1+deb10u3) ... Preparing to unpack .../27-libxpm4_1%3a3.5.12-1+deb10u2_armhf.deb ... Unpacking libxpm4:armhf (1:3.5.12-1+deb10u2) over (1:3.5.12-1+deb10u1) ... Preparing to unpack .../28-nodejs_18.18.1-1nodesource1_armhf.deb ... Detected old npm client, removing... Unpacking nodejs (18.18.1-1nodesource1) over (16.20.2-deb-1nodesource1) ... Preparing to unpack .../29-openjdk-11-jdk_11.0.20+8-1~deb10u1_armhf.deb ... Unpacking openjdk-11-jdk:armhf (11.0.20+8-1~deb10u1) over (11.0.18+10-1~deb10u1) ... Preparing to unpack .../30-openjdk-11-jdk-headless_11.0.20+8-1~deb10u1_armhf.deb ... Unpacking openjdk-11-jdk-headless:armhf (11.0.20+8-1~deb10u1) over (11.0.18+10-1~deb10u1) ... Preparing to unpack .../31-openjdk-11-jre_11.0.20+8-1~deb10u1_armhf.deb ... Unpacking openjdk-11-jre:armhf (11.0.20+8-1~deb10u1) over (11.0.18+10-1~deb10u1) ... Preparing to unpack .../32-openjdk-11-jre-headless_11.0.20+8-1~deb10u1_armhf.deb ... Unpacking openjdk-11-jre-headless:armhf (11.0.20+8-1~deb10u1) over (11.0.18+10-1~deb10u1) ... Preparing to unpack .../33-python-urllib3_1.24.1-1+deb10u1_all.deb ... Unpacking python-urllib3 (1.24.1-1+deb10u1) over (1.24.1-1) ... Preparing to unpack .../34-python3-renderpm_3.5.13-1+deb10u2_armhf.deb ... Unpacking python3-renderpm:armhf (3.5.13-1+deb10u2) over (3.5.13-1+deb10u1) ... Preparing to unpack .../35-python3-reportlab-accel_3.5.13-1+deb10u2_armhf.deb ... Unpacking python3-reportlab-accel:armhf (3.5.13-1+deb10u2) over (3.5.13-1+deb10u1) ... Preparing to unpack .../36-python3-reportlab_3.5.13-1+deb10u2_all.deb ... Unpacking python3-reportlab (3.5.13-1+deb10u2) over (3.5.13-1+deb10u1) ... Preparing to unpack .../37-python3-urllib3_1.24.1-1+deb10u1_all.deb ... Unpacking python3-urllib3 (1.24.1-1+deb10u1) over (1.24.1-1) ... Preparing to unpack .../38-qemu-utils_1%3a3.1+dfsg-8+deb10u11_armhf.deb ... Unpacking qemu-utils (1:3.1+dfsg-8+deb10u11) over (1:3.1+dfsg-8+deb10u9) ... Setting up libgs9-common (9.27~dfsg-2+deb10u9) ... Setting up python-urllib3 (1.24.1-1+deb10u1) ... Setting up libx11-xcb1:armhf (2:1.6.7-1+deb10u4) ... Setting up python3-renderpm:armhf (3.5.13-1+deb10u2) ... Setting up libgs9:armhf (9.27~dfsg-2+deb10u9) ... Setting up openjdk-11-jre-headless:armhf (11.0.20+8-1~deb10u1) ... Installing new version of config file /etc/java-11-openjdk/security/java.policy ... Installing new version of config file /etc/java-11-openjdk/security/java.security ... Setting up libpq5:armhf (11.21-0+deb10u2) ... Setting up libpq-dev (11.21-0+deb10u2) ... Setting up openjdk-11-jdk-headless:armhf (11.0.20+8-1~deb10u1) ... Setting up ghostscript (9.27~dfsg-2+deb10u9) ... Setting up nodejs (18.18.1-1nodesource1) ... Setting up xxd (2:8.1.0875-5+deb10u6) ... Setting up libflac8:armhf (1.3.2-3+deb10u3) ... Setting up libpython2.7-minimal:armhf (2.7.16-2+deb10u3) ... Setting up vim-common (2:8.1.0875-5+deb10u6) ... Setting up libx11-data (2:1.6.7-1+deb10u4) ... Setting up python2.7-minimal (2.7.16-2+deb10u3) ... Setting up libncurses6:armhf (6.1+20181013-2+deb10u4) ... Setting up python3-reportlab-accel:armhf (3.5.13-1+deb10u2) ... Setting up libwebp6:armhf (0.6.1-2+deb10u3) ... Setting up python3-urllib3 (1.24.1-1+deb10u1) ... Setting up python3-reportlab (3.5.13-1+deb10u2) ... Setting up libx11-6:armhf (2:1.6.7-1+deb10u4) ... Setting up qemu-utils (1:3.1+dfsg-8+deb10u11) ... Setting up libwebpmux3:armhf (0.6.1-2+deb10u3) ... Setting up libtinfo5:armhf (6.1+20181013-2+deb10u4) ... Setting up libelf1:armhf (0.176-1.1+deb10u1) ... Setting up libvpx5:armhf (1.7.0-3+deb10u2) ... Setting up ncurses-term (6.1+20181013-2+deb10u4) ... Setting up libdw1:armhf (0.176-1.1+deb10u1) ... Setting up libflac-dev:armhf (1.3.2-3+deb10u3) ... Setting up libxpm4:armhf (1:3.5.12-1+deb10u2) ... Setting up libwebpdemux2:armhf (0.6.1-2+deb10u3) ... Setting up libx11-dev:armhf (2:1.6.7-1+deb10u4) ... Setting up openjdk-11-jre:armhf (11.0.20+8-1~deb10u1) ... Setting up vim-tiny (2:8.1.0875-5+deb10u6) ... Setting up libncurses5:armhf (6.1+20181013-2+deb10u4) ... Setting up libpython2.7-stdlib:armhf (2.7.16-2+deb10u3) ... Setting up libwebp-dev:armhf (0.6.1-2+deb10u3) ... Setting up libvpx-dev:armhf (1.7.0-3+deb10u2) ... Setting up openjdk-11-jdk:armhf (11.0.20+8-1~deb10u1) ... Setting up libncursesw5:armhf (6.1+20181013-2+deb10u4) ... Setting up libx11-xcb-dev:armhf (2:1.6.7-1+deb10u4) ... Setting up libpython2.7:armhf (2.7.16-2+deb10u3) ... Setting up libpython2.7-dev:armhf (2.7.16-2+deb10u3) ... Setting up python2.7 (2.7.16-2+deb10u3) ... Setting up python2.7-dev (2.7.16-2+deb10u3) ... Processing triggers for mime-support (3.62) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for gnome-menus (3.31.4-3) ... Processing triggers for libc-bin (2.28-10+rpt2+rpi1+deb10u2) ... Processing triggers for man-db (2.8.5-2) ... Processing triggers for desktop-file-utils (0.23-4) ... Installing the recommended nodejs version! We tried our best to fix your nodejs. Please run iob diag again to verify. *** RESTARTING ioBroker NOW! *** Please refresh or restart your browser in a few moments."iob diag" findet folgende Fehler:
Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.3 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.9 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.3 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: coffeescript@1.12.7 /opt/iobroker/node_modules/coffeescript npm ERR! invalid: iobroker.energiefluss@3.5.0 /opt/iobroker/node_modules/iobroker.energiefluss npm ERR! invalid: iobroker.sourceanalytix@0.4.12 /opt/iobroker/node_modules/iobroker.sourceanalytix npm ERR! invalid: iobroker.vr200@1.1.0 /opt/iobroker/node_modules/iobroker.vr200 npm ERR! invalid: iobroker.vw-connect@0.1.3 /opt/iobroker/node_modules/iobroker.vw-connect npm ERR! extraneous: jsonata@1.8.6 /opt/iobroker/node_modules/jsonata npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect npm ERR! extraneous: picocolors@1.0.0 /opt/iobroker/node_modules/picocolors npm ERR! extraneous: suncalc2@1.8.1 /opt/iobroker/node_modules/suncalc2 npm ERR! extraneous: typescript@4.7.4 /opt/iobroker/node_modules/typescript npm ERR! extraneous: virtual-tsc@0.6.2 /opt/iobroker/node_modules/virtual-tsc npm ERR! extraneous: wake_on_lan@1.0.0 /opt/iobroker/node_modules/wake_on_lan npm ERR! extraneous: form-data@2.5.1 /opt/iobroker/node_modules/@types/request/node_modules/form-data npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/virtual-tsc/node_modules/debug npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/virtual-tsc/node_modules/ms npm ERR! invalid: xmlbuilder@0.4.2 /opt/iobroker/node_modules/xmlbuilder npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2023-10-10T21_14_39_557Z-debug-0.log -
@thomas-braun
Mit der schiefen Installation hat's funktioniert...
Nodejs 18 scheint eine neue Javascript Engine zu haben. An dem npm icmp scheint sich seit 3 Jahren nichts geändert zu haben. Da muss ich morgen weiter suchen.
Die Raw Sockets sind aktiviert. Daran liegt's nicht. -
Da ist/war aber auch noch wesentlich mehr schief installiert.
sudo apt update sudo apt full-upgradeliefert?
-
@thomas-braun
Das liefert nachfolgenden Output. Die oben gezeigten Fehlerausgaben mit "iob diag" bleiben danach bestehen.
Sollten wir einen anderen Thread nehmen? Das ist zu OT hier...~ $ sudo apt update Holen:1 http://archive.raspberrypi.org/debian buster InRelease [32,6 kB] Holen:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15,0 kB] OK:3 https://deb.nodesource.com/node_18.x nodistro InRelease OK:4 https://apt.pivccu.de/piVCCU testing InRelease Holen:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [400 kB] Es wurden 447 kB in 1 s geholt (357 kB/s). Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Alle Pakete sind aktuell. N: Für das Depot »http://archive.raspberrypi.org/debian buster InRelease« wurde der »Suite«-Wert von »oldstable« in »oldoldstable« geändert. ~ $ sudo apt full-upgrade Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: alsa-base gconf-service gconf2-common gstreamer0.10-alsa gstreamer0.10-plugins-base gyp libc-ares2 libexiv2-14 libgconf-2-4 libgfortran3 libgmime-2.6-0 libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libjs-inherits libjs-is-typedarray libllvm6.0 libmicrodns0 libncurses5 libuv1-dev libva-wayland2 libxfce4util-bin libxfce4util-common libxfce4util7 libxfconf-0-2 lockfile-progs lxplug-volume node-abbrev node-ajv node-ansi node-ansi-align node-ansi-regex node-ansi-styles node-ansistyles node-aproba node-archy node-are-we-there-yet node-asn1 node-assert-plus node-asynckit node-aws-sign2 node-aws4 node-balanced-match node-bcrypt-pbkdf node-bluebird node-boxen node-brace-expansion node-builtin-modules node-builtins node-cacache node-call-limit node-camelcase node-caseless node-chalk node-chownr node-cli-boxes node-cliui node-clone node-co node-color-convert node-color-name node-combined-stream node-concat-map node-concat-stream node-config-chain node-console-control-strings node-copy-concurrently node-core-util-is node-cross-spawn node-cyclist node-dashdash node-decamelize node-decompress-response node-deep-extend node-defaults node-delayed-stream node-delegates node-detect-indent node-detect-newline node-duplexer3 node-duplexify node-ecc-jsbn node-editor node-encoding node-end-of-stream node-errno node-escape-string-regexp node-execa node-extend node-extsprintf node-find-up node-flush-write-stream node-forever-agent node-form-data node-from2 node-fs-vacuum node-fs-write-stream-atomic node-fs.realpath node-gauge node-get-caller-file node-get-stream node-getpass node-glob node-got node-graceful-fs node-har-schema node-har-validator node-has-flag node-has-symbol-support-x node-has-to-string-tag-x node-has-unicode node-hosted-git-info node-http-signature node-iconv-lite node-iferr node-import-lazy node-imurmurhash node-inflight node-inherits node-ini node-invert-kv node-is-builtin-module node-is-npm node-is-object node-is-plain-obj node-is-retry-allowed node-is-stream node-is-typedarray node-isarray node-isexe node-isstream node-isurl node-jsbn node-json-parse-better-errors node-json-schema node-json-stable-stringify node-json-stringify-safe node-jsonify node-jsonparse node-jsonstream node-jsprim node-latest-version node-lazy-property node-lcid node-libnpx node-locate-path node-lockfile node-lowercase-keys node-lru-cache node-mem node-mime-types node-mimic-fn node-mimic-response node-minimatch node-minimist node-mississippi node-mkdirp node-move-concurrently node-mute-stream node-node-uuid node-nopt node-normalize-package-data node-npm-package-arg node-npm-run-path node-npmlog node-oauth-sign node-object-assign node-once node-opener node-os-locale node-osenv node-p-cancelable node-p-finally node-p-limit node-p-locate node-p-timeout node-package-json node-parallel-transform node-path-exists node-path-is-absolute node-path-is-inside node-performance-now node-prepend-http node-process-nextick-args node-promise-inflight node-promzard node-proto-list node-prr node-pump node-pumpify node-punycode node-qs node-qw node-rc node-read node-read-package-json node-readable-stream node-registry-auth-token node-registry-url node-request node-require-directory node-require-main-filename node-resolve-from node-retry node-rimraf node-run-queue node-safe-buffer node-semver node-semver-diff node-set-blocking node-sha node-shebang-command node-shebang-regex node-signal-exit node-slash node-slide node-sorted-object node-spdx-correct node-spdx-expression-parse node-spdx-license-ids node-sshpk node-ssri node-stream-each node-stream-iterate node-stream-shift node-string-decoder node-string-width node-strip-ansi node-strip-eof node-strip-json-comments node-supports-color node-tar node-term-size node-text-table node-through node-through2 node-timed-out node-tough-cookie node-tunnel-agent node-tweetnacl node-typedarray node-uid-number node-unique-filename node-unpipe node-url-parse-lax node-url-to-options node-util-deprecate node-uuid node-validate-npm-package-license node-validate-npm-package-name node-verror node-wcwidth.js node-which node-which-module node-wide-align node-widest-line node-wrap-ansi node-wrappy node-write-file-atomic node-xdg-basedir node-xtend node-y18n node-yallist node-yargs node-yargs-parser pimixer pmount point-rpi python-colorzero python3-pyperclip python3-thonny rtimucli xfconf Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. -
@ichderarnd sagte in Test Adapter ioBroker.backitup v2.8.x:
N: Für das Depot »http://archive.raspberrypi.org/debian buster InRelease« wurde der »Suite«-Wert von »oldstable« in »oldoldstable« geändert.
Upgraden. Buster ist damit 'TOT'.
-
@thomas-braun
OK... Nach welcher Anleitung sollte ich vorgehen? Da gibt's ja mehrere Quellen...
Sollte das "apt autoremove" vorher ausgeführt werden? -
@ichderarnd sagte in Test Adapter ioBroker.backitup v2.8.x:
Nach welcher Anleitung sollte ich vorgehen?
Ich hab mir seinerzeit meine eigene Anleitung geschrieben. Schau durch meine Themen durch.
-
@thomas-braun
Danke, gefunden. Tolle Arbeit
Ich muss es auf's Wochenende verschieben. Leider steht noch Arbeit an.
Bin gespannt! -
Ich hab ein Master/Slave Testsystem und habe gerade mal testweise auf dem Master ein Backup ausgeführt und wollte es danach wiederherstellen.
Das Backup wurde auch angeblich erfolgreich durchgeführt.Wenn ich dann das Backup wiederherstellen will, erscheint nur folgendes Bild. ioBroker wurde im Hintergrund gestoppt und läuft nicht mehr und der Restore wird nicht durchgeführt
Hat noch jemand dieses Verhalten?
Im web Adapter ist folgendes eingestellt
Ausführung von Backup welches erfolgreich war
iob diag
Log in der Browser Konsole beim Starten der Wiederherstellung
-
@feuersturm sagte in Test Adapter ioBroker.backitup v2.8.x:
- run-rpc_pipefs.mount loaded failed failed RPC Pipe File System
Da klemmt es wohl beim mount irgendwo.
Wird das Backup auf eine Freigabe geschoben? -
@thomas-braun Nein, bei dem Testsystem wird das Backup lokal abgelegt
-
@feuersturm socket hat hier keinen Einfluss, da ja iob komplett gestoppt ist. Backitup spannt einen eigenen Webserver für das restore Interface auf.
Auf welchen System hast du dein Testsystem laufen? Docker? -
@feuersturm Normal sollte es so aussehen ... Ist gerade mit aktueller Backitup Version getestet
-
@simatec sagte in Test Adapter ioBroker.backitup v2.8.x:
Auf welchen System hast du dein Testsystem laufen? Docker?
Nein, es läuft unter proxmox in einem lxc Container
-
@feuersturm gut bei mir in dem test auch. Ein lxc mit debian12
-
@simatec Ich hab es mit meinem Firefoxbrowser getestet. Kann es nochmal mit meinem Chromebrowser testen ob es sich dort anders verhält.
-
Ich hab mal ein neues Issue für das Node-Red Backup erstellt.
https://github.com/simatec/ioBroker.backitup/issues/1005
Im Prinzip ist das Backup für die 1. Instanz nun voll nutzbar - man muss aber manuell noch ein npm install ausführen.
Zusätzliche Instanzen werden aber nicht erkannt.
