3:57 a.m.
On Wed, Dec 2, 2015 at 5:56 AM, Willard Dennis <wdennis(a)nec-labs.com> wrote:
Did the following:
1) yum remove vdsm*
[…]
Removed:
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
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
vdsm-xmlrpc.noarch 0:4.17.10.1-0.el7.centos vdsm-yajsonrpc.noarch
0:4.17.10.1-0.el7.centos
Dependency Removed:
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
2) yum install vdsm vdsm-cli vdsm-gluster vdsm-infra vdsm-jsonrpc
vdsm-python vdsm-xmlrpc vdsm-yajsonrpc
[…]
Installed:
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
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
vdsm-xmlrpc.noarch 0:4.17.11-0.el7.centos vdsm-yajsonrpc.noarch
0:4.17.11-0.el7.centos
3) yum install ovirt-hosted-engine-setup ovirt-hosted-engine-ha
[…]
Installed:
ovirt-hosted-engine-ha.noarch 0:1.3.3-1.el7.centos
ovirt-hosted-engine-setup.noarch 0:1.3.1-1.el7.centos
Dependency Updated:
ovirt-host-deploy.noarch 0:1.4.1-1.el7.centos
Result:
[root@ovirt-node-01 ~]# systemctl start vdsmd
Job for vdsmd.service failed. See 'systemctl status vdsmd.service' and
'journalctl -xn' for details.
[root@ovirt-node-01 ~]# systemctl status vdsmd.service
vdsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled)
Active: failed (Result: start-limit) since Tue 2015-12-01 23:55:05 EST;
14s ago
Process: 21336 ExecStartPre=/usr/libexec/vdsm/vdsmd_init_common.sh
--pre-start (code=exited, status=1/FAILURE)
Main PID: 20589 (code=exited, status=1/FAILURE)
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop
Server Manager.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered
failed state.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server
Manager...
Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service holdoff time over,
scheduling restart.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Stopping Virtual Desktop Server
Manager...
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Starting Virtual Desktop Server
Manager...
Dec 01 23:55:05 ovirt-node-01 systemd[1]: vdsmd.service start request
repeated too quickly, refusing to start.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Failed to start Virtual Desktop
Server Manager.
Dec 01 23:55:05 ovirt-node-01 systemd[1]: Unit vdsmd.service entered
failed state.
Different error now, but vdsmd service still won’t restart correctly...
Now can you please now configure it with:
vdsm-tool configure --force
Then you have to restart it
On Dec 1, 2015, at 9:25 AM, Simone Tiraboschi <stirabos(a)redhat.com> wrote:
On Tue, Dec 1, 2015 at 3:15 PM, Will Dennis <wdennis(a)nec-labs.com> wrote:
> 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?
>
It's not required to take any manual action.
Can you please try to reinstall vdsm from its rpms and try it again?
>
> -----Original Message-----
> From: Fabian Deutsch [mailto:fdeutsch@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(a)nec-labs.com> wrote:
> > Any clues out of the strace of vdsm?
>
> 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
>