Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
VDS daemon is not running, and its watchdog is running
# service vdsmd start
vdsm: already running [ OK ]
vdsm start [ OK ]
# service vdsmd status
VDS daemon is not running, and its watchdog is running
The "/var/log/messages" file has the following error
Code:
Jul 8 16:34:46 respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave
Jul 8 16:34:47 python: vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration
I tried commenting out and removing the "Defaults requiretty" line in "/etc/sudoers" file, but I keep getting the same error.
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 ?
Did you make sure these are the last lines of the file? If not they will be overridden by the values that follow.
Okay, I have fixed the issue. The problem was with nsswitch, the linux box was configured to lookup sudo users against ldap directory, and had the below entry in "/etc/nsswitch.conf"
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.