Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. iobroker.js-con 100% cpu

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    iobroker.js-con 100% cpu

    This topic has been deleted. Only users with topic management privileges can see it.
    • spicer
      spicer @Thomas Braun last edited by

      @thomas-braun
      Hm, ist eine Neuinstallation. Hab keinen Plan.

      1 Reply Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @mcm1957 last edited by

        @mcm1957 erlefigt

        @spicer
        Bitte Threadtitel sinnvoll anpassen

        1 Reply Last reply Reply Quote 1
        • Marc Berg
          Marc Berg Most Active last edited by

          @thomas-braun sagte in iobroker.js-con 100% cpu:

          Da wird wohl irgendwas im Umfeld von mqtt / javaskript / history krumm sein.

          Sehe ich auch so. Mit einiger Wahrscheinlichkeit ist eine Schleife im MQTT Umfeld entstanden. Ohne Logs aber nicht final zu bewerten.

          1 Reply Last reply Reply Quote 0
          • spicer
            spicer last edited by spicer

            @marc-berg
            Hier mal der log der letzten 2 Minuten:

            2024-10-29 17:39:36.406  - info: admin.0 (1274) <== Disconnect system.user.admin from ::ffff:192.168.1.10 echarts
2024-10-29 17:39:36.406  - info: admin.0 (1274) <== Disconnect system.user.admin from ::ffff:192.168.1.10 echarts-show
2024-10-29 17:39:54.140  - info: admin.0 (1274) ==> Connected system.user.admin from ::ffff:192.168.1.10
2024-10-29 17:39:55.212  - info: admin.0 (1274) ==> Connected system.user.admin from ::ffff:192.168.1.10
2024-10-29 17:40:00.033  - info: javascript.0 (2413) script.js.common.Ping_zu_ESP_Garage: ESP Garage erreichbar
2024-10-29 17:40:00.037  - info: javascript.0 (2413) script.js.common.Ping_zu_Shelly_Boilersteuerung: erreichbar
2024-10-29 17:40:10.047  - info: mqtt.1 (2853) Client [mosqsub|32094-Dachrollo] connected with secret 1730220010046_3539
2024-10-29 17:40:10.053  - info: mqtt.1 (2853) Client [mosqsub|32094-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Temperatur_Feucht_Si7021.Temperatur"
2024-10-29 17:40:10.252  - info: mqtt.1 (2853) Client [mosqsub|32094-Dachrollo] publishOnSubscribe
2024-10-29 17:40:10.254  - info: mqtt.1 (2853) Client [mosqsub|32094-Dachrollo] connection closed: disconnected
2024-10-29 17:40:10.341  - info: mqtt.1 (2853) Client [mosqsub|32096-Dachrollo] connected with secret 1730220010340_4058
2024-10-29 17:40:10.345  - info: mqtt.1 (2853) Client [mosqsub|32096-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Temperatur_Feucht_Si7021.Luftfeuchtigkeit"
2024-10-29 17:40:10.544  - info: mqtt.1 (2853) Client [mosqsub|32096-Dachrollo] publishOnSubscribe
2024-10-29 17:40:10.546  - info: mqtt.1 (2853) Client [mosqsub|32096-Dachrollo] connection closed: disconnected
2024-10-29 17:40:10.688  - info: mqtt.1 (2853) Client [mosqsub|32098-Dachrollo] connected with secret 1730220010671_5897
2024-10-29 17:40:10.690  - info: mqtt.1 (2853) Client [mosqsub|32098-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.status.LWT"
2024-10-29 17:40:10.895  - info: mqtt.1 (2853) Client [mosqsub|32098-Dachrollo] publishOnSubscribe
2024-10-29 17:40:10.898  - info: mqtt.1 (2853) Client [mosqsub|32098-Dachrollo] connection closed: disconnected
2024-10-29 17:40:10.985  - info: mqtt.1 (2853) Client [mosqsub|32100-Dachrollo] connected with secret 1730220010984_9685
2024-10-29 17:40:10.994  - info: mqtt.1 (2853) Client [mosqsub|32100-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Licht.Licht"
2024-10-29 17:40:11.198  - info: mqtt.1 (2853) Client [mosqsub|32100-Dachrollo] publishOnSubscribe
2024-10-29 17:40:11.201  - info: mqtt.1 (2853) Client [mosqsub|32100-Dachrollo] connection closed: disconnected
2024-10-29 17:40:11.287  - info: mqtt.1 (2853) Client [mosqsub|32102-Dachrollo] connected with secret 1730220011286_3077
2024-10-29 17:40:11.289  - info: mqtt.1 (2853) Client [mosqsub|32102-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Akku_Spannung.AkkuSpannung"
2024-10-29 17:40:11.490  - info: mqtt.1 (2853) Client [mosqsub|32102-Dachrollo] publishOnSubscribe
2024-10-29 17:40:11.493  - info: mqtt.1 (2853) Client [mosqsub|32102-Dachrollo] connection closed: disconnected
2024-10-29 17:40:11.594  - info: mqtt.1 (2853) Client [mosqpub|32104-Dachrollo] connected with secret 1730220011591_1055
2024-10-29 17:40:11.598  - info: mqtt.1 (2853) Client [mosqpub|32104-Dachrollo] connection closed: disconnected
2024-10-29 17:40:11.689  - info: mqtt.1 (2853) Client [mosqpub|32106-Dachrollo] connected with secret 1730220011689_2907
2024-10-29 17:40:11.692  - info: mqtt.1 (2853) Client [mosqpub|32106-Dachrollo] connection closed: disconnected
2024-10-29 17:40:11.787  - info: mqtt.1 (2853) Client [mosqpub|32108-Dachrollo] connected with secret 1730220011786_3598
2024-10-29 17:40:11.792  - info: mqtt.1 (2853) Client [mosqpub|32108-Dachrollo] connection closed: disconnected
2024-10-29 17:40:11.881  - info: mqtt.1 (2853) Client [mosqpub|32110-Dachrollo] connected with secret 1730220011880_7167
2024-10-29 17:40:11.883  - info: mqtt.1 (2853) Client [mosqpub|32110-Dachrollo] connection closed: disconnected
2024-10-29 17:40:11.977  - info: mqtt.1 (2853) Client [mosqpub|32112-Dachrollo] connected with secret 1730220011977_2620
2024-10-29 17:40:11.980  - info: mqtt.1 (2853) Client [mosqpub|32112-Dachrollo] connection closed: disconnected
2024-10-29 17:40:12.264  - info: mqtt.1 (2853) Client [mosqpub|32127-Dachrollo] connected with secret 1730220012263_3993
2024-10-29 17:40:12.267  - info: mqtt.1 (2853) Client [mosqpub|32127-Dachrollo] connection closed: disconnected
2024-10-29 17:40:12.487  - info: mqtt.1 (2853) Client [mosqpub|32133-Dachrollo] connected with secret 1730220012483_2896
2024-10-29 17:40:12.489  - info: mqtt.1 (2853) Client [mosqpub|32133-Dachrollo] connection closed: disconnected
2024-10-29 17:40:15.215  - info: admin.0 (1274) <== Disconnect system.user.admin from ::ffff:192.168.1.10 echarts-show
2024-10-29 17:40:15.216  - info: admin.0 (1274) <== Disconnect system.user.admin from ::ffff:192.168.1.10 echarts
2024-10-29 17:40:26.015  - info: host.iobroker instance system.adapter.solarmanpv.0 in version "0.6.1" started with pid 3525
2024-10-29 17:40:28.155  - info: solarmanpv.0 (3525) starting. Version 0.6.1 in /opt/iobroker/node_modules/iobroker.solarmanpv, node: v20.18.0, js-controller: 6.0.11
2024-10-29 17:40:39.735  - info: solarmanpv.0 (3525) Terminated (ADAPTER_REQUESTED_TERMINATION): Everything done. Going to terminate till next schedule
2024-10-29 17:40:40.303  - info: host.iobroker instance system.adapter.solarmanpv.0 having pid 3525 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-10-29 17:41:09.838  - info: mqtt.1 (2853) Client [mosqsub|32159-Dachrollo] connected with secret 1730220069837_6569
2024-10-29 17:41:09.840  - info: mqtt.1 (2853) Client [mosqsub|32159-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Temperatur_Feucht_Si7021.Temperatur"
2024-10-29 17:41:10.040  - info: mqtt.1 (2853) Client [mosqsub|32159-Dachrollo] publishOnSubscribe
2024-10-29 17:41:10.044  - info: mqtt.1 (2853) Client [mosqsub|32159-Dachrollo] connection closed: disconnected
2024-10-29 17:41:10.137  - info: mqtt.1 (2853) Client [mosqsub|32161-Dachrollo] connected with secret 1730220070134_4114
2024-10-29 17:41:10.141  - info: mqtt.1 (2853) Client [mosqsub|32161-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Temperatur_Feucht_Si7021.Luftfeuchtigkeit"
2024-10-29 17:41:10.342  - info: mqtt.1 (2853) Client [mosqsub|32161-Dachrollo] publishOnSubscribe
2024-10-29 17:41:10.345  - info: mqtt.1 (2853) Client [mosqsub|32161-Dachrollo] connection closed: disconnected
2024-10-29 17:41:10.430  - info: mqtt.1 (2853) Client [mosqsub|32163-Dachrollo] connected with secret 1730220070430_9522
2024-10-29 17:41:10.432  - info: mqtt.1 (2853) Client [mosqsub|32163-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.status.LWT"
2024-10-29 17:41:10.632  - info: mqtt.1 (2853) Client [mosqsub|32163-Dachrollo] publishOnSubscribe
2024-10-29 17:41:10.634  - info: mqtt.1 (2853) Client [mosqsub|32163-Dachrollo] connection closed: disconnected
2024-10-29 17:41:10.754  - info: mqtt.1 (2853) Client [mosqsub|32165-Dachrollo] connected with secret 1730220070754_549
2024-10-29 17:41:10.758  - info: mqtt.1 (2853) Client [mosqsub|32165-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Licht.Licht"
2024-10-29 17:41:10.958  - info: mqtt.1 (2853) Client [mosqsub|32165-Dachrollo] publishOnSubscribe
2024-10-29 17:41:11.034  - info: mqtt.1 (2853) Client [mosqsub|32165-Dachrollo] connection closed: disconnected
2024-10-29 17:41:11.064  - info: mqtt.1 (2853) Client [mosqsub|32167-Dachrollo] connected with secret 1730220071062_4274
2024-10-29 17:41:11.066  - info: mqtt.1 (2853) Client [mosqsub|32167-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Akku_Spannung.AkkuSpannung"
2024-10-29 17:41:11.266  - info: mqtt.1 (2853) Client [mosqsub|32167-Dachrollo] publishOnSubscribe
2024-10-29 17:41:11.268  - info: mqtt.1 (2853) Client [mosqsub|32167-Dachrollo] connection closed: disconnected
2024-10-29 17:41:11.370  - info: mqtt.1 (2853) Client [mosqpub|32169-Dachrollo] connected with secret 1730220071368_6906
2024-10-29 17:41:11.373  - info: mqtt.1 (2853) Client [mosqpub|32169-Dachrollo] connection closed: disconnected
2024-10-29 17:41:11.466  - info: mqtt.1 (2853) Client [mosqpub|32171-Dachrollo] connected with secret 1730220071465_7954
2024-10-29 17:41:11.468  - info: mqtt.1 (2853) Client [mosqpub|32171-Dachrollo] connection closed: disconnected
2024-10-29 17:41:11.574  - info: mqtt.1 (2853) Client [mosqpub|32173-Dachrollo] connected with secret 1730220071573_7598
2024-10-29 17:41:11.577  - info: mqtt.1 (2853) Client [mosqpub|32173-Dachrollo] connection closed: disconnected
2024-10-29 17:41:11.689  - info: mqtt.1 (2853) Client [mosqpub|32175-Dachrollo] connected with secret 1730220071686_3418
2024-10-29 17:41:11.692  - info: mqtt.1 (2853) Client [mosqpub|32175-Dachrollo] connection closed: disconnected
2024-10-29 17:41:11.785  - info: mqtt.1 (2853) Client [mosqpub|32177-Dachrollo] connected with secret 1730220071785_4540
2024-10-29 17:41:11.787  - info: mqtt.1 (2853) Client [mosqpub|32177-Dachrollo] connection closed: disconnected
2024-10-29 17:41:12.102  - info: mqtt.1 (2853) Client [mosqpub|32192-Dachrollo] connected with secret 1730220072083_5782
2024-10-29 17:41:12.104  - info: mqtt.1 (2853) Client [mosqpub|32192-Dachrollo] connection closed: disconnected
2024-10-29 17:41:12.272  - info: mqtt.1 (2853) Client [mosqpub|32198-Dachrollo] connected with secret 1730220072272_4085
2024-10-29 17:41:12.274  - info: mqtt.1 (2853) Client [mosqpub|32198-Dachrollo] connection closed: disconnected
2024-10-29 17:41:50.877  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] connected with secret 1730220110871_4120
2024-10-29 17:41:51.030  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] subscribes on "mqtt.1.12V_on_off"
2024-10-29 17:41:51.046  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] subscribes on "mqtt.1.Wert2"
2024-10-29 17:41:51.046  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] subscribes on "mqtt.1.Wert3"
2024-10-29 17:41:51.046  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] subscribes on "mqtt.1.Wert4"
2024-10-29 17:41:51.047  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] connection closed: disconnected
2024-10-29 17:41:51.230  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] publishOnSubscribe
2024-10-29 17:41:51.247  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] publishOnSubscribe
2024-10-29 17:41:51.247  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] publishOnSubscribe
2024-10-29 17:41:51.247  - info: mqtt.1 (2853) Client [Aussenfuehler-Import] publishOnSubscribe
2024-10-29 17:41:51.526  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] connected with secret 1730220111511_8377
2024-10-29 17:41:51.671  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] subscribes on "mqtt.1.12V_on_off"
2024-10-29 17:41:51.690  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] subscribes on "mqtt.1.Wert2"
2024-10-29 17:41:51.690  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] subscribes on "mqtt.1.Wert3"
2024-10-29 17:41:51.690  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] subscribes on "mqtt.1.Wert4"
2024-10-29 17:41:51.871  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] publishOnSubscribe
2024-10-29 17:41:51.891  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] publishOnSubscribe
2024-10-29 17:41:51.891  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] publishOnSubscribe
2024-10-29 17:41:51.892  - info: mqtt.1 (2853) Client [Aussenfuehler-Import1] publishOnSubscribe
2024-10-29 17:41:52.292  - info: mqtt.1 (2853) Client [ESPClient_4C:11:AE:04:5D:28] connected with secret 1730220112290_6243
2024-10-29 17:41:52.307  - info: mqtt.1 (2853) Client [ESPClient_4C:11:AE:04:5D:28] subscribes on "/Aussenfuehler/#" with regex /^Aussenfuehler\..*/
2024-10-29 17:41:52.307  - info: mqtt.1 (2853) Client [ESPClient_4C:11:AE:04:5D:28] subscribes on "/Aussenfuehler/#"  with regex /^mqtt\.1\.Aussenfuehler\..*/
2024-10-29 17:41:52.521  - info: mqtt.1 (2853) Client [ESPClient_4C:11:AE:04:5D:28] publishOnSubscribe send all known states
2024-10-29 17:42:00.035  - info: javascript.0 (2413) script.js.common.Ping_zu_Shelly_Boilersteuerung: erreichbar
2024-10-29 17:42:00.053  - info: javascript.0 (2413) script.js.Telegram_Bot.System_Temperaturen: GPU Temp: 57.6 °C
2024-10-29 17:42:00.054  - info: javascript.0 (2413) script.js.Telegram_Bot.System_Temperaturen: CPU Temp: 56.2 °C
2024-10-29 17:42:00.054  - info: javascript.0 (2413) script.js.common.Ping_zu_ESP_Garage: ESP Garage erreichbar
2024-10-29 17:42:00.060  - info: javascript.0 (2413) script.js.Telegram_Bot.System_Temperaturen: Freier Swap: 199
 MB von 2048MB (10%)
