Nach Admin Update startet Admin als nicht mehr automatisch

wendy2702

Ist das nur ein logfile vom reboot oder hast du da zwischendurch versucht iobroker zu starten?

Diese Einträge deuten darauf hin das Prozesse bereits laufen:

2018-06-13 09:29:08.578  - error: hm-rega.0 already running
2018-06-13 09:29:08.718  - error: host.lemaker instance system.adapter.scenes.0 terminated with code 7 (Adapter already running)

2018-06-13 09:29:09.727  - error: host.lemaker instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)

Und das System versucht die nochmal zu starten… was nach einem reboot des Rechners eigentlich recht ungewöhnlich ist.

Wirklich nur den Admin upgedated?

Kannst du wenn du einen reboot gemacht hast und der Meinung bist das dein Rechner mit iobroker wieder fertig sein sollte mal das abfragen:

iobroker list instances

holgerwolf

Beides Mal gleich Ausgabe:

Nach Reboot:
system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.amazon-dash.0           : amazon-dash -  enabled
system.adapter.ble.0                   : ble         -  enabled
system.adapter.cloud.0                 : cloud       - disabled
system.adapter.dwd.0                   : dwd         -  enabled
system.adapter.flot.0                  : flot        -  enabled
system.adapter.history.0               : history     -  enabled
system.adapter.hm-rega.0               : hm-rega     -  enabled
system.adapter.hm-rpc.0                : hm-rpc      -  enabled, port: 0
system.adapter.hm-rpc.1                : hm-rpc      -  enabled, port: 0
system.adapter.hm-rpc.2                : hm-rpc      -  enabled, port: 0
system.adapter.icons-mfd-png.0         : icons-mfd-png -  enabled
system.adapter.icons-mfd-svg.0         : icons-mfd-svg -  enabled
system.adapter.javascript.0            : javascript  -  enabled
system.adapter.nanoleaf-lightpanels.0  : nanoleaf-lightpanels - disabled, port: 16021
system.adapter.parser.0                : parser      - disabled
system.adapter.ping.0                  : ping        - disabled
system.adapter.scenes.0                : scenes      -  enabled
system.adapter.simple-api.0            : simple-api  -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
system.adapter.socketio.0              : socketio    -  enabled, port: 8084, bind: 0.0.0.0, run as: admin
system.adapter.sql.0                   : sql         -  enabled, port: 0
system.adapter.sql.1                   : sql         - disabled, port: 3306
system.adapter.squeezebox.0            : squeezebox  - disabled, port: 9090
system.adapter.telegram.0              : telegram    -  enabled, port: 8443, bind: 0.0.0.0
system.adapter.vis-history.0           : vis-history -  enabled
system.adapter.vis-hqwidgets.0         : vis-hqwidgets -  enabled
system.adapter.vis-jqui-mfd.0          : vis-jqui-mfd -  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

Nach sudo iobroker stop - sudo iobroker start
system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.amazon-dash.0           : amazon-dash -  enabled
system.adapter.ble.0                   : ble         -  enabled
system.adapter.cloud.0                 : cloud       - disabled
system.adapter.dwd.0                   : dwd         -  enabled
system.adapter.flot.0                  : flot        -  enabled
system.adapter.history.0               : history     -  enabled
system.adapter.hm-rega.0               : hm-rega     -  enabled
system.adapter.hm-rpc.0                : hm-rpc      -  enabled, port: 0
system.adapter.hm-rpc.1                : hm-rpc      -  enabled, port: 0
system.adapter.hm-rpc.2                : hm-rpc      -  enabled, port: 0
system.adapter.icons-mfd-png.0         : icons-mfd-png -  enabled
system.adapter.icons-mfd-svg.0         : icons-mfd-svg -  enabled
system.adapter.javascript.0            : javascript  -  enabled
system.adapter.nanoleaf-lightpanels.0  : nanoleaf-lightpanels - disabled, port: 16021
system.adapter.parser.0                : parser      - disabled
system.adapter.ping.0                  : ping        - disabled
system.adapter.scenes.0                : scenes      -  enabled
system.adapter.simple-api.0            : simple-api  -  enabled, port: 8087, bind: 0.0.0.0, run as: admin
system.adapter.socketio.0              : socketio    -  enabled, port: 8084, bind: 0.0.0.0, run as: admin
system.adapter.sql.0                   : sql         -  enabled, port: 0
system.adapter.sql.1                   : sql         - disabled, port: 3306
system.adapter.squeezebox.0            : squeezebox  - disabled, port: 9090
system.adapter.telegram.0              : telegram    -  enabled, port: 8443, bind: 0.0.0.0
system.adapter.vis-history.0           : vis-history -  enabled
system.adapter.vis-hqwidgets.0         : vis-hqwidgets -  enabled
system.adapter.vis-jqui-mfd.0          : vis-jqui-mfd -  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

