[gelöst] Nach Update kein Zugriff auf Weboberfläche
-
Ja der broker ist gestartet.
Führt jedoch kein Funktion aus.
z.B. Sprachbefehl an Echo zur Steuerung des Lichtspi@raspberrypi:~ $ iobroker status iobroker is running on this host. Objects type: file States type: file pi@raspberrypi:~ $ iobroker start pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ iobroker list instances system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.denon.0 : denon : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.hm-rega.0 : hm-rega : raspberrypi - disabled system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - disabled, port: 0 system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - disabled, port: 0 system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - disabled, port: 0 system.adapter.info.0 : info : raspberrypi - disabled system.adapter.iot.0 : iot : raspberrypi - disabled system.adapter.ping.0 : ping : raspberrypi - disabled system.adapter.roomba.0 : roomba : raspberrypi - disabled system.adapter.web.0 : web : raspberrypi - disabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive pi@raspberrypi:/opt/iobroker $ -
@lexnared
Da läuft ja auch nix.iobroker start admin -
@thomas-braun said in Nach Update kein Zugriff auf Weboberfläche:
sudo apt update sudo apt dist-upgrade sudor rebootWenn danach der ioBroker nicht startet:
iobroker start adminMache ich!
Melde mich -
@thomas-braun said in Nach Update kein Zugriff auf Weboberfläche:
@lexnared
Da läuft ja auch nix.iobroker start adminJetzt habe ich das update bereits gestartet.
Kann nun etwas dauern -
@lexnared
Ja, da dürfte einiges in der Update-Pipeline gestaut gewesen sein.
Sowas bitte reglmäßiger machen. -
@thomas-braun said in Nach Update kein Zugriff auf Weboberfläche:
@lexnared
Da läuft ja auch nix.iobroker start adminBisher erfolglos.
Welche logdatei wird denn zur weiteren Diagnose benötigt?pi@raspberrypi:~ $ iobroker start admin pi@raspberrypi:~ $ iobroker list instances system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.denon.0 : denon : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - disabled system.adapter.hm-rega.0 : hm-rega : raspberrypi - disabled system.adapter.hm-rpc.0 : hm-rpc : raspberrypi - disabled, port: 0 system.adapter.hm-rpc.1 : hm-rpc : raspberrypi - disabled, port: 0 system.adapter.hm-rpc.2 : hm-rpc : raspberrypi - disabled, port: 0 system.adapter.info.0 : info : raspberrypi - disabled system.adapter.iot.0 : iot : raspberrypi - disabled system.adapter.ping.0 : ping : raspberrypi - disabled system.adapter.roomba.0 : roomba : raspberrypi - disabled system.adapter.web.0 : web : raspberrypi - disabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive -
@lexnared
In einem zweiten Fenster:tail -f /opt/iobroker/log/iobroker.current.logUnd im anderen Fenster:
iobroker restart iobroker start admin -
-
@lexnared sagte in Nach Update kein Zugriff auf Weboberfläche:
error: admin.0 (2160) Cannot create webserver: TypeError: Cannot read property 'domains' of undefined
Das erklärt, dass die admin Oberfläche nicht erreichbar ist. Vielleicht einfach mal stumpf nochmal drauf knallen:
iobroker del admin iobroker add admin -
@thomas-braun
gesagt und getan.Dennoch kein erfolg
pi@raspberrypi:~ $ tail -f /opt/iobroker/log/iobroker.current.log 2021-02-26 14:25:56.848 - info: host.raspberrypi added notifications configuration of host 2021-02-26 14:25:57.520 - info: host.raspberrypi 12 instances found 2021-02-26 14:25:57.586 - info: host.raspberrypi starting 1 instance 2021-02-26 14:25:57.714 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 2532 2021-02-26 14:26:01.461 - info: admin.0 (2532) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.16.0, js-controller: 3.2.16 2021-02-26 14:26:01.545 - info: admin.0 (2532) requesting all states 2021-02-26 14:26:01.547 - info: admin.0 (2532) requesting all objects 2021-02-26 14:26:03.373 - info: admin.0 (2532) received all objects 2021-02-26 14:26:03.765 - info: admin.0 (2532) http server listening on port 8081 2021-02-26 14:26:03.767 - info: admin.0 (2532) Use link "http://localhost:8081" to configure. 2021-02-26 14:26:43.418 - info: admin.0 (2532) terminating http server on port 8081 2021-02-26 14:26:43.412 - info: host.raspberrypi received SIGTERM 2021-02-26 14:26:43.434 - info: host.raspberrypi stopInstance system.adapter.discovery.0 (force=false, process=false) 2021-02-26 14:26:43.436 - info: host.raspberrypi stopInstance system.adapter.info.0 (force=false, process=false) 2021-02-26 14:26:43.437 - info: host.raspberrypi stopInstance system.adapter.iot.0 (force=false, process=false) 2021-02-26 14:26:43.438 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.0 (force=false, process=false) 2021-02-26 14:26:43.440 - info: host.raspberrypi stopInstance system.adapter.hm-rega.0 (force=false, process=false) 2021-02-26 14:26:43.441 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.1 (force=false, process=false) 2021-02-26 14:26:43.442 - info: host.raspberrypi stopInstance system.adapter.hm-rpc.2 (force=false, process=false) 2021-02-26 14:26:43.443 - info: host.raspberrypi stopInstance system.adapter.ping.0 (force=false, process=false) 2021-02-26 14:26:43.444 - info: host.raspberrypi stopInstance system.adapter.web.0 (force=false, process=false) 2021-02-26 14:26:43.445 - info: host.raspberrypi stopInstance system.adapter.roomba.0 (force=false, process=false) 2021-02-26 14:26:43.449 - info: host.raspberrypi stopInstance system.adapter.denon.0 (force=false, process=false) 2021-02-26 14:26:43.451 - info: host.raspberrypi stopInstance system.adapter.admin.0 (force=false, process=true) 2021-02-26 14:26:43.471 - info: admin.0 (2532) Got terminate signal TERMINATE_YOURSELF 2021-02-26 14:26:43.475 - info: host.raspberrypi stopInstance system.adapter.admin.0 send kill signal 2021-02-26 14:26:43.480 - info: admin.0 (2532) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2021-02-26 14:26:44.120 - info: host.raspberrypi instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP) 2021-02-26 14:26:44.122 - info: host.raspberrypi All instances are stopped. 2021-02-26 14:26:44.329 - info: host.raspberrypi terminated 2021-02-26 14:26:47.370 - info: host.raspberrypi iobroker.js-controller version 3.2.16 js-controller starting 2021-02-26 14:26:47.380 - info: host.raspberrypi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker 2021-02-26 14:26:47.381 - info: host.raspberrypi hostname: raspberrypi, node: v14.16.0 2021-02-26 14:26:47.382 - info: host.raspberrypi ip addresses: 192.168.1.30 fe80::b60a:44f4:fdbf:dc08 2021-02-26 14:26:48.150 - info: host.raspberrypi connected to Objects and States 2021-02-26 14:26:48.225 - info: host.raspberrypi added notifications configuration of host 2021-02-26 14:26:48.958 - info: host.raspberrypi 12 instances found 2021-02-26 14:26:49.023 - info: host.raspberrypi starting 1 instance 2021-02-26 14:26:49.150 - info: host.raspberrypi instance system.adapter.admin.0 started with pid 2591 2021-02-26 14:26:52.787 - info: admin.0 (2591) starting. Version 4.2.1 in /opt/iobroker/node_modules/iobroker.admin, node: v14.16.0, js-controller: 3.2.16 2021-02-26 14:26:52.869 - info: admin.0 (2591) requesting all states 2021-02-26 14:26:52.871 - info: admin.0 (2591) requesting all objects 2021-02-26 14:26:54.665 - info: admin.0 (2591) received all objects 2021-02-26 14:26:54.920 - info: admin.0 (2591) http server listening on port 8081 2021-02-26 14:26:54.922 - info: admin.0 (2591) Use link "http://localhost:8081" to configure. -
Fehler gefunden.
Was ich schon einige male versucht hatte...:!
Das https:// durch http:// ersetzt -
@lexnared
Steht doch auch da:Use link "http://localhost:8081" to configure. -
@thomas-braun
ja habe ich auch gelesen.
Muss anscheinend etwas falsch gemacht haben.
Vorhin bin ich jedenfalls nicht auf die Weboberflache gekommen.Vielen Dank für eure schnelle Hilfe!