2024-10-29 17:42:00.064  - info: javascript.0 (2413) script.js.Telegram_Bot.System_Temperaturen: Freier RAM: 4300
 MB von 922MB (466%)
2024-10-29 17:42:09.489  - info: mqtt.1 (2853) Client [mosqsub|32224-Dachrollo] connected with secret 1730220129488_7150
2024-10-29 17:42:09.496  - info: mqtt.1 (2853) Client [mosqsub|32224-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Temperatur_Feucht_Si7021.Temperatur"
2024-10-29 17:42:09.696  - info: mqtt.1 (2853) Client [mosqsub|32224-Dachrollo] publishOnSubscribe
2024-10-29 17:42:09.698  - info: mqtt.1 (2853) Client [mosqsub|32224-Dachrollo] connection closed: disconnected
2024-10-29 17:42:09.784  - info: mqtt.1 (2853) Client [mosqsub|32226-Dachrollo] connected with secret 1730220129783_376
2024-10-29 17:42:09.792  - info: mqtt.1 (2853) Client [mosqsub|32226-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Temperatur_Feucht_Si7021.Luftfeuchtigkeit"
2024-10-29 17:42:09.991  - info: mqtt.1 (2853) Client [mosqsub|32226-Dachrollo] publishOnSubscribe
2024-10-29 17:42:09.995  - info: mqtt.1 (2853) Client [mosqsub|32226-Dachrollo] connection closed: disconnected
2024-10-29 17:42:10.083  - info: mqtt.1 (2853) Client [mosqsub|32228-Dachrollo] connected with secret 1730220130082_8766
2024-10-29 17:42:10.085  - info: mqtt.1 (2853) Client [mosqsub|32228-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.status.LWT"
2024-10-29 17:42:10.290  - info: mqtt.1 (2853) Client [mosqsub|32228-Dachrollo] publishOnSubscribe
2024-10-29 17:42:10.295  - info: mqtt.1 (2853) Client [mosqsub|32228-Dachrollo] connection closed: disconnected
2024-10-29 17:42:10.385  - info: mqtt.1 (2853) Client [mosqsub|32230-Dachrollo] connected with secret 1730220130381_2598
2024-10-29 17:42:10.391  - info: mqtt.1 (2853) Client [mosqsub|32230-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Licht.Licht"
2024-10-29 17:42:10.606  - info: mqtt.1 (2853) Client [mosqsub|32230-Dachrollo] publishOnSubscribe
2024-10-29 17:42:10.613  - info: mqtt.1 (2853) Client [mosqsub|32230-Dachrollo] connection closed: disconnected
2024-10-29 17:42:10.709  - info: mqtt.1 (2853) Client [mosqsub|32232-Dachrollo] connected with secret 1730220130702_1490
2024-10-29 17:42:10.713  - info: mqtt.1 (2853) Client [mosqsub|32232-Dachrollo] subscribes on "mqtt.1.Aussenfuehler.Akku_Spannung.AkkuSpannung"
2024-10-29 17:42:10.926  - info: mqtt.1 (2853) Client [mosqsub|32232-Dachrollo] publishOnSubscribe
2024-10-29 17:42:10.931  - info: mqtt.1 (2853) Client [mosqsub|32232-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.029  - info: mqtt.1 (2853) Client [mosqpub|32234-Dachrollo] connected with secret 1730220131025_2941
2024-10-29 17:42:11.033  - info: mqtt.1 (2853) Client [mosqpub|32234-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.126  - info: mqtt.1 (2853) Client [mosqpub|32236-Dachrollo] connected with secret 1730220131125_3706
2024-10-29 17:42:11.128  - info: mqtt.1 (2853) Client [mosqpub|32236-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.223  - info: mqtt.1 (2853) Client [mosqpub|32238-Dachrollo] connected with secret 1730220131223_4616
2024-10-29 17:42:11.226  - info: mqtt.1 (2853) Client [mosqpub|32238-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.318  - info: mqtt.1 (2853) Client [mosqpub|32240-Dachrollo] connected with secret 1730220131318_7545
2024-10-29 17:42:11.320  - info: mqtt.1 (2853) Client [mosqpub|32240-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.464  - info: mqtt.1 (2853) Client [mosqpub|32242-Dachrollo] connected with secret 1730220131450_8743
2024-10-29 17:42:11.468  - info: mqtt.1 (2853) Client [mosqpub|32242-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.765  - info: mqtt.1 (2853) Client [mosqpub|32257-Dachrollo] connected with secret 1730220131764_8864
2024-10-29 17:42:11.767  - info: mqtt.1 (2853) Client [mosqpub|32257-Dachrollo] connection closed: disconnected
2024-10-29 17:42:11.990  - info: mqtt.1 (2853) Client [mosqpub|32263-Dachrollo] connected with secret 1730220131973_9098
2024-10-29 17:42:11.992  - info: mqtt.1 (2853) Client [mosqpub|32263-Dachrollo] connection closed: disconnected
2024-10-29 17:42:25.976  - info: mqtt.1 (2853) Client [ESPClient_4C:11:AE:04:5D:28] connection closed: disconnected

            Alle Minuten kommen MQTT Daten von der Wetterstation rein. Sieht für mich sorichtig aus.
            Bleibt zu sagen, dass unter der alten Installation auf dem RPI3 keine 100% CPU gebraucht wurden.
            Habe ja beim RPI5 nur alles restored mittels Backitup.

            Wenn ich den MQTT Adapter pausiere, ist die CPU auf 2% !

            Homoran 1 Reply Last reply Reply Quote 0
            • Homoran
              Homoran Global Moderator Administrators @spicer last edited by

              @spicer und was rattert da im Millisekundentakt durch?

              spicer 1 Reply Last reply Reply Quote 0
              • spicer
                spicer @Homoran last edited by

                @homoran
                Alle 1 Minute kommen da die verschiedenen Daten von der Wetterstation.

                wendy2702 Marc Berg 2 Replies Last reply Reply Quote 0
                • wendy2702
                  wendy2702 @spicer last edited by

                  @spicer ist die Wetterstation der “Aussenfühler” ?

                  spicer 1 Reply Last reply Reply Quote 0
                  • spicer
                    spicer @wendy2702 last edited by

                    @wendy2702 Jep

                    wendy2702 1 Reply Last reply Reply Quote 0
                    • Marc Berg
                      Marc Berg Most Active @spicer last edited by

                      @spicer

                      Hast du das Loglevel der MQTT.1 Instanz mal auf "debug" gestellt? Dann sieht man vielleicht mehr. So sieht das erstmal unspektakulär aus.

                      1 Reply Last reply Reply Quote 0
                      • wendy2702
                        wendy2702 @spicer last edited by

                        @spicer der verliert scheinbar im Millisekunden Takt die Verbindung

                        Marc Berg 1 Reply Last reply Reply Quote 0
                        • Marc Berg
                          Marc Berg Most Active @wendy2702 last edited by Marc Berg

                          @wendy2702 sagte in iobroker.js-con 100% cpu:

                          der verliert scheinbar im Millisekunden Takt die Verbindung

                          Oder ein ungünstig progammiertes Script, welches sich anmeldet, Wert subscribed, sich abmeldet, sich wieder anmeldet, nächsten Wert subscribed, ...

                          Darauf deutet der Name hin.

                          spicer 2 Replies Last reply Reply Quote 0
                          • spicer
                            spicer @Marc Berg last edited by

                            @marc-berg
                            Das könnte gut sein. Ich werd mal meine Scripts (Python und BASH) überprüfen.

                            1 Reply Last reply Reply Quote 0
                            • spicer
                              spicer @Marc Berg last edited by

                              @marc-berg
                              Du hast mich auf die richtige Fährte gebracht. Wenn ich die MQTT Server IP ändere (ins Leere), sieht top so aus:

                              Auswahl_006.png

                              Marc Berg 1 Reply Last reply Reply Quote 0
                              • Marc Berg
                                Marc Berg Most Active @spicer last edited by

                                @spicer sagte in iobroker.js-con 100% cpu:

                                Wenn ich die MQTT Server IP ändere (ins Leere)

                                @marc-berg sagte in iobroker.js-con 100% cpu:

                                Hast du das Loglevel der MQTT.1 Instanz mal auf "debug" gestellt?

                                spicer 1 Reply Last reply Reply Quote 0
                                • spicer
                                  spicer @Marc Berg last edited by

                                  @marc-berg
                                  Ja, aber da kann so viel Output, dass top 300% CPU anzeigte ^^

                                  Marc Berg 1 Reply Last reply Reply Quote 0
                                  • Marc Berg
                                    Marc Berg Most Active @spicer last edited by

                                    @spicer sagte in iobroker.js-con 100% cpu:

                                    @marc-berg
                                    Ja, aber da kann so viel Output, dass top 300% CPU anzeigte ^^

                                    Das sagt aber schon alles. Ich bleibe dabei: eine Schleife.

                                    spicer 1 Reply Last reply Reply Quote 1
                                    • spicer
                                      spicer @Marc Berg last edited by

                                      @marc-berg
                                      Jo, das glaube ich Dir.
                                      Muss nun suchen 😞
                                      Ist ziemlich viel.

                                      Marc Berg 1 Reply Last reply Reply Quote 0
                                      • Marc Berg
                                        Marc Berg Most Active @spicer last edited by

                                        @spicer sagte in iobroker.js-con 100% cpu:

                                        Muss nun suchen

                                        Aber wenn du das Debug-Log kurz anmachst, dann wirst du sicher Hinweise sehen.

                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @Marc Berg last edited by

                                          Ist zwar jetzt etwas OT hier, aber hier einer der wirklichen Gründe, warum man keine GUI auf einem Server laufen hat:

                                          https://www.phoronix.com/news/X.Org-CVE-2024-9632

                                          Was nicht läuft und am besten auch erst gar nicht installiert ist kann auch nicht anfällig für eine 'Privilege Escalation' sein.

                                          1 Reply Last reply Reply Quote 0
                                          • spicer
                                            spicer last edited by

                                            Hab das Problem gefunden.
                                            Alle 30 Sekunden oder teilweise sogar 10 Sekunden wurde der MQTT Server mit sub/pub's gelöchert.
                                            Wenn das geschieht, geht die CPU für ca 30 Sekunden auf 100%.
                                            Das war natürlich zuviel.
                                            Habe jetzt das Intervall (ausser Regen und Wind Warnung) auf mind 2 Minuten gesetzt.
                                            So beruhigt sich das Ganze immer für ca 90 Sekunden.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            996
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            9
                                            86
                                            3604
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo