Community Forum

Resolved
1 votes
dmesg log filling up with a ton of these entries. They look to be useless. Any way to squelch?

[16073.733261] systemd[1]: Got notification message for unit webconfig.service
[16073.733271] systemd[1]: webconfig.service: Got notification message from PID 1460 (READY=1, STATUS=Total requests: 1235; Current requests/sec: 0; Current traffic: 0 B/sec)
[16073.733276] systemd[1]: webconfig.service: got READY=1
[16073.733282] systemd[1]: webconfig.service: got STATUS=Total requests: 1235; Current requests/sec: 0; Current traffic: 0 B/sec
[16073.733366] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10926 reply_cookie=0 error=n/a
[16073.733412] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10927 reply_cookie=0 error=n/a
[16073.733528] systemd-logind[538]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10926 reply_cookie=0 error=n/a
[16073.733560] systemd-logind[538]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=10927 reply_cookie=0 error=n/a
[16363.996659] systemd[1]: Got notification message for unit systemd-logind.service
[16363.996664] systemd[1]: systemd-logind.service: Got notification message from PID 538 (WATCHDOG=1)
[16363.996669] systemd[1]: systemd-logind.service: got WATCHDOG=1
[16363.997095] systemd[1]: Got notification message for unit systemd-journald.service
[16363.997101] systemd[1]: systemd-journald.service: Got notification message from PID 384 (WATCHDOG=1)
[16363.997106] systemd[1]: systemd-journald.service: got WATCHDOG=1
[16374.006190] systemd[1]: Got notification message for unit webconfig.service
[16374.006201] systemd[1]: webconfig.service: Got notification message from PID 1460 (READY=1, STATUS=Total requests: 1235; Current requests/sec: 0; Current traffic: 0 B/sec)
[16374.006206] systemd[1]: webconfig.service: got READY=1
[16374.006212] systemd[1]: webconfig.service: got STATUS=Total requests: 1235; Current requests/sec: 0; Current traffic: 0 B/sec
[16374.006298] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11091 reply_cookie=0 error=n/a
[16374.006344] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11092 reply_cookie=0 error=n/a
[16374.006462] systemd-logind[538]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11091 reply_cookie=0 error=n/a
[16374.006495] systemd-logind[538]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11092 reply_cookie=0 error=n/a
[16384.016384] systemd[1]: Got notification message for unit webconfig.service
[16384.016394] systemd[1]: webconfig.service: Got notification message from PID 1460 (READY=1, STATUS=Total requests: 1235; Current requests/sec: 0; Current traffic: 0 B/sec)
[16384.016399] systemd[1]: webconfig.service: got READY=1
[16384.016405] systemd[1]: webconfig.service: got STATUS=Total requests: 1235; Current requests/sec: 0; Current traffic: 0 B/sec
[16384.016493] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11093 reply_cookie=0 error=n/a
[16384.016539] systemd[1]: Sent message type=signal sender=n/a destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11094 reply_cookie=0 error=n/a
[16384.016657] systemd-logind[538]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11093 reply_cookie=0 error=n/a
[16384.016691] systemd-logind[538]: Got message type=signal sender=:1.0 destination=n/a object=/org/freedesktop/systemd1/unit/webconfig_2eservice interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=11094 reply_cookie=0 error=n/a



Every second im getting these systemd/dbus webconfig.service entries.
Sunday, February 26 2017, 10:53 PM
Share this post:
Responses (2)
  • Accepted Answer

    Saturday, March 04 2017, 11:21 PM - #Permalink
    Resolved
    0 votes
    For what it's worth, I found this post because my system updated and I started receiving the mass errors every five minutes in journalctl. The fix is to edit /usr/clearos/apps/base/deploy/servicewatch and remove the services there that aren't on the system (in my case, it was zarafa-*, ibvpn, eziod, and vpnwatchd).
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, February 26 2017, 11:08 PM - #Permalink
    Resolved
    0 votes
    Im also getting flooded with these as well in dmesg

    [ 380.628113] systemctl[2986]: Failed to get unit file state for zarafa-dagent.service: No such file or directory
    [ 380.637530] systemctl[2997]: Failed to determine peer security context: Protocol not available
    [ 380.637664] systemctl[2997]: Looking for unit files in (higher priority first):
    [ 380.637687] systemctl[2997]: Looking for SysV init scripts in:
    [ 380.637690] systemctl[2997]: /etc/rc.d/init.d
    [ 380.637693] systemctl[2997]: Looking for SysV rcN.d links in:
    [ 380.637695] systemctl[2997]: /etc/rc.d
    [ 380.637757] systemctl[2997]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.637954] systemctl[2997]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.637960] systemctl[2997]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.637990] systemctl[2997]: Failed to get unit file state for zarafa-gateway.service: No such file or directory
    [ 380.645561] systemctl[3008]: Failed to determine peer security context: Protocol not available
    [ 380.645646] systemctl[3008]: Looking for unit files in (higher priority first):
    [ 380.645668] systemctl[3008]: Looking for SysV init scripts in:
    [ 380.645671] systemctl[3008]: /etc/rc.d/init.d
    [ 380.645675] systemctl[3008]: Looking for SysV rcN.d links in:
    [ 380.645677] systemctl[3008]: /etc/rc.d
    [ 380.646665] systemctl[3008]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.647196] systemctl[3008]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.647203] systemctl[3008]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.647234] systemctl[3008]: Failed to get unit file state for zarafa-ical.service: No such file or directory
    [ 380.655286] systemctl[3018]: Failed to determine peer security context: Protocol not available
    [ 380.655394] systemctl[3018]: Looking for unit files in (higher priority first):
    [ 380.655417] systemctl[3018]: Looking for SysV init scripts in:
    [ 380.655420] systemctl[3018]: /etc/rc.d/init.d
    [ 380.655423] systemctl[3018]: Looking for SysV rcN.d links in:
    [ 380.655426] systemctl[3018]: /etc/rc.d
    [ 380.658138] systemctl[3018]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.658387] systemctl[3018]: Got unexpected auxiliary data with level=1 and type=2
    [ 380.658393] systemctl[3018]: Got unexpected auxiliary data with level=1 and type=2
    The reply is currently minimized Show
Your Reply