@slibitcs, @rtoelhoej  Thanks for posting. It appears like an issue which Splunk haven't acknowledged or encountered during their testing as it's not listed in the known issues. The daemon is part of the Linux IPC layer and best course of action for you is to immediately raise a Support case with Splunk to report the issue with detailed log information, version information of both your OS and Splunk software.  I have reviewed the known issues for the version and there is no mention about the dbus-daemon spawning repeatedly and consuming CPU resources indicating an issue which they haven't encountered while testing. Reference: Splunk Enterprise 10.2.0 known issues | Splunk Enterprise (last updated 2026-01-17T00:24:43.945Z) > Marking the answer and giving Karma helps others find solutions faster! ... View more