Nur Admin geupdatet stimmt nicht ganz ;-)

Den Controller habe ich auch geupdatet und zweiten iobroker im im Multihost Betrieb dazugenommen. Wann genau der Fehler kam, weiß ich nicht mehr. Nach nem Update habe ich nicht immer rebootet sondern wohl auch oft nur den iobroker neu gestartet.

Gruß

Holger

wendy2702

Also nach reboot läuft der Admin doch:

system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

Und du kommst dann trotzdem nicht auf die Admin Seite oder wie genau äußert sich dein Fehler?

holgerwolf

~~@wendy2702:~~

Also nach reboot läuft der Admin doch:
system.adapter.admin.0                 : admin       -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
Und du kommst dann trotzdem nicht auf die Admin Seite oder wie genau äußert sich dein Fehler? `

Genau, ich komme nicht auf die Webseite vom Admin. Vis geht.

Gruß

Holger

eric2905

Poste bitte mal einen Screenshot der Fehlermeldung im Browser, wenn Du nicht auf den Admin kommst.

Gruß,

Eric

Von unterwegs getippert

holgerwolf

~~@eric2905:~~

Poste bitte mal einen Screenshot der Fehlermeldung im Browser, wenn Du nicht auf den Admin kommst.

Gruß,

Eric

Von unterwegs getippert `

Bitteschön, einmal aus Firefox und einmal mit Chrome.

Vis geht auf beiden.

Gruß

Holger
531_chrome.jpeg
531_firefox.jpeg

wendy2702

Und wenn du jetzt (obwohl scheinbar alles läuft außer Admin Web Seite) iobroker start machst, danach geht direkt die WebSeite?

Wenn das so ist, kannst iobroker start machen und das komplette logfile davon posten was also in der Konsole kommt.

Wie hast du den Multihost eingerichtet? Wird der Slave im Master denn erkannt?

Die ".63" IP ist aber die Adresse von deinem Master !?

holgerwolf

~~@wendy2702:~~

Und wenn du jetzt (obwohl scheinbar alles läuft außer Admin Web Seite) iobroker start machst, danach geht direkt die WebSeite? `
Ohne den iobroker zu stoppen geht das nicht direkt (already running bzw failed to write…)

Nach dem Stoppen kann ich den iobroker wieder starten.

Dann läuft auch die Webseite vom Admin...

~~@wendy2702:~~

Wenn das so ist, kannst iobroker start machen und das komplette logfile davon posten was also in der Konsole kommt. `

… dann kann ich da auch das log sehen und abspeichern:

