systemd becomes unresponsive

Solution Verified - Updated -

Issue

When trying to updating glibc package in the context of any service unit in rescue mode, systemd becomes unresponsive, while outputting the following message repeatedly:

systemd[1]: Looping too fast. Throttling execution a little.

Once systemd process becomes unresponsive, any systemctl commands relevant to D-Bus connections fail. For example, the following systemctl commands cannot be executed:

  • systemctl start
  • systemctl stop
  • systemctl restart
  • systemctl poweroff
  • systemctl reboot

Environment

  • Red Hat Enterprise Linux 7
  • systemd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.