On Sat, Apr 8, 2017 at 3:15 AM, shubham dubey <sdubey504(a)gmail.com> wrote:
I think it will help you getting a proper setup in place starting from a
clean minimal system.
Once the system is up, I would suggest to read also our Administration
Guide at
Recently I have created the first host for my new ovirt setup.But
when I
try to do initialize the host
it was getting failed.So, I think I need to first configure the vdsm in
the host.
I tried "vdsm-tool configure" it is giving me this error.
[root@localhost ~]# vdsm-tool configure
Checking configuration status...
lvm is configured for vdsm
libvirt is already configured for vdsm
FAILED: conflicting vdsm and libvirt-qemu tls configuration.
vdsm.conf with ssl=False requires the following changes:
libvirtd.conf: listen_tcp=1, auth_tcp="none", listen_tls=0
qemu.conf: spice_tls=0.
Error: Configuration of libvirt is invalid
I have changed those values in libvirtd.conf but still getting this same
error.
On Sat, Apr 8, 2017 at 12:19 AM, Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
>
>
> Il 07/Apr/2017 19:53, "shubham dubey" <sdubey504(a)gmail.com> ha
scritto:
>
> Hello,
> I am trying to install and configure vdsm in a newly created centos
> 7.3.The packages that I have installed is vdsm, vdsm-cli and libvirtd.
>
>
> May I ask why are you trying to run vdsm by hand on the host?
>
>
>
> Now when I am trying to start the vdsm service I am getting this error.
>
> [root@localhost ~]# systemctl start vdsmd
>
>
>
>
> Please set a hostname on the host. Localhost won't work very well.
>
> Did you configure vdsm before trying to start it?
> Something like "vdsm-tool configure".
>
>
> Job for vdsmd.service failed because the control process exited with
> error code. See "systemctl status vdsmd.service" and "journalctl
-xe" for
> details.
>
> [root@localhost ~]# journalctl -xe
> -- The result is failed.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Dependency failed for
> MOM instance configured for VDSM purposes.
> -- Subject: Unit mom-vdsm.service has failed
> -- Defined-By: systemd
> -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit mom-vdsm.service has failed.
> --
> -- The result is dependency.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Job
> mom-vdsm.service/start failed with result 'dependency'.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Unit vdsmd.service
> entered failed state.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: vdsmd.service failed.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Cannot add dependency
> job for unit lvm2-lvmetad.socket, ignoring: Invalid re
> Apr 07 23:06:47 localhost.localdomain systemd[1]: vdsmd.service holdoff
> time over, scheduling restart.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Cannot add dependency
> job for unit lvm2-lvmetad.socket, ignoring: Unit is ma
> Apr 07 23:06:47 localhost.localdomain systemd[1]: start request repeated
> too quickly for vdsmd.service
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Failed to start Virtual
> Desktop Server Manager.
> -- Subject: Unit vdsmd.service has failed
> -- Defined-By: systemd
> -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit vdsmd.service has failed.
> --
> -- The result is failed.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Dependency failed for
> MOM instance configured for VDSM purposes.
> -- Subject: Unit mom-vdsm.service has failed
> -- Defined-By: systemd
> -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit mom-vdsm.service has failed.
> --
> -- The result is dependency.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Job
> mom-vdsm.service/start failed with result 'dependency'.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: Unit vdsmd.service
> entered failed state.
> Apr 07 23:06:47 localhost.localdomain systemd[1]: vdsmd.service failed.
>
> the momd service output is
>
> [root@localhost ~]# systemctl status momd
> ● momd.service - Memory Overcommitment Manager Daemon
> Loaded: loaded (/usr/lib/systemd/system/momd.service; static; vendor
> preset: disabled)
> Active: inactive (dead) since Fri 2017-04-07 23:15:32 IST; 3s ago
> Process: 13031 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file
> /var/run/momd.pid (code=exited, status=0/SUCCESS)
> Main PID: 13034 (code=exited, status=0/SUCCESS)
>
> Apr 07 23:15:32 localhost.localdomain systemd[1]: Starting Memory
> Overcommitment Manager Daemon...
> Apr 07 23:15:32 localhost.localdomain systemd[1]: PID file
> /var/run/momd.pid not readable (yet?) after start.
> Apr 07 23:15:32 localhost.localdomain systemd[1]: Started Memory
> Overcommitment Manager Daemon.
> Apr 07 23:15:32 localhost.localdomain python[13034]: No worthy mechs found
>
>
> the output for starting mom-vdsm service is
>
> [root@localhost ~]# systemctl restart mom-vdsm.service
> A dependency job for mom-vdsm.service failed. See 'journalctl -xe' for
> details.
> [root@localhost ~]# journalctl -xe
> -- The result is failed.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Dependency failed for
> MOM instance configured for VDSM purposes.
> -- Subject: Unit mom-vdsm.service has failed
> -- Defined-By: systemd
> -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit mom-vdsm.service has failed.
> --
> -- The result is dependency.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Job
> mom-vdsm.service/start failed with result 'dependency'.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Unit vdsmd.service
> entered failed state.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: vdsmd.service failed.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Cannot add dependency
> job for unit lvm2-lvmetad.socket, ignoring: Invalid re
> Apr 07 23:18:40 localhost.localdomain systemd[1]: vdsmd.service holdoff
> time over, scheduling restart.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Cannot add dependency
> job for unit lvm2-lvmetad.socket, ignoring: Unit is ma
> Apr 07 23:18:40 localhost.localdomain systemd[1]: start request repeated
> too quickly for vdsmd.service
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Failed to start Virtual
> Desktop Server Manager.
> -- Subject: Unit vdsmd.service has failed
> -- Defined-By: systemd
> -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit vdsmd.service has failed.
> --
> -- The result is failed.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Dependency failed for
> MOM instance configured for VDSM purposes.
> -- Subject: Unit mom-vdsm.service has failed
> -- Defined-By: systemd
> -- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> --
> -- Unit mom-vdsm.service has failed.
> --
> -- The result is dependency.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Job
> mom-vdsm.service/start failed with result 'dependency'.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: Unit vdsmd.service
> entered failed state.
> Apr 07 23:18:40 localhost.localdomain systemd[1]: vdsmd.service failed.
>
>
> Thanks,
> Shubham
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
>
http://lists.ovirt.org/mailman/listinfo/users
>
>
>
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <
TRIED. TESTED. TRUSTED. <