Test js-controller v2.0.x (GitHub)

[Jan1]

@SBorg
Node-Red läuft bei mir einwandfrei.

[apollon77]

@SBorg Dann bitte mal Logs zeigen. Bzw bitte am besten den js-controller mal auf Debug stellen (kannst Du im Konfigfile machen oder unter system.host.NAME.logLevel)

Und dann log von so einem Start ... genauso node-red auf Debug stellen (das aber unter Instanzen -> Expertenmodus -> Spalte Logstufe)

[apollon77]

@Yetiberg Ist die gleiche Fehler-Ecke wie das andere. Ich fixe das. Gibt heute Abend ein Update wo das gefixt sein sollte. Falls es für dich dringender ist sag mir per PN bescheid

[A Former User]

@apollon77
Nee nee, alles OK.
Mach mal in ruhe.

[Jan1]

Der BLE Adapter scheint wohl Probleme im compact mode zu mache. Der Adapter an sich läuft unauffällig, lediglich im Log steht dann die Meldung das der Status des compact mode nicht ermittelt werden kann und wenn ich den BLE Adapter neu starte, gehen einige andere Adapter mit in die Knie.
Hab den compact mode für den BLE Adapter nun wieder deaktiviert und alles ist OK.

host.Beelink.compactgroup1	2019-09-20 17:50:08.348	error	Cannot start ble.0 in compact mode: Cannot read property 'on' of undefined

root@Beelink:~# iobroker compact ble.0 status
Compact mode supported: true
Compact mode enabled:   true
Compact group:          1

root@Beelink:~# iobroker compact ble.0 disable
Compact mode supported: true
Compact mode enabled:   true --> false
Compact group:          1
Instance settings for "ble.0" are changed.

[apollon77]

@Jan1 Mach mal bitte Issue beim controller auf in dem Fall ... In dem Fall findet er das Start File nicht. was genau passier tbeim beenden? Hast Du da logs?

[Jan1]

@apollon77
Da an der Stelle einige Andere Adapter auch neu starten ist das Log recht voll.

[apollon77]

@Jan1 Aber findest Du Fehler oder nur Neustarts?

[Jan1]

@apollon77
Hier mal das Log wenn ich den BLE neustarte:

Spoiler

host.Beelink	2019-09-20 18:01:34.337	info	Restart compact group controller 1
host.Beelink	2019-09-20 18:01:34.337	error	Caught by controller[13]: at process._fatalException (internal/bootstrap/node.js:496:27)
host.Beelink	2019-09-20 18:01:34.337	error	Caught by controller[13]: at process.emit (events.js:203:15)
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: at process.on.err (/opt/iobroker/node_modules/iobroker.ble/build/main.js:382:17)
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: ^
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: adapter.log.error("unhandled exception:" + err.message);
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[13]: /opt/iobroker/node_modules/iobroker.ble/build/main.js:382
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.336	error	Caught by controller[12]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[12]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[11]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.335	error	Caught by controller[10]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[10]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[9]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[8]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.334	error	Caught by controller[8]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[8]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[8]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[8]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.333	error	Caught by controller[7]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[6]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.332	error	Caught by controller[5]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[5]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[4]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.331	error	Caught by controller[3]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[3]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[3]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[3]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[2]: TypeError: Cannot read property 'error' of undefined
host.Beelink	2019-09-20 18:01:34.330	error	Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:69:34)
host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: at emitPromiseRejectionWarnings (internal/process/promises.js:119:20)
host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: at process.emit (events.js:198:13)
host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: at process.on.r (/opt/iobroker/node_modules/iobroker.ble/build/main.js:377:17)
host.Beelink	2019-09-20 18:01:34.329	error	Caught by controller[1]: TypeError: Cannot read property 'error' of undefined
iqontrol.0	2019-09-20 18:01:34.188	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
alexa2.0	2019-09-20 18:01:34.185	warn	(COMPACT) Exception: TypeError: Cannot read property 'error' of undefined
info.0	2019-09-20 18:01:34.183	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
fritzdect.0	2019-09-20 18:01:34.181	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
javascript.0	2019-09-20 18:01:34.169	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
telegram.0	2019-09-20 18:01:34.167	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
tankerkoenig.0	2019-09-20 18:01:34.165	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
harmony.0	2019-09-20 18:01:34.162	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
history.0	2019-09-20 18:01:34.155	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
iot.0	2019-09-20 18:01:34.152	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
backitup.0	2019-09-20 18:01:34.150	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
admin.0	2019-09-20 18:01:34.138	error	(COMPACT) uncaught exception: Cannot read property 'error' of undefined
ble	2019-09-20 18:01:33.387	warn	(COMPACT) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
ble	2019-09-20 18:01:33.386	error	(COMPACT) ble.0 already running
host.Beelink.compactgroup1	2019-09-20 18:01:33.361	error	Cannot start ble.0 in compact mode: Cannot read property 'on' of undefined
host.Beelink	2019-09-20 18:01:33.351	info	stopInstance system.adapter.ble.0
host.Beelink	2019-09-20 18:01:33.350	info	object change system.adapter.ble.0 (from: system.adapter.admin.0)
host.Beelink.compactgroup1	2019-09-20 18:01:41.391	info	instance system.adapter.backitup.0 started in COMPACT mode

