4

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).

1 Answer 1

3

There is a mapping between a unique connection name and process accessible through busctl.

If it remains stable for a few seconds you could try your luck in trying to catch it as it occurs.

journalctl -f | \
while read line ; do
        echo "$line" | grep "sender=:"
        if [ $? = 0 ]
        then
                busctl --no-pager | grep
        fi
done

(Based on this answer)

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .