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

smartboart

Hi, habe auch mal upgedatet. Alles sofort geklappt. Mir fällt nur auf, dass ich unter den Objekten welche mittels Historie oder statistics mitlogge nicht mehr deaktivieren kann. Also die Maulschlüssel öffnen ganz normal die Einstellungen.Der Haken aktiv lässt sich auch ohne weiteres deaktiviern nur beim Speichern werden Änderungen nicht übernommen.

Systemdaten:

 ioBroker-Rock

    Typ: js-controller
    Titel: JS controller
    OS: linux
    Verfügbar: 2.0.29
    Eingerichtet: 2.0.29
    Ereignisse: ⇥24 / ↦13



ioBroker-Rock

Betriebssystem
    linux
Architektur
    arm64
CPUs
    4
Geschwindigkeit
    1296 MHz
Modell
    unknown
RAM
    3.9 GB
System Betriebszeit
    2 T. 18:38:11
Node.js
    v10.16.3
NPM
    6.9.0
Festplatte Größe
    56.1 GB
Festplatte frei
    47.85 GB
Anzahl der Adapter
    293
Betriebszeit
    00:11:12
Aktive Instanzen
    22
Hostname
    ioBroker-Rock

das hier taucht auch im log auf.Nach neustart..
Error 2019-10-14 17:46:22.010 warn from InMemDB: Error: Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f
Error 2019-10-14 17:46:22.007 warn from InMemDB: Error: Unknown Script 47ca5e051ba19850d94c45a1fc8725ff04ae868f

apollon77

@smartboart Die Scripts Fehler könnten kommen wenn Du verschiedene Versionen laufen hast (Master/Slave ode rso) . Kann dass sein? Ggf bitte nochmal neu starten. Ich arbeite noch an einer nächsten version die da Dinge noch fixt.

Das andere mit Custom ich ansehen. Ist aktuell nicht bekannt. Kann es noch jemand nachvollziehen?

smartboart

@apollon77
ja hab nen multihost system, aber beide hochgezogen...
Beides neu gestartet, der Skript Fehler ist aber immernoch im log..

Der tauchte auch im master bei iobroker upgrade self im Anschluss auf. Das Upgrade ging erst beim 2 mal durch.. Hatte vorher das vorletzte releas drauf 2.0.25, was ohne Probleme zu installieren war..

smartboart

@apollon77
hallo, hatte vorher nur states auf redis..Hab jetzt auch file auf redis umgestellt. Im Anschluss waren meine oben beschriebenen Fehler beseitigt.. Falls die Info hilfreich ist. Danke für eure tolle Arbeit!

smartboart

Bei Adapter Updates habe ich folgende Gyp Fehler im Log.. oben wurde beschrieben es hat hier mit dem js controller nix zu tun . Meine Python Installation meldet bei
apt-get install python-dev allerdings dass alles aktuell ist und nichts upzudaten wäre.. Die fehler haben keine Auswirkungen. mich würde trotzdem interessieren was die Ursache dafür ist...

host.ioBroker-Rock 2019-10-14 19:39:11.291 info iobroker ERR! not ok
host.ioBroker-Rock 2019-10-14 19:39:11.289 info iobroker gyp
host.ioBroker-Rock 2019-10-14 19:39:11.277 info iobroker v3.8.0
host.ioBroker-Rock 2019-10-14 19:39:11.274 info iobroker node -v v10.16.3gyp ERR! node-gyp -v
host.ioBroker-Rock 2019-10-14 19:39:11.271 info iobroker cwd /opt/iobroker/node_modules/utf-8-validategyp ERR!
host.ioBroker-Rock 2019-10-14 19:39:11.269 info iobroker ERR!
host.ioBroker-Rock 2019-10-14 19:39:11.266 info iobroker "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp
host.ioBroker-Rock 2019-10-14 19:39:11.264 info iobroker ERR! command
host.ioBroker-Rock 2019-10-14 19:39:11.261 info iobroker gyp
host.ioBroker-Rock 2019-10-14 19:39:11.258 info iobroker at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)gyp ERR! stack at ChildProcess.emit (events.js:198:13)gyp ERR! stack at Process.Child
host.ioBroker-Rock 2019-10-14 19:39:11.256 info iobroker stack
host.ioBroker-Rock 2019-10-14 19:39:11.253 info iobroker ERR!
host.ioBroker-Rock 2019-10-14 19:39:11.251 info iobroker Error: make failed with exit code: 2gyp
host.ioBroker-Rock 2019-10-14 19:39:11.248 info iobroker stack
host.ioBroker-Rock 2019-10-14 19:39:11.246 info iobroker ERR!
host.ioBroker-Rock 2019-10-14 19:39:11.243 info iobroker gyp
host.ioBroker-Rock 2019-10-14 19:39:11.240 info iobroker build error
host.ioBroker-Rock 2019-10-14 19:39:11.238 info iobroker ERR!
host.ioBroker-Rock 2019-10-14 19:39:11.236 info iobroker
host.ioBroker-Rock 2019-10-14 19:39:11.233 info iobroker gyp

