Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. MQTT Adapter füllt RAM >400MB

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    MQTT Adapter füllt RAM >400MB

    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Masifi last edited by

      Hallo Zusammen,

      ich bin neu hier und auch neu im Thema IoBroker. Aktuell versuche ich den Iobroker zusammen mit EDOMI laufen zu lassen. Das funktioniert eigentlich und die Daten kommen in beide Richtungen so an wie sie sollen. Aber irgendwie bekomme ich im Log immer diese Meldungen und nach einem Tag belegt der MQTT Adapter im RAM mehr als 400MB. Ich starte den Iobroker jeden Tag um 4UHr neu.

      2018-11-23 00:00:04.368 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf734f45a047)] connected with secret 1542927604367_7072
      2018-11-23 00:00:04.582 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf734f45a047)] connection closed: disconnected
      2018-11-23 00:00:17.102 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf7350115541)] connected with secret 1542927617101_9526
      2018-11-23 00:00:17.315 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf7350115541)] connection closed: disconnected
      2018-11-23 00:00:21.698 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf73505aaf4c)] connected with secret 1542927621697_3819
      2018-11-23 00:00:21.912 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf73505aaf4c)] connection closed: disconnected
      2018-11-23 00:00:25.347 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf7350954f16)] connected with secret 1542927625346_1702
      2018-11-23 00:00:25.561 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf7350954f16)] connection closed: disconnected
      2018-11-23 00:00:34.148 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf7351224656)] connected with secret 1542927634147_9905
      2018-11-23 00:00:34.383 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf7351224656)] connection closed: disconnected
      2018-11-23 00:03:25.543 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735bd81284)] connected with secret 1542927805542_6105
      2018-11-23 00:03:25.756 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735bd81284)] connection closed: disconnected
      2018-11-23 00:03:28.264 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735c040a78)] connected with secret 1542927808262_2091
      2018-11-23 00:03:28.475 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735c040a78)] connection closed: disconnected
      2018-11-23 00:04:02.574 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735e28c7fa)] connected with secret 1542927842573_9496
      2018-11-23 00:04:02.786 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735e28c7fa)] connection closed: disconnected
      2018-11-23 00:04:06.713 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735e6ae7e7)] connected with secret 1542927846712_994
      2018-11-23 00:04:06.925 - info: mqtt.0 Client [EDOMI MQTT Publish Client (835-5bf735e6ae7e7)] connection closed: disconnected
      ...
      ...
      

      Das geht immer so weiter und kann doch nicht normal sein !? Weiß jemand was hier nicht stimmt !?

      Gruß Mat

      1 Reply Last reply Reply Quote 0
      • E
        edyelektrik last edited by

        Hallo zusammen

        Ich habe leider auch das Problem das mir der MQTT Adapter das logfile füllt.

        Gibt es da schon Ansätze für eine Lösung

        Gruß

        Mario

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

          Conection Closed bedeutet das der MQTT Server die Verbindung zu macht. Findet doch am besten mal raus warum das so ist.

          Der hohe Speicherverbrauch wäre ein Github Issue wert.

          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

          898
          Online

          31.9k
          Users

          80.2k
          Topics

          1.3m
          Posts

          3
          3
          352
          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