Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start (RESOLVED)

The vdsmd startup failing problem is now resolved :) The root cause was that the /etc/sudoers file (that we maintain a customized version of which thru Ansible) was missing the "#includedir /etc/sudoers.d" stanza, which caused a sudo problem with the vdsmd startup, since the sudoers include file "50-vdsm" wasn't being parsed. In going back and reviewing the thread, this was the first post that pointed out the real problem... -----Original Message----- From: Fabian Deutsch [mailto:fdeutsch at redhat.com] Sent: Tuesday, December 01, 2015 12:58 AM To: Will Dennis Cc: Simone Tiraboschi; users Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis <wdennis at nec-labs.com> wrote: read(9, "sudo: a password is required\n", 4096) = 29 Could it be that sudo is not configured to operate passwordless? The strat-up can then fail, because sudo requires a ty, but this isn't available during service start. - fabian -----Message End----- However, not knowing about the missing sudoers include file, we continued to chase a vdsm config problem (uninstall / reinstall vdsm RPM pkgs, & use "vdsm-tool configure --force") Shame on me, it looks like I didn't think to check /var/log/messages for "vdsm"-string entries until today, where we found the "vdsm user could not manage to run sudo operation: (stderr: ['sudo: sorry, you must have a tty to run sudo']). Verify sudoer rules configuration” message that ultimately led to the solution :( However, not sure if it's possible to do so, but could /usr/share/vdsm/vdsm be made to emit a error to STDERR if it cannot run correctly? That's the only thing I could think of that may have helped me to resolve this earlier with what I did do... Thanks for everyone's kind assistance, this really is a great community! :) -Will