it's plausible that systemctl restart supervdsm
is required as well On Mon, Nov 25, 2019 at 12:17 PM Parth Dhanjal <dpa...@redhat.com> wrote: > As such there are no errors in the vdsm log. > Maybe you can try these steps again > > *ovirt-hosted-engine-cleanup* > *vdsm-tool configure --force* > *systemctl restart libvirtd* > *systemctl restart vdsm* > > And continue with the hosted engine deployment, in case the hosted engine > deployment fails you can look for errors > under /var/log/ovirt-hosted-engine-setup/engine.log > > > On Mon, Nov 25, 2019 at 3:13 PM Rob <rob.dow...@orbitalsystems.co.uk> > wrote: > >> >> >> On 25 Nov 2019, at 09:28, Parth Dhanjal <dpa...@redhat.com> wrote: >> >> /var/log/vdsm/vdsm.log >> >> >> _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/XD3TXRCVGTSJFULHGWGBUEHV43CRWPE2/ >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/M4NBRK272ZO3DC4HBBAUEAOMUKFTQARK/
