Re: [ovirt-users] VDSM service won't start

[Edward Haas]

On Fri, Jan 13, 2017 at 11:46 PM, paul.greene.va  wrote:

> Oh, I stumbled onto something relevant.
>
> I noticed on the host that was working correctly that the ifcfg-enp6s0
> file included a line for "BRIDGE=ovirtmgmt", and the other two didn't have
> that line. When I added that line to the other two hosts, and restarted
> networking, I was able to get those hosts in a status of "UP".
>
> That file is autogenerated by VDSM, so I wondered if it would survive a
> reboot. When I rebooted, the line had been removed again by VDSM.
>
> So, I guess the final question then is how to get persistence in keeping
> this BRIDGE line from getting removed across reboots?


VDSM on reboot will compare the current config to the persisted one and try
to sync it.
Perhaps you have a corrupted persistent configuration.

Could you please send us the following items:
- vdsm and supervdsm logs (from /var/log/vdsm)
- All your ifcfg files.
- The persisted VDSM network configuration from:
/var/lib/vdsm/persistence/netconf

Thanks,
Edy.


>
>
>
> On 1/13/2017 2:54 PM, Nir Soffer wrote:
>
>> On Fri, Jan 13, 2017 at 9:24 PM, paul.greene.va
>>  wrote:
>>
>>> Output below ...
>>>
>>>
>>>
>>> On 1/13/2017 1:47 PM, Nir Soffer wrote:
>>>
 On Fri, Jan 13, 2017 at 5:45 PM, paul.greene.va
  wrote:

