How do I work out which process/service/program is sending systemd dbus messages?












0















Currently my systemd journal is filling up with messages of the form:



Feb 01 16:40:31 host systemd[1]: Got message type=method_call sender=:1.58666 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=Get cookie=2 reply_cookie=0 error=n/a



The only identifier seems to be the sender, which appears to change every few seconds (so I've failed at trying to map the sender to a PID), and this does not appear to happen on other systems on similar hardware or OS. Is there some way of identifying what is sending this messages (so that I can either stop that process/service/whatever or control the amount of messages sent).









share



























    0















    Currently my systemd journal is filling up with messages of the form:



    Feb 01 16:40:31 host systemd[1]: Got message type=method_call sender=:1.58666 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=Get cookie=2 reply_cookie=0 error=n/a



    The only identifier seems to be the sender, which appears to change every few seconds (so I've failed at trying to map the sender to a PID), and this does not appear to happen on other systems on similar hardware or OS. Is there some way of identifying what is sending this messages (so that I can either stop that process/service/whatever or control the amount of messages sent).









    share

























      0












      0








      0








      Currently my systemd journal is filling up with messages of the form:



      Feb 01 16:40:31 host systemd[1]: Got message type=method_call sender=:1.58666 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=Get cookie=2 reply_cookie=0 error=n/a



      The only identifier seems to be the sender, which appears to change every few seconds (so I've failed at trying to map the sender to a PID), and this does not appear to happen on other systems on similar hardware or OS. Is there some way of identifying what is sending this messages (so that I can either stop that process/service/whatever or control the amount of messages sent).









      share














      Currently my systemd journal is filling up with messages of the form:



      Feb 01 16:40:31 host systemd[1]: Got message type=method_call sender=:1.58666 destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.DBus.Properties member=Get cookie=2 reply_cookie=0 error=n/a



      The only identifier seems to be the sender, which appears to change every few seconds (so I've failed at trying to map the sender to a PID), and this does not appear to happen on other systems on similar hardware or OS. Is there some way of identifying what is sending this messages (so that I can either stop that process/service/whatever or control the amount of messages sent).







      debian systemd systemd-journald journalctl





      share












      share










      share



      share










      asked 7 mins ago









      James TocknellJames Tocknell

      14028




      14028






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498062%2fhow-do-i-work-out-which-process-service-program-is-sending-systemd-dbus-messages%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498062%2fhow-do-i-work-out-which-process-service-program-is-sending-systemd-dbus-messages%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Accessing regular linux commands in Huawei's Dopra Linux

          Can't connect RFCOMM socket: Host is down

          Kernel panic - not syncing: Fatal Exception in Interrupt