Dann noch die comact mode Übersicht:

Spoiler

root@Beelink:~# iobroker list instances
+ system.adapter.admin.0                 : admin                 -  enabled, compact enabled (group 1), port: 8081, bind: 0.0.0.0, run as: admin
 system.adapter.admin.1                 : admin                 - disabled, compact disabled, port: 8082, bind: 0.0.0.0 (SSL), run as: admin
+ system.adapter.alexa2.0                : alexa2                -  enabled, compact enabled (group 1)
+ system.adapter.backitup.0              : backitup              -  enabled, compact enabled (group 1)
+ system.adapter.ble.0                   : ble                   -  enabled, compact disabled
+ system.adapter.email.0                 : email                 -  enabled, compact disabled
+ system.adapter.enigma2.0               : enigma2               -  enabled, compact disabled
+ system.adapter.fritzdect.0             : fritzdect             -  enabled, compact enabled (group 1)
+ system.adapter.google-sharedlocations.0: google-sharedlocations -  enabled, compact disabled
+ system.adapter.harmony.0               : harmony               -  enabled, compact enabled (group 1)
+ system.adapter.history.0               : history               -  enabled, compact enabled (group 1)
 system.adapter.ical.0                  : ical                  -  enabled, compact disabled
+ system.adapter.info.0                  : info                  -  enabled, compact enabled (group 1)
+ system.adapter.iot.0                   : iot                   -  enabled, compact enabled (group 1)
+ system.adapter.iqontrol.0              : iqontrol              -  enabled, compact enabled (group 1)
+ system.adapter.javascript.0            : javascript            -  enabled, compact enabled (group 1)
+ system.adapter.milight-smart-light.0   : milight-smart-light   -  enabled, compact disabled
+ system.adapter.node-red.0              : node-red              -  enabled, compact disabled, port: 1880, bind: 0.0.0.0
 system.adapter.openweathermap.0        : openweathermap        -  enabled, compact disabled
+ system.adapter.scenes.0                : scenes                -  enabled, compact disabled
 system.adapter.simple-api.0            : simple-api            -  enabled, compact enabled (group 1), port: 8087, bind: 0.0.0.0, run as: admin
+ system.adapter.sonoff.0                : sonoff                -  enabled, compact disabled, port: 1883, bind: 0.0.0.0
+ system.adapter.tankerkoenig.0          : tankerkoenig          -  enabled, compact enabled (group 1)
+ system.adapter.telegram.0              : telegram              -  enabled, compact enabled (group 1), port: 8443, bind: 0.0.0.0
+ system.adapter.tr-064-community.0      : tr-064-community      -  enabled, compact disabled
+ system.adapter.vr200.0                 : vr200                 -  enabled, compact disabled
+ system.adapter.web.0                   : web                   -  enabled, compact disabled, port: 8082, bind: 0.0.0.0, run as: admin
+ system.adapter.wifilight.0             : wifilight             -  enabled, compact disabled
+ system.adapter.zigbee.0                : zigbee                -  enabled, compact disabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED3DD2-if00

