Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Javascript loggt zu viele debug messages

    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

    Javascript loggt zu viele debug messages

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

      Ich habe 2 Instanzen von dem Javascript-Adapter laufen, eine für Produktion mit 'info' level und eine Instanz zum testen und scripte kreieren die ich auf debug level stellen will.

      Nun füllt der Adapter aber den log mit 20-50 logs pro Sekunde welche von irgendwelchen internen messages stammen:

      javascript.1	2016-11-30 18:53:51.740	debug	host. redis pmessage io.* io.system.adapter.fritzbox.0.memHeapUsed {"val":12.42,"ack":true,"ts":1480528431722,"q":0,"from":"system.adapter.fritzbox.0","lc":1480528431722}
      javascript.1	2016-11-30 18:53:51.739	debug	host. redis pmessage io.* io.system.adapter.fritzbox.0.memHeapTotal {"val":14.36,"ack":true,"ts":1480528431722,"q":0,"from":"system.adapter.fritzbox.0","lc":1480486549592}
      javascript.1	2016-11-30 18:53:51.739	debug	host. redis pmessage io.* io.system.adapter.fritzbox.0.memRss {"val":30.68,"ack":true,"ts":1480528431721,"q":0,"from":"system.adapter.fritzbox.0","lc":1480528431721}
      javascript.1	2016-11-30 18:53:51.738	debug	host. redis pmessage io.* io.system.adapter.fritzbox.0.connected {"val":true,"ack":true,"ts":1480528431721,"q":0,"from":"system.adapter.fritzbox.0","lc":1480427223860}
      javascript.1	2016-11-30 18:53:51.738	debug	host. redis pmessage io.* io.system.adapter.fritzbox.0.alive {"val":true,"ack":true,"ts":1480528431720,"q":0,"from":"system.adapter.fritzbox.0","lc":1480427223858}
      javascript.1	2016-11-30 18:53:49.637	debug	host. redis pmessage io.* io.system.adapter.radar.0.uptime {"val":17185,"ack":true,"ts":1480528429622,"q":0,"from":"system.adapter.radar.0","lc":1480528429622}
      javascript.1	2016-11-30 18:53:49.636	debug	host. redis pmessage io.* io.system.adapter.radar.0.memHeapUsed {"val":14.02,"ack":true,"ts":1480528429621,"q":0,"from":"system.adapter.radar.0","lc":1480528429621}
      javascript.1	2016-11-30 18:53:49.636	debug	host. redis pmessage io.* io.system.adapter.radar.0.memHeapTotal {"val":16.33,"ack":true,"ts":1480528429621,"q":0,"from":"system.adapter.radar.0","lc":1480528354608}
      javascript.1	2016-11-30 18:53:49.635	debug	host. redis pmessage io.* io.system.adapter.radar.0.memRss {"val":33.53,"ack":true,"ts":1480528429620,"q":0,"from":"system.adapter.radar.0","lc":1480528429620}
      javascript.1	2016-11-30 18:53:49.635	debug	host. redis pmessage io.* io.system.adapter.radar.0.connected {"val":true,"ack":true,"ts":1480528429619,"q":0,"from":"system.adapter.radar.0","lc":1480511247049}
      javascript.1	2016-11-30 18:53:49.634	debug	host. redis pmessage io.* io.system.adapter.radar.0.alive {"val":true,"ack":true,"ts":1480528429619,"q":0,"from":"system.adapter.radar.0","lc":1480511247046}
      javascript.1	2016-11-30 18:53:49.093	debug	host. redis pmessage io.* io.system.adapter.javascript.0.uptime {"val":783,"ack":true,"ts":1480528429080,"q":0,"from":"system.adapter.javascript.0","lc":1480528429080}
      javascript.1	2016-11-30 18:53:49.093	debug	host. redis pmessage io.* io.system.adapter.javascript.0.memHeapUsed {"val":27.97,"ack":true,"ts":1480528429079,"q":0,"from":"system.adapter.javascript.0","lc":1480528429079}
      javascript.1	2016-11-30 18:53:49.092	debug	host. redis pmessage io.* io.system.adapter.javascript.0.memHeapTotal {"val":28.93,"ack":true,"ts":1480528429078,"q":0,"from":"system.adapter.javascript.0","lc":1480527978958}
      javascript.1	2016-11-30 18:53:49.092	debug	host. redis pmessage io.* io.system.adapter.javascript.0.memRss {"val":50.5,"ack":true,"ts":1480528429077,"q":0,"from":"system.adapter.javascript.0","lc":1480528414073}
      javascript.1	2016-11-30 18:53:49.091	debug	host. redis pmessage io.* io.system.adapter.javascript.0.connected {"val":true,"ack":true,"ts":1480528429076,"q":0,"from":"system.adapter.javascript.0","lc":1480527648902}
      javascript.1	2016-11-30 18:53:49.081	debug	host. redis pmessage io.* io.system.adapter.javascript.0.alive {"val":true,"ack":true,"ts":1480528429075,"q":0,"from":"system.adapter.javascript.0","lc":1480527648899}
      javascript.1	2016-11-30 18:53:48.767	debug	host. redis pmessage io.* io.system.adapter.javascript.1.uptime {"val":332,"ack":true,"ts":1480528428748,"q":0,"from":"system.adapter.javascript.1","lc":1480528428748}
      javascript.1	2016-11-30 18:53:48.767	debug	host. redis pmessage io.* io.system.adapter.javascript.1.memHeapUsed {"val":17.41,"ack":true,"ts":1480528428747,"q":0,"from":"system.adapter.javascript.1","lc":1480528428747}
      javascript.1	2016-11-30 18:53:48.767	debug	host. redis pmessage io.* io.system.adapter.javascript.1.memHeapTotal {"val":25.98,"ack":true,"ts":1480528428745,"q":0,"from":"system.adapter.javascript.1","lc":1480528398741}
      javascript.1	2016-11-30 18:53:48.766	debug	host. redis pmessage io.* io.system.adapter.javascript.1.memRss {"val":45.29,"ack":true,"ts":1480528428744,"q":0,"from":"system.adapter.javascript.1","lc":1480528428744}
      javascript.1	2016-11-30 18:53:48.766	debug	host. redis pmessage io.* io.system.adapter.javascript.1.connected {"val":true,"ack":true,"ts":1480528428741,"q":0,"from":"system.adapter.javascript.1","lc":1480528098666}
      javascript.1	2016-11-30 18:53:48.764	debug	host. redis pmessage io.* io.system.adapter.javascript.1.alive {"val":true,"ack":true,"ts":1480528428739,"q":0,"from":"system.adapter.javascript.1","lc":1480528098663}
      javascrip
      

      Im adapter unter dem log des scriptes tauchen die einträge nicht auf, jedoch im globalen log sehr wohl.

      Somit kann man kaum einen Javascript-Adapter auf debug level schalten da man sonst den normalen log nicht wirklich mehr verwenden kann um das Zusammenspiel von Adaptern/scripten zu beobachten.

      Ist es möglich diese internen debug-messages irgendwie auszuschalten und nur die messages durchzulassen die wirklich im adapter durch die scripts erzeugt werden?

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

        Der Effekt tritt auf sobald man Redis hat. Ist auch bei allen Adaptern so

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

          Ok, kann man das irgendwie ausschalten? Möglicherweise im redis-Teil?

          Ich verstehe dass es zum Debuggen von Adaptern oder dem redis notwendig ist aber ich möchte Messages ausschalten können die ich nicht selbst generiert habe.

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

          Support us

          ioBroker
          Community Adapters
          Donate

          746
          Online

          31.8k
          Users

          80.0k
          Topics

          1.3m
          Posts

          2
          3
          525
          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