2018-06-13 14:11:32.912 - info: host.lemaker iobroker.js-controller version 1.4.2 js-controller starting
2018-06-13 14:11:32.946 - info: host.lemaker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
2018-06-13 14:11:32.950 - info: host.lemaker hostname: lemaker, node: v6.14.1
2018-06-13 14:11:32.955 - info: host.lemaker ip addresses: 192.168.178.63 fe80::d9:5ff:fe01:28ab
2018-06-13 14:11:33.363 - info: host.lemaker inMem-states listening on port 9000
2018-06-13 14:11:34.356 - info: host.lemaker inMem-objects listening on port 9001
2018-06-13 14:11:34.417 - info: host.lemaker InMemoryDB connected
2018-06-13 14:11:34.451 - warn: Host on this system is not possible, because IP address is for states is 0.0.0.0
2018-06-13 14:11:34.524 - info: host.lemaker 31 instances found
2018-06-13 14:11:34.662 - info: host.lemaker starting 21 instances
2018-06-13 14:11:34.686 - warn: host.lemaker startInstance cannot find adapter "nanoleaf-lightpanels". Try to install it... 1 attempt
2018-06-13 14:11:34.687 - info: iobroker install nanoleaf-lightpanels
2018-06-13 14:11:34.921 - info: host.lemaker instance system.adapter.admin.0 started with pid 1987
2018-06-13 14:11:35.238 - warn: host.lemaker multihost service started on 0.0.0.0:50005
2018-06-13 14:11:39.227 - info: host.lemaker instance system.adapter.hm-rpc.0 started with pid 1994
2018-06-13 14:11:44.044 - info: host.lemaker instance system.adapter.hm-rega.0 started with pid 2001
2018-06-13 14:11:46.801 - info: host.lemaker instance system.adapter.sql.0 started with pid 2020
2018-06-13 14:11:46.622 - info: admin.0 starting. Version 3.4.3 in /opt/iobroker/node_modules/iobroker.admin, node: v6.14.1
2018-06-13 14:11:46.933 - info: admin.0 requesting all states
2018-06-13 14:11:46.583 - info: hm-rpc.0 starting. Version 1.6.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.1
2018-06-13 14:11:47.009 - info: admin.0 requesting all objects
2018-06-13 14:11:47.047 - info: admin.0 Request actual repository...
2018-06-13 14:11:51.693 - error: iobroker host.lemaker Unknown packetName nanoleaf-lightpanels
2018-06-13 14:11:51.735 - info: iobroker exit 5
2018-06-13 14:11:51.801 - info: host.lemaker instance system.adapter.history.0 started with pid 2027
2018-06-13 14:11:53.546 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.178.63:2001
2018-06-13 14:11:53.569 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.178.83:2001 with ["xmlrpc_bin://192.168.178.63:2001","hm-rpc.0"]
2018-06-13 14:11:53.875 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
2018-06-13 14:11:54.075 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
2018-06-13 14:11:54.412 - info: hm-rpc.0 binrpc -> 223 devices
2018-06-13 14:11:54.982 - info: host.lemaker instance system.adapter.web.0 started with pid 2034
2018-06-13 14:11:55.994 - info: admin.0 received all states
2018-06-13 14:11:57.279 - info: hm-rpc.0 Connected
2018-06-13 14:11:59.248 - info: host.lemaker instance scheduled system.adapter.dwd.0 */15 * * * *
2018-06-13 14:11:59.371 - info: host.lemaker instance system.adapter.dwd.0 started with pid 2045
2018-06-13 14:12:03.009 - info: host.lemaker instance system.adapter.javascript.0 started with pid 2052
2018-06-13 14:11:55.865 - info: hm-rega.0 starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.hm-rega, node: v6.14.1
2018-06-13 14:11:56.133 - info: hm-rega.0 subscribe hm-rpc.0.BidCoS-RF.50.PRESS_SHORT
2018-06-13 14:12:06.310 - info: hm-rega.0 ReGaHSS 192.168.178.83 up
2018-06-13 14:12:06.891 - info: hm-rega.0 time difference local-ccu 1s
2018-06-13 14:12:07.224 - info: host.lemaker instance system.adapter.scenes.0 started with pid 2063
2018-06-13 14:12:07.742 - info: hm-rega.0 added/updated 7 favorites to enum.favorites
2018-06-13 14:12:04.098 - info: sql.0 starting. Version 1.8.0 in /opt/iobroker/node_modules/iobroker.sql, node: v6.14.1
2018-06-13 14:12:08.095 - info: hm-rega.0 added/updated functions to enum.functions
2018-06-13 14:12:08.758 - info: hm-rega.0 added/updated rooms to enum.rooms
2018-06-13 14:12:08.180 - info: history.0 starting. Version 1.7.4 in /opt/iobroker/node_modules/iobroker.history, node: v6.14.1
2018-06-13 14:12:09.156 - info: sql.0 enabled logging of hm-rega.0.4154
2018-06-13 14:12:09.227 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.BRIGHTNESS
2018-06-13 14:12:09.230 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.HUMIDITY
2018-06-13 14:12:09.233 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.RAINING
2018-06-13 14:12:09.235 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.RAIN_COUNTER
2018-06-13 14:12:09.279 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.SUNSHINEDURATION
2018-06-13 14:12:09.280 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.TEMPERATURE
2018-06-13 14:12:09.282 - info: sql.0 enabled logging of hm-rpc.0.HEQ0118211.1.WIND_SPEED
2018-06-13 14:12:09.283 - info: sql.0 enabled logging of hm-rpc.0.HEQ0406280.1.MOTION
2018-06-13 14:12:09.285 - info: sql.0 enabled logging of hm-rpc.0.JEQ0148365.1.OPEN
2018-06-13 14:12:09.317 - info: sql.0 enabled logging of hm-rpc.0.JEQ0148365.1.STATE
2018-06-13 14:12:09.332 - info: sql.0 enabled logging of ping.0.lemaker.192_168_178_75
2018-06-13 14:12:09.334 - info: sql.0 enabled logging of hm-rpc.0.LEQ1344755.1.STATE
2018-06-13 14:12:09.335 - info: sql.0 enabled logging of hm-rpc.0.LEQ1344755.2.ENERGY_COUNTER
2018-06-13 14:12:09.347 - info: sql.0 enabled logging of hm-rpc.0.LEQ1344755.2.POWER
2018-06-13 14:12:09.348 - info: sql.0 enabled logging of hm-rpc.0.LEQ1344755.3.DECISION_VALUE
2018-06-13 14:12:09.350 - info: sql.0 enabled logging of hm-rega.0.15272
2018-06-13 14:12:09.353 - info: sql.0 enabled logging of hm-rpc.2.000E5709A11F9A.1.HUMIDITY
2018-06-13 14:12:09.355 - info: sql.0 enabled logging of hm-rpc.2.000E5709A11F9A.1.ACTUAL_TEMPERATURE
2018-06-13 14:12:09.385 - info: sql.0 enabled logging of hm-rpc.2.000E5709A11C71.1.HUMIDITY
2018-06-13 14:12:09.387 - info: sql.0 enabled logging of hm-rpc.2.000E5709A11C71.1.ACTUAL_TEMPERATURE
2018-06-13 14:12:09.407 - info: sql.0 enabled logging of ble.0.c4:7c:8d:66:43:31.fertility
2018-06-13 14:12:09.411 - info: sql.0 enabled logging of ble.0.c4:7c:8d:66:43:31.temperature
2018-06-13 14:12:09.413 - info: sql.0 enabled logging of ble.0.c4:7c:8d:66:43:31.illuminance
2018-06-13 14:12:09.414 - info: sql.0 enabled logging of ble.0.c4:7c:8d:66:43:31.moisture
2018-06-13 14:12:10.269 - info: sql.0 Connected to mysql
2018-06-13 14:12:10.850 - info: host.lemaker instance system.adapter.amazon-dash.0 started with pid 2073
2018-06-13 14:12:12.861 - info: admin.0 received all objects
2018-06-13 14:12:16.065 - info: host.lemaker instance system.adapter.telegram.0 started with pid 2080
2018-06-13 14:12:17.411 - info: hm-rega.0 got 57 programs
2018-06-13 14:12:18.980 - info: host.lemaker instance system.adapter.simple-api.0 started with pid 2087
2018-06-13 14:12:16.852 - info: admin.0 http server listening on port 8081
2018-06-13 14:12:16.854 - info: admin.0 Use link "http://localhost:8081" to configure.
2018-06-13 14:12:19.480 - info: hm-rega.0 added/updated 57 programs
2018-06-13 14:12:19.507 - info: hm-rega.0 deleted 0 programs
2018-06-13 14:12:25.635 - info: host.lemaker instance system.adapter.socketio.0 started with pid 2094
2018-06-13 14:12:26.969 - error: dwd.0 no connection to objects DB
2018-06-13 14:12:27.361 - error: scenes.0 no connection to objects DB
2018-06-13 14:12:29.798 - error: amazon-dash.0 no connection to objects DB
2018-06-13 14:12:32.545 - info: host.lemaker Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
2018-06-13 14:12:36.574 - error: simple-api.0 no connection to objects DB
2018-06-13 14:12:37.289 - info: host.lemaker instance system.adapter.hm-rpc.1 started with pid 2119
2018-06-13 14:12:39.070 - info: host.lemaker instance system.adapter.hm-rpc.2 started with pid 2125
2018-06-13 14:12:41.474 - info: hm-rega.0 got 69 variables
2018-06-13 14:12:42.153 - warn: admin.0 Reconnection to DB.
2018-06-13 14:12:42.293 - warn: admin.0 Reconnection to DB.
2018-06-13 14:12:42.767 - info: hm-rega.0 added/updated 69 variables
2018-06-13 14:12:42.769 - info: hm-rega.0 deleted 0 variables
2018-06-13 14:12:42.773 - info: hm-rega.0 request state values
2018-06-13 14:12:45.269 - error: javascript.0 no connection to objects DB
2018-06-13 14:12:45.489 - error: socketio.0 no connection to objects DB
2018-06-13 14:12:47.188 - info: hm-rega.0 got state values
2018-06-13 14:12:47.267 - error: telegram.0 no connection to objects DB
2018-06-13 14:12:48.800 - error: scenes.0 no connection to states DB: Connection timeout
2018-06-13 14:12:48.835 - warn: history.0 Reconnection to DB.
2018-06-13 14:12:48.901 - error: amazon-dash.0 no connection to states DB: Connection timeout
2018-06-13 14:12:48.952 - warn: history.0 Reconnection to DB.
2018-06-13 14:12:49.041 - error: simple-api.0 no connection to states DB: Connection timeout
2018-06-13 14:12:49.162 - info: sql.0 enabled logging of hm-rega.0.4154
2018-06-13 14:12:49.168 - info: sql.0 disabled logging of hm-rega.0.4185
2018-06-13 14:12:49.194 - info: sql.0 disabled logging of hm-rega.0.4186
2018-06-13 14:12:49.200 - info: sql.0 enabled logging of hm-rega.0.15272
2018-06-13 14:12:55.281 - error: socketio.0 no connection to states DB: Connection timeout
2018-06-13 14:12:55.304 - error: hm-rpc.1 no connection to objects DB
2018-06-13 14:12:55.939 - warn: hm-rpc.0 Reconnection to DB.
2018-06-13 14:12:55.953 - warn: hm-rpc.0 Reconnection to DB.
2018-06-13 14:12:57.141 - error: hm-rpc.2 no connection to objects DB
2018-06-13 14:12:57.207 - error: vis.0 no connection to objects DB
2018-06-13 14:13:00.182 - error: hm-rpc.0 already running
2018-06-13 14:13:00.933 - warn: hm-rega.0 Reconnection to DB.
2018-06-13 14:13:00.953 - warn: hm-rega.0 Reconnection to DB.
2018-06-13 14:13:01.475 - error: host.lemaker instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
2018-06-13 14:13:01.613 - info: amazon-dash.0 starting. Version 0.2.9 in /opt/iobroker/node_modules/iobroker.amazon-dash, node: v6.14.1
2018-06-13 14:13:01.479 - info: host.lemaker Restart adapter system.adapter.hm-rpc.0 because enabled
2018-06-13 14:13:01.654 - info: amazon-dash.0 starting pcap session on default interface
2018-06-13 14:13:03.536 - info: scenes.0 starting. Version 1.1.0 in /opt/iobroker/node_modules/iobroker.scenes, node: v6.14.1
2018-06-13 14:13:03.679 - info: simple-api.0 starting. Version 1.6.3 in /opt/iobroker/node_modules/iobroker.simple-api, node: v6.14.1
2018-06-13 14:13:03.794 - info: simple-api.0 simpleAPI server listening on port 8087
2018-06-13 14:13:03.820 - info: simple-api.0 Allow states only when user is owner: false
2018-06-13 14:13:03.842 - info: simple-api.0 http server listening on port 8087
2018-06-13 14:13:04.329 - info: socketio.0 starting. Version 2.1.0 in /opt/iobroker/node_modules/iobroker.socketio, node: v6.14.1
2018-06-13 14:13:04.543 - info: socketio.0 socket.io server listening on port 8084
2018-06-13 14:13:05.488 - info: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.14.1
2018-06-13 14:13:05.039 - info: web.0 starting. Version 2.3.4 in /opt/iobroker/node_modules/iobroker.web, node: v6.14.1
2018-06-13 14:13:05.616 - info: web.0 starting. Version 2.3.4 in /opt/iobroker/node_modules/iobroker.web, node: v6.14.1
2018-06-13 14:13:05.633 - info: javascript.0 requesting all states
2018-06-13 14:13:05.668 - info: javascript.0 requesting all objects
2018-06-13 14:13:08.191 - info: hm-rpc.2 starting. Version 1.6.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.1
2018-06-13 14:13:09.427 - info: vis.0 starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.vis, node: v6.14.1
2018-06-13 14:13:09.555 - info: hm-rpc.1 starting. Version 1.6.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.1
2018-06-13 14:13:10.346 - info: admin.0 Repository received successfully.
2018-06-13 14:13:10.392 - info: vis.0 vis license is OK.
2018-06-13 14:13:12.789 - info: telegram.0 starting. Version 1.2.4 in /opt/iobroker/node_modules/iobroker.telegram, node: v6.14.1
2018-06-13 14:13:12.916 - info: hm-rpc.2 xmlrpc server is trying to listen on 192.168.178.63:2010
2018-06-13 14:13:13.119 - info: dwd.0 starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v6.14.1
2018-06-13 14:13:12.938 - info: hm-rpc.2 xmlrpc client is trying to connect to 192.168.178.83:2010 with ["http://192.168.178.63:2010","hm-rpc.2"]
2018-06-13 14:13:13.467 - info: hm-rpc.2 Connected
2018-06-13 14:13:13.648 - info: hm-rpc.2 xmlrpc <- listDevices ["hm-rpc.2"]
2018-06-13 14:13:13.757 - info: web.0 socket.io server listening on port 8082
2018-06-13 14:13:13.785 - info: web.0 http server listening on port 8082
2018-06-13 14:13:14.110 - info: web.0 socket.io server listening on port 8082
2018-06-13 14:13:14.248 - error: web.0 port 8082 already in use
2018-06-13 14:13:14.494 - info: telegram.0 getMe: {"id":266475642,"is_bot":true,"first_name":"iobroker-hw","username":"ioHWbot"}
2018-06-13 14:13:14.771 - warn: admin.0 Reconnection to DB.
2018-06-13 14:13:14.852 - warn: sql.0 Reconnection to DB.
2018-06-13 14:13:14.784 - warn: admin.0 Reconnection to DB.
2018-06-13 14:13:14.908 - warn: sql.0 Reconnection to DB.
2018-06-13 14:13:15.104 - error: host.lemaker instance system.adapter.web.0 terminated with code 1 ()
2018-06-13 14:13:15.107 - info: host.lemaker Restart adapter system.adapter.web.0 because enabled
2018-06-13 14:13:15.224 - info: hm-rpc.2 xmlrpc -> 0 devices
2018-06-13 14:13:15.301 - info: hm-rpc.1 binrpc server is trying to listen on 192.168.178.63:8701
2018-06-13 14:13:15.305 - info: hm-rpc.1 binrpc client is trying to connect to 192.168.178.83:8701 with ["xmlrpc_bin://192.168.178.63:8701","hm-rpc.1"]
2018-06-13 14:13:15.954 - info: javascript.0 received all states
2018-06-13 14:13:18.108 - info: host.lemaker instance system.adapter.dwd.0 terminated with code 0 (OK)
2018-06-13 14:13:18.159 - info: hm-rpc.2 xmlrpc <- newDevices 38
2018-06-13 14:13:18.219 - info: hm-rpc.2 new HmIP devices/channels after filter: 0
2018-06-13 14:13:18.704 - info: host.lemaker instance system.adapter.vis.0 terminated while should be started once
2018-06-13 14:13:19.102 - info: hm-rpc.1 binrpc -> listDevices 59
2018-06-13 14:13:19.178 - info: hm-rpc.1 new CUxD devices/channels after filter: 0
2018-06-13 14:13:19.212 - info: hm-rpc.1 Connected
2018-06-13 14:13:21.870 - info: javascript.0 received all objects
2018-06-13 14:13:22.146 - info: javascript.0 Start javascript script.js.common.DWD_Anzeige
2018-06-13 14:13:22.224 - info: javascript.0 script.js.common.DWD_Anzeige: registered 1 subscription and 0 schedules
2018-06-13 14:13:22.232 - info: javascript.0 Start javascript script.js.common.Dash-Kuechenlicht
2018-06-13 14:13:22.256 - info: javascript.0 script.js.common.Dash-Kuechenlicht: subscribe: {"pattern":{"id":"amazon-dash.0.ac-63-be-5e-aa-7d.switch","change":"ne"},"name":"script.js.common.Dash-Kuechenlicht"}
2018-06-13 14:13:22.260 - info: javascript.0 script.js.common.Dash-Kuechenlicht: registered 1 subscription and 0 schedules
2018-06-13 14:13:22.262 - info: javascript.0 Start javascript script.js.common.Feuchte_UV_OG
2018-06-13 14:13:22.274 - info: javascript.0 script.js.common.Feuchte_UV_OG: subscribe: {"pattern":{"id":"hm-rpc.2.000E5709A11F9A.1.HUMIDITY","change":"ne"},"name":"script.js.common.Feuchte_UV_OG"}
2018-06-13 14:13:22.277 - info: javascript.0 script.js.common.Feuchte_UV_OG: registered 1 subscription and 0 schedules
2018-06-13 14:13:22.279 - info: javascript.0 Start javascript script.js.common.Feuchte_UV_EG
2018-06-13 14:13:22.290 - info: javascript.0 script.js.common.Feuchte_UV_EG: subscribe: {"pattern":{"id":"hm-rpc.2.000E5709A11C71.1.HUMIDITY","change":"ne"},"name":"script.js.common.Feuchte_UV_EG"}
2018-06-13 14:13:22.292 - info: javascript.0 script.js.common.Feuchte_UV_EG: registered 1 subscription and 0 schedules
2018-06-13 14:13:31.526 - info: host.lemaker instance system.adapter.hm-rpc.0 started with pid 2176
2018-06-13 14:13:36.831 - info: hm-rpc.0 starting. Version 1.6.2 in /opt/iobroker/node_modules/iobroker.hm-rpc, node: v6.14.1
2018-06-13 14:13:38.167 - info: hm-rpc.0 binrpc server is trying to listen on 192.168.178.63:2001
2018-06-13 14:13:38.177 - info: hm-rpc.0 binrpc client is trying to connect to 192.168.178.83:2001 with ["xmlrpc_bin://192.168.178.63:2001","hm-rpc.0"]
2018-06-13 14:13:38.387 - info: hm-rpc.0 binrpc <- system.listMethods ["hm-rpc.0"]
2018-06-13 14:13:38.477 - info: hm-rpc.0 binrpc <- listDevices ["hm-rpc.0"]
2018-06-13 14:13:38.667 - info: hm-rpc.0 binrpc -> 223 devices
2018-06-13 14:13:39.565 - info: hm-rpc.0 Connected
2018-06-13 14:13:45.148 - info: host.lemaker instance system.adapter.web.0 started with pid 2188
2018-06-13 14:13:49.879 - info: web.0 starting. Version 2.3.4 in /opt/iobroker/node_modules/iobroker.web, node: v6.14.1
2018-06-13 14:13:51.452 - info: web.0 socket.io server listening on port 8082
2018-06-13 14:13:51.495 - info: web.0 http server listening on port 8082
2018-06-13 14:13:52.681 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:13:52.742 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:13:53.229 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:13:53.343 - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:13:57.237 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:13:57.740 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:13:59.041 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:14:02.950 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:14:06.368 - info: web.0 ==>Connected system.user.admin from ::ffff:192.168.178.110
2018-06-13 14:15:00.346 - info: host.lemaker instance system.adapter.dwd.0 started with pid 2227
2018-06-13 14:15:08.378 - info: dwd.0 starting. Version 2.2.2 in /opt/iobroker/node_modules/iobroker.dwd, node: v6.14.1
2018-06-13 14:15:10.453 - info: host.lemaker instance system.adapter.dwd.0 terminated with code 0 (OK)
2018-06-13 14:15:18.372 - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.178.110 vis.0
2018-06-13 14:15:24.030 - info: web.0 <==Disconnect system.user.admin from ::ffff:192.168.178.110

