http://bugzilla.suse.com/show_bug.cgi?id=1056011 Bug ID: 1056011 Summary: multipathd produces too many sd_notify events Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: martin.wilck@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- The state DAEMON_RUNNING is used by multipathd's checkerloop to indicate that path checkers are running. checkerloop switches back and forth between DAEMON_IDLE and DAEMON_RUNNING in every iteration, i.e. it performs two status changes per second on an idle system, and sends a notification to systemd using sd_notify every time. The repeated sd_notify() calls cause a lot of traffic on dbus as systemd forwards these messages on the system bus. This can be seen with systemd.log_level=debug. Better skip these notifications that don't provide useful information to the user, who is very unlikely to catch the daemon in "running" state anyway. If booting with systemd.log_level=debug and serial console, this can basically prevent the system from booting because multipathd/systemd generate log messages constantly at the same speed the serial console is able to print them. I have a patch for this which I'm going to submit upstream. -- You are receiving this mail because: You are on the CC list for the bug.