›

Why is dbus-org.freedesktop.timedate1 started so frequently?

guchshenskayaguchshenskaya
in Repetier-Server
syslog:
...
Mar 23 00:00:33 Repetier-Server dbus-daemon[390]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.32358' (uid=0 pid=19311 comm="timedatectl ")
Mar 23 00:00:33 Repetier-Server systemd[1]: Starting Time & Date Service...
Mar 23 00:00:33 Repetier-Server dbus-daemon[390]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 00:00:33 Repetier-Server systemd[1]: Started Time & Date Service.
Mar 23 00:01:03 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.
Mar 23 00:01:35 Repetier-Server dbus-daemon[390]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.32363' (uid=0 pid=19451 comm="timedatectl ")
Mar 23 00:01:35 Repetier-Server systemd[1]: Starting Time & Date Service...
Mar 23 00:01:36 Repetier-Server dbus-daemon[390]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 00:01:36 Repetier-Server systemd[1]: Started Time & Date Service.
Mar 23 00:02:06 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.
Mar 23 00:02:38 Repetier-Server dbus-daemon[390]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.32368' (uid=0 pid=19595 comm="timedatectl ")
Mar 23 00:02:38 Repetier-Server systemd[1]: Starting Time & Date Service...
Mar 23 00:02:38 Repetier-Server dbus-daemon[390]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 00:02:38 Repetier-Server systemd[1]: Started Time & Date Service.
Mar 23 00:03:08 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.
Mar 23 00:03:40 Repetier-Server dbus-daemon[390]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.32373' (uid=0 pid=19737 comm="timedatectl ")
Mar 23 00:03:40 Repetier-Server systemd[1]: Starting Time & Date Service...
Mar 23 00:03:41 Repetier-Server dbus-daemon[390]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 00:03:41 Repetier-Server systemd[1]: Started Time & Date Service.
Mar 23 00:04:11 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.
Mar 23 00:04:43 Repetier-Server dbus-daemon[390]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.32378' (uid=0 pid=19879 comm="timedatectl ")
Mar 23 00:04:43 Repetier-Server systemd[1]: Starting Time & Date Service...
Mar 23 00:04:43 Repetier-Server dbus-daemon[390]: [system] Successfully activated service 'org.freedesktop.timedate1'
Mar 23 00:04:43 Repetier-Server systemd[1]: Started Time & Date Service.
Mar 23 00:05:13 Repetier-Server systemd[1]: systemd-timedated.service: Succeeded.
...

Comments

  • RepetierRepetier
    I also wondered my self. I could not really find a satisfying answer. The service it self is meant to be called and finish directly. It gets activated automatically by a special message on the dbus. So the fact that it is there so frequently is no bug, just a result of getting that signal on dbus so often. Has something to do with systemd time synchronization, but it is really awkward to get so much logging for that reason.
  • TT_VertTT_Vert
    Sorry to bring up a super old thread but are we just good leaving this?  I've been going through various logs lately to try to optimize somethings.  I am using the repetier image w/ only pi-hole as an additional app on there.  Given others have have the same result I assume it's due to repetier in some way.  @guchshenskaya, do you have a repetier image installed or just a repetier install on an existing Raspbian install?  In looking at logs, I see mine is running exactly every one minute and it's really filling up syslog.  There has to be something restarting this every minute but not sure what.

    In my research I found someone who had mentioned this:

    It turns out that a configuration management system was calling timedatectl every ~10 minutes in order to check the current timezone.

    This calls timedate1 over DBUS to get the answer, which only activates on incoming messages.


  • RepetierRepetier
    It is from linux and independent of us. You can configure linux to filter these messages. Add file

    /etc/rsyslog.d/00-filter.conf

    with this content:
    :msg, contains, "systemd-timedated" ~
    :msg, contains, " RRM: Ignoring radio" ~
    :msg, contains, "org.freedesktop.timedate1" ~

    after restart it stops adding lines with these text in message.
  • TT_VertTT_Vert
    Thanks, yeah I knew I could suppress it, i just wanted to see if I could change the time from 1 minute to something longer while still having it in logs.

    Dave
  • TT_VertTT_Vert
    BTW, rsyslog complains using ~ so i'd just use stop instead of ~ to prevent seeing this in logs instead:

    Jan 15 08:50:14 pi rsyslogd: warning: ~ action is deprecated, consider using the 'stop' statement instead [v8.2102.0 try https://www.rsyslog.com/e/2307 ;                          ]


    Dave
  • RepetierRepetier
    Thanks for the deprecated message. Missed this on new image I had this for.
Sign In or Register to comment.