Kein Zugriff auf Admin per Web
-
Lass uns hier weitermachen. Keine Sorge wir haben alle klein angefangen und auch ich lerne jeden Tag noch viel dazu.
Auf was ich aus bin, sieht in Deiner Logdatei hoffentlich in etwa so aus (da startet der Admin nämlich):
`2018-07-26 18:41:53.727 - [32minfo[39m: host.ARBEITSZIMMER iobroker.js-controller version 1.5.0 js-controller starting 2018-07-26 18:41:53.731 - [32minfo[39m: host.ARBEITSZIMMER Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker 2018-07-26 18:41:53.732 - [32minfo[39m: host.ARBEITSZIMMER hostname: ARBEITSZIMMER, node: v8.11.1 2018-07-26 18:41:53.734 - [32minfo[39m: host.ARBEITSZIMMER ip addresses: fe80::10b3:228f:5b23:fa97 192.168.179.64 fe80::386a:874c:3959:9b57 169.254.155.87 2018-07-26 18:41:53.892 - [32minfo[39m: host.ARBEITSZIMMER inMem-states listening on port 9000 2018-07-26 18:41:54.037 - [32minfo[39m: host.ARBEITSZIMMER inMem-objects listening on port 9001 2018-07-26 18:41:54.045 - [32minfo[39m: host.ARBEITSZIMMER InMemoryDB connected 2018-07-26 18:41:54.055 - [32minfo[39m: host.ARBEITSZIMMER 57 instances found 2018-07-26 18:41:54.067 - [32minfo[39m: host.ARBEITSZIMMER starting 38 instances 2018-07-26 18:41:54.090 - [32minfo[39m: host.ARBEITSZIMMER instance system.adapter.admin.0 started with pid 34692 2018-07-26 18:41:55.182 - [32minfo[39m: admin.0 starting. Version 3.4.8 in C:/dev/iobroker/node_modules/iobroker.admin, node: v8.11.1 2018-07-26 18:41:55.203 - [32minfo[39m: admin.0 requesting all states 2018-07-26 18:41:55.204 - [32minfo[39m: admin.0 requesting all objects 2018-07-26 18:41:55.204 - [32minfo[39m: admin.0 Request actual repository... 2018-07-26 18:41:56.258 - [32minfo[39m: admin.0 received all objects 2018-07-26 18:41:56.263 - [33mwarn[39m: admin.0 No repository source configured 2018-07-26 18:41:56.279 - [32minfo[39m: host.ARBEITSZIMMER Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json" 2018-07-26 18:41:56.507 - [32minfo[39m: admin.0 received all states 2018-07-26 18:41:56.515 - [32minfo[39m: admin.0 http server listening on port 8081 2018-07-26 18:41:56.515 - [32minfo[39m: admin.0 Use link "http://localhost:8081" to configure. 2018-07-26 18:41:56.864 - [32minfo[39m: admin.0 Repository received successfully. 2018-07-26 18:41:58.074 - [32minfo[39m: host.ARBEITSZIMMER instance system.adapter.discovery.0 started with pid 13204 2018-07-26 18:41:58.641 - [32minfo[39m: discovery.0 starting. Version 1.1.1 in C:/dev/iobroker/node_modules/iobroker.discovery, node: v8.11.1 2018-07-26 18:42:02.072 - [32minfo[39m: host.ARBEITSZIMMER instance system.adapter.tr-064.0 started with pid 13948 2018-07-26 18:42:02.943 - [32minfo[39m: tr-064.0 starting. Version 0.4.18 in C:/dev/iobroker/node_modules/iobroker.tr-064, node: v8.11.1 2018-07-26 18:42:06.074 - [32minfo[39m: host.ARBEITSZIMMER instance system.adapter.history.0 started with pid 18500 2018-07-26 18:42:06.702 - [32minfo[39m: history.0 starting. Version 1.8.5 in C:/dev/iobroker/node_modules/iobroker.history, node: v8.11.1 2018-07-26 18:42:06.743 - [32minfo[39m: history.0 enabled logging of fritzdect.0.DECT200_087610075340.power (Count=1), Alias=false 2018-07-26 18:42:06.743 - [32minfo[39m: history.0 enabled logging of fritzdect.0.DECT200_087610075340.temp (Count=2), Alias=false[/code]` So zeigen hier die Zeilen `~~[code]~~admin.0 http server listening on port 8081 admin.0 Use link "http://localhost:8081" to configure. admin.0 Repository received successfully.[/code]` an, dass bis dahin mit dem Admin alles ok ist. Wenn dann keine weiteren Fehlermeldungen kommen, wäre das gut. Eine Fehlermeldung im Log (von was ganz anderm) sieht z.B. so aus: `~~[code]~~2018-07-20 15:46:09.636 - [31merror[39m: harmony.0 Error: Unhandled "error" event. (XMPP authentication failure) at Client.emit (events.js:186:19) at Client._handleAuthState (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-client\lib\Client.js:298:10) at Client._handleStanza (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-client\lib\Client.js:234:12) at Client.onStanza (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-client\lib\Client.js:222:8) at emitOne (events.js:116:13) at Connection.emit (events.js:211:7) at Connection.onStanza (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-core\lib\Connection.js:369:10) at StreamParser. <anonymous>(C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-core\lib\Connection.js:226:10) at emitOne (events.js:116:13) at StreamParser.emit (events.js:211:7) 2018-07-20 15:46:09.652 - [31merror[39m: Caught by controller[0]: { Error: Unhandled "error" event. (XMPP authentication failure) 2018-07-20 15:46:09.652 - [31merror[39m: Caught by controller[0]: at Client.emit (events.js:186:19) 2018-07-20 15:46:09.652 - [31merror[39m: Caught by controller[0]: at Client._handleAuthState (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-client\lib\Client.js:298:10) 2018-07-20 15:46:09.652 - [31merror[39m: Caught by controller[0]: at Client._handleStanza (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-client\lib\Client.js:234:12) 2018-07-20 15:46:09.652 - [31merror[39m: Caught by controller[0]: at Client.onStanza (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-client\lib\Client.js:222:8) 2018-07-20 15:46:09.652 - [31merror[39m: Caught by controller[0]: at emitOne (events.js:116:13) 2018-07-20 15:46:09.653 - [31merror[39m: Caught by controller[0]: at Connection.emit (events.js:211:7) 2018-07-20 15:46:09.653 - [31merror[39m: Caught by controller[0]: at Connection.onStanza (C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-core\lib\Connection.js:369:10) 2018-07-20 15:46:09.653 - [31merror[39m: Caught by controller[0]: at StreamParser. <anonymous>(C:\dev\iobroker\node_modules\iobroker.harmony\node_modules\node-xmpp-core\lib\Connection.js:226:10) 2018-07-20 15:46:09.653 - [31merror[39m: Caught by controller[0]: at emitOne (events.js:116:13) 2018-07-20 15:46:09.653 - [31merror[39m: Caught by controller[0]: at StreamParser.emit (events.js:211:7) context: 'XMPP authentication failure' }[/code]</anonymous></anonymous>` Wenn Du Dir unsicher bist, poste halt mal den Teil, den ich Dir hier gezeigt habe. Bitte in "code"-Tags -
Ich glaub ich bin zu blöd :-)
Per FileZilla hab ich mich auf den Rasperry eigewählt, bin dann unter /home/pi/.npm/_logs gegangen und finde da nur 7 Dateisätze aber da sieht nichts der gleichen aus wenn ich mir die angucke wie das was du gepostet hast.
Bin ich völlig verteilt und gehe einen komplett falschen weg oder versteh ich es einfach nur nicht????? Das was ich da rausgelesen hab, hab ich mal als Anhang mit gepostet
-
Schau nochmal das Posting weiter oben mit dem richtigen Pfad an: viewtopic.php?p=165259#p165021
-
Schau nochmal das Posting weiter oben mit dem richtigen Pfad an: viewtopic.php?p=165259#p165021 `
langsam wird peinlich ;)
pi@raspberrypi:~ $ /opt/iobroker/log/
-bash: /opt/iobroker/log/: Ist ein Verzeichnis
und mehr ist nicht zu sehen
-
Genau. /opt/iobroker/log ist ein Verzeichnis, in das Du mit
cd /opt/iobroker/logwechseln kannst.
Mit
ls -lakannst Du Dir die Dateien dann in diesem Ordner ansehen.
Oder Du nimmst Filezilla dafür, wie Du es vorher schon mit /home gemacht hast.
-
Jetzt hab ich es…...war per FileZilla ganz einfach, man muss nur auf den richtigen Pfad gestoßen werden [emoji6]
Hab die Datei dann im Editor geöffnet und nach Biobroker gesucht. Das einzige was ich gefunden habe ist dieses.
Sat Jul 21 2018 16:20:10 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 16:20:10 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 16:20:16 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 16:20:17 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:01:53 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:01:53 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:01:54 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:01:54 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:01:56 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:02:02 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:02:02 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:02:13 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:02:13 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:02:15 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:02:21 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:02:21 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:02:32 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:02:32 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:02:34 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:02:40 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:02:40 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:02:51 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:02:51 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:02:52 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:02:59 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:02:59 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:03:09 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:03:09 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:03:11 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:03:18 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:03:18 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:03:28 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:03:28 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:03:30 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:03:37 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:03:37 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:03:47 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:03:47 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:03:49 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:03:56 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:03:56 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:04:06 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:04:06 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:04:08 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:04:15 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:04:15 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:04:25 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:04:25 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:04:27 GMT+0200 (CEST)Daemon iobroker started Sat Jul 21 2018 17:04:34 GMT+0200 (CEST)Restarting iobroker... Sat Jul 21 2018 17:04:34 GMT+0200 (CEST)Stopping daemon iobroker... Sat Jul 21 2018 17:04:44 GMT+0200 (CEST)Cannot create "/opt/iobroker/node_modules/iobroker.js-controller/lib/../killall.sh" Sat Jul 21 2018 17:04:44 GMT+0200 (CEST)Starting daemon iobroker... Sat Jul 21 2018 17:04:44 GMT+0200 (CEST)Daemon iobroker startedNach einem Neustart heutemorgen hab ich dann das gefunden:
`2018-07-28 04:56:54.305 - [32minfo[39m: cloud.0 Trying to connect as system.user.admin 2018-07-28 04:57:54.332 - [32minfo[39m: cloud.0 Trying to connect as system.user.admin 2018-07-28 04:58:54.360 - [32minfo[39m: cloud.0 Trying to connect as system.user.admin 2018-07-28 05:32:55.185 - [32minfo[39m: cloud.0 Trying to connect as system.user.admin 2018-07-28 11:14:00.665 - [32minfo[39m: host.raspberrypi stopInstance system.adapter.admin.0 2018-07-28 11:14:00.665 - [33mwarn[39m: host.raspberrypi stopInstance system.adapter.admin.0 not running[/code]` ~~[color]~~Edit by eric2905, Code-Tags korrigiert [/color] -
Moin,
in der letzten Log-Zeile steht, das der Admin.0 nicht läuft.
Gehe mal in die Konsole (Putty, o.ä.) und gibt mal ein:
cd /opt/iobroker iobroker list instancesund poste das Ergebnis (in Code-Tags)
Wenn da auch zu sehen ist, das der Admin nicht läuft, gib mal
iobroker start admin.0ein und poste das Ergebnis.
Gruß,
Eric
-
Hallo,
wenn ich das richtig sehe ist der Admin hier auch eingeschaltet. Einen Zugriff auf das System hab ich trotzdem nicht.
pi@raspberrypi:/opt/iobroker $ iobroker list instances system.adapter.admin.0 : admin - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa.0 : alexa - enabled system.adapter.cloud.0 : cloud - enabled system.adapter.discovery.0 : discovery - enabled system.adapter.feiertage.0 : feiertage - enabled system.adapter.fritzdect.0 : fritzdect - enabled system.adapter.hs100.0 : hs100 - enabled system.adapter.hue.0 : hue - enabled, port: 80 system.adapter.javascript.1 : javascript - enabled system.adapter.landroid-s.0 : landroid-s - enabled system.adapter.node-red.0 : node-red - enabled, port: 1880 system.adapter.radar.0 : radar - enabled system.adapter.sonoff.0 : sonoff - enabled, port: 1883, bind: 0.0.0.0 system.adapter.tankerkoenig.0 : tankerkoenig - enabled system.adapter.telegram.0 : telegram - enabled, port: 8443, bind: 0.0.0.0 system.adapter.terminal.0 : terminal - enabled, port: 8088, bind: 0.0.0.0, run as: admin system.adapter.text2command.0 : text2command - enabled system.adapter.vis-bars.0 : vis-bars - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd - enabled system.adapter.vis-justgage.0 : vis-justgage - enabled system.adapter.vis-metro.0 : vis-metro - enabled system.adapter.vis-players.0 : vis-players - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather - enabled system.adapter.vis-weather.0 : vis-weather - enabled system.adapter.vis.0 : vis - enabled system.adapter.web.0 : web - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.yahka.0 : yahka - enabledund nach iobroker start admin.0 kommt das:
pi@raspberrypi:/opt/iobroker $ iobroker start admin.0 Adapter "admin.0" started. fs.js:549 return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode); ^ Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/../../../../iobroker-data/objects.json.bak' at Error (native) at Object.fs.openSync (fs.js:549:18) at Object.fs.writeFileSync (fs.js:1155:15) at saveConfig (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:1774:16) at ObjectsInMemServer.destroy (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2778:26) at processExit (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2746:45) at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:238:49 at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2276:17) at processImmediate [as _immediateCallback] (timers.js:371:17)
610
Online32.7k
Benutzer82.5k
Themen1.3m
Beiträge