RHEL host is marked as non-responsive after being registered to RHEV-M 3.2

Solution Unverified - Updated -

Issue

  • RHEL host is marked as non-responsive after being registered to RHEV-M 3.2
  • The vdsmd service is not running.
  • abrt reports a large number of python exceptions from /usr/share/vdsm/vdsm

Environment

  • Red Hat Enterprise Linux 6.4
  • VDSM

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.