NEWS
Adapter werden nicht mehr geupdated
ioBroker Allgemein
74
Beiträge
5
Kommentatoren
2.8k
Aufrufe
5
Watching
-
@thomas-braun hatte es nach 2h abgebrochen weil sich nix mehr getan hat. Jetzt gerade noch mal probiert:
Last login: Sun Dec 3 15:37:58 on ttys000 accu@iMac ~ % ssh pi@192.168.1.13 pi@192.168.1.13's password: Linux Raspi 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Dec 3 15:39:14 2023 from 192.168.1.92 pi@Raspi:~ $ cd /opt/iobroker pi@Raspi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/agent-base npm ERR! dest /opt/iobroker/node_modules/.agent-base-ZzrsLltQ npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/agent-base' -> '/opt/iobroker/node_modules/.agent-base-ZzrsLltQ' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2023-12-03T14_46_44_145Z-debug-0.log pi@Raspi:/opt/iobroker $gibts noch irgendeine Möglichkeit das alte System vorerst wieder zum Laufen zu bringen?
iob fix -
@accu sagte in Adapter werden nicht mehr geupdated:
@homoran wie bereitet man die neue Karte am PC vor? einfach übern Card Reader?
wie sonst?
was hast du denn bisher gemacht? -
iob fix@thomas-braun habe ich schon 2x drüber laufen lassen. Der Fehler bleibt der gleiche:
pi@Raspi:~ $ iob fix library: loaded Library version=2023-10-13 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-10-13 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 https://deb.nodesource.com/node_18.x nodistro InRelease OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease Paketlisten werden gelesen... Fertig ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@Raspi:~ $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code EACCES npm ERR! syscall mkdir npm ERR! path /home/pi/node_modules/iobroker.js-controller npm ERR! errno -13 npm ERR! Error: EACCES: permission denied, mkdir '/home/pi/node_modules/iobroker.js-controller' npm ERR! [Error: EACCES: permission denied, mkdir '/home/pi/node_modules/iobroker.js-controller'] { npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'mkdir', npm ERR! path: '/home/pi/node_modules/iobroker.js-controller' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! A complete -
@thomas-braun sagte in Adapter werden nicht mehr geupdated:
Soweit ich weiß geht's nur per Raspberry Imager an einem Bildschirm. Hab mich aber noch nie damit beschäftigt, das Headless zu machen.
wieso nicht.
neue Karte am PC vorbereiten
alte Installation per ssh runterfahren
in den Keller gehen, Karte tauschen, Power onbis er wieder am PC sitzt ist Bookworm hochgefahren
alles andere geht wieder mit SSH@homoran sagte in Adapter werden nicht mehr geupdated:
wieso nicht.
:-) Hatte irgendwie Richtung 'Image auf der Kommandozeile flashen' gedacht... Der Raspberry Imager hat aber afaik kein CLI.
-
@thomas-braun habe ich schon 2x drüber laufen lassen. Der Fehler bleibt der gleiche:
pi@Raspi:~ $ iob fix library: loaded Library version=2023-10-13 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-10-13 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== OK:1 http://archive.raspberrypi.org/debian buster InRelease OK:2 https://deb.nodesource.com/node_18.x nodistro InRelease OK:3 http://raspbian.raspberrypi.org/raspbian buster InRelease Paketlisten werden gelesen... Fertig ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@Raspi:~ $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code EACCES npm ERR! syscall mkdir npm ERR! path /home/pi/node_modules/iobroker.js-controller npm ERR! errno -13 npm ERR! Error: EACCES: permission denied, mkdir '/home/pi/node_modules/iobroker.js-controller' npm ERR! [Error: EACCES: permission denied, mkdir '/home/pi/node_modules/iobroker.js-controller'] { npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'mkdir', npm ERR! path: '/home/pi/node_modules/iobroker.js-controller' npm ERR! } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! A complete@accu sagte in Adapter werden nicht mehr geupdated:
pi@Raspi:~ $ sudo -H -u iobroker npm install iobroker.js-controller
Du stehst im falschen Verzeichnis.
Und nein, der Fehler ist nicht der gleiche...
-
@accu sagte in Adapter werden nicht mehr geupdated:
pi@Raspi:~ $ sudo -H -u iobroker npm install iobroker.js-controller
Du stehst im falschen Verzeichnis.
Und nein, der Fehler ist nicht der gleiche...
@thomas-braun ich habe jetzt mal meine Backup Speicherkarte vom System genommen, weil die andere Installation komplett zerschossen war.
Habe jetzt alle Updates gemacht und der iobroker läuft wieder.
Allerdings habe ich Probleme bei der Authentifizierung in den Adapter settings. Der Button lässt sich nicht drücken und erscheint ausgegraut. Auch in Firefox das gleiche. Liegt das evtl. an der veralteten Node Version. Gibt's da eine Möglichkeit noch aktuellere Versionen zu installieren ohne das bestehende Altsystem wieder zu Schrotten?
mein System sieht so aus:
Es gibt keine Nutzer-Sitzungen mit veralteten Prozessen. pi@Raspi:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 nodejs: Installiert: 14.21.3-deb-1nodesource1 Installationskandidat: 14.21.3-deb-1nodesource1 Versionstabelle: *** 14.21.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.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 -
@thomas-braun ich habe jetzt mal meine Backup Speicherkarte vom System genommen, weil die andere Installation komplett zerschossen war.
Habe jetzt alle Updates gemacht und der iobroker läuft wieder.
Allerdings habe ich Probleme bei der Authentifizierung in den Adapter settings. Der Button lässt sich nicht drücken und erscheint ausgegraut. Auch in Firefox das gleiche. Liegt das evtl. an der veralteten Node Version. Gibt's da eine Möglichkeit noch aktuellere Versionen zu installieren ohne das bestehende Altsystem wieder zu Schrotten?mein System sieht so aus:
Es gibt keine Nutzer-Sitzungen mit veralteten Prozessen. pi@Raspi:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 nodejs: Installiert: 14.21.3-deb-1nodesource1 Installationskandidat: 14.21.3-deb-1nodesource1 Versionstabelle: *** 14.21.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.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 Packagesiob nodejs-update -
iob nodejs-updateioBroker nodejs fixer 2023-10-13 No recommendation for a nodejs version found on your system. We recommend to install latest version from nodejs v18 tree. Your current setup is: /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/local/bin/npx 8.1.2 /usr/local/bin/corepack 0.10.0 *** nodejs is NOT correctly installed *** We found these nodejs versions available for installation: nodejs: Installed: 14.21.3-deb-1nodesource1 Candidate: 14.21.3-deb-1nodesource1 Version table: *** 14.21.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.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 Your nodejs-Installation seems to be faulty. Shall we try to fix it? Press <y> to continue or any other key to quit Fixing your nodejs setup *** Deleting /usr/local/bin/npx *** *** Deleting /usr/local/bin/corepack *** Wrong paths have been fixed. Run 'iob diag' or 'iob node-fix' again to check if your installation is fine now You are running nodejs v14.21.3. Do you want to install latest version from nodejs v.18 tree? Press <y> to continue or any other key to quit Trying to update your installation now. Please be patient. Waiting for ioBroker to shut down - Give me a minute... ############################################################ *** These repos are active on your system: Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 http://archive.raspberrypi.org/debian buster InRelease 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 Get:3 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB] Get:4 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages [6272 B] Fetched 18.4 kB in 4s (5030 B/s) Reading package lists... Done Installing the recommended nodejs version now! Exact recommended version unknown, installing a fallback! (Reading database ... 144794 files and directories currently installed.) Preparing to unpack .../nodejs_18.0.0-1nodesource1_armhf.deb ... Detected old npm client, removing... Unpacking nodejs (18.0.0-1nodesource1) over (14.21.3-deb-1nodesource1) ... Setting up nodejs (18.0.0-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... Scanning processes... Scanning candidates... Scanning linux images... Failed to check for processor microcode upgrades. Restarting services... systemctl restart pm2.service No containers need to be restarted. No user sessions are running outdated binaries. Updating fallback to latest nodejs v18 release (Reading database ... 145600 files and directories currently installed.) Preparing to unpack .../nodejs_18.19.0-1nodesource1_armhf.deb ... Detected old npm client, removing... Unpacking nodejs (18.19.0-1nodesource1) over (18.0.0-1nodesource1) ... Setting up nodejs (18.19.0-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... Scanning processes... Scanning candidates... Scanning linux images... Failed to check for processor microcode upgrades. Restarting services... systemctl restart pm2.service No containers need to be restarted. No user sessions are running outdated binaries. v18.19.0 has been installed! You are using the latest version now! 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. -
ioBroker nodejs fixer 2023-10-13 No recommendation for a nodejs version found on your system. We recommend to install latest version from nodejs v18 tree. Your current setup is: /usr/bin/nodejs v14.21.3 /usr/bin/node v14.21.3 /usr/bin/npm 6.14.18 /usr/local/bin/npx 8.1.2 /usr/local/bin/corepack 0.10.0 *** nodejs is NOT correctly installed *** We found these nodejs versions available for installation: nodejs: Installed: 14.21.3-deb-1nodesource1 Candidate: 14.21.3-deb-1nodesource1 Version table: *** 14.21.3-deb-1nodesource1 500 500 https://deb.nodesource.com/node_14.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 Your nodejs-Installation seems to be faulty. Shall we try to fix it? Press <y> to continue or any other key to quit Fixing your nodejs setup *** Deleting /usr/local/bin/npx *** *** Deleting /usr/local/bin/corepack *** Wrong paths have been fixed. Run 'iob diag' or 'iob node-fix' again to check if your installation is fine now You are running nodejs v14.21.3. Do you want to install latest version from nodejs v.18 tree? Press <y> to continue or any other key to quit Trying to update your installation now. Please be patient. Waiting for ioBroker to shut down - Give me a minute... ############################################################ *** These repos are active on your system: Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:2 http://archive.raspberrypi.org/debian buster InRelease 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 Get:3 https://deb.nodesource.com/node_18.x nodistro InRelease [12.1 kB] Get:4 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages [6272 B] Fetched 18.4 kB in 4s (5030 B/s) Reading package lists... Done Installing the recommended nodejs version now! Exact recommended version unknown, installing a fallback! (Reading database ... 144794 files and directories currently installed.) Preparing to unpack .../nodejs_18.0.0-1nodesource1_armhf.deb ... Detected old npm client, removing... Unpacking nodejs (18.0.0-1nodesource1) over (14.21.3-deb-1nodesource1) ... Setting up nodejs (18.0.0-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... Scanning processes... Scanning candidates... Scanning linux images... Failed to check for processor microcode upgrades. Restarting services... systemctl restart pm2.service No containers need to be restarted. No user sessions are running outdated binaries. Updating fallback to latest nodejs v18 release (Reading database ... 145600 files and directories currently installed.) Preparing to unpack .../nodejs_18.19.0-1nodesource1_armhf.deb ... Detected old npm client, removing... Unpacking nodejs (18.19.0-1nodesource1) over (18.0.0-1nodesource1) ... Setting up nodejs (18.19.0-1nodesource1) ... Processing triggers for man-db (2.8.5-2) ... Scanning processes... Scanning candidates... Scanning linux images... Failed to check for processor microcode upgrades. Restarting services... systemctl restart pm2.service No containers need to be restarted. No user sessions are running outdated binaries. v18.19.0 has been installed! You are using the latest version now! 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. -
@thomas-braun leider ist der Netatmo Authenticate Button immer noch ausgegraut :(
======================= SUMMARY ======================= v.2023-10-10 Static hostname: Raspi Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 6.1.64-v7+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 32 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 922M 650M 109M 1.0M 162M 209M Swap: 99M 99M 0.0K Total: 1.0G 750M 109M Active iob-Instances: 11 Active repo: stable ioBroker Core: js-controller 3.3.22 admin 5.2.3 ioBroker Status: iobroker is running on this host. Objects type: file States type: file Status admin and web instance: + system.adapter.admin.0 : admin : Raspi - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : Raspi - disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 28472 States: 14139 Size of iob-Database: 20M /opt/iobroker/iobroker-data/objects.json.bak 20M /opt/iobroker/iobroker-data/objects.json 17M /opt/iobroker/iobroker-data/objects.json.broken 12K /opt/iobroker/iobroker-data/objects.json.old 2.8M /opt/iobroker/iobroker-data/states.json.bak 2.8M /opt/iobroker/iobroker-data/states.json 1.9M /opt/iobroker/iobroker-data/states.json.old 0 /opt/iobroker/iobroker-data/states.json.broken =================== END OF SUMMARY ==================== -
@thomas-braun leider ist der Netatmo Authenticate Button immer noch ausgegraut :(
======================= SUMMARY ======================= v.2023-10-10 Static hostname: Raspi Icon name: computer Operating System: Raspbian GNU/Linux 10 (buster) Kernel: Linux 6.1.64-v7+ Architecture: arm Installation: native Kernel: armv7l Userland: armhf Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 32 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 922M 650M 109M 1.0M 162M 209M Swap: 99M 99M 0.0K Total: 1.0G 750M 109M Active iob-Instances: 11 Active repo: stable ioBroker Core: js-controller 3.3.22 admin 5.2.3 ioBroker Status: iobroker is running on this host. Objects type: file States type: file Status admin and web instance: + system.adapter.admin.0 : admin : Raspi - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.web.0 : web : Raspi - disabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 28472 States: 14139 Size of iob-Database: 20M /opt/iobroker/iobroker-data/objects.json.bak 20M /opt/iobroker/iobroker-data/objects.json 17M /opt/iobroker/iobroker-data/objects.json.broken 12K /opt/iobroker/iobroker-data/objects.json.old 2.8M /opt/iobroker/iobroker-data/states.json.bak 2.8M /opt/iobroker/iobroker-data/states.json 1.9M /opt/iobroker/iobroker-data/states.json.old 0 /opt/iobroker/iobroker-data/states.json.broken =================== END OF SUMMARY ====================@accu sagte in Adapter werden nicht mehr geupdated:
Pending iob updates: 32
Und 1 GB RAM ist zu wenig.
-
@accu sagte in Adapter werden nicht mehr geupdated:
Pending iob updates: 32
Und 1 GB RAM ist zu wenig.
-
@thomas-braun wie gesagt die updates macht er nicht bzw. läuft durch bei den updates aber bietet diese dann wieder zum update an
-
@thomas-braun glaube meine sicherungskopie hat es jetzt auch hinter sich:
Last login: Sun Dec 10 10:20:16 on console accu@iMac ~ % ssh pi@192.168.1.13 pi@192.168.1.13's password: Linux Raspi 6.1.64-v7+ #1702 SMP Wed Nov 29 14:16:46 GMT 2023 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Dec 10 08:29:18 2023 pi@Raspi:~ $ iob status node:internal/modules/cjs/loader:1137 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) at Module._load (node:internal/modules/cjs/loader:975:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.19.0 pi@Raspi:~ $ iob upgrade all node:internal/modules/cjs/loader:1137 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) at Module._load (node:internal/modules/cjs/loader:975:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.19.0 pi@Raspi:~ $ -
Dein Betriebssysrem ist zu alt.
Aktualisier das auf Raspberry OS 12 'Bookworm'@thomas-braun
ich installiere jetzt mal die Bookworm Version auf ner anderen Speicherkarte und berichte ... -
@thomas-braun glaube meine sicherungskopie hat es jetzt auch hinter sich:
Last login: Sun Dec 10 10:20:16 on console accu@iMac ~ % ssh pi@192.168.1.13 pi@192.168.1.13's password: Linux Raspi 6.1.64-v7+ #1702 SMP Wed Nov 29 14:16:46 GMT 2023 armv7l The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Sun Dec 10 08:29:18 2023 pi@Raspi:~ $ iob status node:internal/modules/cjs/loader:1137 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) at Module._load (node:internal/modules/cjs/loader:975:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.19.0 pi@Raspi:~ $ iob upgrade all node:internal/modules/cjs/loader:1137 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1134:15) at Module._load (node:internal/modules/cjs/loader:975:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.19.0 pi@Raspi:~ $cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller@thomas-braun ich hoffe er läuft diesmal durch. Musste nach 4h letztens abbrechen, weil er eingeforen ist.
pi@Raspi:~ $ cd /opt/iobroker pi@Raspi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed. npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. npm WARN deprecated multer@1.4.2: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated passport.socketio@3.7.0: Please check the workaround in https://github.com/jfromaniello/passport.socketio/issues/148 npm WARN deprecated request@2.88.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated bcrypt@3.0.6: versions < v5.0.0 do not handle NUL in passwords properly npm WARN deprecated bcrypt@3.0.8: versions < v5.0.0 do not handle NUL in passwords properly npm WARN deprecated vm2@3.9.19: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm. npm WARN deprecated node-pre-gyp@0.12.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future npm WARN deprecated node-pre-gyp@0.14.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future npm WARN deprecated appium-logger@2.1.0: Moved into appium-support npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. (##################) ⠹ reify:iobroker.admin: http fetch GET 200 https://registry.npmjs.org/iobroker.admin/-/iobroker.admin-5.4.9.tgz 923762ms (cache miss) -
Einem Rpi3 würde ich aber die 64Bit-Version spendieren.
@thomas-braun installation ist erfolgreich durchgelaufen und der neu ioBroker installiert gerade die Instanzen.
Was schmerzt sind, dass ich meine skripte aus dem alten ioB nicht mehr habe.Die speicherkarte mit der geschrotteten iob instanz habe ich noch. Gibts da irgendeine chance die Blockly Skripte rauszuextrahieren?
-
@thomas-braun installation ist erfolgreich durchgelaufen und der neu ioBroker installiert gerade die Instanzen.
Was schmerzt sind, dass ich meine skripte aus dem alten ioB nicht mehr habe.Die speicherkarte mit der geschrotteten iob instanz habe ich noch. Gibts da irgendeine chance die Blockly Skripte rauszuextrahieren?
Hast du kein gescheites Backup extern liegen?
-
Hast du kein gescheites Backup extern liegen?
709
Online32.6k
Benutzer82.2k
Themen1.3m
Beiträge