> All,
>
> I'm having an issue with the vdsmd service refusing to start on a fresh
> install of RHEL 7.2, RHEV version 4.0.
>
> It initially came up correctly, and the command "ip a" showed a
> "vdsmdummy"
> interface and a "ovirtmgmt" interface. However after a couple of
> reboots,
> those interfaces disappeared, and running "systemctl status vdsmd"
> generated
> the message "Dependency failed for Virtual Desktop Service Manager/Job
> vdsmd.service/start failed with result 'dependency'". Didn't say what
> dependency though
>
> I have 3 hosts where this happening on 2 out of 3 hosts. For some odd
> reason, the one host isn't having any problems.
>
> In a Google search I found an instance where system clock timing was
> out
> of
> sync, and that messed it up. I checked all three hosts, as well as the
> RHEV
> manager and they all had chronyd running and the clocks appeared to be
> in
> sync.
>
> After a reboot the virtual interfaces usually initially come up, but go
> down
> again within a few minutes.
>
> Running journalctl -xe gives these three messages:
>
> "failed to start Virtual Desktop Server Manager network restoration"
>
> "Dependency failed for Virtual Desktop Server Manager"  (but it doesn't
> say
> which dependency failed"
>
> "Dependency failed for MOM instance configured for VDSM purposes"
> (again,
> doesn't way which dependency)
>
> Any suggestions?
>
 Can you share the output of:

 systemctl status vdsmd
 systemctl status mom
 systemctl status libvirtd
 journalctl -xe

 Nir

 Sure, here you go 
>>>
>>>
>>>
>>> [root@rhevh03 vdsm]# systemctl status vdsmd
>>> ā vdsmd.service - Virtual Desktop Server Manager
>>> Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled;
>>> vendor
>>> preset: enabled)
>>> Active: inactive (dead)
>>>
>>> Jan 13 12:01:53 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
>>> Server Manager.
>>> Jan 13 12:01:53 rhevh03 systemd[1]: Job vdsmd.service/start failed with
>>> result 'dependency'.
>>> Jan 13 13:51:50 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
>>> Server Manager.
>>> Jan 13 13:51:50 rhevh03 systemd[1]: Job vdsmd.service/start failed with
>>> result 'dependency'.
>>> Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
>>> Server Manager.
>>> Jan 13 13:55:15 rhevh03 systemd[1]: Job vdsmd.service/start failed with
>>> result 'dependency'.
>>>
>>>
>>>
>>> [root@rhevh03 vdsm]# 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-01-13 13:53:09 EST; 2min 26s
>>> ago
>>>Process: 28294 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d
>>> --pid-file
>>> /var/run/momd.pid (code=exited, status=0/SUCCESS)
>>>   Main PID: 28298 (code=exited, status=0/SUCCESS)
>>>
>>> Jan 13 13:53:09 rhevh03 systemd[1]: Starting Memory Overcommitment
>>> Manager
>>> Daemon...
>>> Jan 13 13:53:09 rhevh03 systemd[1]: momd.service: Supervising process
>>> 28298
>>> which is not our child. We'll most likely not notice when it exits.
>>> Jan 13 13:53:09 rhevh03 systemd[1]: Started Memory Overcommitment Manager
>>> Daemon.
>>> Jan 13 13:53:09 rhevh03 python[28298]: No worthy mechs found
>>>
>>>
>>>
>>> [root@rhevh03 vdsm]# systemctl status libvirtd
>>> ā libvirtd.service - Virtualization daemon
>>> Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled;
>>> 

Re: [ovirt-users] VDSM service won't start

[paul.greene.va]

Oh, I stumbled onto something relevant.

I noticed on the host that was working correctly that the ifcfg-enp6s0 
file included a line for "BRIDGE=ovirtmgmt", and the other two didn't 
have that line. When I added that line to the other two hosts, and 
restarted networking, I was able to get those hosts in a status of "UP".


That file is autogenerated by VDSM, so I wondered if it would survive a 
reboot. When I rebooted, the line had been removed again by VDSM.


So, I guess the final question then is how to get persistence in keeping 
this BRIDGE line from getting removed across reboots?



On 1/13/2017 2:54 PM, Nir Soffer wrote:

On Fri, Jan 13, 2017 at 9:24 PM, paul.greene.va
 wrote:

Output below ...



On 1/13/2017 1:47 PM, Nir Soffer wrote:

On Fri, Jan 13, 2017 at 5:45 PM, paul.greene.va
 wrote:

All,

I'm having an issue with the vdsmd service refusing to start on a fresh
install of RHEL 7.2, RHEV version 4.0.

It initially came up correctly, and the command "ip a" showed a
"vdsmdummy"
interface and a "ovirtmgmt" interface. However after a couple of reboots,
those interfaces disappeared, and running "systemctl status vdsmd"
generated
the message "Dependency failed for Virtual Desktop Service Manager/Job
vdsmd.service/start failed with result 'dependency'". Didn't say what
dependency though

I have 3 hosts where this happening on 2 out of 3 hosts. For some odd
reason, the one host isn't having any problems.

In a Google search I found an instance where system clock timing was out
of
sync, and that messed it up. I checked all three hosts, as well as the
RHEV
manager and they all had chronyd running and the clocks appeared to be in
sync.

After a reboot the virtual interfaces usually initially come up, but go
down
again within a few minutes.

Running journalctl -xe gives these three messages:

"failed to start Virtual Desktop Server Manager network restoration"

"Dependency failed for Virtual Desktop Server Manager"  (but it doesn't
say
which dependency failed"

"Dependency failed for MOM instance configured for VDSM purposes"
(again,
doesn't way which dependency)

Any suggestions?

Can you share the output of:

systemctl status vdsmd
systemctl status mom
systemctl status libvirtd
journalctl -xe

Nir


Sure, here you go 



[root@rhevh03 vdsm]# systemctl status vdsmd
ā vdsmd.service - Virtual Desktop Server Manager
Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
preset: enabled)
Active: inactive (dead)

Jan 13 12:01:53 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
Server Manager.
Jan 13 12:01:53 rhevh03 systemd[1]: Job vdsmd.service/start failed with
result 'dependency'.
Jan 13 13:51:50 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
Server Manager.
Jan 13 13:51:50 rhevh03 systemd[1]: Job vdsmd.service/start failed with
result 'dependency'.
Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
Server Manager.
Jan 13 13:55:15 rhevh03 systemd[1]: Job vdsmd.service/start failed with
result 'dependency'.



[root@rhevh03 vdsm]# 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-01-13 13:53:09 EST; 2min 26s ago
   Process: 28294 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file
/var/run/momd.pid (code=exited, status=0/SUCCESS)
  Main PID: 28298 (code=exited, status=0/SUCCESS)

Jan 13 13:53:09 rhevh03 systemd[1]: Starting Memory Overcommitment Manager
Daemon...
Jan 13 13:53:09 rhevh03 systemd[1]: momd.service: Supervising process 28298
which is not our child. We'll most likely not notice when it exits.
Jan 13 13:53:09 rhevh03 systemd[1]: Started Memory Overcommitment Manager
Daemon.
Jan 13 13:53:09 rhevh03 python[28298]: No worthy mechs found



[root@rhevh03 vdsm]# systemctl status libvirtd
ā libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor
preset: enabled)
   Drop-In: /etc/systemd/system/libvirtd.service.d
āāunlimited-core.conf
Active: active (running) since Fri 2017-01-13 13:50:47 EST; 8min ago
  Docs: man:libvirtd(8)
http://libvirt.org
  Main PID: 27964 (libvirtd)
CGroup: /system.slice/libvirtd.service
āā27964 /usr/sbin/libvirtd --listen

Jan 13 13:50:47 rhevh03 systemd[1]: Starting Virtualization daemon...
Jan 13 13:50:47 rhevh03 systemd[1]: Started Virtualization daemon.
Jan 13 13:53:09 rhevh03 libvirtd[27964]: libvirt version: 2.0.0, package:
10.el7_3.2 (Red Hat, Inc. ,
2016-11-10-04:43:57, x86-034.build.eng.bos.redhat.com)
Jan 13 13:53:09 rhevh03 libvirtd[27964]: hostname: rhevh03
Jan 13 13:53:09 rhevh03 libvirtd[27964]: End of file while reading data:
Input/output error


[root@rhevh03 vdsm]# journalctl -xe
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File
"/usr/lib/python2.7/site-packages/vdsm/network/configu

Re: [ovirt-users] VDSM service won't start

[paul.greene.va]

Output below ...


On 1/13/2017 1:47 PM, Nir Soffer wrote:

On Fri, Jan 13, 2017 at 5:45 PM, paul.greene.va
 wrote:

All,

I'm having an issue with the vdsmd service refusing to start on a fresh
install of RHEL 7.2, RHEV version 4.0.

It initially came up correctly, and the command "ip a" showed a "vdsmdummy"
interface and a "ovirtmgmt" interface. However after a couple of reboots,
those interfaces disappeared, and running "systemctl status vdsmd" generated
the message "Dependency failed for Virtual Desktop Service Manager/Job
vdsmd.service/start failed with result 'dependency'". Didn't say what
dependency though

I have 3 hosts where this happening on 2 out of 3 hosts. For some odd
reason, the one host isn't having any problems.

In a Google search I found an instance where system clock timing was out of
sync, and that messed it up. I checked all three hosts, as well as the RHEV
manager and they all had chronyd running and the clocks appeared to be in
sync.

After a reboot the virtual interfaces usually initially come up, but go down
again within a few minutes.

Running journalctl -xe gives these three messages:

"failed to start Virtual Desktop Server Manager network restoration"

"Dependency failed for Virtual Desktop Server Manager"  (but it doesn't say
which dependency failed"

"Dependency failed for MOM instance configured for VDSM purposes"  (again,
doesn't way which dependency)

Any suggestions?

Can you share the output of:

systemctl status vdsmd
systemctl status mom
systemctl status libvirtd
journalctl -xe

Nir



Sure, here you go 



[root@rhevh03 vdsm]# systemctl status vdsmd
ā vdsmd.service - Virtual Desktop Server Manager
   Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; 
vendor preset: enabled)

   Active: inactive (dead)

Jan 13 12:01:53 rhevh03 systemd[1]: Dependency failed for Virtual 
Desktop Server Manager.
Jan 13 12:01:53 rhevh03 systemd[1]: Job vdsmd.service/start failed with 
result 'dependency'.
Jan 13 13:51:50 rhevh03 systemd[1]: Dependency failed for Virtual 
Desktop Server Manager.
Jan 13 13:51:50 rhevh03 systemd[1]: Job vdsmd.service/start failed with 
result 'dependency'.
Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for Virtual 
Desktop Server Manager.
Jan 13 13:55:15 rhevh03 systemd[1]: Job vdsmd.service/start failed with 
result 'dependency'.




[root@rhevh03 vdsm]# 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-01-13 13:53:09 EST; 2min 26s ago
  Process: 28294 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d 
--pid-file /var/run/momd.pid (code=exited, status=0/SUCCESS)

 Main PID: 28298 (code=exited, status=0/SUCCESS)

Jan 13 13:53:09 rhevh03 systemd[1]: Starting Memory Overcommitment 
Manager Daemon...
Jan 13 13:53:09 rhevh03 systemd[1]: momd.service: Supervising process 
28298 which is not our child. We'll most likely not notice when it exits.
Jan 13 13:53:09 rhevh03 systemd[1]: Started Memory Overcommitment 
Manager Daemon.

Jan 13 13:53:09 rhevh03 python[28298]: No worthy mechs found



[root@rhevh03 vdsm]# systemctl status libvirtd
ā libvirtd.service - Virtualization daemon
   Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; 
vendor preset: enabled)

  Drop-In: /etc/systemd/system/libvirtd.service.d
   āāunlimited-core.conf
   Active: active (running) since Fri 2017-01-13 13:50:47 EST; 8min ago
 Docs: man:libvirtd(8)
   http://libvirt.org
 Main PID: 27964 (libvirtd)
   CGroup: /system.slice/libvirtd.service
   āā27964 /usr/sbin/libvirtd --listen

Jan 13 13:50:47 rhevh03 systemd[1]: Starting Virtualization daemon...
Jan 13 13:50:47 rhevh03 systemd[1]: Started Virtualization daemon.
Jan 13 13:53:09 rhevh03 libvirtd[27964]: libvirt version: 2.0.0, 
package: 10.el7_3.2 (Red Hat, Inc. 
, 2016-11-10-04:43:57, 
x86-034.build.eng.bos.redhat.com)

Jan 13 13:53:09 rhevh03 libvirtd[27964]: hostname: rhevh03
Jan 13 13:53:09 rhevh03 libvirtd[27964]: End of file while reading data: 
Input/output error



[root@rhevh03 vdsm]# journalctl -xe
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", 
line 951, in _exec_ifup
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: _exec_ifup_by_name(iface.name, 
cgroup)
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File 
"/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", 
line 937, in _exec_ifup_by_name
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: raise 
ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '')
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: 
vdsm.network.errors.ConfigNetworkError: (29, 'Determining IP information 
for ovirtmgmt... failed.')

Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: Traceback (most recent call last):
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File "/usr/bin/vdsm-tool", 
line 2

Re: [ovirt-users] VDSM service won't start

[Nir Soffer]

On Fri, Jan 13, 2017 at 9:24 PM, paul.greene.va
 wrote:
> Output below ...
>
>
>
> On 1/13/2017 1:47 PM, Nir Soffer wrote:
>>
>> On Fri, Jan 13, 2017 at 5:45 PM, paul.greene.va
>>  wrote:
>>>
>>> All,
>>>
>>> I'm having an issue with the vdsmd service refusing to start on a fresh
>>> install of RHEL 7.2, RHEV version 4.0.
>>>
>>> It initially came up correctly, and the command "ip a" showed a
>>> "vdsmdummy"
>>> interface and a "ovirtmgmt" interface. However after a couple of reboots,
>>> those interfaces disappeared, and running "systemctl status vdsmd"
>>> generated
>>> the message "Dependency failed for Virtual Desktop Service Manager/Job
>>> vdsmd.service/start failed with result 'dependency'". Didn't say what
>>> dependency though
>>>
>>> I have 3 hosts where this happening on 2 out of 3 hosts. For some odd
>>> reason, the one host isn't having any problems.
>>>
>>> In a Google search I found an instance where system clock timing was out
>>> of
>>> sync, and that messed it up. I checked all three hosts, as well as the
>>> RHEV
>>> manager and they all had chronyd running and the clocks appeared to be in
>>> sync.
>>>
>>> After a reboot the virtual interfaces usually initially come up, but go
>>> down
>>> again within a few minutes.
>>>
>>> Running journalctl -xe gives these three messages:
>>>
>>> "failed to start Virtual Desktop Server Manager network restoration"
>>>
>>> "Dependency failed for Virtual Desktop Server Manager"  (but it doesn't
>>> say
>>> which dependency failed"
>>>
>>> "Dependency failed for MOM instance configured for VDSM purposes"
>>> (again,
>>> doesn't way which dependency)
>>>
>>> Any suggestions?
>>
>> Can you share the output of:
>>
>> systemctl status vdsmd
>> systemctl status mom
>> systemctl status libvirtd
>> journalctl -xe
>>
>> Nir
>>
>
> Sure, here you go 
>
>
>
> [root@rhevh03 vdsm]# systemctl status vdsmd
> ā vdsmd.service - Virtual Desktop Server Manager
>Loaded: loaded (/usr/lib/systemd/system/vdsmd.service; enabled; vendor
> preset: enabled)
>Active: inactive (dead)
>
> Jan 13 12:01:53 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
> Server Manager.
> Jan 13 12:01:53 rhevh03 systemd[1]: Job vdsmd.service/start failed with
> result 'dependency'.
> Jan 13 13:51:50 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
> Server Manager.
> Jan 13 13:51:50 rhevh03 systemd[1]: Job vdsmd.service/start failed with
> result 'dependency'.
> Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for Virtual Desktop
> Server Manager.
> Jan 13 13:55:15 rhevh03 systemd[1]: Job vdsmd.service/start failed with
> result 'dependency'.
>
>
>
> [root@rhevh03 vdsm]# 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-01-13 13:53:09 EST; 2min 26s ago
>   Process: 28294 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file
> /var/run/momd.pid (code=exited, status=0/SUCCESS)
>  Main PID: 28298 (code=exited, status=0/SUCCESS)
>
> Jan 13 13:53:09 rhevh03 systemd[1]: Starting Memory Overcommitment Manager
> Daemon...
> Jan 13 13:53:09 rhevh03 systemd[1]: momd.service: Supervising process 28298
> which is not our child. We'll most likely not notice when it exits.
> Jan 13 13:53:09 rhevh03 systemd[1]: Started Memory Overcommitment Manager
> Daemon.
> Jan 13 13:53:09 rhevh03 python[28298]: No worthy mechs found
>
>
>
> [root@rhevh03 vdsm]# systemctl status libvirtd
> ā libvirtd.service - Virtualization daemon
>Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor
> preset: enabled)
>   Drop-In: /etc/systemd/system/libvirtd.service.d
>āāunlimited-core.conf
>Active: active (running) since Fri 2017-01-13 13:50:47 EST; 8min ago
>  Docs: man:libvirtd(8)
>http://libvirt.org
>  Main PID: 27964 (libvirtd)
>CGroup: /system.slice/libvirtd.service
>āā27964 /usr/sbin/libvirtd --listen
>
> Jan 13 13:50:47 rhevh03 systemd[1]: Starting Virtualization daemon...
> Jan 13 13:50:47 rhevh03 systemd[1]: Started Virtualization daemon.
> Jan 13 13:53:09 rhevh03 libvirtd[27964]: libvirt version: 2.0.0, package:
> 10.el7_3.2 (Red Hat, Inc. ,
> 2016-11-10-04:43:57, x86-034.build.eng.bos.redhat.com)
> Jan 13 13:53:09 rhevh03 libvirtd[27964]: hostname: rhevh03
> Jan 13 13:53:09 rhevh03 libvirtd[27964]: End of file while reading data:
> Input/output error
>
>
> [root@rhevh03 vdsm]# journalctl -xe
> Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File
> "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line
> 951, in _exec_ifup
> Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: _exec_ifup_by_name(iface.name,
> cgroup)
> Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File
> "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line
> 937, in _exec_ifup_by_name
> Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: ra

Re: [ovirt-users] VDSM service won't start

[Nir Soffer]

On Fri, Jan 13, 2017 at 5:45 PM, paul.greene.va
 wrote:
> All,
>
> I'm having an issue with the vdsmd service refusing to start on a fresh
> install of RHEL 7.2, RHEV version 4.0.
>
> It initially came up correctly, and the command "ip a" showed a "vdsmdummy"
> interface and a "ovirtmgmt" interface. However after a couple of reboots,
> those interfaces disappeared, and running "systemctl status vdsmd" generated
> the message "Dependency failed for Virtual Desktop Service Manager/Job
> vdsmd.service/start failed with result 'dependency'". Didn't say what
> dependency though
>
> I have 3 hosts where this happening on 2 out of 3 hosts. For some odd
> reason, the one host isn't having any problems.
>
> In a Google search I found an instance where system clock timing was out of
> sync, and that messed it up. I checked all three hosts, as well as the RHEV
> manager and they all had chronyd running and the clocks appeared to be in
> sync.
>
> After a reboot the virtual interfaces usually initially come up, but go down
> again within a few minutes.
>
> Running journalctl -xe gives these three messages:
>
> "failed to start Virtual Desktop Server Manager network restoration"
>
> "Dependency failed for Virtual Desktop Server Manager"  (but it doesn't say
> which dependency failed"
>
> "Dependency failed for MOM instance configured for VDSM purposes"  (again,
> doesn't way which dependency)
>
> Any suggestions?

Can you share the output of:

systemctl status vdsmd
systemctl status mom
systemctl status libvirtd
journalctl -xe

Nir

>
> Paul
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VDSM service won't start

[Dominik Holler]

On Fri, 13 Jan 2017 10:45:43 -0500
"paul.greene.va"  wrote:

> 
> After a reboot the virtual interfaces usually initially come up, but
> go down again within a few minutes.
> 
> Running journalctl -xe gives these three messages:
> 
> "failed to start Virtual Desktop Server Manager network restoration"
> 
> "Dependency failed for Virtual Desktop Server Manager"  (but it
> doesn't say which dependency failed"
> 
> "Dependency failed for MOM instance configured for VDSM purposes"  
> (again, doesn't way which dependency)
> 
> Any suggestions?
> 

Is libvirtd.service running?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] VDSM service won't start

[paul.greene.va]

All,

I'm having an issue with the vdsmd service refusing to start on a fresh 
install of RHEL 7.2, RHEV version 4.0.


It initially came up correctly, and the command "ip a" showed a 
"vdsmdummy" interface and a "ovirtmgmt" interface. However after a 
couple of reboots, those interfaces disappeared, and running "systemctl 
status vdsmd" generated the message "Dependency failed for Virtual 
Desktop Service Manager/Job vdsmd.service/start failed with result 
'dependency'". Didn't say what dependency though


I have 3 hosts where this happening on 2 out of 3 hosts. For some odd 
reason, the one host isn't having any problems.


In a Google search I found an instance where system clock timing was out 
of sync, and that messed it up. I checked all three hosts, as well as 
the RHEV manager and they all had chronyd running and the clocks 
appeared to be in sync.


After a reboot the virtual interfaces usually initially come up, but go 
down again within a few minutes.


Running journalctl -xe gives these three messages:

"failed to start Virtual Desktop Server Manager network restoration"

"Dependency failed for Virtual Desktop Server Manager"  (but it doesn't 
say which dependency failed"


"Dependency failed for MOM instance configured for VDSM purposes"  
(again, doesn't way which dependency)


Any suggestions?

Paul

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users