Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum
donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test js-controller v2.0.x (GitHub)

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.4k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.0k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.6k

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

Geplant Angeheftet Gesperrt Verschoben Tester
js-controller
1.0k Beiträge 48 Kommentatoren 315.4k Aufrufe 35 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • D Online
    D Online
    darkiop
    Most Active
    schrieb am zuletzt editiert von
    #780

    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

    Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

    1 Antwort Letzte Antwort
    0
    • D Online
      D Online
      darkiop
      Most Active
      schrieb am zuletzt editiert von
      #781

      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

      Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

      1 Antwort Letzte Antwort
      0
      • D Online
        D Online
        darkiop
        Most Active
        schrieb am zuletzt editiert von
        #782

        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

        Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

        1 Antwort Letzte Antwort
        0
        • D Online
          D Online
          darkiop
          Most Active
          schrieb am zuletzt editiert von darkiop
          #783

          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!

          9d6934f0-bc1c-4b95-99fe-2c5f4222c80a-grafik.png

          Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

          1 Antwort Letzte Antwort
          0
          • D 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]
╰─>#

            apollon77A Online
            apollon77A Online
            apollon77
            schrieb am zuletzt editiert von
            #784

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

            Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

            • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
            • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
            1 Antwort Letzte Antwort
            0
            • apollon77A Online
              apollon77A Online
              apollon77
              schrieb am zuletzt editiert von
              #785

              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 :-)

              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
              D 1 Antwort Letzte Antwort
              0
              • apollon77A 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 :-)
                D Online
                D Online
                darkiop
                Most Active
                schrieb am zuletzt editiert von darkiop
                #786

                @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:

                8c13e0ad-b485-4464-b5b5-2fb9bf9a6f8e-grafik.png

                Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                apollon77A 2 Antworten Letzte Antwort
                0
                • D 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:

                  8c13e0ad-b485-4464-b5b5-2fb9bf9a6f8e-grafik.png

                  apollon77A Online
                  apollon77A Online
                  apollon77
                  schrieb am zuletzt editiert von
                  #787

                  @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?!

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  1 Antwort Letzte Antwort
                  0
                  • D 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:

                    8c13e0ad-b485-4464-b5b5-2fb9bf9a6f8e-grafik.png

                    apollon77A Online
                    apollon77A Online
                    apollon77
                    schrieb am zuletzt editiert von
                    #788

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

                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                    D 1 Antwort Letzte Antwort
                    0
                    • D Online
                      D Online
                      darkiop
                      Most Active
                      schrieb am zuletzt editiert von darkiop
                      #789

                      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.

                      c96f9e81-1b16-4465-afaa-d74b44acdc4c-grafik.png

                      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:

                      d57fbaeb-9e0a-49d0-bf9d-53f79fde46ad-grafik.png

                      Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                      apollon77A 1 Antwort Letzte Antwort
                      0
                      • apollon77A apollon77

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

                        D Online
                        D Online
                        darkiop
                        Most Active
                        schrieb am zuletzt editiert von
                        #790

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

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

                        Ja.

                        Proxmox-ioBroker-Redis-HA Doku: https://forum.iobroker.net/topic/47478/dokumentation-einer-proxmox-iobroker-redis-ha-umgebung

                        1 Antwort Letzte Antwort
                        0
                        • apollon77A apollon77

                          @smartboart mehr log bitte

                          smartboartS Offline
                          smartboartS Offline
                          smartboart
                          schrieb am zuletzt editiert von
                          #791

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

                          @smartboart mehr log bitte

                          gerne


                          2019-10-14 19:36:28.810 - info: host.ioBroker-Rock Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
                          2019-10-14 19:37:21.257 - info: host.ioBroker-Rock iobroker upgrade statistics
                          2019-10-14 19:37:23.968 - info: host.ioBroker-Rock iobroker Update statistics from @0.2.0 to @0.2.2
                          2019-10-14 19:37:25.117 - info: host.ioBroker-Rock iobroker NPM version: 6.9.0npm install iobroker.statistics@0.2.2 --loglevel error --production --save --prefix "/opt/iobroker" (System call)
                          2019-10-14 19:39:04.319 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Integer; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:29:66: warning: ‘v8::Local v8::Value::ToInteger() const’ is deprecated: Use maybe version [-Wdeprecated-declarations] To(v8::Handle i) { return i->ToInteger(); } ^
                          2019-10-14 19:39:04.321 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:10052:16: note: declared here Local Value::ToInteger() const { ^In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Int32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:34:64: error: no matching function for call to ‘v8::Integer::ToInt32()’ To(v8::Handle i) { return i->ToInt32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate: v8::MaybeLocal v8::Value::ToInt32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToInt32(Local context) const; ^/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate expects 1 argument, 0 providedIn file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate: v8::Local v8::Value::ToInt32(v8::Isolate*) const Local ToInt32(Isolate* isolate) 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))) ^~~~~~~~
                          2019-10-14 19:39:04.324 - info: host.ioBroker-Rock iobroker /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate expects 1 argument, 0 provided Local ToInt32(Isolate* isolate) 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))) ^~~~~~~~~~
                          2019-10-14 19:39:04.327 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Uint32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:39:65: error: no matching function for call to ‘v8::Integer::ToUint32()’ To(v8::Handle i) { return i->ToUint32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate: v8::MaybeLocal v8::Value::ToUint32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToUint32( ^~/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate expects 1 argument, 0 provided
                          2019-10-14 19:39:04.349 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(bool)’:../node_modules/nan/nan_implementation_12_inl.h:49:38: error: no matching function for call to ‘v8::BooleanObject::New(bool&)’ return v8::BooleanObject::New(value).As(); ^
                          2019-10-14 19:39:04.352 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate: static v8::Local v8::BooleanObject::New(v8::Isolate*, bool) static Local New(Isolate* isolate, bool value); ^                          /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate expects 2 arguments, 1 providedIn file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h:49:60: error: expected primary-expression before ‘>’ token return v8::BooleanObject::New(value).As(); ^../node_modules/nan/nan_implementation_12_inl.h:49:62: error: expected primary-expression before ‘)’ token return v8::BooleanObject::New(value).As(); ^
                          2019-10-14 19:39:04.371 - info: host.ioBroker-Rock iobroker ../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Handle, v8::RegExp::Flags)’:../node_modules/nan/nan_implementation_12_inl.h:158:40: warning: ‘static v8::Local v8::RegExp::New(v8::Local, v8::RegExp::Flags)’ is deprecated: Use maybe version [-Wdeprecated-declarations] return v8::RegExp::New(pattern, flags); ^
                          2019-10-14 19:39:04.373 - info: host.ioBroker-Rock iobroker In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5110:38: note: declared here Local New(Local pattern, Flags flags)); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^                          ~~~~~
                          2019-10-14 19:39:04.378 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Local)’:../node_modules/nan/nan_implementation_12_inl.h:166:69: error: no matching function for call to ‘v8::ScriptCompiler::Compile(v8::Isolate*, v8::ScriptCompiler::Source*)’ return v8::ScriptCompiler::Compile(v8::Isolate::GetCurrent(), &src); ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:1510:51: note: candidate: static v8::MaybeLocal v8::ScriptCompiler::Compile(v8::Local, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions, v8::ScriptCompiler::NoCacheReason) static V8_WARN_UNUSED_RESULT MaybeLocal

                          apollon77A 1 Antwort Letzte Antwort
                          0
                          • smartboartS Offline
                            smartboartS Offline
                            smartboart
                            schrieb am zuletzt editiert von smartboart
                            #792

                            Mir ist noch was aufgefallen. Hab für den fullybrowser nen Chron Job im Admin angelegt.
                            Alle 4 Stunden neustarten.... Der Log sieht dann so aus. Ist der einzige adapter mit nem Chron job bei mir..


                            host.ioBroker-Rock 2019-10-15 12:56:00.433 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                            host.ioBroker-Rock 2019-10-15 12:55:01.467 info instance system.adapter.fullybrowser.0 started with pid 28554
                            host.ioBroker-Rock 2019-10-15 12:55:00.449 info Restart adapter system.adapter.fullybrowser.0 because enabled
                            host.ioBroker-Rock 2019-10-15 12:55:00.443 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                            host.ioBroker-Rock 2019-10-15 12:54:01.492 info instance system.adapter.fullybrowser.0 started with pid 27182
                            host.ioBroker-Rock 2019-10-15 12:54:00.446 info Restart adapter system.adapter.fullybrowser.0 because enabled
                            host.ioBroker-Rock 2019-10-15 12:54:00.446 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                            host.ioBroker-Rock 2019-10-15 12:53:01.526 info instance system.adapter.fullybrowser.0 started with pid 25634
                            host.ioBroker-Rock 2019-10-15 12:53:00.508 info Restart adapter system.adapter.fullybrowser.0 because enabled
                            host.ioBroker-Rock 2019-10-15 12:53:00.507 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                            host.ioBroker-Rock 2019-10-15 12:52:01.455 info instance system.adapter.fullybrowser.0 started with pid 24280
                            host.ioBroker-Rock 2019-10-15 12:52:00.435 info Restart adapter system.adapter.fullybrowser.0 because enabled
                            host.ioBroker-Rock 2019-10-15 12:52:00.434 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                            host.ioBroker-Rock 2019-10-15 12:51:01.458 info instance system.adapter.fullybrowser.0 started with pid 22758
                            host.ioBroker-Rock 2019-10-15 12:51:00.441 info Restart adapter system.adapter.fullybrowser.0 because enabled
                            host.ioBroker-Rock 2019-10-15 12:51:00.440 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)

                            apollon77A 1 Antwort Letzte Antwort
                            0
                            • smartboartS smartboart

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

                              @smartboart mehr log bitte

                              gerne


                              2019-10-14 19:36:28.810 - info: host.ioBroker-Rock Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
                              2019-10-14 19:37:21.257 - info: host.ioBroker-Rock iobroker upgrade statistics
                              2019-10-14 19:37:23.968 - info: host.ioBroker-Rock iobroker Update statistics from @0.2.0 to @0.2.2
                              2019-10-14 19:37:25.117 - info: host.ioBroker-Rock iobroker NPM version: 6.9.0npm install iobroker.statistics@0.2.2 --loglevel error --production --save --prefix "/opt/iobroker" (System call)
                              2019-10-14 19:39:04.319 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Integer; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:29:66: warning: ‘v8::Local v8::Value::ToInteger() const’ is deprecated: Use maybe version [-Wdeprecated-declarations] To(v8::Handle i) { return i->ToInteger(); } ^
                              2019-10-14 19:39:04.321 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:10052:16: note: declared here Local Value::ToInteger() const { ^In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Int32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:34:64: error: no matching function for call to ‘v8::Integer::ToInt32()’ To(v8::Handle i) { return i->ToInt32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate: v8::MaybeLocal v8::Value::ToInt32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToInt32(Local context) const; ^/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2437:43: note: candidate expects 1 argument, 0 providedIn file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate: v8::Local v8::Value::ToInt32(v8::Isolate*) const Local ToInt32(Isolate* isolate) 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))) ^~~~~~~~
                              2019-10-14 19:39:04.324 - info: host.ioBroker-Rock iobroker /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2450:30: note: candidate expects 1 argument, 0 provided Local ToInt32(Isolate* isolate) 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))) ^~~~~~~~~~
                              2019-10-14 19:39:04.327 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan.h:82:0, from ../src/bufferutil.cc:16:../node_modules/nan/nan_new.h: In function ‘v8::Local NanIntern::To(v8::Handle) [with T = v8::Uint32; v8::Handle = v8::Local]’:../node_modules/nan/nan_new.h:39:65: error: no matching function for call to ‘v8::Integer::ToUint32()’ To(v8::Handle i) { return i->ToUint32(); } ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate: v8::MaybeLocal v8::Value::ToUint32(v8::Local) const V8_WARN_UNUSED_RESULT MaybeLocal ToUint32( ^~/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:2435:44: note: candidate expects 1 argument, 0 provided
                              2019-10-14 19:39:04.349 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(bool)’:../node_modules/nan/nan_implementation_12_inl.h:49:38: error: no matching function for call to ‘v8::BooleanObject::New(bool&)’ return v8::BooleanObject::New(value).As(); ^
                              2019-10-14 19:39:04.352 - info: host.ioBroker-Rock iobroker In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate: static v8::Local v8::BooleanObject::New(v8::Isolate*, bool) static Local New(Isolate* isolate, bool value); ^                              /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5035:23: note: candidate expects 2 arguments, 1 providedIn file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h:49:60: error: expected primary-expression before ‘>’ token return v8::BooleanObject::New(value).As(); ^../node_modules/nan/nan_implementation_12_inl.h:49:62: error: expected primary-expression before ‘)’ token return v8::BooleanObject::New(value).As(); ^
                              2019-10-14 19:39:04.371 - info: host.ioBroker-Rock iobroker ../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Handle, v8::RegExp::Flags)’:../node_modules/nan/nan_implementation_12_inl.h:158:40: warning: ‘static v8::Local v8::RegExp::New(v8::Local, v8::RegExp::Flags)’ is deprecated: Use maybe version [-Wdeprecated-declarations] return v8::RegExp::New(pattern, flags); ^
                              2019-10-14 19:39:04.373 - info: host.ioBroker-Rock iobroker In file included from /home/iobroker/.node-gyp/10.16.3/include/node/v8.h:26:0, from ../src/bufferutil.cc:7:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:5110:38: note: declared here Local New(Local pattern, Flags flags)); ^/home/iobroker/.node-gyp/10.16.3/include/node/v8config.h:324:3: note: in definition of macro ‘V8_DEPRECATED’ declarator attribute((deprecated(message))) ^                              ~~~~~
                              2019-10-14 19:39:04.378 - info: host.ioBroker-Rock iobroker In file included from ../node_modules/nan/nan_new.h:189:0, from ../node_modules/nan/nan.h:82, from ../src/bufferutil.cc:16:../node_modules/nan/nan_implementation_12_inl.h: In static member function ‘static NanIntern::FactoryBase::return_t NanIntern::Factory::New(v8::Local)’:../node_modules/nan/nan_implementation_12_inl.h:166:69: error: no matching function for call to ‘v8::ScriptCompiler::Compile(v8::Isolate*, v8::ScriptCompiler::Source*)’ return v8::ScriptCompiler::Compile(v8::Isolate::GetCurrent(), &src); ^In file included from ../src/bufferutil.cc:7:0:/home/iobroker/.node-gyp/10.16.3/include/node/v8.h:1510:51: note: candidate: static v8::MaybeLocal v8::ScriptCompiler::Compile(v8::Local, v8::ScriptCompiler::Source*, v8::ScriptCompiler::CompileOptions, v8::ScriptCompiler::NoCacheReason) static V8_WARN_UNUSED_RESULT MaybeLocal

                              apollon77A Online
                              apollon77A Online
                              apollon77
                              schrieb am zuletzt editiert von
                              #793

                              @smartboart denke alles nur Warnungen.

                              Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                              • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                              • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                              smartboartS 1 Antwort Letzte Antwort
                              0
                              • smartboartS smartboart

                                Mir ist noch was aufgefallen. Hab für den fullybrowser nen Chron Job im Admin angelegt.
                                Alle 4 Stunden neustarten.... Der Log sieht dann so aus. Ist der einzige adapter mit nem Chron job bei mir..


                                host.ioBroker-Rock 2019-10-15 12:56:00.433 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                host.ioBroker-Rock 2019-10-15 12:55:01.467 info instance system.adapter.fullybrowser.0 started with pid 28554
                                host.ioBroker-Rock 2019-10-15 12:55:00.449 info Restart adapter system.adapter.fullybrowser.0 because enabled
                                host.ioBroker-Rock 2019-10-15 12:55:00.443 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                host.ioBroker-Rock 2019-10-15 12:54:01.492 info instance system.adapter.fullybrowser.0 started with pid 27182
                                host.ioBroker-Rock 2019-10-15 12:54:00.446 info Restart adapter system.adapter.fullybrowser.0 because enabled
                                host.ioBroker-Rock 2019-10-15 12:54:00.446 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                host.ioBroker-Rock 2019-10-15 12:53:01.526 info instance system.adapter.fullybrowser.0 started with pid 25634
                                host.ioBroker-Rock 2019-10-15 12:53:00.508 info Restart adapter system.adapter.fullybrowser.0 because enabled
                                host.ioBroker-Rock 2019-10-15 12:53:00.507 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                host.ioBroker-Rock 2019-10-15 12:52:01.455 info instance system.adapter.fullybrowser.0 started with pid 24280
                                host.ioBroker-Rock 2019-10-15 12:52:00.435 info Restart adapter system.adapter.fullybrowser.0 because enabled
                                host.ioBroker-Rock 2019-10-15 12:52:00.434 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                host.ioBroker-Rock 2019-10-15 12:51:01.458 info instance system.adapter.fullybrowser.0 started with pid 22758
                                host.ioBroker-Rock 2019-10-15 12:51:00.441 info Restart adapter system.adapter.fullybrowser.0 because enabled
                                host.ioBroker-Rock 2019-10-15 12:51:00.440 error instance system.adapter.fullybrowser.0 terminated with code 156 (156)

                                apollon77A Online
                                apollon77A Online
                                apollon77
                                schrieb am zuletzt editiert von
                                #794

                                @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.

                                Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                smartboartS 1 Antwort Letzte Antwort
                                0
                                • D 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.

                                  c96f9e81-1b16-4465-afaa-d74b44acdc4c-grafik.png

                                  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:

                                  d57fbaeb-9e0a-49d0-bf9d-53f79fde46ad-grafik.png

                                  apollon77A Online
                                  apollon77A Online
                                  apollon77
                                  schrieb am zuletzt editiert von
                                  #795

                                  @darkiop hast du hier bitte das Slave log komplett von dem Zeitraum?

                                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                  D 1 Antwort Letzte Antwort
                                  0
                                  • apollon77A apollon77

                                    @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.

                                    smartboartS Offline
                                    smartboartS Offline
                                    smartboart
                                    schrieb am zuletzt editiert von smartboart
                                    #796

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

                                    @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.
                                    ja sehr sicher...

                                    Das ist jadas verwunderliche...noch dazu der Fehler.
                                    instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                    Unbenannt.JPG

                                    J 1 Antwort Letzte Antwort
                                    0
                                    • smartboartS smartboart

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

                                      @smartboart sicher das es 4 stündlich ist? Das siehe eher nach minütlich aus.
                                      ja sehr sicher...

                                      Das ist jadas verwunderliche...noch dazu der Fehler.
                                      instance system.adapter.fullybrowser.0 terminated with code 156 (156)
                                      Unbenannt.JPG

                                      J Offline
                                      J Offline
                                      Jan1
                                      schrieb am zuletzt editiert von
                                      #797

                                      @smartboart
                                      das ist alle 4 Stunden jede Minute

                                      smartboartS 1 Antwort Letzte Antwort
                                      0
                                      • J Jan1

                                        @smartboart
                                        das ist alle 4 Stunden jede Minute

                                        smartboartS Offline
                                        smartboartS Offline
                                        smartboart
                                        schrieb am zuletzt editiert von
                                        #798

                                        @Jan1 oh ok..ich glaube ich sollte mich nochmal mit den Chron Zeiten auseinanderstzen..Danke!!!

                                        1 Antwort Letzte Antwort
                                        0
                                        • apollon77A apollon77

                                          @smartboart denke alles nur Warnungen.

                                          smartboartS Offline
                                          smartboartS Offline
                                          smartboart
                                          schrieb am zuletzt editiert von
                                          #799

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

                                          @smartboart denke alles nur Warnungen.

                                          ok danke..hab ich mir gedacht, macht auch keine Probleme. Wenn du oder sonst wer dennoch ne Idee hat wie man diese gyp und nan Warnungen abstellt, gerne her damit.....

                                          smartboartS 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          932

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden
                                          • Du hast noch kein Konto? Registrieren
                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Home
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe