Skip to main content
Question

Can't reboot Commvault server

  • October 1, 2026
  • 1 reply
  • 20 views

Forum|alt.badge.img

I find all jobs in waiting state e the volume offline.

I restart Media agent and the volume comeback online, but the jobs stay in waiting mode , then I try to restart the comvault server (LIUX - Roky), but the server don’t start anymore and in boot screen appear the fail error : Failed to start D-Bus Dbus system message BUS.

1 reply

Forum|alt.badge.img+17
  • Vaulter
  • October 2, 2026

Hi ​@Roberto ITPVS ,

The error "Failed to start D-Bus: Dbus system message bus" usually means the D-Bus service is not running, failed to start, or is corrupted. Verify for the following.
 

  • Permission denied
  • Identify the reason the D-Bus service failed.

  • Failed to bind socket
  • Missing configuration files
  • Corrupted package

I would recommend involving the Linux Administrator team to further investigate the "Failed to start D-Bus System Message Bus" error. They can review the system logs and service status to determine the root cause and recommend appropriate remediation steps.

logs to validate:

  • journalctl -u dbus -b
  • journalctl -u dbus-broker -b
  • journalctl -xe
  • systemctl status dbus dbus-broker dbus.socket
  • /var/log/messages
  • /var/log/secure
  • SELinux audit logs (/var/log/audit/audit.log), if applicable

The Linux team can analyze these logs for service startup failures, permission issues, missing dependencies, socket creation failures, filesystem-related issues, or SELinux denials, and advise on the next steps based on their findings.