Untersuchung: code 25 fehlerlösung
-
Lass die GUI aus dem Spiel.
iobroker upgrade node-red@4.0.0 cat /opt/iobroker/package.json | grep node-red -
@thomas-braun sagte in Untersuchung: code 25 fehlerlösung:
cat /opt/iobroker/package.json | grep node-red
Mag er nicht, wie es aussieht.
root@iobroker:/opt/iobroker# iobroker upgrade node-red@4.0.0 Would you like to reinstall version 4.0.0 of node-red now? [(y)es, (n)o]: y Update node-red from @4.0.0 to @4.0.0 NPM version: 8.15.0 Installing iobroker.node-red@4.0.0... (System call) host.iobroker Cannot install iobroker.node-red@4.0.0: 217 root@iobroker:/opt/iobroker# cat /opt/iobroker/package.json | grep node-red "iobroker.node-red": "3.3.1", -
cat /opt/iobroker/package-lock.json | grep -A5 iobroker.node-red -
root@iobroker:/opt/iobroker# cat /opt/iobroker/package-lock.json | grep -A5 iobroker.node-red "iobroker.node-red": "3.3.1", "iobroker.pushover": "3.0.2", "iobroker.pvforecast": "2.3.0", "iobroker.rtspStream": "https://github.com/dbweb-ch/ioBroker.rtspStream/tarball/3891a8545b5566946b89b6f4dbfe ac1e2a6527a5", "iobroker.seko": "github:TA2k/ioBroker.seko#b3c7090c4907fa76d1b2c63d5250b80889445f53", "iobroker.shelly": "6.0.0", -- "node_modules/iobroker.node-red": { "version": "3.3.1", "resolved": "https://registry.npmjs.org/iobroker.node-red/-/iobroker.node-red-3.3.1.tgz", "integrity": "sha512-kCcPDsCvQa5DkNsS7ZWEWcDvAgnB4+ff7EVAsUc2+plVA8jy4F31AS1269z2MWgH5OjgL+t7acqbjYFSehHDgA==" , "dependencies": { "@iobroker/adapter-core": "^2.6.0", "node-red": "^2.2.2", "node-red-contrib-aggregator": "^2.0.0", -- "iobroker.node-red": { "version": "3.3.1", "resolved": "https://registry.npmjs.org/iobroker.node-red/-/iobroker.node-red-3.3.1.tgz", "integrity": "sha512-kCcPDsCvQa5DkNsS7ZWEWcDvAgnB4+ff7EVAsUc2+plVA8jy4F31AS1269z2MWgH5OjgL+t7acqbjYFSehHDgA==" , "requires": { "@iobroker/adapter-core": "^2.6.0", "feedparser": "^2.2.10", "fs.notify": "^0.0.4", -
@nwh Da ist auch die alte Versionsnummer festgetackert.
cd ~ for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; done iobroker upgrade node-red@4.0.0 cat /opt/iobroker/package-lock.json | grep iobroker.node-red cat /opt/iobroker/package.json | grep iobroker.node-red -
@thomas-braun sagte in Untersuchung: code 25 fehlerlösung:
cat /opt/iobroker/package.json | grep iobroker.node-red
root@iobroker:~# cat /opt/iobroker/package.json | grep iobroker.node-red "iobroker.node-red": "4.0.0",sieht so aus als würde es funktioniert haben. in der Gui steht jetzt auch 4.0.
-
cat /opt/iobroker/package-lock.json | grep iobroker.node-redStand in der GUI nicht schon die ganze Zeit 4.0.0 drin?
-
@thomas-braun sagte in Untersuchung: code 25 fehlerlösung:
cat /opt/iobroker/package-lock.json | grep iobroker.node-red
Nein,
root@iobroker:/opt/iobroker# cat /opt/iobroker/package-lock.json | grep iobroker.node-red "iobroker.node-red": "4.0.0", "node_modules/iobroker.node-red": { "resolved": "https://registry.npmjs.org/iobroker.node-red/-/iobroker.node-red-4.0.0.tgz", "iobroker.node-red": { "resolved": "https://registry.npmjs.org/iobroker.node-red/-/iobroker.node-red-4.0.0.tgz", -
iobroker update iobroker upgrade all -
@thomas-braun alles ohne Problem durchgelaufen.
-
-
@thomas-braun
sieht gut ausiobroker.inst@2.0.3 /opt/iobroker ├── colors@1.4.0 ├── fs-extra@7.0.1 ├── iobroker.admin@6.2.22 ├── iobroker.backitup@2.4.12 ├── iobroker.bwt@0.0.4 ├── iobroker.cloud@4.2.2 ├── iobroker.coronavirus-statistics@0.8.7 ├── iobroker.daswetter@3.1.3 ├── iobroker.deconz@2.0.5 ├── iobroker.denon@1.13.4 ├── iobroker.discovery@3.0.5 ├── iobroker.echarts@1.0.12 ├── iobroker.enigma2@1.3.3 (git+ssh://git@github.com/Matten-Matten/ioBroker.enigma2.git#17f9d0c2d8a337e46a5e16cbabb9 b305d32fd233) ├── iobroker.flot@1.11.0 ├── iobroker.fullybrowser@2.1.2 ├── iobroker.harmony@1.2.2 ├── iobroker.heos@1.10.0 ├── iobroker.history@2.2.0 ├── iobroker.hm-rega@3.0.40 ├── iobroker.hm-rpc@1.15.12 ├── iobroker.hoover@0.0.1 (git+ssh://git@github.com/TA2k/ioBroker.hoover.git#d8483c0a1d07a4747f35439baceaa9be981bd83 c) ├── iobroker.hue-extended@2.0.0 ├── iobroker.hue@3.7.1 ├── iobroker.icons-material-png@0.1.0 ├── iobroker.icons-mfd-png@1.1.0 ├── iobroker.icons-mfd-svg@1.1.0 ├── iobroker.influxdb@3.1.8 ├── iobroker.info@1.9.19 ├── iobroker.iot@1.11.9 ├── iobroker.javascript@6.0.3 ├── iobroker.js-controller@4.0.23 ├── iobroker.lgtv@1.1.10 ├── iobroker.mbus@2.4.0 ├── iobroker.mihome-vacuum@3.4.2 ├── iobroker.modbus@5.0.5 ├── iobroker.mqtt@4.0.7 ├── iobroker.netatmo@2.0.5 ├── iobroker.node-red@4.0.0 ├── iobroker.pushover@3.0.3 ├── iobroker.pvforecast@2.3.0 ├── iobroker.rtspStream@0.0.2 ├── iobroker.seko@0.0.1 (git+ssh://git@github.com/TA2k/ioBroker.seko.git#b3c7090c4907fa76d1b2c63d5250b80889445f53) ├── iobroker.shelly@6.0.0 ├── iobroker.simple-api@2.7.0 ├── iobroker.smartmeter@3.3.4 ├── iobroker.socketio@4.2.0 ├── iobroker.sourceanalytix@0.4.12 ├── iobroker.tuya@3.6.15 ├── iobroker.unifi@0.5.10 ├── iobroker.virtualpowermeter@1.4.6 ├── iobroker.vis-colorpicker@1.2.0 ├── iobroker.vis-hqwidgets@1.3.0 ├── iobroker.vis-icontwo@0.89.0 ├── iobroker.vis-inventwo@3.3.1 ├── iobroker.vis-jqui-mfd@1.0.12 ├── iobroker.vis-material-webfont@0.0.3 ├── iobroker.vis-material@0.1.3 ├── iobroker.vis-materialdesign@0.4.2 ├── iobroker.vis-players@0.1.6 ├── iobroker.vis-timeandweather@1.2.2 ├── iobroker.vis-weather@2.5.5 ├── iobroker.vis@1.4.15 ├── iobroker.weatherunderground@3.4.2 ├── iobroker.web@4.3.0 ├── iobroker.zigbee@1.7.5 ├── iobroker@2.0.3 ├── semver@5.7.1 └── yargs@7.1.1 -
Gut, schaut jetzt sauber aus.
Warum die package.json und package-lock.json beim node-red nicht aktualisiert werden weiß ich jetzt aber immer noch nicht.
-
@thomas-braun Was soll ich sagen, ausser mal Danke für die Hilfe.
Wenn ich noch was für die Aufklärung beitragen kann, lass es mich wissen. -
Ich würde mich hier leider auch einreihen.
Beim Update von backitup von 2.4.10 auf 2.4.12 kommt bei mir auch der code 25...
npm ls meldet beim SQL (ich glaube, den hab ich zuletzt aktualisiert - ohne Fehler):
iobroker.sql@2.1.8 invalid: "2.1.7" from the root projectnpm update hab ich gemacht, npm upgrade all möchte ich noch nicht, da ich mich erst noch um die States vom netatmo-Adapter kümmern muss, um die History zu erhalten.
Was kann ich am besten tun?
-
Mit npm direkt hantiert man am besten ohnehin nicht herum.
cat /opt/iobroker/package-lock.json | grep iobroker.sql cat /opt/iobroker/package.json | grep iobroker.sql iobroker updateDa dürfte dann 2.1.7 drin stehen, vermute ich.
-
pi@raspberrypi:~ $ cat /opt/iobroker/package-lock.json | grep iobroker.sql "iobroker.sql": "2.1.7", "node_modules/iobroker.sql": { "resolved": "https://registry.npmjs.org/iobroker.sql/-/iobroker.sql-2.1.7.tgz", "iobroker.sql": { "resolved": "https://registry.npmjs.org/iobroker.sql/-/iobroker.sql-2.1.7.tgz", pi@raspberrypi:~ $ cat /opt/iobroker/package.json | grep iobroker.sql {"name":"iobroker.inst","version":"3.0.0","private":true,"description":"Automate your Life","engines":{"node":">=10.0.0"},"dependencies":{"iobroker.admin":"6.2.22","iobroker.backitup":"2.4.10","iobroker.discovery":"3.0.5","iobroker.email":"1.1.3","iobroker.feiertage":"1.1.0","iobroker.flot":"1.11.0","iobroker.history":"2.2.0","iobroker.icons-addictive-flavour-png":"0.1.0","iobroker.info":"1.9.19","iobroker.javascript":"6.0.3","iobroker.js-controller":"stable","iobroker.kecontact":"github:iobroker-community-adapters/ioBroker.kecontact","iobroker.mobile":"1.0.1","iobroker.modbus":"5.0.5","iobroker.musiccast":"0.1.5","iobroker.netatmo":"1.7.1","iobroker.ping":"1.5.3","iobroker.pioneer_sc_vsx":"github:Sneak-L8/ioBroker.pioneer_sc_vsx#37cb50cf74d3e7117ffcd31557b8977edfd2b19d","iobroker.rpi2":"1.3.2","iobroker.simple-api":"2.7.0","iobroker.sma-em":"github:iobroker-community-adapters/ioBroker.sma-em#55ef1a101f7f3920a6b1a5b2b2ab0501aea2be5c","iobroker.sma-speedwire":"github:Apollon77/iobroker.sma-speedwire#3dce8e5d3fb9112502ba697a0f41ec0ab0aa90f4","iobroker.socketio":"4.2.0","iobroker.sonos":"2.2.3","iobroker.sql":"2.1.7","iobroker.tr-064":"4.2.16","iobroker.vis":"1.4.15","iobroker.vis-icontwo":"0.89.0","iobroker.vis-inventwo":"3.3.1","iobroker.vw-connect":"0.0.51","iobroker.web":"4.3.0","iobroker.whatsapp-cmb":"0.2.2","iobroker.ws":"1.3.0","iobroker.yamaha":"0.5.3"}} pi@raspberrypi:~ $ iobroker update Used repository: stable Adapter "admin" : 6.2.22 , installed 6.2.22 Adapter "backitup" : 2.4.12 , installed 2.4.10 [Updatable] Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "email" : 1.1.3 , installed 1.1.3 Adapter "feiertage" : 1.1.0 , installed 1.1.0 Adapter "flot" : 1.11.0 , installed 1.11.0 Adapter "history" : 2.2.0 , installed 2.2.0 Adapter "icons-addictive-flavour-png": 0.1.0, installed 0.1.0 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "javascript" : 6.0.3 , installed 6.0.3 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "kecontact" : 1.4.1 , installed 1.4.1 Adapter "mobile" : 1.0.1 , installed 1.0.1 Adapter "modbus" : 5.0.5 , installed 5.0.5 Adapter "musiccast" : 0.1.5 , installed 0.1.5 Adapter "netatmo" : 2.0.5 , installed 1.7.1 [Updatable] Adapter "ping" : 1.5.3 , installed 1.5.3 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "simple-api" : 2.7.0 , installed 2.7.0 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonos" : 2.2.3 , installed 2.2.3 Adapter "sql" : 2.1.8 , installed 2.1.8 Adapter "tr-064" : 4.2.16 , installed 4.2.16 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-icontwo" : 0.89.0 , installed 0.89.0 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.1 Adapter "vw-connect" : 0.0.51 , installed 0.0.51 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "whatsapp-cmb" : 0.2.2 , installed 0.2.2 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "yamaha" : 0.5.3 , installed 0.5.3Korrekt
-
for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; done iobroker upgrade sql@2.1.8 -
@thomas-braun sagte in Untersuchung: code 25 fehlerlösung:
for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; done
Hatte ich schon gemacht, ohne Ergebnis. Es werden ein paar Fehler geworfen:
rm: cannot remove '/opt/iobroker/node_modules/.sqlite3-8qPhwEH9/build-tmp-napi-v6/Release/obj/gen/sqlite-autoconf-3390200/tea/configure.ac': Permission deniedaber das dürften icht relevant sein.
iobroker upgrade sql@2.1.8
ergibt leider:
Would you like to reinstall version 2.1.8 of sql now? [(y)es, (n)o]: y Update sql from @2.1.8 to @2.1.8 host.raspberrypi Adapter "system.adapter.sql.0" is stopped. NPM version: 8.11.0 Installing iobroker.sql@2.1.8... (System call) host.raspberrypi Cannot install iobroker.sql@2.1.8: 217Die 217 kam auch bei backitup.
-
@sneak-l8 sagte in Untersuchung: code 25 fehlerlösung:
aber das dürften icht relevant sein.
Das ist sogar SEHR relevant, das zeigt mir nämlich, dass da mal mit den falschen Rechten/Usern herumgefahren worden ist.
iobroker stop iobroker fix for i in $(find /opt/iobroker/node_modules -type d -iname ".*-????????" ! -iname ".local-chromium"); do rm -rf ${i%%/}; done iobroker upgrade sql@2.1.8
