vdsm service is failing to start
I am currently evaluating Red Hat Enterprise Virtualization and have managed to set up the management server and the bare metal hypervisor. Now I'm trying to add a regular box running RHEL server 6.5 to the data center as a host. The add new host process starts fine and installs all the packages successfully. But after a certain time it fails saying network communication failure. From the engine.log I figured out this was caused by vdsmd service not restarting properly on the target. And indeed when I manually try to start the service at the host itself, it fails.
Code:
# service vdsmd status Code:
Jul 8 16:34:46 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave As i'm evaluating RHEV, i am not entitled to red hat support and have to fix it myself. Any ideas on what to do ? |
vdsm ALL=(ALL) NOPASSWD:'/usr/share/vdsm/vdsm
Defaults:vdsm !requiretty or vdsm ALL=(ALL) ALL Defaults:vdsm !requiretty |
Quote:
|
Did you make sure these are the last lines of the file? If not they will be overridden by the values that follow.
|
Quote:
|
The manager added the line "#includedir /etc/sudoers.d" at the end of the sudoers file and the directory has a file with custom vdsm rules
Code:
cat /etc/sudoers.d/50_vdsm |
Try putting this at the top instead of the bottom:
Defaults:vdsm !requiretty Defaults:vdsm !syslog |
Quote:
Code:
sudoers: files ldap when I changed the order to "ldap files" everything started to work normally, but that somewhat doesn't makes sense sisnce the existing entry was supposed to make sudo search local file before ldap lookup. The main issue is fixed, but the mystery of "files ldap" not working remains. |
All times are GMT -5. The time now is 08:29 PM. |