Läuft node mehrmals?

Reply to Läuft node mehrmals? on Fri, 05 Feb 2021 08:03:19 GMT

Thomas Braun — Fri, 05 Feb 2021 08:03:19 GMT

@sms Keine Vis, keine Graphen.

Reply to Läuft node mehrmals? on Fri, 05 Feb 2021 07:45:02 GMT

SMS — Fri, 05 Feb 2021 07:45:02 GMT

@thomas-braun was nutzt du oder machst du nichts mit Graphen

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 21:21:21 GMT

Thomas Braun — Thu, 04 Feb 2021 21:21:21 GMT

@sms
Keine Ahnung. Hier läuft weder history, noch flot noch influx.

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 21:17:30 GMT

SMS — Thu, 04 Feb 2021 21:17:30 GMT

@thomas-braun
Die Frage ist nur leider warum? Ca. 100 Datenpunkte sind ja wiederum nicht viel. Und anderst kann ich die ja in flot nicht darstellen . Oder doch? Geht das mit "Daten mit InfluxDB protokollieren"?

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 21:03:29 GMT

Thomas Braun — Thu, 04 Feb 2021 21:03:29 GMT

@sms Okay, passt.

Die Meldungen deuten meiner Meinung daraufhin, dass die Datenbank überfordert ist. Aber das wusstest du ja schon.

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 21:00:31 GMT

SMS — Thu, 04 Feb 2021 21:00:31 GMT

@thomas-braun

pi@Homee:~ $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
/usr/bin/nodejs
v12.20.1
/usr/bin/node
v12.20.1
/usr/bin/npm
6.14.10
nodejs:
 Installiert:           12.20.1-1nodesource1
 Installationskandidat: 12.20.1-1nodesource1
 Versionstabelle:
*** 12.20.1-1nodesource1 500
       500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
       100 /var/lib/dpkg/status
    10.23.1~dfsg-1~deb10u1 500
       500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
pi@Homee:~ $

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 20:28:42 GMT

Thomas Braun — Thu, 04 Feb 2021 20:28:42 GMT

@sms sagte in Läuft node mehrmals?:

which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 20:25:23 GMT

SMS — Thu, 04 Feb 2021 20:25:23 GMT

@thomas-braun