+ instance is alive

[apollon77]

@Jan1 Ich habe mal https://github.com/AlCalzone/ioBroker.ble/issues/203 angelegt, was quasi die Ursache ist dafür das alles abraucht. Das muss @AlCalzone im Adapter fixen.

Der Grund warum das init nicht klappt muss ich mir mit Ihm ansehen ... Grund gefunden ... https://github.com/AlCalzone/ioBroker.ble/issues/204

Apollon77 created this issue in AlCalzone/ioBroker.ble

closed Make sure to checkexietence of "adapter" and "adapter.log" when handling process exceptions #203

Apollon77 created this issue in AlCalzone/ioBroker.ble

closed Cannot be started in compact mode, adapter object not returned by startAdapter method #204

[apollon77]

@Jan1 Also mit den zwei Issues ist ble gerade nicht compact Kompatibel, bitte erstmal bis zu nem Fix ausschalten

[Jan1]

@apollon77
schon passiert und danke für die Mühe

[SBorg]

Node-RED Start: log.txt

Restart Node-RED Adapter:

2019-09-20 17:41:40.013 - debug: node-red.0 (16880) system.adapter.admin.0: logging false
2019-09-20 17:41:40.038 - debug: node-red.0 (16971) system.adapter.admin.0: logging false
2019-09-20 17:41:40.722 - info: host.Ubuntu object change system.adapter.node-red.0 (from: system.adapter.admin.0)
2019-09-20 17:41:40.723 - info: node-red.0 (16971) Adapter is disabled => stop
2019-09-20 17:41:40.729 - info: node-red.0 (16880) kill node-red task
2019-09-20 17:41:40.723 - info: host.Ubuntu "system.adapter.node-red.0" disabled
2019-09-20 17:41:40.726 - info: host.Ubuntu stopInstance system.adapter.node-red.0
2019-09-20 17:41:41.307 - info: node-red.0 (16971) terminating
2019-09-20 17:41:41.344 - info: node-red.0 (16880) node-red exited with 0
2019-09-20 17:41:41.348 - info: mqtt.0 (16456) Client [ioBroker] connection closed: closed
2019-09-20 17:41:41.731 - info: host.Ubuntu stopInstance timeout "1000 system.adapter.node-red.0 killing pid 16880
2019-09-20 17:41:41.808 - info: node-red.0 (16880) Terminated (NO_ERROR): Without reason
2019-09-20 17:41:41.840 - info: host.Ubuntu instance system.adapter.node-red.0 terminated with code 0 (NO_ERROR)
2019-09-20 17:41:49.504 - info: host.Ubuntu object change system.adapter.node-red.0 (from: system.adapter.admin.0)
2019-09-20 17:41:49.505 - info: host.Ubuntu "system.adapter.node-red.0" enabled
2019-09-20 17:41:49.588 - info: host.Ubuntu instance system.adapter.node-red.0 started with pid 6366
2019-09-20 17:41:52.629 - debug: node-red (6366) Redis Objects: Use Redis connection: 127.0.0.1:9001
2019-09-20 17:41:55.060 - debug: node-red (6366) Objects connected to redis: 127.0.0.1:9001
2019-09-20 17:41:55.078 - debug: node-red (6366) objectDB connected
2019-09-20 17:41:55.084 - debug: node-red (6366) Redis States: Use Redis connection: 127.0.0.1:9000
2019-09-20 17:41:55.098 - debug: node-red (6366) statesDB connected
2019-09-20 17:41:55.124 - error: node-red (6366) node-red.0 invalid instance object: {"_id":"","type":"channel","common":{"name":"States created by node-red.%INSTANCE%","role":"info"},"native":{}}
2019-09-20 17:41:55.136 - debug: node-red (6366) States connected to redis: 127.0.0.1:9000
2019-09-20 17:41:56.034 - info: node-red.0 (6366) starting. Version 1.9.0 in /opt/iobroker/node_modules/iobroker.node-red, node: v8.16.1
2019-09-20 17:41:58.051 - info: node-red.0 (6366) Starting node-red: --max-old-space-size=156 /opt/iobroker/node_modules/iobroker.node-red/node_modules/node-red/red.js -v --settings /opt/iobroker/iobroker-data/node-red/settings.js
2019-09-20 17:42:03.598 - debug: node-red.0 (6366) 20 Sep 17:42:03 - [info]
Willkommen bei Node-RED!
===================
2019-09-20 17:42:03.601 - debug: node-red.0 (6366) 20 Sep 17:42:03 - [info] Node-RED Version: v0.20.7
2019-09-20 17:42:03.611 - debug: node-red.0 (6366) 20 Sep 17:42:03 - [info] Node.js Version: v8.16.1
20 Sep 17:42:03 - [info] Linux 5.0.0-29-generic ia32 LE
2019-09-20 17:42:06.394 - debug: node-red.0 (6366) 20 Sep 17:42:06 - [info] Paletten-Nodes werden geladen
2019-09-20 17:42:36.179 - debug: node-red.0 (6366) 20 Sep 17:42:36 - [info] Polymer started at /node-red/polymer
2019-09-20 17:42:39.590 - debug: node-red.0 (6366) 20 Sep 17:42:39 - [info] Dashboard version 2.15.5 started at /node-red/ui
2019-09-20 17:42:43.523 - debug: node-red.0 (6366) 20 Sep 17:42:43 - [info] Einstellungsdatei: /opt/iobroker/iobroker-data/node-red/settings.js
2019-09-20 17:42:43.529 - debug: node-red.0 (6366) 20 Sep 17:42:43 - [info] Kontextspeicher: 'default' [ module=memory]
2019-09-20 17:42:43.533 - debug: node-red.0 (6366) 20 Sep 17:42:43 - [info] Benutzerverzeichnis: /opt/iobroker/iobroker-data/node-red/
2019-09-20 17:42:43.535 - warn: node-red.0 (6366) 20 Sep 17:42:43 - [warn] Projekte inaktiviert: setze editorTheme.projects.enabled=true zum Aktivieren
2019-09-20 17:42:43.541 - debug: node-red.0 (6366) 20 Sep 17:42:43 - [info] Flow-Datei: /opt/iobroker/iobroker-data/node-red/flows.json
2019-09-20 17:42:33.761 - debug: node-red (6646) Redis Objects: Use Redis connection: 127.0.0.1:9001
2019-09-20 17:42:43.617 - debug: node-red (6646) objectDB connected
2019-09-20 17:42:43.622 - debug: node-red (6646) Redis States: Use Redis connection: 127.0.0.1:9000
2019-09-20 17:42:43.628 - debug: node-red (6646) Objects connected to redis: 127.0.0.1:9001
2019-09-20 17:42:43.661 - debug: node-red (6646) statesDB connected
2019-09-20 17:42:43.692 - debug: node-red.0 (6366) 20 Sep 17:42:43 - [info] Server wird jetzt auf http://192.168.1.30:1880/node-red/ ausgeführt.
2019-09-20 17:42:43.823 - debug: node-red.0 (6366) 20 Sep 17:42:43 - [info] Flows starten
2019-09-20 17:42:44.258 - debug: node-red.0 (6366) 20 Sep 17:42:44 - [info] Flows gestartet
2019-09-20 17:42:44.787 - debug: node-red (6646) States connected to redis: 127.0.0.1:9000
2019-09-20 17:42:44.821 - info: mqtt.0 (16456) Client [ioBroker] connected with secret xxx
2019-09-20 17:42:44.867 - debug: node-red.0 (6366) 20 Sep 17:42:44 - [info] [mqtt-broker:MQTT@1883] Verbindung zum Broker ioBroker@mqtt://192.168.1.30:1883 hergestellt.
2019-09-20 17:42:44.879 - info: mqtt.0 (16456) Client [ioBroker] subscribes on "mqtt.0.cmnd.Wohnzimmer-Nebler.POWER"
2019-09-20 17:42:44.880 - info: mqtt.0 (16456) Client [ioBroker] publishOnSubscribe
2019-09-20 17:42:44.883 - info: mqtt.0 (16456) Client [ioBroker] subscribes on "mqtt.0.stat.HeizCon.PowerUP"
2019-09-20 17:42:44.883 - info: mqtt.0 (16456) Client [ioBroker] publishOnSubscribe
2019-09-20 17:43:44.212 - debug: node-red.0 (6366) 20 Sep 17:43:44 - [info] [inject:Tablettenbestand] Wiederholen = 3600000
2019-09-20 17:44:38.649 - info: tankerkoenig.0 (16423) Reading data from tankerkoenig ...
...