~~@wendy2702:~~

Wie hast du den Multihost eingerichtet? Wird der Slave im Master denn erkannt? `

Mit der "manuelle" Methode:

http://www.iobroker.net/docu/?page_id=3068&lang=de

Bei der ganzen unten beschriebenen Methode wollte sich der Host nicht verbinden.

Ich sehe den SlaveHost im Admin. Da werden nur über den BLE Adapter Daten empfangen und dann im MasterHost über den SQL-Adapter geloggt.

Das geht prima und auch wenn ich nicht auf die Admin Seite komme.

~~@wendy2702:~~

Die ".63" IP ist aber die Adresse von deinem Master !? `

Ja, .63 ist die Adresse des Masters (historisch gewachsen ;-)

Gruß

Holger

wendy2702

Hm,

möglich das etwas bei der Multihost config falsch gelaufen ist !?

warn: Host on this system is not possible, because IP address is for states is 0.0.0.0

Kommst du nach reboot so auf die Admin Seite:

http://localhost:8081

holgerwolf

~~@wendy2702:~~

Hm,

möglich das etwas bei der Multihost config falsch gelaufen ist !?
warn: Host on this system is not possible, because IP address is for states is 0.0.0.0
```` `  

Das man hier in der Multiconfig 0.0.0.0 eingeben musste fand ich auch komisch. Allerdings war es ja auch so in der Hilfe beschrieben:

Type of objects DB [file, couch, redis], default [file]: ENTER

Host of objects DB(file), default[127.0.0.1]: <0.0.0.0>

Port of objects DB(file), default[9001]: ENTER

Type of states DB [file, redis], default [file]: ENTER

Host of states DB (file), default[0.0.0.0]: ENTER

Port of states DB (file), default[9000]: ENTER

Host name of this machine [hostname]: ENTER

Ich komme dann auch nicht lokal auf dem Host über http://localhost:8081 auf den Admin.

Gruß

Holger

wendy2702

Kannst du mal auf Host und Slave das machen````
cat /opt/iobroker/iobroker-data/iobroker.json

holgerwolf

~~@wendy2702:~~

Kannst du mal auf Host und Slave das machen cat /opt/iobroker/iobroker-data/iobroker.jsonund hier Posten. `

