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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content