Skip to content
  • Home
  • Recent
  • Tags
  • 0 Unread 0
  • Categories
  • Unreplied
  • Popular
  • 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
  • Default (No Skin)
  • No Skin
Collapse
ioBroker Logo

Community Forum
donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Beta Test js-controller 3.0.x auf GitHub

NEWS

  • Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨
    BluefoxB
    Bluefox
    16
    1
    1.7k
  • Neuer Blogbeitrag: Monatsrückblick - Dezember 2025 🎄
    BluefoxB
    Bluefox
    13
    1
    880
  • Weihnachtsangebot 2025! 🎄
    BluefoxB
    Bluefox
    25
    1
    2.1k

Beta Test js-controller 3.0.x auf GitHub

Scheduled Pinned Locked Moved Tester
js-controller
416 Posts 39 Posters 74.5k Views 38 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Kueppert

    Hi @apollon77 ich habe das neuen Rebuild-Kommando mal für Zigbee ausgeführt. Habe folgenden Output erhalten. Gehört das hier her oder zum Adapter?

    root@ioBroker2:/opt/iobroker# iobroker stop
root@ioBroker2:/opt/iobroker# iobroker rebuild zigbee
npm rebuild --loglevel error (System call) in "/opt/iobroker/node_modules/iobroker.zigbee"
In file included from ../src/./serialport.h:6,
                 from ../src/serialport.cpp:1:
../../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:78:69: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                                                                     ^~~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:135:71: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                                                                       ^~~~~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:175:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                                                                      ^~~~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:215:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                                                                      ^~~~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:270:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                                                                    ^~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:314:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                                                                    ^~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:363:76: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                                                                            ^~~~~~~~~~~~~~~~~~~~
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:409:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
   uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                                                                      ^~~~~~~~~~~~~~
../src/serialport.cpp: At global scope:
../src/serialport.cpp:430:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
 SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                            ^
../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
 SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                              ^
In file included from ../../../nan/nan.h:54,
                 from ../src/./serialport.h:6,
                 from ../src/serialport.cpp:1:
/home/iobroker/.cache/node-gyp/13.12.0/include/node/node.h:618:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
       (node::addon_register_func) (regfunc),                          \
                                           ^
/home/iobroker/.cache/node-gyp/13.12.0/include/node/node.h:652:3: note: in expansion of macro ‘NODE_MODULE_X’
   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
   ^~~~~~~~~~~~~
../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’
 NODE_MODULE(serialport, init);
 ^~~~~~~~~~~
In file included from ../src/serialport.h:6,
                 from ../src/serialport_unix.cpp:2:
../../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                              ^
../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’:
../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=]
     snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
                                                            ^~~~~~~~~~~~~~~~~~~~~~~~~
../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024
     snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’:
../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=]
     snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
                                                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024
     snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
     ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ../src/poller.cpp:1:
../../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:
../../../nan/nan.h:2298:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)
                                                              ^

    Ich erkenne aus den Meldungen nur, dass irgendwas nicht funbktioniert hat?
    Danke dir und vG, Thorsten

    PS: der Vollständigkeit halber auch Befehl Nr. 2:

    root@ioBroker2:/opt/iobroker# iobroker rebuild zigbee --install
npm install --loglevel error --production (System call) in "/opt/iobroker/node_modules/iobroker.zigbee"

Rebuild zigbee done

    Der sah besser aus :)

    apollon77A Offline
    apollon77A Offline
    apollon77
    wrote on last edited by
    #226

    @Kueppert Das andere waren auch nur warnungen. Aber mit dem --install scheint es teilweise besser zu tun. Wir hatten schon Fälle wo das eine besser war und manchmal das andere. Die gründe aufzuführen wäre recht technisch ;-) Daher haben wir einfach beides gebaut

    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 Reply Last reply
    0
    • apollon77A Offline
      apollon77A Offline
      apollon77
      wrote on last edited by
      #227

      Nach zwei Sentry Crash Reports habe ich hier die 3.0.9 Aka Latest RC2 für Euch auf Github:

      3.0.9 (2020-04-15) Release Elena

      • (Apollon77) fix reported crash on obsolete object deletion (Sentry IOBROKER-JS-CONTROLLER-8)
      • (Apollon77) fix reported crash when a new process can not be started because of ENOMEM (Sentry IOBROKER-JS-CONTROLLER-7)
      • (foxriver76) make sure errors are return the same in two places

      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
      K ? 2 Replies Last reply
      1
      • apollon77A apollon77

        Nach zwei Sentry Crash Reports habe ich hier die 3.0.9 Aka Latest RC2 für Euch auf Github:

        3.0.9 (2020-04-15) Release Elena

        • (Apollon77) fix reported crash on obsolete object deletion (Sentry IOBROKER-JS-CONTROLLER-8)
        • (Apollon77) fix reported crash when a new process can not be started because of ENOMEM (Sentry IOBROKER-JS-CONTROLLER-7)
        • (foxriver76) make sure errors are return the same in two places
        K Offline
        K Offline
        Kueppert
        wrote on last edited by
        #228

        @apollon77 Update lief problemlos durch - mit folgenden Befehlszeilen (auch für alle, die sich mit dem Verzeichnis schwer tun nochmal zur Erinnerung):

        cd /opt/iobroker
