Named-chroot.service causes soft lockup, hard lockup or OOM when it was restarted or stopped.

Solution Verified - Updated -

Issue

  • Trigger a soft lockup, hard lockup or OOM in /var/log/messages when executing "systemctl restart or stop named-chroot.service".
  • Named-chroot.service causes memory leaks and kernel panics.

Environment

  • Red Hat Enterprise Linux 7.4
  • bind-chroot-9.9.4-50.el7.x86_64
  • bind-9.9.4-50.el7.x86_64

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

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