Master:

{
  "system": {
    "memoryLimitMB": 0,
    "hostname": ""
  },
  "network": {
    "IPv4": true,
    "IPv6": true,
    "bindAddress": null,
    "useSystemNpm": true
  },
  "objects": {
    "type": "file",
    "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].",
    "host": "0.0.0.0",
    "port": 9001,
    "user": "",
    "pass": "",
    "noFileCache": false,
    "connectTimeout": 10000
  },
  "states": {
    "type": "file",
    "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].",
    "host": "0.0.0.0",
    "port": 9000,
    "options": {
      "auth_pass": null,
      "retry_max_delay": 15000
    }
  },
  "log": {
    "level": "info",
    "maxDays": 7,
    "noStdout": true,
    "transport": {
      "file1": {
        "type": "file",
        "enabled": true,
        "filename": "log/iobroker",
        "fileext": ".log",
        "maxsize": null,
        "maxFiles": null
      },
      "syslog1": {
        "type": "syslog",
        "enabled": false,
        "host": "localhost",
        "host_comment": "The host running syslogd, defaults to localhost.",
        "port_comment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).",
        "protocol": "udp4",
        "protocol_comment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).",
        "path_comment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).",
        "facility_comment": "Syslog facility to use (Default: local0).",
        "localhost": "iobroker",
        "localhost_comment": "Host to indicate that log messages are coming from (Default: localhost).",
        "sysLogType_comment": "The type of the syslog protocol to use (Default: BSD).",
        "app_name_comment": "The name of the application (Default: process.title).",
        "eol_comment": "The end of line character to be added to the end of the message (Default: Message without modifications)."
      }
    }
  },
  "dataDirComment": "Always relative to iobroker.js-controller/",
  "dataDir": "../../iobroker-data/",
  "multihostService": {
    "enabled": true,
    "secure": true,
    "password": "30a840b7b157206bcfe4f692ce6fc51e"
  }
}

