RHEV: vdsm is down due to unconfigured sanlock module

Solution Verified - Updated -

Issue

  • vdsmd got killed by wrong manipulation of system files
  • /etc/group changed
  • now vdsmd fails to restart
  • vdsmd communication broken
  • RHEV-M is not able to communicate with this hypervisor anymore
  • following error can be seen when trying to start vdsm again:
# /etc/init.d/vdsmd start
vdsm: Running mkdirs
vdsm: Running configure_coredump
vdsm: Running configure_vdsm_logs
vdsm: Running wait_for_network
vdsm: Running run_init_hooks
vdsm: Running upgraded_version_check
vdsm: Running check_is_configured
libvirt is already configured for vdsm
Modules sanlock are not configured
Error:  

One of the modules is not configured to work with VDSM.
To configure the module use the following:
'vdsm-tool configure [--module module-name]'.

If all modules are not configured try to use:
'vdsm-tool configure --force'
(The force flag will stop the module's service and start it
afterwards automatically to load the new configuration.)

vdsm: stopped during execute check_is_configured task (task returned with error code 1).
vdsm start                                                 [FAILED]

Environment

  • Red Hat Enterprise Virtualization 3.5
  • Red Hat Enterprise Linux 6.7
    • sanlock-2.8-2.el6_5
    • vdsm-4.16.13.1-1.el6ev
    • vdsm-python-4.16.13.1-1.el6ev
    • libvirt-0.10.2-54.el6

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