[apollon77]

@SBorg das sieht aber an sich korrekt aus oder?! ... ja das start log. Checke.

[apollon77]

@SBorg Hm ... das problem ist das node-red "zu schnell" startet. Wie Du im log schön siehst will er schon states abrufen 17:31:41.477 ... aber die ioBroker-Datenbank-Verbindungen sind erst 17:31:42.659 verfügbar. Das sind einige "Get"-Nodes die in dem Zuge wohl recht am Anfang stehen. Und weil bei einem kompletten Start natürlich der Host recht zu viel tun hat kann das mal etwas dauern ...

Bitte GitHub Issue bei node-red anlegen. Das muss man irgendwie "delayen" bis der Adapter ready ist. Bitte so einen 2getObject" Fehler mit Stack Trace reinpacken ins Issue.

[apollon77]

@SBorg Bitte mal node-red vom GitHub versuchen. Ist blind gemacht kann also auch schieff gehen Das sollte das prüfen der States verzögern falls die DBs noch nicht da sind.

[e-i-k-e]

Guten Abend,

habe soeben mein Multihost System mit redis nach Anleitung aktualisiert.
Master: Rock64 4GB + SSD, 6x Slave Raspberry).
Iobroker: Node.js 10.16.3, js controller: 2.0.4, npm: 6.11.3