iobroker stop
npm install ioBroker/ioBroker.js-controller

        (ggf. sudo nutzen, wenn man nicht mit root-Rechten unterwegs ist)

        UDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+

        1 Reply Last reply
        1
        • apollon77A apollon77

          Nach zwei Sentry Crash Reports habe ich hier die 3.0.9 Aka Latest RC2 für Euch auf Github:

          3.0.9 (2020-04-15) Release Elena

          • (Apollon77) fix reported crash on obsolete object deletion (Sentry IOBROKER-JS-CONTROLLER-8)
          • (Apollon77) fix reported crash when a new process can not be started because of ENOMEM (Sentry IOBROKER-JS-CONTROLLER-7)
          • (foxriver76) make sure errors are return the same in two places
          ? Offline
          ? Offline
          A Former User
          wrote on last edited by
          #229

          @apollon77 Hi,
          die 3.09 wirft recht häufig das hier raus, die Adapter stehen dann auf rot:

          host.iobroker 2020-04-15 10:24:00.018 error instance system.adapter.freifunk.0 could not be started: Error: spawn ENOMEM
          host.iobroker 2020-04-15 10:23:58.590 error instance system.adapter.enigma2.0 could not be started: Error: spawn ENOMEM

          Betrifft auch Socketio, mihome-vacuum Adapter...

          K ? apollon77A 3 Replies Last reply
          0
          • ? A Former User

            @apollon77 Hi,
            die 3.09 wirft recht häufig das hier raus, die Adapter stehen dann auf rot:

            host.iobroker 2020-04-15 10:24:00.018 error instance system.adapter.freifunk.0 could not be started: Error: spawn ENOMEM
            host.iobroker 2020-04-15 10:23:58.590 error instance system.adapter.enigma2.0 could not be started: Error: spawn ENOMEM

            Betrifft auch Socketio, mihome-vacuum Adapter...

            K Offline
            K Offline
            Kueppert
            wrote on last edited by Kueppert
            #230

            @ilovegym hm...ich habe nur den MiHome-Vacuum, der läuft bei mir. Hab nur ein zwei warns gehabt:

            mihome-vacuum.0	2020-04-15 10:26:14.963	info	(24740) create state for carpet_mode
mihome-vacuum.0	2020-04-15 10:26:13.437	info	(24740) set nächster Timer: Nicht verfügbar
mihome-vacuum.0	2020-04-15 10:26:13.007	info	(24740) Connected
mihome-vacuum.0	2020-04-15 10:26:12.968	info	(24740) connecting, this can take up to 10 minutes ...
mihome-vacuum.0	2020-04-15 10:26:12.967	warn	(24740) Time difference between Mihome Vacuum and ioBroker: 1 sec
mihome-vacuum.0	2020-04-15 10:26:12.955	info	(24740) New generation or new fw(3.5.4,004004) detected, create new states goto and zoneclean
mihome-vacuum.0	2020-04-15 10:26:12.912	info	(24740) Create state clean_home for controlling by cloud adapter
mihome-vacuum.0	2020-04-15 10:26:12.910	info	(24740) Expert mode disabled, states deleted
mihome-vacuum.0	2020-04-15 10:26:12.860	info	(24740) starting. Version 2.0.9-RC07 in /opt/iobroker/node_modules/iobroker.mihome-vacuum, node: v13.12.0, js-controller: 3.0.9
mihome-vacuum.0	2020-04-15 10:26:12.121	warn	(24740) This object will not be created in future versions. Please report this to the developer.
mihome-vacuum.0	2020-04-15 10:26:12.119	warn	(24740) Object mihome-vacuum.0.info.dnd is invalid: obj.common.type has an invalid value (switch) but has to be one of number, string, boolean, array, object, mixed, file, json

            socketio läuft ohne Auffälligkeiten bei mir.

            UDM Pro, Intel NUC - ioBroker in Proxmox-VM, PiHole+Grafana&Influx+TasmoAdmin in LXCs, Raspberry Pi3 (als CCU), Zigbee-Stick Sonoff, Synology DS918+

            1 Reply Last reply
            0
            • ? A Former User

              @apollon77 Hi,
              die 3.09 wirft recht häufig das hier raus, die Adapter stehen dann auf rot:

              host.iobroker 2020-04-15 10:24:00.018 error instance system.adapter.freifunk.0 could not be started: Error: spawn ENOMEM
              host.iobroker 2020-04-15 10:23:58.590 error instance system.adapter.enigma2.0 could not be started: Error: spawn ENOMEM

              Betrifft auch Socketio, mihome-vacuum Adapter...

              ? Offline
              ? Offline
              A Former User
              wrote on last edited by
              #231

              @ilovegym sagte in Beta Test js-controller 3.0.x auf GitHub:

              @apollon77 Hi,
              die 3.09 wirft recht häufig das hier raus, die Adapter stehen dann auf rot:

              host.iobroker 2020-04-15 10:24:00.018 error instance system.adapter.freifunk.0 could not be started: Error: spawn ENOMEM
              host.iobroker 2020-04-15 10:23:58.590 error instance system.adapter.enigma2.0 could not be started: Error: spawn ENOMEM

              Betrifft auch Socketio, mihome-vacuum Adapter...

              Reboot tat gut... danach war ruhe.. bis auf jede Menge warnings vom Socketio.. und web Adapter:

              web.0 2020-04-15 10:49:56.703 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"
              web.0 2020-04-15 10:49:54.612 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"
              web.0 2020-04-15 10:49:46.704 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"
              web.0 2020-04-15 10:49:44.372 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"

              apollon77A 1 Reply Last reply
              0
              • apollon77A apollon77

                @Homer-J Yahka 0.11.0 muss auch mit nodejs12 tun!

                Homer.J.H Offline
                Homer.J.H Offline
                Homer.J.
                wrote on last edited by Homer.J.
                #232

                @apollon77 läuft zwar ich kann aber nichts schalten es reagiert nichts. Bin auch erstmal wieder zurück auf die 10.20.1 Version.
                Hab mal auf die 3.0.9 hochgezogen und die node.js 12... Installiert jetzt läuft es warum auch immer.

                apollon77A 2 Replies Last reply
                0
                • apollon77A apollon77

                  @e-i-k-e Welche js-controller Version ist im Einsatz? Laut Log kam das vor als es noch die 2.2.9 war. Dann ab 17:47:49.463 war es der 3.0.8er controller und da gabs das nimmer. oder sehe ich was falsch?

                  E Offline
                  E Offline
                  e-i-k-e
                  wrote on last edited by e-i-k-e
                  #233

                  @apollon77
                  Gut möglich, jetzt läuft die 3.0.8er.
                  Anbei ein Auszug aus dem log, nachdem ich versucht habe diesen neu zu starten..

                  js.JPG

                  Slave:

                  2020-04-15 11:26:18.431  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 (force=false, process=true)
