Untersuchung: code 25 fehlerlösung
-
@mickym sagte in Untersuchung: code 25 fehlerlösung:
Diese Diskussionen sind doch unsinnig .
Was für Diskussionen? Wir versuchen den Grund für das Verhalten zu finden.
-
root@iobroker:/opt/iobroker# iobroker update Used repository: Stable (default) Adapter "admin" : 6.2.22 , installed 6.2.22 Adapter "backitup" : 2.4.12 , installed 2.4.10 [Updatable] Adapter "bwt" : 0.0.4 , installed 0.0.4 Adapter "cloud" : 4.2.2 , installed 4.2.2 Adapter "coronavirus-statistics": 0.8.7, installed 0.8.7 Adapter "daswetter" : 3.1.3 , installed 3.1.3 Adapter "deconz" : 1.3.21 , installed 2.0.5 Adapter "denon" : 1.13.4 , installed 1.13.4 Adapter "discovery" : 3.0.5 , installed 3.0.5 Adapter "echarts" : 1.0.12 , installed 1.0.12 Adapter "flot" : 1.11.0 , installed 1.11.0 Adapter "fullybrowser" : 2.1.2 , installed 2.1.2 Adapter "harmony" : 1.2.2 , installed 1.2.2 Adapter "heos" : 1.10.0 , installed 1.10.0 Adapter "history" : 2.2.0 , installed 2.2.0 Adapter "hm-rega" : 3.0.40 , installed 3.0.40 Adapter "hm-rpc" : 1.15.12 , installed 1.15.12 Adapter "hue" : 3.7.1 , installed 3.7.1 Adapter "hue-extended" : 2.0.0 , installed 2.0.0 Adapter "icons-material-png": 0.1.0, installed 0.1.0 Adapter "icons-mfd-png": 1.1.0 , installed 1.1.0 Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0 Adapter "influxdb" : 3.1.8 , installed 3.1.8 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.11.9 , installed 1.11.9 Adapter "javascript" : 6.0.3 , installed 6.0.3 Controller "js-controller": 4.0.23 , installed 4.0.23 Adapter "lgtv" : 1.1.10 , installed 1.1.10 Adapter "mbus" : 2.4.0 , installed 2.4.0 Adapter "mihome-vacuum": 3.4.2 , installed 3.4.2 Adapter "modbus" : 5.0.5 , installed 5.0.5 Adapter "mqtt" : 4.0.7 , installed 4.0.7 Adapter "netatmo" : 2.0.5 , installed 1.7.1 [Updatable] Adapter "node-red" : 4.0.0 , installed 4.0.0 Adapter "pushover" : 3.0.3 , installed 3.0.2 [Updatable] Adapter "pvforecast" : 2.3.0 , installed 2.3.0 Adapter "shelly" : 6.0.0 , installed 6.0.0 Adapter "simple-api" : 2.7.0 , installed 2.7.0 Adapter "smartmeter" : 3.3.4 , installed 3.3.4 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "tuya" : 3.6.15 , installed 3.6.15 Adapter "unifi" : 0.5.10 , installed 0.5.10 Adapter "virtualpowermeter": 1.4.6, installed 1.4.6 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-colorpicker": 1.2.0 , installed 1.2.0 Adapter "vis-hqwidgets": 1.3.0 , installed 1.2.0 [Updatable] Adapter "vis-icontwo" : 0.89.0 , installed 0.89.0 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.1 Adapter "vis-jqui-mfd" : 1.0.12 , installed 1.0.12 Adapter "vis-players" : 0.1.6 , installed 0.1.6 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "vis-weather" : 2.5.5 , installed 2.5.5 Adapter "weatherunderground": 3.4.2, installed 3.4.2 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.7.5 , installed 1.7.5 -
cat package.json -
@thomas-braun sagte in Untersuchung: code 25 fehlerlösung:
cat package.json
root@iobroker:/opt/iobroker# cat package.json { "name": "iobroker.inst", "version": "2.0.3", "private": true, "description": "Automation platform in node.js", "scripts": { "install": "node lib/checkVersions.js", "postinstall": "node lib/install.js", "test": "node node_modules/mocha/bin/mocha --exit" }, "dependencies": { "colors": "^1.3.3", "fs-extra": "^7.0.1", "iobroker": "^2.0.3", "iobroker.admin": "6.2.22", "iobroker.backitup": "2.4.10", "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": "github:Matten-Matten/ioBroker.enigma2#17f9d0c2d8a337e46a5e16cbabb9b305d32fd233", "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":"github:TA2k/ioBroker.hoover#d8483c0a1d07a4747f35439baceaa9be981bd83c", "iobroker.hue": "3.7.1", "iobroker.hue-extended": "^2.0.0", "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": "1.7.1", "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/3891a8545b5566946b89b6f4dbfeac1e "iobroker.seko": "github:TA2k/ioBroker.seko#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": "1.4.15", "iobroker.vis-colorpicker": "^1.2.0", "iobroker.vis-hqwidgets": "1.2.0", "iobroker.vis-icontwo": "0.89.0", "iobroker.vis-inventwo": "3.3.1", "iobroker.vis-jqui-mfd": "^1.0.12", "iobroker.vis-material": "^0.1.3", "iobroker.vis-material-webfont": "0.0.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.weatherunderground": "3.4.2", "iobroker.web": "4.3.0", "iobroker.zigbee": "1.7.5", "semver": "^5.6.0", "yargs": "^7.0.2" } } -
@thomas-braun Ok - wenn es um Ursachenforschung und nicht um Fehlerbehebung geht. Nur kann im Fall von NodeRed weder der Adapter was dafür, noch das Produkt selbst. Das wird deshalb sicher nicht geändert, weil es im iobroker Probleme gibt.
-
@mickym sagte in Untersuchung: code 25 fehlerlösung:
Das wird deshalb sicher nicht geändert, weil es im iobroker Probleme gibt.
Wer redet denn von irgendwelchen Änderungen irgendwo? Erstmal muss der Grund gefunden werden.
-
@nwh sagte in Untersuchung: code 25 fehlerlösung:
"iobroker.node-red": "3.3.1",
Das erklärt die 'INVALID'-Meldung. Da sollte eigentlich 4.0.0 eingetragen worden sein.
-
Wenn der Befehl Iobroker update kommt wird node-red nicht angezeigt weil er denkt es ist auf dem neuesten Stand. Aber das hast du sicher schon gesehen.
-
@nwh sagte in Untersuchung: code 25 fehlerlösung:
Wenn der Befehl Iobroker update kommt wird node-red nicht angezeigt weil er denkt es ist auf dem neuesten Stand
Ja. Aber in der /opt/iobroker/package.json ist 3.3.1 eingetragen. Und das scheppert dann. Ich weiß nur nicht warum.
-
@thomas-braun Wie schon mal gefragt, was ist wenn ich über die Iob Oberfläche(Instanzen) Node lösche. werden dann die Verzeichnisse gelöscht?
-
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.