2021-02-03 14:36:21.384 - [31merror[39m: host.Homee instance system.adapter.history.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-02-03 14:36:21.389 - [32minfo[39m: host.Homee Restart adapter system.adapter.history.0 because enabled

2021-02-03 14:51:38.869 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:51:41.965 - [31merror[39m: history.0 (21608) uncaught exception: write EPIPE
2021-02-03 14:51:41.966 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)

2021-02-03 14:54:11.134 - [33mwarn[39m: history.0 (21608) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-02-03 14:54:11.195 - [32minfo[39m: history.0 (21608) terminating
2021-02-03 14:54:11.220 - [31merror[39m: history.0 (21608) uncaught exception: write EPIPE
2021-02-03 14:54:11.220 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.234 - [31merror[39m: history.0 (21608) uncaught exception: write EPIPE
2021-02-03 14:54:11.234 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.393 - [31merror[39m: host.Homee Caught by controller[1]: Error: write EPIPE
2021-02-03 14:54:11.399 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.target._send (internal/child_process.js:807:20)
2021-02-03 14:54:11.399 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.target.send (internal/child_process.js:678:19)
2021-02-03 14:54:11.399 - [31merror[39m: host.Homee Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
2021-02-03 14:54:11.400 - [31merror[39m: host.Homee Caught by controller[1]: at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
2021-02-03 14:54:11.400 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
2021-02-03 14:54:11.401 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.emit (events.js:314:20)
2021-02-03 14:54:11.401 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.EventEmitter.emit (domain.js:483:12)
2021-02-03 14:54:11.402 - [31merror[39m: host.Homee Caught by controller[1]: at emit (internal/child_process.js:877:12)
2021-02-03 14:54:11.402 - [31merror[39m: host.Homee Caught by controller[1]: at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.402 - [31merror[39m: host.Homee Caught by controller[2]: Error: write EPIPE
2021-02-03 14:54:11.403 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.target._send (internal/child_process.js:807:20)
2021-02-03 14:54:11.403 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.target.send (internal/child_process.js:678:19)
2021-02-03 14:54:11.404 - [31merror[39m: host.Homee Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
2021-02-03 14:54:11.404 - [31merror[39m: host.Homee Caught by controller[2]: at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
2021-02-03 14:54:11.404 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
2021-02-03 14:54:11.405 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.emit (events.js:314:20)
2021-02-03 14:54:11.405 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.EventEmitter.emit (domain.js:483:12)
2021-02-03 14:54:11.405 - [31merror[39m: host.Homee Caught by controller[2]: at emit (internal/child_process.js:877:12)
2021-02-03 14:54:11.406 - [31merror[39m: host.Homee Caught by controller[2]: at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.406 - [31merror[39m: host.Homee instance system.adapter.history.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2021-02-03 14:54:11.407 - [32minfo[39m: host.Homee Restart adapter system.adapter.history.0 because enabled

2021-02-03 14:57:58.744 - [33mwarn[39m: javascript.0 (25592) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1358:20)
2021-02-03 14:57:58.745 - [33mwarn[39m: javascript.0 (25592) at Object. (script.js.PV-Anlage.Wechselrichter:35:5)
2021-02-03 14:57:58.745 - [33mwarn[39m: javascript.0 (25592) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1055:38)
2021-02-03 14:57:58.745 - [33mwarn[39m: javascript.0 (25592) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:472:25)
2021-02-03 14:57:58.746 - [33mwarn[39m: javascript.0 (25592) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
2021-02-03 14:57:58.747 - [33mwarn[39m: javascript.0 (25592) at processImmediate (internal/timers.js:461:21)

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 19:37:59 GMT

Thomas Braun — Thu, 04 Feb 2021 19:37:59 GMT

@sms
Bitte CodeTags setzen.

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 19:35:35 GMT

SMS — Thu, 04 Feb 2021 19:35:35 GMT

@thomas-braun Hier mal noch was aus der LOG Datei, vielleicht hilft das:

2021-02-03 14:36:21.384 - [31merror[39m: host.Homee instance system.adapter.history.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2021-02-03 14:36:21.389 - [32minfo[39m: host.Homee Restart adapter system.adapter.history.0 because enabled
...
2021-02-03 14:51:38.869 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:51:41.965 - [31merror[39m: history.0 (21608) uncaught exception: write EPIPE
2021-02-03 14:51:41.966 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
...
2021-02-03 14:54:11.134 - [33mwarn[39m: history.0 (21608) Terminated (UNCAUGHT_EXCEPTION): Without reason
2021-02-03 14:54:11.195 - [32minfo[39m: history.0 (21608) terminating
2021-02-03 14:54:11.220 - [31merror[39m: history.0 (21608) uncaught exception: write EPIPE
2021-02-03 14:54:11.220 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.234 - [31merror[39m: history.0 (21608) uncaught exception: write EPIPE
2021-02-03 14:54:11.234 - [31merror[39m: history.0 (21608) Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:807:20)
at ChildProcess.target.send (internal/child_process.js:678:19)
at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
at ChildProcess.emit (events.js:314:20)
at ChildProcess.EventEmitter.emit (domain.js:483:12)
at emit (internal/child_process.js:877:12)
at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.393 - [31merror[39m: host.Homee Caught by controller[1]: Error: write EPIPE
2021-02-03 14:54:11.399 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.target._send (internal/child_process.js:807:20)
2021-02-03 14:54:11.399 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.target.send (internal/child_process.js:678:19)
2021-02-03 14:54:11.399 - [31merror[39m: host.Homee Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
2021-02-03 14:54:11.400 - [31merror[39m: host.Homee Caught by controller[1]: at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
2021-02-03 14:54:11.400 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
2021-02-03 14:54:11.401 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.emit (events.js:314:20)
2021-02-03 14:54:11.401 - [31merror[39m: host.Homee Caught by controller[1]: at ChildProcess.EventEmitter.emit (domain.js:483:12)
2021-02-03 14:54:11.402 - [31merror[39m: host.Homee Caught by controller[1]: at emit (internal/child_process.js:877:12)
2021-02-03 14:54:11.402 - [31merror[39m: host.Homee Caught by controller[1]: at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.402 - [31merror[39m: host.Homee Caught by controller[2]: Error: write EPIPE
2021-02-03 14:54:11.403 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.target._send (internal/child_process.js:807:20)
2021-02-03 14:54:11.403 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.target.send (internal/child_process.js:678:19)
2021-02-03 14:54:11.404 - [31merror[39m: host.Homee Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.history/main.js:1052:28
2021-02-03 14:54:11.404 - [31merror[39m: host.Homee Caught by controller[2]: at getCachedData (/opt/iobroker/node_modules/iobroker.history/main.js:828:5)
2021-02-03 14:54:11.404 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess. (/opt/iobroker/node_modules/iobroker.history/main.js:1051:21)
2021-02-03 14:54:11.405 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.emit (events.js:314:20)
2021-02-03 14:54:11.405 - [31merror[39m: host.Homee Caught by controller[2]: at ChildProcess.EventEmitter.emit (domain.js:483:12)
2021-02-03 14:54:11.405 - [31merror[39m: host.Homee Caught by controller[2]: at emit (internal/child_process.js:877:12)
2021-02-03 14:54:11.406 - [31merror[39m: host.Homee Caught by controller[2]: at processTicksAndRejections (internal/process/task_queues.js:85:21)
2021-02-03 14:54:11.406 - [31merror[39m: host.Homee instance system.adapter.history.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2021-02-03 14:54:11.407 - [32minfo[39m: host.Homee Restart adapter system.adapter.history.0 because enabled
...
Das hier kommt auch öfters:

2021-02-03 14:57:58.744 - [33mwarn[39m: javascript.0 (25592) at setState (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1358:20)
2021-02-03 14:57:58.745 - [33mwarn[39m: javascript.0 (25592) at Object. (script.js.PV-Anlage.Wechselrichter:35:5)
2021-02-03 14:57:58.745 - [33mwarn[39m: javascript.0 (25592) at Object.callback (/opt/iobroker/node_modules/iobroker.javascript/lib/sandbox.js:1055:38)
2021-02-03 14:57:58.745 - [33mwarn[39m: javascript.0 (25592) at Object.stateChange (/opt/iobroker/node_modules/iobroker.javascript/main.js:472:25)
2021-02-03 14:57:58.746 - [33mwarn[39m: javascript.0 (25592) at Immediate._onImmediate (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:5384:37)
2021-02-03 14:57:58.747 - [33mwarn[39m: javascript.0 (25592) at processImmediate (internal/timers.js:461:21)

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 14:11:33 GMT

SMS — Thu, 04 Feb 2021 14:11:33 GMT

@thomas-braun
Nach dem es nun ein paar Tage fast ohne Probleme lief, häufen sich die Abstürze vom history.0 Adapter.

Was soll man da auch groß einstellen?

Was meinst mit: Was schiebst da rein? In dem Ordner liegen täglich so ca. 110 Dateien. Ich meine in einem Video was von ca 200 gehört zu haben.

Was auch komisch ist, letzt war die Auslastung über 9%. Generell würde ich sagen das selbst das nicht viel ist. Ich muss es nochmal verfolgen, habe auch das Gefühl das der benutze Arbeitsspeicher, aktuell 2,6GB von 8GB) auch eine Rolle spielt. Wobei ich auch hier 2,6GB nicht viel finde.

Ich verstehe nicht wo das Problem liegen könnte?

Reply to Läuft node mehrmals? on Thu, 04 Feb 2021 14:28:10 GMT

Thomas Braun — Thu, 04 Feb 2021 14:28:10 GMT

@sms


  1  [||||                                                                              3.9%]   Tasks: 51, 156 thr; 4 running
  2  [||||||||||||                                                                     12.3%]   Load average: 0.77 0.65 0.65
  3  [||||||||||||||                                                                   14.8%]   Uptime: 1 day, 03:15:53
  4  [||||||                                                                            5.8%]
  Mem[|||||||||||||||||||||||||||||||||||||||||||                                 964M/3.74G]
  Swp[                                                                             0K/100.0M]

  PID USER      PRI  NI  VIRT   RES   SHR S CPU% MEM%   TIME+  Command  
555 iobroker   20   0  298M  173M 28080 S  0.0  4.5  0:00.00 iobroker.js-controller                                                                                                             556 iobroker   20   0  298M  173M 28080 R  0.6  4.5 16:18.78 iobroker.js-controller
557 iobroker   20   0  298M  173M 28080 R  0.0  4.5 16:17.79 iobroker.js-controller
558 iobroker   20   0  298M  173M 28080 S  0.0  4.5 16:18.15 iobroker.js-controller
559 iobroker   20   0  298M  173M 28080 S  0.0  4.5 16:20.99 iobroker.js-controller
560 iobroker   20   0  298M  173M 28080 S  0.0  4.5  0:00.00 iobroker.js-controller
564 iobroker   20   0  298M  173M 28080 S  0.0  4.5  0:04.26 iobroker.js-controller
565 iobroker   20   0  298M  173M 28080 S  0.0  4.5  0:04.72 iobroker.js-controller
566 iobroker   20   0  298M  173M 28080 S  0.0  4.5  0:04.78 iobroker.js-controller
567 iobroker   20   0  298M  173M 28080 S  0.0  4.5  0:04.51 iobroker.js-controller
538 iobroker   20   0  298M  173M 28080 S 17.5  4.5  3h31:55 iobroker.js-controller
26716 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:00.00 io.javascript.0
26717 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:23.46 io.javascript.0
26718 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:23.80 io.javascript.0
26719 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:23.81 io.javascript.0
26720 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:24.64 io.javascript.0
26721 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:00.00 io.javascript.0
26783 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:00.48 io.javascript.0
26784 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:00.49 io.javascript.0
26785 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:00.50 io.javascript.0
26786 iobroker   20   0  271M  163M 31012 S  0.0  4.3  0:00.51 io.javascript.0
26715 iobroker   20   0  271M  163M 31012 S  0.0  4.3 38:11.17 io.javascript.0
  704 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.00 io.backitup.0
  705 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.87 io.backitup.0
  706 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.98 io.backitup.0
  707 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.56 io.backitup.0
  708 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.69 io.backitup.0
  709 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.00 io.backitup.0
  730 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.61 io.backitup.0
  731 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.65 io.backitup.0
  732 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.60 io.backitup.0
  733 iobroker   20   0  205M 98012 29000 S  0.0  2.5  0:00.67 io.backitup.0
  703 iobroker   20   0  205M 98012 29000 S  0.0  2.5  1:12.23 io.backitup.0
  577 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:00.00 io.admin.0
  578 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:13.15 io.admin.0
  579 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:13.28 io.admin.0
  580 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:13.17 io.admin.0
  581 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:12.74 io.admin.0
  582 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:00.00 io.admin.0
  612 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:00.62 io.admin.0
  613 iobroker   20   0  204M 97548 32752 S  0.0  2.5  0:00.59 io.admin.0
F1Help  F2Setup F3SearchF4FilterF5Tree  F6SortByF7Nice -F8Nice +F9Kill  F10Quit

Komisch, hier geht es als Text...

Wie bereits gesagt, ich würde mir den history-Adapter anschauen. Wie ist der einstellt und was schiebt da rein.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 21:41:38 GMT

SMS — Tue, 26 Jan 2021 21:41:38 GMT

@thomas-braun
sorry, anderst bekomme ich es nicht hin als per Screenshoot:

Was sagt mir das jetzt und was kann ich dagegen tun?

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 21:24:54 GMT

Thomas Braun — Tue, 26 Jan 2021 21:24:54 GMT

@sms sagte in Läuft node mehrmals?:

js-controllet mit höheren Werten. Das Ganze geht aber so schnell ... Bis ich da den Namen. gelesen habe ist es sch

Dann hast du mit history ja ggf. einen Ansatz.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 21:24:15 GMT

SMS — Tue, 26 Jan 2021 21:24:15 GMT

@thomas-braun
Als unwissender vermute ich node, da das mehrmals auftaucht. Mit htop ist das ja genauer.
Da finde ich history und js-controllet mit höheren Werten. Das Ganze geht aber so schnell ... Bis ich da den Namen. gelesen habe ist es schon wieder weg.
History schaltet sich auch öfters ab.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 21:16:16 GMT

Thomas Braun — Tue, 26 Jan 2021 21:16:16 GMT

@sms
Wenn du dir die Ausgabe von top nochmal anschaust siehst du eigentlich, was etwas aus der Reihe tanzt.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 20:37:30 GMT

SMS — Tue, 26 Jan 2021 20:37:30 GMT

@thomas-braun
Meinst du CPU%? Was ist "mehr als üblich"?

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 20:05:39 GMT

Thomas Braun — Tue, 26 Jan 2021 20:05:39 GMT

@sms Die PID dürfte mittlerweile Vergangenheit sein. Halt nach einem Prozess, der sich etwas mehr als üblich genehmigt.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 19:59:49 GMT

SMS — Tue, 26 Jan 2021 19:59:49 GMT

@homoran
@Thomas-Braun

Auf was sollte ich denn mit dem Befehl htop schauen? PID 28269 taucht dort nicht auf

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 13:58:55 GMT

Homoran — Tue, 26 Jan 2021 13:58:55 GMT

@sms sagte in Läuft node mehrmals?:

Rauskopieren kann ich dort auch nichts.

warum nicht?
einfach markieren und schon ist es im Zwischenspeicher

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 13:50:47 GMT

SMS — Tue, 26 Jan 2021 13:50:47 GMT

@thomas-braun
PID 28269 finde ich dort nicht. Rauskopieren kann ich dort auch nichts.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 09:32:05 GMT

Thomas Braun — Tue, 26 Jan 2021 09:32:05 GMT

@sms
Bitte keine Konsolen-Screenshots, da kann man u.a. nicht draus kopieren.

PID 28269 schaut 'merkwürdig' aus. Schau mal per htop danach, da werden die Prozessnamen besser ausgewiesen. Ich vermute da ist noch irgendwas falsch oder zu häufig eingestellt.

Reply to Läuft node mehrmals? on Tue, 26 Jan 2021 09:26:37 GMT

SMS — Tue, 26 Jan 2021 09:26:37 GMT

@paul53
@Homoran
@Thomas-Braun

Hi
Mal wieder zurück zum Thema bzw. hier mal der Verlauf der CPU Auslastung:
3-Tage:

14-Tage:

Meist Nachts steigt die Auslastung, obwohl da eigentlich nichts ist. Ich sollte mittlerweile nichts mehr im Sekundentakt laufen haben bzw. keine CRON Abfrage.

Hier mal meine installierten Adapter:

Ist da was dabei was das verursachen könnte? Ich habe mal nach und nach alle abgeschaltet die nicht unbedingt sein müssen. Schalte jetzt mal wieder nach und nach alle wieder ein.

Dann hier nochmal die Frage ob node mehrmals läuft?

Danke!!

Reply to Läuft node mehrmals? on Wed, 13 Jan 2021 18:21:34 GMT

paul53 — Wed, 13 Jan 2021 18:21:34 GMT

@sms said: Das ganze sieht so aus:

Gibt es dafür nicht einen Adapter ?

Für diese Aufgabenstellung benötigt man CRON-Trigger. Dies ist ein Fall, bei dem auch ein ständiger CRON (z.B. alle 30 Minuten) verwendet werden kann, in dem die Abfragen nach "Auto", "Wochentag" und "Uhrzeit" erfolgen.

Der Anfang für Montag könnte so aussehen: