<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 13, 2017 at 11:46 PM, <a href="http://paul.greene.va">paul.greene.va</a> <span dir="ltr"><<a target="_blank" href="mailto:paul.greene.va@verizon.net">paul.greene.va@verizon.net</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Oh, I stumbled onto something relevant.<br>
<br>
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".<br>
<br>
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.<br>
<br>
So, I guess the final question then is how to get persistence in keeping this BRIDGE line from getting removed across reboots?</blockquote><div><br></div><div>VDSM on reboot will compare the current config to the persisted one and try to sync it.<br></div><div>Perhaps you have a corrupted persistent configuration.<br></div><div><br></div><div>Could you please send us the following items:<br></div><div>- vdsm and supervdsm logs (from /var/log/vdsm)<br></div><div>- All your ifcfg files.<br></div><div>- The persisted VDSM network configuration from: /var/lib/vdsm/persistence/netconf<br><br></div><div>Thanks,<br></div><div>Edy.<br></div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div class="gmail-HOEnZb"><div class="gmail-h5"><br>
<br>
<br>
On 1/13/2017 2:54 PM, Nir Soffer wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
On Fri, Jan 13, 2017 at 9:24 PM, <a target="_blank" rel="noreferrer" href="http://paul.greene.va">paul.greene.va</a><br>
<<a target="_blank" href="mailto:paul.greene.va@verizon.net">paul.greene.va@verizon.net</a>> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
Output below ...<br>
<br>
<br>
<br>
On 1/13/2017 1:47 PM, Nir Soffer wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
On Fri, Jan 13, 2017 at 5:45 PM, <a target="_blank" rel="noreferrer" href="http://paul.greene.va">paul.greene.va</a><br>
<<a target="_blank" href="mailto:paul.greene.va@verizon.net">paul.greene.va@verizon.net</a>> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
All,<br>
<br>
I'm having an issue with the vdsmd service refusing to start on a fresh<br>
install of RHEL 7.2, RHEV version 4.0.<br>
<br>
It initially came up correctly, and the command "ip a" showed a<br>
"vdsmdummy"<br>
interface and a "ovirtmgmt" interface. However after a couple of reboots,<br>
those interfaces disappeared, and running "systemctl status vdsmd"<br>
generated<br>
the message "Dependency failed for Virtual Desktop Service Manager/Job<br>
vdsmd.service/start failed with result 'dependency'". Didn't say what<br>
dependency though<br>
<br>
I have 3 hosts where this happening on 2 out of 3 hosts. For some odd<br>
reason, the one host isn't having any problems.<br>
<br>
In a Google search I found an instance where system clock timing was out<br>
of<br>
sync, and that messed it up. I checked all three hosts, as well as the<br>
RHEV<br>
manager and they all had chronyd running and the clocks appeared to be in<br>
sync.<br>
<br>
After a reboot the virtual interfaces usually initially come up, but go<br>
down<br>
again within a few minutes.<br>
<br>
Running journalctl -xe gives these three messages:<br>
<br>
"failed to start Virtual Desktop Server Manager network restoration"<br>
<br>
"Dependency failed for Virtual Desktop Server Manager" (but it doesn't<br>
say<br>
which dependency failed"<br>
<br>
"Dependency failed for MOM instance configured for VDSM purposes"<br>
(again,<br>
doesn't way which dependency)<br>
<br>
Any suggestions?<br>
</blockquote>
Can you share the output of:<br>
<br>
systemctl status vdsmd<br>
systemctl status mom<br>
systemctl status libvirtd<br>
journalctl -xe<br>
<br>
Nir<br>
<br>
</blockquote>
Sure, here you go ....<br>
<br>
<br>
<br>
[root@rhevh03 vdsm]# systemctl status vdsmd<br>
ā vdsmd.service - Virtual Desktop Server Manager<br>
Loaded: loaded (/usr/lib/systemd/system/vdsmd<wbr>.service; enabled; vendor<br>
preset: enabled)<br>
Active: inactive (dead)<br>
<br>
Jan 13 12:01:53 rhevh03 systemd[1]: Dependency failed for Virtual Desktop<br>
Server Manager.<br>
Jan 13 12:01:53 rhevh03 systemd[1]: Job vdsmd.service/start failed with<br>
result 'dependency'.<br>
Jan 13 13:51:50 rhevh03 systemd[1]: Dependency failed for Virtual Desktop<br>
Server Manager.<br>
Jan 13 13:51:50 rhevh03 systemd[1]: Job vdsmd.service/start failed with<br>
result 'dependency'.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for Virtual Desktop<br>
Server Manager.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Job vdsmd.service/start failed with<br>
result 'dependency'.<br>
<br>
<br>
<br>
[root@rhevh03 vdsm]# systemctl status momd<br>
ā momd.service - Memory Overcommitment Manager Daemon<br>
Loaded: loaded (/usr/lib/systemd/system/momd.<wbr>service; static; vendor<br>
preset: disabled)<br>
Active: inactive (dead) since Fri 2017-01-13 13:53:09 EST; 2min 26s ago<br>
Process: 28294 ExecStart=/usr/sbin/momd -c /etc/momd.conf -d --pid-file<br>
/var/run/momd.pid (code=exited, status=0/SUCCESS)<br>
Main PID: 28298 (code=exited, status=0/SUCCESS)<br>
<br>
Jan 13 13:53:09 rhevh03 systemd[1]: Starting Memory Overcommitment Manager<br>
Daemon...<br>
Jan 13 13:53:09 rhevh03 systemd[1]: momd.service: Supervising process 28298<br>
which is not our child. We'll most likely not notice when it exits.<br>
Jan 13 13:53:09 rhevh03 systemd[1]: Started Memory Overcommitment Manager<br>
Daemon.<br>
Jan 13 13:53:09 rhevh03 python[28298]: No worthy mechs found<br>
<br>
<br>
<br>
[root@rhevh03 vdsm]# systemctl status libvirtd<br>
ā libvirtd.service - Virtualization daemon<br>
Loaded: loaded (/usr/lib/systemd/system/libvi<wbr>rtd.service; enabled; vendor<br>
preset: enabled)<br>
Drop-In: /etc/systemd/system/libvirtd.s<wbr>ervice.d<br>
āāunlimited-core.conf<br>
Active: active (running) since Fri 2017-01-13 13:50:47 EST; 8min ago<br>
Docs: man:libvirtd(8)<br>
<a target="_blank" rel="noreferrer" href="http://libvirt.org">http://libvirt.org</a><br>
Main PID: 27964 (libvirtd)<br>
CGroup: /system.slice/libvirtd.service<br>
āā27964 /usr/sbin/libvirtd --listen<br>
<br>
Jan 13 13:50:47 rhevh03 systemd[1]: Starting Virtualization daemon...<br>
Jan 13 13:50:47 rhevh03 systemd[1]: Started Virtualization daemon.<br>
Jan 13 13:53:09 rhevh03 libvirtd[27964]: libvirt version: 2.0.0, package:<br>
10.el7_3.2 (Red Hat, Inc. <<a target="_blank" rel="noreferrer" href="http://bugzilla.redhat.com/bugzilla">http://bugzilla.redhat.com/bu<wbr>gzilla</a>>,<br>
<a target="_blank" value="+12016111004" href="tel:2016-11-10-04">2016-11-10-04</a>:43:57, <a target="_blank" rel="noreferrer" href="http://x86-034.build.eng.bos.redhat.com">x86-034.build.eng.bos.redhat.c<wbr>om</a>)<br>
Jan 13 13:53:09 rhevh03 libvirtd[27964]: hostname: rhevh03<br>
Jan 13 13:53:09 rhevh03 libvirtd[27964]: End of file while reading data:<br>
Input/output error<br>
<br>
<br>
[root@rhevh03 vdsm]# journalctl -xe<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File<br>
"/usr/lib/python2.7/site-packa<wbr>ges/vdsm/network/configurators<wbr>/ifcfg.py", line<br>
951, in _exec_ifup<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: _exec_ifup_by_name(<a target="_blank" rel="noreferrer" href="http://iface.name">iface.name</a>,<br>
cgroup)<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File<br>
"/usr/lib/python2.7/site-packa<wbr>ges/vdsm/network/configurators<wbr>/ifcfg.py", line<br>
937, in _exec_ifup_by_name<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: raise<br>
ConfigNetworkError(ERR_FAILED_<wbr>IFUP, out[-1] if out else '')<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]:<br>
vdsm.network.errors.ConfigNetw<wbr>orkError: (29, 'Determining IP information for<br>
ovirtmgmt... failed.')<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: Traceback (most recent call last):<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File "/usr/bin/vdsm-tool", line<br>
219, in main<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: return<br>
tool_command[cmd]["command"](*<wbr>args)<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File<br>
"/usr/lib/python2.7/site-packa<wbr>ges/vdsm/tool/restore_nets.py"<wbr>, line 41, in<br>
restore_command<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: exec_restore(cmd)<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: File<br>
"/usr/lib/python2.7/site-packa<wbr>ges/vdsm/tool/restore_nets.py"<wbr>, line 54, in<br>
exec_restore<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: raise EnvironmentError('Failed to<br>
restore the persisted networks')<br>
Jan 13 13:55:15 rhevh03 vdsm-tool[28334]: EnvironmentError: Failed to<br>
restore the persisted networks<br>
Jan 13 13:55:15 rhevh03 postfix/local[28598]: 05920804620D:<br>
to=<root@localhost.localdomain<wbr>>, orig_to=<root@localhost>, relay=local,<br>
delay=0.03, delays=0.02/0.01/0/0, dsn=2.0.0, status=sent (delivered to<br>
Jan 13 13:55:15 rhevh03 postfix/qmgr[3522]: 05920804620D: removed<br>
Jan 13 13:55:15 rhevh03 systemd[1]: vdsm-network.service: main process<br>
exited, code=exited, status=1/FAILURE<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Failed to start Virtual Desktop Server<br>
Manager network restoration.<br>
-- Subject: Unit vdsm-network.service has failed<br>
-- Defined-By: systemd<br>
-- Support: <a target="_blank" rel="noreferrer" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
--<br>
-- Unit vdsm-network.service has failed.<br>
</blockquote>
Seems that you have a networking issue, adding Dan.<br>
<br>
<blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
--<br>
-- The result is failed.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for Virtual Desktop<br>
Server Manager.<br>
-- Subject: Unit vdsmd.service has failed<br>
-- Defined-By: systemd<br>
-- Support: <a target="_blank" rel="noreferrer" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
--<br>
-- Unit vdsmd.service has failed.<br>
--<br>
-- The result is dependency.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Dependency failed for MOM instance<br>
configured for VDSM purposes.<br>
-- Subject: Unit mom-vdsm.service has failed<br>
-- Defined-By: systemd<br>
-- Support: <a target="_blank" rel="noreferrer" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
--<br>
-- Unit mom-vdsm.service has failed.<br>
--<br>
-- The result is dependency.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Job mom-vdsm.service/start failed with<br>
result 'dependency'.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Job vdsmd.service/start failed with<br>
result 'dependency'.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: Unit vdsm-network.service entered failed<br>
state.<br>
Jan 13 13:55:15 rhevh03 systemd[1]: vdsm-network.service failed.<br>
Jan 13 13:55:15 rhevh03 polkitd[1675]: Unregistered Authentication Agent for<br>
unix-process:28317:681858 (system bus name :1.121, object path<br>
/org/freedesktop/PolicyKit1/Au<wbr>thenticationAgent, locale en_US.<br>
Jan 13 14:00:01 rhevh03 systemd[1]: Started Session 16 of user root.<br>
-- Subject: Unit session-16.scope has finished start-up<br>
-- Defined-By: systemd<br>
-- Support: <a target="_blank" rel="noreferrer" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
--<br>
-- Unit session-16.scope has finished starting up.<br>
--<br>
-- The start-up result is done.<br>
Jan 13 14:00:01 rhevh03 systemd[1]: Starting Session 16 of user root.<br>
-- Subject: Unit session-16.scope has begun start-up<br>
-- Defined-By: systemd<br>
-- Support: <a target="_blank" rel="noreferrer" href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel">http://lists.freedesktop.org/m<wbr>ailman/listinfo/systemd-devel</a><br>
--<br>
-- Unit session-16.scope has begun starting up.<br>
Jan 13 14:00:01 rhevh03 CROND[28607]: (root) CMD (/usr/lib64/sa/sa1 1 1)<br>
<br>
</blockquote></blockquote>
<br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a target="_blank" href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a target="_blank" rel="noreferrer" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
</div></div></blockquote></div><br></div></div>