<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 2, 2015 at 5:56 AM, Willard Dennis <span dir="ltr"><<a href="mailto:wdennis@nec-labs.com" target="_blank">wdennis@nec-labs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Did the following:</div><div><br></div><div>1) yum remove vdsm*</div><div>[…]</div><div>Removed:</div><div> vdsm.noarch 0:4.17.10.1-0.el7.centos vdsm-cli.noarch 0:4.17.10.1-0.el7.centos vdsm-gluster.noarch 0:4.17.10.1-0.el7.centos</div><div> vdsm-infra.noarch 0:4.17.10.1-0.el7.centos vdsm-jsonrpc.noarch 0:4.17.10.1-0.el7.centos vdsm-python.noarch 0:4.17.10.1-0.el7.centos</div><div> vdsm-xmlrpc.noarch 0:4.17.10.1-0.el7.centos vdsm-yajsonrpc.noarch 0:4.17.10.1-0.el7.centos</div><div><br></div><div>Dependency Removed:</div><div> ovirt-hosted-engine-ha.noarch 0:1.3.2.1-1.el7.centos ovirt-hosted-engine-setup.noarch 0:1.3.0-1.el7.centos </div><div><br></div><div><br></div><div>2) yum install vdsm vdsm-cli vdsm-gluster vdsm-infra vdsm-jsonrpc vdsm-python vdsm-xmlrpc vdsm-yajsonrpc</div><div>[…]</div><div><div>Installed:</div><div> vdsm.noarch 0:4.17.11-0.el7.centos vdsm-cli.noarch 0:4.17.11-0.el7.centos vdsm-gluster.noarch 0:4.17.11-0.el7.centos</div><div> vdsm-infra.noarch 0:4.17.11-0.el7.centos vdsm-jsonrpc.noarch 0:4.17.11-0.el7.centos vdsm-python.noarch 0:4.17.11-0.el7.centos</div><div> vdsm-xmlrpc.noarch 0:4.17.11-0.el7.centos vdsm-yajsonrpc.noarch 0:4.17.11-0.el7.centos</div></div><div><br></div><div>3) yum install ovirt-hosted-engine-setup ovirt-hosted-engine-ha</div><div>[…]</div><div><div>Installed:</div><div> ovirt-hosted-engine-ha.noarch 0:1.3.3-1.el7.centos ovirt-hosted-engine-setup.noarch 0:1.3.1-1.el7.centos</div><div><br></div><div>Dependency Updated:</div><div> ovirt-host-deploy.noarch 0:1.4.1-1.el7.centos</div></div><div><br></div><div><br></div><div>Result:</div><div><div>[root@ovirt-node-01 ~]# systemctl start vdsmd</div><div>Job for vdsmd.service failed. See 'systemctl status vdsmd.service' and 'journalctl -xn' for details.</div><div>[root@ovirt-node-01 ~]# systemctl status vdsmd.service</div><div>vdsmd.service - Virtual Desktop Server Manager</div><div> Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)</div><div> Active: failed (Result: start-limit) since Tue 2015-12-01 23:55:05 EST; 14s ago</div><div> Process: 21336 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh --pre-start (code=exited, status=1/FAILURE)</div><div> Main PID: 20589 (code=exited, status=1/FAILURE)</div><div><br></div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop Server Manager.</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed state.</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server Manager...</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over, scheduling restart.</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Stopping Virtual Desktop Server Manager...</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server Manager...</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service start request repeated too quickly, refusing to start.</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop Server Manager.</div><div>Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered failed state.</div></div><div><br></div><div>Different error now, but vdsmd service still won’t restart correctly...</div></div></blockquote><div><br></div><div>Now can you please now configure it with:</div><div> vdsm-tool configure --force<br></div><div><br></div><div>Then you have to restart it</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><span><div><br></div><br><div><blockquote type="cite"><div>On Dec 1, 2015, at 9:25 AM, Simone Tiraboschi <<a href="mailto:stirabos@redhat.com" target="_blank">stirabos@redhat.com</a>> wrote:</div><div><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 1, 2015 at 3:15 PM, Will Dennis <span dir="ltr"><<a href="mailto:wdennis@nec-labs.com" target="_blank">wdennis@nec-labs.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I believe sudo is NOT setup for passwordless (then again, didn't see that in any pre-req instructions...) Who would be the sudoer in this case?<br></blockquote><div><br></div><div>It's not required to take any manual action.</div><div>Can you please try to reinstall vdsm from its rpms and try it again?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<span><br>
-----Original Message-----<br>
From: Fabian Deutsch [mailto:<a href="mailto:fdeutsch@redhat.com" target="_blank">fdeutsch@redhat.com</a>]<br>
Sent: Tuesday, December 01, 2015 12:58 AM<br>
To: Will Dennis<br>
</span><div><div>Cc: Simone Tiraboschi; users<br>
Subject: Re: [ovirt-users] Problem with hosted engine setup - vsdmd does not start<br>
<br>
On Tue, Dec 1, 2015 at 4:52 AM, Will Dennis <<a href="mailto:wdennis@nec-labs.com" target="_blank">wdennis@nec-labs.com</a>> wrote:<br>
> Any clues out of the strace of vdsm?<br>
<br>
read(9, "sudo: a password is required\n", 4096) = 29<br>
<br>
Could it be that sudo is not configured to operate passwordless?<br>
<br>
The strat-up can then fail, because sudo requires a ty, but this isn't available during service start.<br>
<br>
- fabian<br></div></div></blockquote></div></div></div></div></blockquote></div><br></span></div></blockquote></div><br></div></div>