Slave:

{
  "system": {
    "memoryLimitMB": 0,
    "hostname": ""
  },
  "multihostService": {
    "enabled": false,
    "secure": true
  },
  "network": {
    "IPv4": true,
    "IPv6": true,
    "bindAddress": null,
    "useSystemNpm": true
  },
  "objects": {
    "type": "file",
    "typeComment": "Possible values: 'file' - [port 9001], redis - [port 6379], couch - [port 5984].",
    "host": "192.168.178.63",
    "port": 9001,
    "user": "",
    "pass": "",
    "noFileCache": false,
    "connectTimeout": 2000
  },
  "states": {
    "type": "file",
    "typeComment": "Possible values: 'file' - [port 9000], 'redis' - [port 6379].",
    "host": "192.168.178.63",
    "port": 9000,
    "maxQueue": 1000,
    "options": {
      "auth_pass": null,
      "retry_max_delay": 15000
    }
  },
  "log": {
    "level": "info",
    "maxDays": 7,
    "noStdout": true,
    "transport": {
      "file1": {
        "type": "file",
        "enabled": true,
        "filename": "log/iobroker",
        "fileext": ".log",
        "maxsize": null,
        "maxFiles": null
      },
      "syslog1": {
        "type": "syslog",
        "enabled": false,
        "host": "localhost",
        "host_comment": "The host running syslogd, defaults to localhost.",
        "port_comment": "The port on the host that syslog is running on, defaults to syslogd's default port(514/UDP).",
        "protocol": "udp4",
        "protocol_comment": "The network protocol to log over (e.g. tcp4, udp4, unix, unix-connect, etc).",
        "path_comment": "The path to the syslog dgram socket (i.e. /dev/log or /var/run/syslog for OS X).",
        "facility_comment": "Syslog facility to use (Default: local0).",
        "localhost": "iobroker",
        "localhost_comment": "Host to indicate that log messages are coming from (Default: localhost).",
        "sysLogType_comment": "The type of the syslog protocol to use (Default: BSD).",
        "app_name_comment": "The name of the application (Default: process.title).",
        "eol_comment": "The end of line character to be added to the end of the message (Default: Message without modifications)."
      }
    }
  },
  "dataDirComment": "Always relative to iobroker.js-controller/",
  "dataDir": "../../iobroker-data/"

Gruß

Holger

wendy2702

OK.

Hatte gehofft das mit meinen Vergleichen zu können. Aber entweder ist das Master file von dir anders aus als meins oder meins ist einfach schon zu alt.

Sieht jedenfalls anders aus bei mir aber ich weiß jetzt nicht was richtig ist da sich in den verschiedenen JS-Controllern ja beim Multihost immer mal was geändert hat.

Community Forum

NEWS

Nach Admin Update startet Admin als nicht mehr automatisch

Support us

885

32.5k

81.6k

1.3m