Ich bekomme nun folgende Fehlermeldung unzählige mal im Log Angezeigt (mit geänderterer IP-Adresse)

Bis auf die Adapter der Slave Geräte, sind alle Adapter Grün.
Unter Host werden die Slave als verfügbar angezeigt.

[apollon77]

@e-i-k-e Die Slaves sind also auch alle auf die 2.0 aktualisiert? Es scheint als ob die Slaves nicht zum Master kommen. WIe ist die Ausgabe von "iobroker setup custom" von allen Hosts bitte?

[apollon77]

Hey All,

die 2.0.5 ist soeben auf GitHub gelandet und sollte alle hier verifizierten Themen behandeln. Daher bitte folgendes Re-Testen:

• Zugriff auf Files/Images in Vis oder web (oder iqontrol?) sollte tun, auch eigene File-Locations die eigentlich nicht supported sind
• Für node-red gibts eine neue node-red Adapterversion ...
• Bitte auch mit ble nochmal testen. Es sollte jetzt mal mindestens beim versuch den in compact-Modus zu starten den Fehler geben und das zu einem Fallback-Start als normaler Prozess führen. Beim Restart kann es immer noch zu craseds kommen, das kann nur der Adapter fixen. Aber wäre cool zu wissen wie sich das jetzt verhält.

Weiterhin ist die Migration jetzt noch ausgeklügelter was das Nachfragen angehtund die Entscheidung ob eine Migration erlaubt wird.

[e-i-k-e]

@apollon77

Danke für deine schnelle Antwort.

Ein Neustart der Slave Geräte hat das Problem behoben. Evtl. sollte man diese Info in die Anleitung mit aufnehmen?