[gelöst] iobroker offline nach admin update
-
@DaBa6 danke dir für die Antwort. Brachte leider keinen Erfolg.
-
@JRiddim hast du das Update gemacht? Ich hatte gestern Vormittag das gleiche Problem
https://forum.iobroker.net/topic/29463/gelöst-admin-upd-iobroker-nicht-mehr-erreichbar/24
-
@HeinrichB ja leider nicht über die Konsole
-
Siehe meinen Dialog gestern dazu
https://forum.iobroker.net/topic/29463/gelöst-admin-upd-iobroker-nicht-mehr-erreichbar/24
-
@HeinrichB danke dir, den Thread habe ich gesehen, habe alles auch durchprobiert...
-
@JRiddim verzeih meine Einmischung
-
@HeinrichB ich bin für jede Hilfe dankbar!
-
-
ps -A | grep iobroker 541 ? 00:19:16 iobroker.js-con -
@JRiddim
ok
erst den befehl eingeben
cd /opt/iobrokerdann den
node node_modules/iobroker.js-controller/controller.js --logs -
@haselchen sagte in iobroker nicht mehr erreichbar nach admin update:
node node_modules/iobroker.js-controller/controller.js --logs
node node_modules/iobroker.js-controller/controller.js --logs 2020-01-29 22:32:59.327 - info: host.raspberrypi iobroker.js-controller version 2.2.8 js-controller starting 2020-01-29 22:32:59.336 - info: host.raspberrypi Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker 2020-01-29 22:32:59.337 - info: host.raspberrypi hostname: raspberrypi, node: v10.18.1 2020-01-29 22:32:59.339 - info: host.raspberrypi ip addresses: 192.168.100.50 fe80::dea6:32ff:fe0a:7cb6 fe80::fc97:c0ff:fef0:a5a8 2020-01-29 22:32:59.803 - info: host.raspberrypi Error inMem-objects listening on port 9001 2020-01-29 22:33:00.351 - info: host.raspberrypi Error inMem-states listening on port 9000 2020-01-29 22:33:00.405 - info: host.raspberrypi connected to Objects and States 2020-01-29 22:33:00.551 - info: host.raspberrypi 33 instances found host.raspberrypi check instance "system.adapter.discovery.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.info.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.mihome-vacuum.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.telegram.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.hue.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.hm-rpc.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.hm-rega.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.hm-rpc.1" for host "raspberrypi" host.raspberrypi check instance "system.adapter.ping.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.web.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-hqwidgets.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-timeandweather.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-jqui-mfd.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-metro.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.spotify-premium.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-google-fonts.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-fancyswitch.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-bars.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-history.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.ical.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.vis-justgage.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.weatherunderground.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.yr.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.backitup.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.terminal.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.zigbee.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.javascript.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.yahka.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.youtube.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.admin.0" for host "raspberrypi" host.raspberrypi check instance "system.adapter.admin.1" for host "raspberrypi" 2020-01-29 22:33:00.615 - info: host.raspberrypi starting 30 instances 2020-01-29 22:33:00.665 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 19462 ================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped] 2020-01-29 22:33:02.894 - error: host.raspberrypi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-01-29 22:33:02.894 - info: host.raspberrypi Do not restart adapter system.adapter.admin.0 because desired by instance ================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging] 2020-01-29 22:33:04.633 - info: host.raspberrypi instance system.adapter.admin.1 started with pid 19655 ================================== > LOG REDIRECT system.adapter.admin.1 => false [Process stopped] 2020-01-29 22:33:06.831 - error: host.raspberrypi instance system.adapter.admin.1 terminated by request of the instance itself and will not be restarted, before user restarts it. 2020-01-29 22:33:06.832 - info: host.raspberrypi Do not restart adapter system.adapter.admin.1 because desired by instance ================================== > LOG REDIRECT system.adapter.admin.1 => false [system.adapter.admin.1.logging] 2020-01-29 22:33:08.633 - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 19684 2020-01-29 22:33:10.198 - error: host.raspberrypi instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2020-01-29 22:33:10.199 - info: host.raspberrypi Restart adapter system.adapter.discovery.0 because enabled 2020-01-29 22:33:12.632 - info: host.raspberrypi instance system.adapter.info.0 started with pid 19861 2020-01-29 22:33:14.750 - error: host.raspberrypi instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2020-01-29 22:33:14.751 - info: host.raspberrypi Restart adapter system.adapter.info.0 because enabled 2020-01-29 22:33:16.630 - info: host.raspberrypi instance system.adapter.mihome-vacuum.0 started with pid 19893 2020-01-29 22:33:18.147 - error: host.raspberrypi instance system.adapter.mihome-vacuum.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING) 2020-01-29 22:33:18.148 - info: host.raspberrypi Restart adapter system.adapter.mihome-vacuum.0 because enabled 2020-01-29 22:33:20.631 - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20087das will nicht mehr aufhören geht ewig weiter
-
gib iobroker stop ein
dann
npm install iobroker.js-controller
dann
iobroker start -
@haselchen sagte in iobroker nicht mehr erreichbar nach admin update:
gib iobroker stop ein
tut sich nichts läuft munter weiter. Kann ich die Konsole einfach schließen?
-
Ich mach das immer nach try and error.
Auf eigene Gefahr.
Ich hatte das Problem auch.
Und bin die Befehle durchgegangen.
Versuch mal iobroker neu zu starten. Also das Gerät. -
@haselchen sagte in iobroker nicht mehr erreichbar nach admin update:
gib iobroker stop ein
dann
npm install iobroker.js-controller
dann
iobroker startauf der Ebene opt/iobroker oder?
-
richtig.
-
erhalte diese Meldung dabei.
npm install iobroker.js-controller npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor. > iobroker.js-controller@2.2.8 preinstall /opt/iobroker/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.13.4 > iobroker.js-controller@2.2.8 install /opt/iobroker/node_modules/iobroker.js-controller > node iobroker.js setup first npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself. npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) + iobroker.js-controller@2.2.8 updated 1 package and audited 4821 packages in 35.829s 12 packages are looking for funding run `npm fund` for details found 57 vulnerabilities (40 low, 3 moderate, 14 high) run `npm audit fix` to fix them, or `npm audit` for details -
Viele Wege führen hier nach Rom.
Kommste mit iobroker start oder iobroker start admin.0 jetzt auf die Oberfläche?Ansonsten kannst du noch den Fixer laufen lassen oder clever wäre auch beim raspi ein
sudo apt update und dann ein
sudo apt full-upgrade
zu machen.
dann ist der raspberry erstmal auf dem neuesten stand. -
habe den rpi jetzt aktualisiert. port: 8081 funktioniert immer noch nicht.
Wie kann ich den Fixer laufen lassen?
-
curl -sL https://iobroker.net/fix.sh | bash -