Chaot

Den ersten Härtetest hat das System heute schon hinter sich.
Stromausfall und die USV war abgeschaltet :dizzy_face: weil ich den Batteriepack mit zur Arbeit hatte zum Austausch.
Nach 30 Minuten fährt das System wieder hoch als wäre nichts geschehen. :blush:

apollon77

@smartboart mehr log bitte

apollon77

Hallo nochmals ich,

ich habe mit das Reconnection Handling nochmal angesehen, weil es anders war wie gewollt.
Die 2.0.30 auf GitHub hat das umgebaut.

Ich wäre hier nochmal froh wenn Ihr checken könntet. Vor allem interessant ist das Verhalten von Slaves wenn der Master weg ist bzw. das verhalten des Gesamtsystems bei Redis-Nutzung wenn Redis weg ist.
Mit der 2.0.30 wird bis zu ca. 40s versucht die Verbindung wieder herzustellen. Wenn das gelingt kommt das ganze ohne Restarts aus und auch aufgelaufene Datenänderungen (zB setState oder Infos zu State-Änderungen) werden nachgespielt.
Wenn es länger braucht beenden sich die Adapter wie bisher und alles wartet das die DB wieder da ist.

darkiop

Habe beide auf die 2.0.30 gezogen.

Beim installieren gab es ungewöhnlich viele Warnungen, die hatte ich vorher nicht - siehe Log. Beide laufen aber ohne Auffälligkeiten.

iobroker-switch.sh 
type '1.5' (latest) or '2.0' (from github)
switch js-controller to: 2.0
ioBroker is terminated ...
Install js-controller 2.0.x ...

> iobroker.js-controller@2.0.30 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.9.0

> unix-dgram@2.0.2 install /opt/iobroker/node_modules/unix-dgram
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird betreten
  CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
../src/unix_dgram.cc: In function ‘void {anonymous}::OnRecv({anonymous}::SocketContext*)’:
../src/unix_dgram.cc:121:25: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
                     argv);
                         ^
In file included from ../src/unix_dgram.cc:5:0:
../../nan/nan.h:1024:46: note: declared here
   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                              ^~~~~~~~~~~~
../src/unix_dgram.cc: In function ‘void {anonymous}::OnWritable({anonymous}::SocketContext*)’:
../src/unix_dgram.cc:129:28: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]
                     0, NULL);
                            ^