2020-04-15 11:26:18.436  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 send kill signal
2020-04-15 11:26:19.440  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 killing pid 27154
2020-04-15 11:26:21.611  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7635
2020-04-15 11:26:27.195  - error: javascript.2 (7635) javascript.2 already running
2020-04-15 11:26:27.201  - warn: javascript.2 (7635) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:26:28.455  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:26:28.456  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:26:58.472  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7696
2020-04-15 11:27:02.372  - info: javascript.2 (27154) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:27:03.439  - error: javascript.2 (7696) javascript.2 already running
2020-04-15 11:27:03.446  - warn: javascript.2 (7696) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:27:04.718  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:27:04.719  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:27:34.735  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7769
2020-04-15 11:27:39.805  - info: javascript.2 (7769) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
2020-04-15 11:27:40.039  - info: javascript.2 (7769) requesting all states
2020-04-15 11:27:40.044  - info: javascript.2 (7769) requesting all objects
2020-04-15 11:27:40.045  - warn: javascript.2 (7769) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2020-04-15 11:27:43.854  - info: javascript.2 (7769) received all objects
2020-04-15 11:27:46.488  - info: javascript.2 (7769) received all states
2020-04-15 11:27:47.519  - info: javascript.2 (7769) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:27:47.690  - info: javascript.2 (7769) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
2020-04-15 11:28:01.522  - info: javascript.2 (27154) Got terminate signal TERMINATE_YOURSELF
2020-04-15 11:28:01.523  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:28:01.524  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7635 vs own PID 27154
2020-04-15 11:28:01.525  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:28:01.526  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7696 vs own PID 27154
2020-04-15 11:29:05.133  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:29:05.135  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7769 vs own PID 27154
2020-04-15 11:29:05.153  - info: javascript.2 (27154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-04-15 11:30:07.086  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-04-15 11:30:07.088  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:30:08.121  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 8043
2020-04-15 11:30:10.498  - warn: javascript.2 (7769) Got terminate signal. Checking desired PID: 0 vs own PID 7769
2020-04-15 11:30:10.503  - info: javascript.2 (7769) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:30:10.506  - warn: javascript.2 (7769) Got terminate signal. Checking desired PID: 8043 vs own PID 7769
2020-04-15 11:30:10.521  - info: javascript.2 (7769) terminating
2020-04-15 11:30:10.522  - info: javascript.2 (7769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-04-15 11:30:13.072  - error: javascript.2 (8043) javascript.2 already running
2020-04-15 11:30:13.078  - warn: javascript.2 (8043) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:30:14.213  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:30:14.214  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:30:44.227  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 8116
2020-04-15 11:30:49.289  - info: javascript.2 (8116) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
2020-04-15 11:30:49.447  - info: javascript.2 (8116) requesting all states
2020-04-15 11:30:49.451  - info: javascript.2 (8116) requesting all objects
2020-04-15 11:30:49.453  - warn: javascript.2 (8116) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2020-04-15 11:30:53.281  - info: javascript.2 (8116) received all objects
2020-04-15 11:30:55.801  - info: javascript.2 (8116) received all states
2020-04-15 11:30:56.851  - info: javascript.2 (8116) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:30:57.000  - info: javascript.2 (8116) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
2020-04-15 11:31:04.118  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-04-15 11:31:04.119  - info: host.raspberrypi-display1 Do not restart adapter system.adapter.javascript.2 because desired by instance

                  Master:

                  javascript.2	2020-04-15 11:30:57.000	info	(8116) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
javascript.2	2020-04-15 11:30:56.851	info	(8116) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:30:55.801	info	(8116) received all states
javascript.2	2020-04-15 11:30:53.281	info	(8116) received all objects
javascript.2	2020-04-15 11:30:49.453	warn	(8116) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
javascript.2	2020-04-15 11:30:49.451	info	(8116) requesting all objects
javascript.2	2020-04-15 11:30:49.447	info	(8116) requesting all states
javascript.2	2020-04-15 11:30:49.289	info	(8116) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
javascript.2	2020-04-15 11:30:13.078	warn	(8043) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:30:13.072	error	(8043) javascript.2 already running
javascript.2	2020-04-15 11:30:10.522	info	(7769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
javascript.2	2020-04-15 11:30:10.521	info	(7769) terminating
javascript.2	2020-04-15 11:30:10.506	warn	(7769) Got terminate signal. Checking desired PID: 8043 vs own PID 7769
javascript.2	2020-04-15 11:30:10.503	info	(7769) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:30:10.498	warn	(7769) Got terminate signal. Checking desired PID: 0 vs own PID 7769
javascript.2	2020-04-15 11:29:05.153	info	(27154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
javascript.2	2020-04-15 11:29:05.135	warn	(27154) Got terminate signal. Checking desired PID: 7769 vs own PID 27154
javascript.2	2020-04-15 11:29:05.133	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.526	warn	(27154) Got terminate signal. Checking desired PID: 7696 vs own PID 27154
javascript.2	2020-04-15 11:28:01.525	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.524	warn	(27154) Got terminate signal. Checking desired PID: 7635 vs own PID 27154
javascript.2	2020-04-15 11:28:01.523	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.522	info	(27154) Got terminate signal TERMINATE_YOURSELF
javascript.2	2020-04-15 11:27:47.690	info	(7769) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
javascript.2	2020-04-15 11:27:47.519	info	(7769) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:27:46.488	info	(7769) received all states
javascript.2	2020-04-15 11:27:43.854	info	(7769) received all objects
javascript.2	2020-04-15 11:27:40.045	warn	(7769) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
javascript.2	2020-04-15 11:27:40.044	info	(7769) requesting all objects
javascript.2	2020-04-15 11:27:40.039	info	(7769) requesting all states
javascript.2	2020-04-15 11:27:39.805	info	(7769) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
javascript.2	2020-04-15 11:27:03.446	warn	(7696) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:27:03.439	error	(7696) javascript.2 already running
javascript.2	2020-04-15 11:27:02.372	info	(27154) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:26:27.201	warn	(7635) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:26:27.195	error	(7635) javascript.2 already running
                  1 Reply Last reply
                  0
                  • apollon77A apollon77

                    @e-i-k-e Welche js-controller Version ist im Einsatz? Laut Log kam das vor als es noch die 2.2.9 war. Dann ab 17:47:49.463 war es der 3.0.8er controller und da gabs das nimmer. oder sehe ich was falsch?

                    E Offline
                    E Offline
                    e-i-k-e
                    wrote on last edited by
                    #234

                    @apollon77 said in Beta Test js-controller 3.0.x auf GitHub:

                    @e-i-k-e Welche js-controller Version ist im Einsatz? Laut Log kam das vor als es noch die 2.2.9 war. Dann ab 17:47:49.463 war es der 3.0.8er controller und da gabs das nimmer. oder sehe ich was falsch?

                    @apollon77
                    Gut möglich, jetzt läuft die 3.0.8er.
                    Anbei ein Auszug aus dem log, nachdem ich versucht habe diesen neu zu starten..

                    js.JPG

                    Slave:

                    2020-04-15 11:26:18.431  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 (force=false, process=true)
2020-04-15 11:26:18.436  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 send kill signal
2020-04-15 11:26:19.440  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 killing pid 27154
2020-04-15 11:26:21.611  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7635
2020-04-15 11:26:27.195  - error: javascript.2 (7635) javascript.2 already running
2020-04-15 11:26:27.201  - warn: javascript.2 (7635) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:26:28.455  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:26:28.456  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:26:58.472  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7696
2020-04-15 11:27:02.372  - info: javascript.2 (27154) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:27:03.439  - error: javascript.2 (7696) javascript.2 already running
2020-04-15 11:27:03.446  - warn: javascript.2 (7696) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:27:04.718  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:27:04.719  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:27:34.735  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7769
2020-04-15 11:27:39.805  - info: javascript.2 (7769) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
2020-04-15 11:27:40.039  - info: javascript.2 (7769) requesting all states
2020-04-15 11:27:40.044  - info: javascript.2 (7769) requesting all objects
2020-04-15 11:27:40.045  - warn: javascript.2 (7769) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2020-04-15 11:27:43.854  - info: javascript.2 (7769) received all objects
2020-04-15 11:27:46.488  - info: javascript.2 (7769) received all states
2020-04-15 11:27:47.519  - info: javascript.2 (7769) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:27:47.690  - info: javascript.2 (7769) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
2020-04-15 11:28:01.522  - info: javascript.2 (27154) Got terminate signal TERMINATE_YOURSELF
2020-04-15 11:28:01.523  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:28:01.524  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7635 vs own PID 27154
2020-04-15 11:28:01.525  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:28:01.526  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7696 vs own PID 27154
2020-04-15 11:29:05.133  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:29:05.135  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7769 vs own PID 27154
2020-04-15 11:29:05.153  - info: javascript.2 (27154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-04-15 11:30:07.086  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-04-15 11:30:07.088  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:30:08.121  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 8043
2020-04-15 11:30:10.498  - warn: javascript.2 (7769) Got terminate signal. Checking desired PID: 0 vs own PID 7769
2020-04-15 11:30:10.503  - info: javascript.2 (7769) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:30:10.506  - warn: javascript.2 (7769) Got terminate signal. Checking desired PID: 8043 vs own PID 7769
2020-04-15 11:30:10.521  - info: javascript.2 (7769) terminating
2020-04-15 11:30:10.522  - info: javascript.2 (7769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-04-15 11:30:13.072  - error: javascript.2 (8043) javascript.2 already running
2020-04-15 11:30:13.078  - warn: javascript.2 (8043) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:30:14.213  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:30:14.214  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:30:44.227  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 8116
2020-04-15 11:30:49.289  - info: javascript.2 (8116) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
2020-04-15 11:30:49.447  - info: javascript.2 (8116) requesting all states
2020-04-15 11:30:49.451  - info: javascript.2 (8116) requesting all objects
2020-04-15 11:30:49.453  - warn: javascript.2 (8116) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2020-04-15 11:30:53.281  - info: javascript.2 (8116) received all objects
2020-04-15 11:30:55.801  - info: javascript.2 (8116) received all states
2020-04-15 11:30:56.851  - info: javascript.2 (8116) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:30:57.000  - info: javascript.2 (8116) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
2020-04-15 11:31:04.118  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-04-15 11:31:04.119  - info: host.raspberrypi-display1 Do not restart adapter system.adapter.javascript.2 because desired by instance

                    Master:

                    javascript.2	2020-04-15 11:30:57.000	info	(8116) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
javascript.2	2020-04-15 11:30:56.851	info	(8116) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:30:55.801	info	(8116) received all states
javascript.2	2020-04-15 11:30:53.281	info	(8116) received all objects
javascript.2	2020-04-15 11:30:49.453	warn	(8116) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
javascript.2	2020-04-15 11:30:49.451	info	(8116) requesting all objects
javascript.2	2020-04-15 11:30:49.447	info	(8116) requesting all states
javascript.2	2020-04-15 11:30:49.289	info	(8116) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
javascript.2	2020-04-15 11:30:13.078	warn	(8043) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:30:13.072	error	(8043) javascript.2 already running
javascript.2	2020-04-15 11:30:10.522	info	(7769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
javascript.2	2020-04-15 11:30:10.521	info	(7769) terminating
javascript.2	2020-04-15 11:30:10.506	warn	(7769) Got terminate signal. Checking desired PID: 8043 vs own PID 7769
javascript.2	2020-04-15 11:30:10.503	info	(7769) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:30:10.498	warn	(7769) Got terminate signal. Checking desired PID: 0 vs own PID 7769
javascript.2	2020-04-15 11:29:05.153	info	(27154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
javascript.2	2020-04-15 11:29:05.135	warn	(27154) Got terminate signal. Checking desired PID: 7769 vs own PID 27154
javascript.2	2020-04-15 11:29:05.133	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.526	warn	(27154) Got terminate signal. Checking desired PID: 7696 vs own PID 27154
javascript.2	2020-04-15 11:28:01.525	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.524	warn	(27154) Got terminate signal. Checking desired PID: 7635 vs own PID 27154
javascript.2	2020-04-15 11:28:01.523	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.522	info	(27154) Got terminate signal TERMINATE_YOURSELF
javascript.2	2020-04-15 11:27:47.690	info	(7769) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
javascript.2	2020-04-15 11:27:47.519	info	(7769) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:27:46.488	info	(7769) received all states
javascript.2	2020-04-15 11:27:43.854	info	(7769) received all objects
javascript.2	2020-04-15 11:27:40.045	warn	(7769) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
javascript.2	2020-04-15 11:27:40.044	info	(7769) requesting all objects
javascript.2	2020-04-15 11:27:40.039	info	(7769) requesting all states
javascript.2	2020-04-15 11:27:39.805	info	(7769) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
javascript.2	2020-04-15 11:27:03.446	warn	(7696) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:27:03.439	error	(7696) javascript.2 already running
javascript.2	2020-04-15 11:27:02.372	info	(27154) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:26:27.201	warn	(7635) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:26:27.195	error	(7635) javascript.2 already running
                    apollon77A 2 Replies Last reply
                    0
                    • ? A Former User

                      @apollon77 Hi,
                      die 3.09 wirft recht häufig das hier raus, die Adapter stehen dann auf rot:

                      host.iobroker 2020-04-15 10:24:00.018 error instance system.adapter.freifunk.0 could not be started: Error: spawn ENOMEM
                      host.iobroker 2020-04-15 10:23:58.590 error instance system.adapter.enigma2.0 could not be started: Error: spawn ENOMEM

                      Betrifft auch Socketio, mihome-vacuum Adapter...

                      apollon77A Offline
                      apollon77A Offline
                      apollon77
                      wrote on last edited by
                      #235

                      @ilovegym Aah dann bist Du das :-) bisher ist da immer der controller gecrasht. ENOMEM heisst das der Prozess nicht gestartet werden konnte weil kein RAM mehr frei ist ...

                      Schau Dir mal dein system genau an bzw reboote mal.

                      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 Reply Last reply
                      0
                      • E e-i-k-e

                        @apollon77 said in Beta Test js-controller 3.0.x auf GitHub:

                        @e-i-k-e Welche js-controller Version ist im Einsatz? Laut Log kam das vor als es noch die 2.2.9 war. Dann ab 17:47:49.463 war es der 3.0.8er controller und da gabs das nimmer. oder sehe ich was falsch?

                        @apollon77
                        Gut möglich, jetzt läuft die 3.0.8er.
                        Anbei ein Auszug aus dem log, nachdem ich versucht habe diesen neu zu starten..

                        js.JPG

                        Slave:

                        2020-04-15 11:26:18.431  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 (force=false, process=true)
2020-04-15 11:26:18.436  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 send kill signal
2020-04-15 11:26:19.440  - info: host.raspberrypi-display1 stopInstance system.adapter.javascript.2 killing pid 27154
2020-04-15 11:26:21.611  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7635
2020-04-15 11:26:27.195  - error: javascript.2 (7635) javascript.2 already running
2020-04-15 11:26:27.201  - warn: javascript.2 (7635) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:26:28.455  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:26:28.456  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:26:58.472  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7696
2020-04-15 11:27:02.372  - info: javascript.2 (27154) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:27:03.439  - error: javascript.2 (7696) javascript.2 already running
2020-04-15 11:27:03.446  - warn: javascript.2 (7696) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:27:04.718  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:27:04.719  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:27:34.735  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 7769
2020-04-15 11:27:39.805  - info: javascript.2 (7769) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
2020-04-15 11:27:40.039  - info: javascript.2 (7769) requesting all states
2020-04-15 11:27:40.044  - info: javascript.2 (7769) requesting all objects
2020-04-15 11:27:40.045  - warn: javascript.2 (7769) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2020-04-15 11:27:43.854  - info: javascript.2 (7769) received all objects
2020-04-15 11:27:46.488  - info: javascript.2 (7769) received all states
2020-04-15 11:27:47.519  - info: javascript.2 (7769) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:27:47.690  - info: javascript.2 (7769) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
2020-04-15 11:28:01.522  - info: javascript.2 (27154) Got terminate signal TERMINATE_YOURSELF
2020-04-15 11:28:01.523  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:28:01.524  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7635 vs own PID 27154
2020-04-15 11:28:01.525  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:28:01.526  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7696 vs own PID 27154
2020-04-15 11:29:05.133  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
2020-04-15 11:29:05.135  - warn: javascript.2 (27154) Got terminate signal. Checking desired PID: 7769 vs own PID 27154
2020-04-15 11:29:05.153  - info: javascript.2 (27154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2020-04-15 11:30:07.086  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-04-15 11:30:07.088  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:30:08.121  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 8043
2020-04-15 11:30:10.498  - warn: javascript.2 (7769) Got terminate signal. Checking desired PID: 0 vs own PID 7769
2020-04-15 11:30:10.503  - info: javascript.2 (7769) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:30:10.506  - warn: javascript.2 (7769) Got terminate signal. Checking desired PID: 8043 vs own PID 7769
2020-04-15 11:30:10.521  - info: javascript.2 (7769) terminating
2020-04-15 11:30:10.522  - info: javascript.2 (7769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2020-04-15 11:30:13.072  - error: javascript.2 (8043) javascript.2 already running
2020-04-15 11:30:13.078  - warn: javascript.2 (8043) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2020-04-15 11:30:14.213  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-04-15 11:30:14.214  - info: host.raspberrypi-display1 Restart adapter system.adapter.javascript.2 because enabled
2020-04-15 11:30:44.227  - info: host.raspberrypi-display1 instance system.adapter.javascript.2 started with pid 8116
2020-04-15 11:30:49.289  - info: javascript.2 (8116) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
2020-04-15 11:30:49.447  - info: javascript.2 (8116) requesting all states
2020-04-15 11:30:49.451  - info: javascript.2 (8116) requesting all objects
2020-04-15 11:30:49.453  - warn: javascript.2 (8116) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
2020-04-15 11:30:53.281  - info: javascript.2 (8116) received all objects
2020-04-15 11:30:55.801  - info: javascript.2 (8116) received all states
2020-04-15 11:30:56.851  - info: javascript.2 (8116) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
2020-04-15 11:30:57.000  - info: javascript.2 (8116) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
2020-04-15 11:31:04.118  - error: host.raspberrypi-display1 instance system.adapter.javascript.2 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-04-15 11:31:04.119  - info: host.raspberrypi-display1 Do not restart adapter system.adapter.javascript.2 because desired by instance

                        Master:

                        javascript.2	2020-04-15 11:30:57.000	info	(8116) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
javascript.2	2020-04-15 11:30:56.851	info	(8116) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:30:55.801	info	(8116) received all states
javascript.2	2020-04-15 11:30:53.281	info	(8116) received all objects
javascript.2	2020-04-15 11:30:49.453	warn	(8116) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
javascript.2	2020-04-15 11:30:49.451	info	(8116) requesting all objects
javascript.2	2020-04-15 11:30:49.447	info	(8116) requesting all states
javascript.2	2020-04-15 11:30:49.289	info	(8116) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
javascript.2	2020-04-15 11:30:13.078	warn	(8043) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:30:13.072	error	(8043) javascript.2 already running
javascript.2	2020-04-15 11:30:10.522	info	(7769) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
javascript.2	2020-04-15 11:30:10.521	info	(7769) terminating
javascript.2	2020-04-15 11:30:10.506	warn	(7769) Got terminate signal. Checking desired PID: 8043 vs own PID 7769
javascript.2	2020-04-15 11:30:10.503	info	(7769) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:30:10.498	warn	(7769) Got terminate signal. Checking desired PID: 0 vs own PID 7769
javascript.2	2020-04-15 11:29:05.153	info	(27154) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
javascript.2	2020-04-15 11:29:05.135	warn	(27154) Got terminate signal. Checking desired PID: 7769 vs own PID 27154
javascript.2	2020-04-15 11:29:05.133	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.526	warn	(27154) Got terminate signal. Checking desired PID: 7696 vs own PID 27154
javascript.2	2020-04-15 11:28:01.525	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.524	warn	(27154) Got terminate signal. Checking desired PID: 7635 vs own PID 27154
javascript.2	2020-04-15 11:28:01.523	warn	(27154) Got terminate signal. Checking desired PID: 0 vs own PID 27154
javascript.2	2020-04-15 11:28:01.522	info	(27154) Got terminate signal TERMINATE_YOURSELF
javascript.2	2020-04-15 11:27:47.690	info	(7769) script.js.Raspberry.Bildschirm_über_BWM_Flur_unten: registered 3 subscriptions and 0 schedules
javascript.2	2020-04-15 11:27:47.519	info	(7769) Start javascript script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:27:46.488	info	(7769) received all states
javascript.2	2020-04-15 11:27:43.854	info	(7769) received all objects
javascript.2	2020-04-15 11:27:40.045	warn	(7769) adapter.objects.getObjectList is deprecated, and will be removed in the future. Please use adapter.getObjectList/Async. Report this to Developer!
javascript.2	2020-04-15 11:27:40.044	info	(7769) requesting all objects
javascript.2	2020-04-15 11:27:40.039	info	(7769) requesting all states
javascript.2	2020-04-15 11:27:39.805	info	(7769) starting. Version 4.4.3 in /opt/iobroker/node_modules/iobroker.javascript, node: v10.20.0, js-controller: 3.0.8
javascript.2	2020-04-15 11:27:03.446	warn	(7696) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:27:03.439	error	(7696) javascript.2 already running
javascript.2	2020-04-15 11:27:02.372	info	(27154) Stop script script.js.Raspberry.Bildschirm_über_BWM_Flur_unten
javascript.2	2020-04-15 11:26:27.201	warn	(7635) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
javascript.2	2020-04-15 11:26:27.195	error	(7635) javascript.2 already running
                        apollon77A Offline
                        apollon77A Offline
                        apollon77
                        wrote on last edited by
                        #236

                        @e-i-k-e sagte in Beta Test js-controller 3.0.x auf GitHub:

                        Also bei mir sieht es so aus als ob die Instanz hier ein Problem beim stoppen hat. Hängt vllt irgendeins der Skripte oder so? In jedem Fall verhält sich das System laut Log korrekt.
                        Beim Slave sehe ich in dem Log Auszug:

                        • 11:26:19.440 controller sagt prozess 27154 er solle sich beenden
                        • 11:26:19.440 adapter hat nicht reagiert, controller sendet dem prozess ein kill signal 27154
                        • 11:26:21.611 controller startet neuen prozess (7635)
                        • 11:27:02.372 prozess 27154 meldet das er das erste Skript gestoppt hat
                        • 11:27:03.439 prozess 7635 beendet sich weil noch ein anderer läuft
                        • 11:27:34.735 controller startet neuen prozess (7769) ... der startet weil der andere Prozess ewig sein alive nicht mehr aktualisiert hat
                          *11:28:01.522 prozess 27154 läuft immer noch und bekommt JETZT erst die Info über state changes vom 7635 start (1:40 Minuten später!!) und dnan alle
                        • 11:29:05.153 ENDLICH beendet sich 27154 (2:46 Minuten nachdem er den Kill befehl erhalten hat)

                        Alles in Allem schau ich mal was ich optimieren kann, aber fakt ist das irgendein Skript deine Instanz mega blockiert und damit alles durcheinander bringt ... Finde das Skript und fixe es :-)

                        Um das Thema zu ohne Skript Fix zu beheben musst Du schauen das du stop drückst, wartest bis der alte prozess wirklich weg ist und dann neu startest.

                        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 Reply Last reply
                        0
                        • ? A Former User

                          @ilovegym sagte in Beta Test js-controller 3.0.x auf GitHub:

                          @apollon77 Hi,
                          die 3.09 wirft recht häufig das hier raus, die Adapter stehen dann auf rot:

                          host.iobroker 2020-04-15 10:24:00.018 error instance system.adapter.freifunk.0 could not be started: Error: spawn ENOMEM
                          host.iobroker 2020-04-15 10:23:58.590 error instance system.adapter.enigma2.0 could not be started: Error: spawn ENOMEM

                          Betrifft auch Socketio, mihome-vacuum Adapter...

                          Reboot tat gut... danach war ruhe.. bis auf jede Menge warnings vom Socketio.. und web Adapter:

                          web.0 2020-04-15 10:49:56.703 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"
                          web.0 2020-04-15 10:49:54.612 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"
                          web.0 2020-04-15 10:49:46.704 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"
                          web.0 2020-04-15 10:49:44.372 warn readFile will not read this file (index.html) in future versions: socket.io is not an object of type "meta"

                          apollon77A Offline
                          apollon77A Offline
                          apollon77
                          wrote on last edited by
                          #237

                          @ilovegym Versuch mal rauszufinden wann genau das kommt. Also welchen Visu adapter du aufrufen musst damit das im Log kommt. und dann bei dem ein "iobroker upload NAME" ausführen .

                          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 Reply Last reply
                          0
                          • Homer.J.H Homer.J.

                            @apollon77 läuft zwar ich kann aber nichts schalten es reagiert nichts. Bin auch erstmal wieder zurück auf die 10.20.1 Version.
                            Hab mal auf die 3.0.9 hochgezogen und die node.js 12... Installiert jetzt läuft es warum auch immer.

                            apollon77A Offline
                            apollon77A Offline
                            apollon77
                            wrote on last edited by
                            #238

                            @Homer-J sagte in Beta Test js-controller 3.0.x auf GitHub:

                            läuft zwar ich kann a

                            Bitte Issue beim Adapter öffnen

                            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 Reply Last reply
                            0
                            • Homer.J.H Homer.J.

                              @apollon77 läuft zwar ich kann aber nichts schalten es reagiert nichts. Bin auch erstmal wieder zurück auf die 10.20.1 Version.
                              Hab mal auf die 3.0.9 hochgezogen und die node.js 12... Installiert jetzt läuft es warum auch immer.

                              apollon77A Offline
                              apollon77A Offline
                              apollon77
                              wrote on last edited by
                              #239

                              @Homer-J sagte in Beta Test js-controller 3.0.x auf GitHub:

                              läuft zwar ich kann aber nichts schalten es reagiert nichts.

                              Log?

                              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
                              Homer.J.H 1 Reply Last reply
                              0
                              • apollon77A apollon77

                                @Homer-J sagte in Beta Test js-controller 3.0.x auf GitHub:

                                läuft zwar ich kann aber nichts schalten es reagiert nichts.

                                Log?

                                Homer.J.H Offline
                                Homer.J.H Offline
                                Homer.J.
                                wrote on last edited by
                                #240

                                Hi @apollon77 Hab heut morgen die 3.0.9 Version installiert im Anschluss die Node.js auf die 12.. Version angehoben nochmal zur Sicherheit den Fixer drüber laufen lassen und seitdem läuft er.

                                apollon77A 1 Reply Last reply
                                0
                                • J Offline
                                  J Offline
                                  Jan1
                                  wrote on last edited by
                                  #241

                                  Bei mir gibts zwar keine Fehler im Log und alle Adapter sind grün, aber einige Scripte haben gesponnen und der TR-064 findet keine Geräte mehr.
                                  Bin gerade dabei ein Backup zurück zuspielen um zu testen, ob es tatsächlich am JS liegt, oder sich einfach das System was eingefangen hat.

                                  apollon77A 1 Reply Last reply
                                  0
                                  • Homer.J.H Homer.J.

                                    Hi @apollon77 Hab heut morgen die 3.0.9 Version installiert im Anschluss die Node.js auf die 12.. Version angehoben nochmal zur Sicherheit den Fixer drüber laufen lassen und seitdem läuft er.

                                    apollon77A Offline
                                    apollon77A Offline
                                    apollon77
                                    wrote on last edited by
                                    #242

                                    @Homer-J Und Yahka tut?

                                    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
                                    Homer.J.H 1 Reply Last reply
                                    0
                                    • J Jan1

                                      Bei mir gibts zwar keine Fehler im Log und alle Adapter sind grün, aber einige Scripte haben gesponnen und der TR-064 findet keine Geräte mehr.
                                      Bin gerade dabei ein Backup zurück zuspielen um zu testen, ob es tatsächlich am JS liegt, oder sich einfach das System was eingefangen hat.

                                      apollon77A Offline
                                      apollon77A Offline
                                      apollon77
                                      wrote on last edited by
                                      #243

                                      @Jan1 Hm ... ohne Details schwierig

                                      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
                                      J 1 Reply Last reply
                                      0
                                      • apollon77A apollon77

                                        @Homer-J Und Yahka tut?

                                        Homer.J.H Offline
                                        Homer.J.H Offline
                                        Homer.J.
                                        wrote on last edited by
                                        #244

                                        @apollon77 :+1: läuft

                                        1 Reply Last reply
                                        0
                                        • apollon77A apollon77

                                          @Jan1 Hm ... ohne Details schwierig

                                          J Offline
                                          J Offline
                                          Jan1
                                          wrote on last edited by
                                          #245

                                          @apollon77
                                          Wenn keine Fehler im Log stehen ist es eben etwas blöd mehr zu sagen. Augenscheinlich lief ja alles, mich hatte heute gewundert, warum der Saugroboter nicht lief. Der fährt nur bei Abwesenheit und der DP wurde das letzte mal am WE geändert. Dann geschaut ob der TR-064 mein Handy im WLAN erkennt und das bliebt auf true, ebenfalls das Handy meiner Holden, die immer noch samt Handy auf Arbeit ist.
                                          Das Backup ist drauf und der TR-064 läuft wieder. Nun kommt der JS 3.0.9 dazu, mal sehen ob s dann immer noch läuft :-)

                                          apollon77A 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate

                                          450

                                          Online

                                          32.6k

                                          Users

                                          82.1k

                                          Topics

                                          1.3m

                                          Posts
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Recent
                                          • Tags
                                          • Unread 0
                                          • Categories
                                          • Unreplied
                                          • Popular
                                          • GitHub
                                          • Docu
                                          • Hilfe