Simone,

Here it is.

● vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor preset: enabled)
   Active: activating (start-pre) since Fri 2019-03-22 12:46:48 MSK; 3s ago
  Process: 56712 ExecStopPost=/usr/libexec/vdsm/vdsmd_init_common.sh --post-stop (code=exited, status=0/SUCCESS)
  Control: 116050 (vdsmd_init_comm)
    Tasks: 3
   CGroup: /system.slice/vdsmd.service
           └─control
             ├─116050 /bin/sh /usr/libexec/vdsm/vdsmd_init_common.sh --pre-start
             └─116066 /usr/bin/python2 /usr/libexec/vdsm/wait_for_ipv4s

Mar 22 12:46:48 ovirt2.domain.org systemd[1]: Starting Virtual Desktop Server Manager...
Mar 22 12:46:48 ovirt2.domain.org vdsmd_init_common.sh[116050]: vdsm: Running mkdirs
Mar 22 12:46:49 ovirt2.domain.org vdsmd_init_common.sh[116050]: vdsm: Running configure_coredump
Mar 22 12:46:49 ovirt2.domain.org vdsmd_init_common.sh[116050]: vdsm: Running configure_vdsm_logs
Mar 22 12:46:49 ovirt2.domain.org vdsmd_init_common.sh[116050]: vdsm: Running wait_for_network

vdsm.log attached.


On Fri, Mar 22, 2019 at 12:10 PM Simone Tiraboschi <stirabos@redhat.com> wrote:


On Fri, Mar 22, 2019 at 10:06 AM Artem Tambovskiy <artem.tambovskiy@gmail.com> wrote:
Hi,

I have exactly the same issue after upgrade from 4.2.8 to 4.3.2. I can reach the host from SHE but the VDSM is constantly failing to start on the host after upgrade.

Can you please attach the output of
systemctl status vdsmd

and your /var/log/vdsm/vdsm.log?
 

чт, 21 мар. 2019 г., 19:48 Simone Tiraboschi <stirabos@redhat.com>:


On Thu, Mar 21, 2019 at 3:47 PM Arif Ali <mail@arif-ali.co.uk> wrote:
Hi all,

Recently deployed oVirt version 4.3.1

It's in a self-hosted engine environment

Used the steps via cockpit to install the engine, and was able to add
the rest of the oVirt nodes without any specific problems

We tested the HA of the hosted-engine without a problem, and then at one
point of turn off the machine that was hosting the engine, to mimic
failure to see how it goes; the vm was able to move over successfully,
but some of the oVirt started to go into Unassigned. From a total of 6
oVirt hosts, I have 4 of them in this state.

Clicking on the host, I see the following message in the events. I can
get to the hosts via the engine, and ping the machine, so not sure what
it's doing that it's no longer working

VDSM <snip> command Get Host Capabilities failed: Message timeout which
can be caused by communication issues

Mind you, I have been trying to resolve this issue since Monday, and
have tried various things, like rebooting and re-installing the oVirt
hosts, without having much luck

So any assistance on this would be grateful, maybe I've missed something
really simple, and I am overlooking it

Can you please check that VDSM is correctly running on that nodes?
Are you able to correctly reach that nodes from the engine VM? 
 

--
regards,

Arif Ali
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/FYG7NEV24JCCR4RIXLOMZ2CAPYAH4GDH/
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@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/Y7YVXSLFJ3XCQSPJSPQ2K2OCCMS2F465/


--
Regards,
Artem