In file included from ../src/unix_dgram.cc:5:0:
../../nan/nan.h:1024:46: note: declared here
   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(
                                              ^~~~~~~~~~~~
../src/unix_dgram.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE {anonymous}::Socket(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix_dgram.cc:189:37: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   domain      = info[0]->Int32Value();
                                     ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:190:37: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   type        = info[1]->Int32Value();
                                     ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:191:37: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   protocol    = info[2]->Int32Value();
                                     ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE {anonymous}::Bind(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix_dgram.cc:230:28: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   fd = info[0]->Int32Value();
                            ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:231:33: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
   String::Utf8Value path(info[1]);
                                 ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2892:28: note: declared here
                   explicit Utf8Value(Local<v8::Value> obj));
                            ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE {anonymous}::SendTo(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix_dgram.cc:258:28: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   fd = info[0]->Int32Value();
                            ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:259:27: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   buf = info[1]->ToObject();
                           ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63:0,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
 Local<Object> Value::ToObject() const {
               ^~~~~
../src/unix_dgram.cc:260:33: warning: ‘uint32_t v8::Value::Uint32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   offset = info[2]->Uint32Value();
                                 ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2477:47: note: declared here
   V8_DEPRECATED("Use maybe version", uint32_t Uint32Value() const);
                                               ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:261:33: warning: ‘uint32_t v8::Value::Uint32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   length = info[3]->Uint32Value();
                                 ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2477:47: note: declared here
   V8_DEPRECATED("Use maybe version", uint32_t Uint32Value() const);
                                               ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:262:33: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
   String::Utf8Value path(info[4]);
                                 ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2892:28: note: declared here
                   explicit Utf8Value(Local<v8::Value> obj));
                            ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE {anonymous}::Send(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix_dgram.cc:302:28: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   fd = info[0]->Int32Value();
                            ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:303:27: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   buf = info[1]->ToObject();
                           ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63:0,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:10046:15: note: declared here
 Local<Object> Value::ToObject() const {
               ^~~~~
../src/unix_dgram.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE {anonymous}::Connect(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix_dgram.cc:340:28: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   fd = info[0]->Int32Value();
                            ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc:341:33: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is deprecated: Use Isolate version [-Wdeprecated-declarations]
   String::Utf8Value path(info[1]);
                                 ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2892:28: note: declared here
                   explicit Utf8Value(Local<v8::Value> obj));
                            ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../src/unix_dgram.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE {anonymous}::Close(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/unix_dgram.cc:361:28: warning: ‘int32_t v8::Value::Int32Value() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   fd = info[0]->Int32Value();
                            ^
In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0,
                 from /home/iobroker/.node-gyp/10.16.3/include/node/node.h:63,
                 from ../../nan/nan.h:54,
                 from ../src/unix_dgram.cc:5:
/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2478:46: note: declared here
   V8_DEPRECATED("Use maybe version", int32_t Int32Value() const);
                                              ^
/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
  COPY Release/unix_dgram.node
make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird verlassen

> iobroker.js-controller@2.0.30 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+ iobroker.js-controller@2.0.30
updated 4 packages and audited 35156 packages in 96.546s
found 52 vulnerabilities (40 low, 12 high)
  run `npm audit fix` to fix them, or `npm audit` for details
ioBroker will be started ...
Starting iobroker controller daemon...
iobroker controller daemon started. PID: 20872
┬─[root@iobroker-master:/opt/iobroker]─[10:16:27]
╰─>#

darkiop

Zu deinen gewünschten Tests:

Testfall 1:

master + slave = alive
master beenden
nicht wieder starten

Testfall 2:

master + slave = alive
master beenden
20s warten
wieder starten

Testfall 3:

master + slave = alive
redis beenden
nicht wieder starten

Testfall 4:

master + slave = alive
redis beenden
paar Sekunden warten
redis starten
prüfen ob States die innerhalb der 40s erzeugt werden nach dem starten von redis verfügbar sind

darkiop

Testfall 1:

iobroker-master um 10:26:02 beendet und nicht wieder gestartet, log auf slave. Nach ner gewissen Zeit beenden sich die Adapter und der controller lauert:

2019-10-15 10:26:31.418  - error: host.iobroker-hwr connect ETIMEDOUT
2019-10-15 10:26:31.415  - error: smartmeter.1 (641) connect ETIMEDOUT
2019-10-15 10:26:31.416  - error: smartmeter.0 (626) connect ETIMEDOUT
2019-10-15 10:26:43.421  - error: host.iobroker-hwr connect ETIMEDOUT
2019-10-15 10:26:43.423  - error: smartmeter.1 (641) connect ETIMEDOUT
2019-10-15 10:26:43.423  - error: smartmeter.0 (626) connect ETIMEDOUT
2019-10-15 10:26:45.929  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:26:45.929  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:26:45.928  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:26:57.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:26:57.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:26:57.928  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:03.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:03.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:03.928  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:09.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:09.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:09.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:15.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:15.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:18.927  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:21.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:21.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:24.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:27.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:30.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:33.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:33.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:36.927  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:36.927  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:39.927  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:42.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:42.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:45.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:48.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:48.927  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:51.927  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:54.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:54.926  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:57.926  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:27:57.927  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:28:00.927  - error: smartmeter.1 (641) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:28:00.929  - error: smartmeter.0 (626) connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:28:03.430  - warn: host.iobroker-hwr Slave controller detected objects disconnection. Stop all instances.
2019-10-15 10:28:03.435  - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.0
2019-10-15 10:28:03.436  - info: host.iobroker-hwr stopInstance forced system.adapter.smartmeter.0 killing pid 626
2019-10-15 10:28:03.437  - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.1
2019-10-15 10:28:03.438  - info: host.iobroker-hwr stopInstance forced system.adapter.smartmeter.1 killing pid 641
2019-10-15 10:28:03.926  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:28:06.927  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:28:09.927  - error: host.iobroker-hwr connect EHOSTUNREACH 192.168.1.82:9001
2019-10-15 10:28:09.938  - error: host.iobroker-hwr Cannot find view "system" for search "instance" : Error: Connection is closed.
2019-10-15 10:28:09.942  - info: host.iobroker-hwr instance system.adapter.smartmeter.1 terminated with code 156 (156)
2019-10-15 10:28:09.943  - info: host.iobroker-hwr All instances are stopped.
2019-10-15 10:28:09.944  - error: host.iobroker-hwr Cannot find view "system" for search "instance" : Error: Connection is closed.
2019-10-15 10:28:09.945  - info: host.iobroker-hwr instance system.adapter.smartmeter.0 terminated with code 156 (156)
2019-10-15 10:28:09.945  - info: host.iobroker-hwr All instances are stopped.
2019-10-15 10:28:12.439  - warn: host.iobroker-hwr Slave controller detected objects disconnection. Stop all instances.
2019-10-15 10:28:12.440  - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.0
2019-10-15 10:28:12.441  - info: host.iobroker-hwr stopInstance system.adapter.smartmeter.1
2019-10-15 10:28:25.052  - info: host.iobroker-hwr iobroker _restart
2019-10-15 10:28:25.602  - info: host.iobroker-hwr iobroker Starting node restart.js
2019-10-15 10:28:27.058  - info: host.iobroker-hwr iobroker.js-controller version 2.0.30 js-controller starting
2019-10-15 10:28:27.065  - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-10-15 10:28:27.066  - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3
2019-10-15 10:28:27.068  - info: host.iobroker-hwr ip addresses: 10.3.1.22 fe80::561e:8619:1900:f27

darkiop

Testfall 2:

iobroker-master um 10:30:05 beendet und nach 20s wieder gestartet, log auf slave:

--> Kein Log das die Verbindung wieder besteht. 10:32:37 wurde der iobroker-master wieder gestartet und war ein paar Sekunden später auch wieder Verbunden (--> ersichtlich im Admin).

2019-10-15 10:30:01.626  - info: host.iobroker-hwr iobroker Starting node restart.js
2019-10-15 10:30:03.055  - info: host.iobroker-hwr iobroker.js-controller version 2.0.30 js-controller starting
2019-10-15 10:30:03.063  - info: host.iobroker-hwr Copyright (c) 2014-2019 bluefox, 2014 hobbyquaker
2019-10-15 10:30:03.064  - info: host.iobroker-hwr hostname: iobroker-hwr, node: v10.16.3
2019-10-15 10:30:03.065  - info: host.iobroker-hwr ip addresses: 10.3.1.22 fe80::561e:8619:1900:f27
2019-10-15 10:30:20.413  - info: host.iobroker-hwr connected to Objects and States
2019-10-15 10:30:20.684  - info: host.iobroker-hwr 87 instances found
2019-10-15 10:30:20.709  - info: host.iobroker-hwr starting 2 instances
2019-10-15 10:30:20.727  - info: host.iobroker-hwr instance system.adapter.smartmeter.0 started with pid 928
2019-10-15 10:30:24.719  - info: host.iobroker-hwr instance system.adapter.smartmeter.1 started with pid 943
2019-10-15 10:32:28.828  - error: host.iobroker-hwr connect ETIMEDOUT
2019-10-15 10:32:28.833  - error: smartmeter.0 (928) connect ETIMEDOUT
2019-10-15 10:32:28.838  - error: smartmeter.1 (943) connect ETIMEDOUT
2019-10-15 10:32:40.833  - error: host.iobroker-hwr connect ETIMEDOUT
2019-10-15 10:32:40.841  - error: smartmeter.0 (928) connect ETIMEDOUT
2019-10-15 10:32:40.864  - error: smartmeter.1 (943) connect ETIMEDOUT
2019-10-15 10:32:42.839  - error: host.iobroker-hwr connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:42.847  - error: smartmeter.0 (928) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:42.867  - error: smartmeter.1 (943) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:44.844  - error: host.iobroker-hwr connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:44.850  - error: smartmeter.0 (928) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:44.870  - error: smartmeter.1 (943) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:46.846  - error: host.iobroker-hwr connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:46.851  - error: smartmeter.0 (928) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:46.873  - error: smartmeter.1 (943) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:48.850  - error: host.iobroker-hwr connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:48.854  - error: smartmeter.0 (928) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:48.876  - error: smartmeter.1 (943) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:50.852  - error: host.iobroker-hwr connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:50.857  - error: smartmeter.0 (928) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:50.878  - error: smartmeter.1 (943) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:52.855  - error: host.iobroker-hwr connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:52.859  - error: smartmeter.0 (928) connect ECONNREFUSED 192.168.1.82:9001
2019-10-15 10:32:52.881  - error: smartmeter.1 (943) connect ECONNREFUSED 192.168.1.82:9001

darkiop

Testfall 3

iobroker-redis um 10:45:13 Uhr beendet. Log Master.
Einige Minuten später iobroker-redis wieder gestartet - der iobroker-master schafft es nicht wieder auf die Beine. Nach einem restart des Containers für den Master ist wieder alles verbunden.

log_tf3.txt

darkiop

Testfall 4

┬─[darkiop@odin:~]─[11:00:32]
╰─>$ docker stop iobroker-redis

┬─[darkiop@odin:~]─[11:02:15]
╰─>$ docker start iobroker-redis

smartmeter.1 hat einen Wert von 2019-10-15 11:01:34.726 über sql.0 in die DB geschrieben!

apollon77 · Habe beide auf die 2.0.30 gezogen.

@darkiop Alles unix dgram complier warnungen :-( Aber ja ist egal, tut alles

apollon77

Danke für die Tests!!

Testfall1 : So soll es sein
Testfall 2: Auch hier soll es so sein. Wenn Du auf "debug" oder "silly" log hättest würdest du die reconnects als Log sehen.
Testfall 3 Bitte mit der neuen 2.0.31 auf Github nochmal testen
Testfall 4; Cooool :-)

darkiop

@apollon77 sagte in [Aufruf] js-controller 2.0 Beta Test:

Danke für die Tests!!

Gern!

Testfall 3 Bitte mit der neuen 2.0.31 auf Github nochmal testen

Da stimmt was nicht:

┬─[darkiop@odin:~]─[13:35:02]
╰─>$ docker stop iobroker-redis
iobroker-redis
┬─[darkiop@odin:~]─[13:41:53]
╰─>$ docker start iobroker-redis
iobroker-redis

Log Master:

2019-10-15 13:41:48.364  - error: scenes.0 (1492) connect ETIMEDOUT
2019-10-15 13:41:48.366  - error: pi-hole.0 (1228) connect ETIMEDOUT
2019-10-15 13:41:48.368  - error: harmony.0 (388) connect ETIMEDOUT
2019-10-15 13:41:48.368  - error: simple-api.0 (1695) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: javascript.1 (1068) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: sql.0 (1819) connect ETIMEDOUT
2019-10-15 13:41:48.372  - error: telegram.0 (2364) connect ETIMEDOUT
2019-10-15 13:41:48.375  - error: host.iobroker-master connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: hm-rega.0 (403) connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: hs100.0 (480) connect ETIMEDOUT
2019-10-15 13:41:48.379  - error: tr-064-community.0 (2710) connect ETIMEDOUT
2019-10-15 13:41:48.385  - error: stiebel-isg.0 (2029) connect ETIMEDOUT
2019-10-15 13:41:48.385  - error: moma.0 (1162) connect ETIMEDOUT
2019-10-15 13:41:48.390  - error: ping.0 (1378) connect ETIMEDOUT
2019-10-15 13:41:48.391  - error: hm-rpc.1 (426) connect ETIMEDOUT
2019-10-15 13:41:48.392  - error: backitup.0 (457) connect ETIMEDOUT
2019-10-15 13:41:48.393  - error: hm-rpc.2 (450) connect ETIMEDOUT
2019-10-15 13:41:48.393  - error: javascript.0 (808) connect ETIMEDOUT
2019-10-15 13:41:48.399  - error: mercedesme.0 (1108) connect ETIMEDOUT
2019-10-15 13:41:48.407  - error: info.0 (789) connect ETIMEDOUT
2019-10-15 13:42:00.004  - warn: host.iobroker-master instance system.adapter.daswetter.0 already running with pid 11372
2019-10-15 13:42:03.215  - info: host.iobroker-master instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)
2019-10-15 13:42:04.501  - debug: harmony.0 (388) system.adapter.admin.0: logging true
2019-10-15 13:42:04.532  - debug: harmony.0 (388) States connected to redis: 192.168.1.86:6379
2019-10-15 13:42:20.048  - error: admin.0 (419) uncaught exception: Maximum call stack size exceeded
2019-10-15 13:42:20.052  - error: admin.0 (419) RangeError: Maximum call stack size exceeded
    at Sender.frameAndSend (/opt/iobroker/node_modules/ws/lib/Sender.js:166:14)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:126:12
    at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
    at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:270:10
    at /opt/iobroker/node_modules/ws/lib/Sender.js:127:7
    at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
    at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
    at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.318  - error: host.iobroker-master Caught by controller[0]: RangeError: Maximum call stack size exceeded
2019-10-15 13:42:20.320  - error: host.iobroker-master Caught by controller[0]:     at Sender.frameAndSend (/opt/iobroker/node_modules/ws/lib/Sender.js:166:14)
2019-10-15 13:42:20.321  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:126:12
2019-10-15 13:42:20.323  - error: host.iobroker-master Caught by controller[0]:     at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
2019-10-15 13:42:20.324  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
2019-10-15 13:42:20.325  - error: host.iobroker-master Caught by controller[0]:     at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.326  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:270:10
2019-10-15 13:42:20.327  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:127:7
2019-10-15 13:42:20.328  - error: host.iobroker-master Caught by controller[0]:     at Sender.applyExtensions (/opt/iobroker/node_modules/ws/lib/Sender.js:287:5)
2019-10-15 13:42:20.328  - error: host.iobroker-master Caught by controller[0]:     at /opt/iobroker/node_modules/ws/lib/Sender.js:120:10
2019-10-15 13:42:20.329  - error: host.iobroker-master Caught by controller[0]:     at Sender.flush (/opt/iobroker/node_modules/ws/lib/Sender.js:268:3)
2019-10-15 13:42:20.331  - info: host.iobroker-master instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
2019-10-15 13:42:20.333  - info: host.iobroker-master Restart adapter system.adapter.admin.0 because enabled
2019-10-15 13:42:20.340  - debug: harmony.0 (388) system.adapter.admin.0: logging false
2019-10-15 13:42:49.810  - info: tankerkoenig.0 (2155) Reading data from tankerkoenig ...
2019-10-15 13:42:50.388  - info: host.iobroker-master instance system.adapter.admin.0 started with pid 27743
2019-10-15 13:43:00.021  - info: host.iobroker-master instance system.adapter.daswetter.0 started with pid 28216
2019-10-15 13:43:09.649  - info: host.iobroker-master instance system.adapter.daswetter.0 terminated with code 0 (NO_ERROR)

Keine neue States da:

apollon77

@darkiop in dem Fall ist Admin gestorben weil sich irgendwie Dinge aufgestaut haben und Admin restartet. Ggf fehlen dadurch Daten? Lad im browser mal neu. Jetzt fehlende States da?

Ansonsten hat sich der iobroker aber wieder gefangen mit der Version oder?!

apollon77

@darkiop Aahhh noch eine Frage: du hast nur States im redis, korrekt?

darkiop

Ok, zweiter Test - jetzt ohne den admin.0 crash ....

der Master ist wieder auf den Beinen, der Slave hat es aber nicht geschaft. stop/start aufm Slave und er ist wieder verbunden.

Puffert der controller auch Logs? Die 3 hier sind eigentlich entstanden während redis weg war, geschrieben wurden sie nach dem redis wieder da war:

2019-10-15 14:00:00.786  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 31.8 | Licht wird nicht geschaltet. +++
2019-10-15 14:00:01.180  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 32.6 | Licht wird nicht geschaltet. +++
2019-10-15 14:00:01.523  - info: javascript.0 (618) script.js.PRODUKTIV.Beleuchtung.01_Bewegungsmelder_Flur: +++ Bewegung im Flur. Helligkeitsschwelle bei < 10 | Aktuelle Helligkeit: 32.6 | Licht wird nicht geschaltet. +++

Edit:

So lange war redis weg:

Community Forum

NEWS

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

Testfall 1:

Testfall 2:

Testfall 3:

Testfall 4:

Support us

565

32.4k

81.4k

1.3m