6:30 a.m.
This is a multi-part message in MIME format.
--------------080709040101080905010803
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Had a problem where on the host the vdsm service would not start. The
following is from #ovirt IRC chat after I emailed the sos report from
the host
13:29:06) sbonazzo: jkp looks like an issue while starting supervdsm, I
see:
(13:29:08) sbonazzo: Mar 9 12:41:30 kvm1 daemonAdapter: OSError: [Errno
2] No such file or directory: '/var/run/vdsm/svdsm.sock'
(13:29:08) sbonazzo: Mar 9 12:41:30 kvm1 systemd: start request repeated
too quickly for supervdsmd.service
(13:29:26) sbonazzo: danken: ybronhei: nsoffer ^^
(13:30:57) sbonazzo: msivak: i see also Mar 9 12:27:18 kvm1 systemd:
[/usr/lib/systemd/system/momd.service:11] Unknown lvalue 'Timeout' in
section 'Service'
(13:31:30) sbonazzo: msivak: maybe epel7 mom should be updated
(13:32:33) sbonazzo: after that, vdsm doesn't come up due to Mar 9
12:27:55 kvm1 daemonAdapter: OSError: [Errno 2] No such file or
directory: '/var/run/vdsm/svdsm.sock since supervdsmd didn't run
(13:34:50) sbonazzo: jkp: can you try to manually start supervdsmd service?
(13:35:07) jkp: sbonazzo, it is confirmed that the file is not there.
But shouldn't the service create this file -- Yes I'll try
(13:35:19) sbonazzo: jkp: yes, it's supposed to
(13:39:07) jkp: sbonazzo, still gives me the : OSError: [Errno 2] No
such file or directory: '/var/run/vdsm/svdsm.sock'
(13:39:35) sbonazzo: jkp does /var/run/vdsm/ exist?
(13:40:55) jkp: sbonazzo, yes it contains [root@kvm1 ~]# ls
/var/run/vdsm/ lvm sourceRoutes trackedInterfaces v2v
Later I received a email
Mar 9 10:41:21 kvm1 journal: Module
/usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Mar 9 10:41:21 kvm1 journal: The server certificate /etc/pki/vdsm/certs/vdsmcert.pem is
not yet active
Mar 9 10:41:21 kvm1 systemd: libvirtd.service: main process exited, code=exited,
status=6/NOTCONFIGURED
Mar 9 10:41:21 kvm1 systemd: Failed to start Virtualization daemon.
Mar 9 10:41:21 kvm1 systemd: Dependency failed for Virtual Desktop Server Manager.
Mar 9 10:41:21 kvm1 systemd: Dependency failed for MOM instance configured for VDSM
purposes.
Mar 9 10:41:21 kvm1 systemd: Job mom-vdsm.service/start failed with result
'dependency'.
Mar 9 10:41:21 kvm1 systemd: Job vdsmd.service/start failed with result
'dependency'.
Mar 9 10:41:21 kvm1 systemd: Dependency failed for Virtual Desktop Server Manager network
restoration.
Mar 9 10:41:21 kvm1 systemd: Job vdsm-network.service/start failed with result
'dependency'.
Mar 9 10:41:21 kvm1 systemd: Unit libvirtd.service entered failed state.
Mar 9 10:41:21 kvm1 systemd: libvirtd.service failed.
Mar 9 10:41:21 kvm1 systemd-logind: Removed session 4.
Mar 9 10:41:21 kvm1 systemd: libvirtd.service holdoff time over, scheduling restart.
I see that libvirtd fails to start.
It might be due to Engine system clock being deep in the future?
What I had failed to notice was that the vdsmcert.pem that was not active.
The ntp service running on the Engine was out of sync with a year
resulting in that of cause the certificate did not work and then the
vdsm would not start.
I have a fairly new engine so I removed it and fixed the time issue and
all was perfect
Thanks for a great help on the chat and on email
--
Jonas Kirk Pedersen
ASOM-Net
Systemadministrator
--------------080709040101080905010803
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Had a problem where on the host the vdsm service would not start.
The following is from #ovirt IRC chat after I emailed the sos report
from the host<br>
<br>
<font size="2"><font color="#204a87">13:29:06)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>jkp
looks like an issue while starting supervdsm, I see: <br>
<font size="2"><font color="#204a87">(13:29:08)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>Mar
9 12:41:30 kvm1 daemonAdapter: OSError: [Errno 2] No such file or
directory: '/var/run/vdsm/svdsm.sock'<br>
<font size="2"><font color="#204a87">(13:29:08)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>Mar
9 12:41:30 kvm1 systemd: start request repeated too quickly for
supervdsmd.service<br>
<font size="2"><font color="#204a87">(13:29:26)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>danken:
ybronhei: nsoffer ^^<br>
<font size="2"><font color="#204a87">(13:30:57)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>msivak:
i see also Mar 9 12:27:18 kvm1 systemd:
[/usr/lib/systemd/system/momd.service:11] Unknown lvalue 'Timeout'
in section 'Service'<br>
<font size="2"><font color="#204a87">(13:31:30)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>msivak:
maybe epel7 mom should be updated<br>
<font size="2"><font color="#204a87">(13:32:33)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>after
that, vdsm doesn't come up due to Mar 9 12:27:55 kvm1 daemonAdapter:
OSError: [Errno 2] No such file or directory:
'/var/run/vdsm/svdsm.sock since supervdsmd didn't run<br>
<font size="2"><font color="#204a87">(13:34:50)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>jkp:
can you try to manually start supervdsmd service?<br>
<font size="2"><font color="#af7f00">(13:35:07)
</font></font><span
style="font-weight:bold;color:rgb(175,127,0)">jkp:
</span>sbonazzo,
it is confirmed that the file is not there. But shouldn't the
service create this file -- Yes I'll try<br>
<font size="2"><font color="#204a87">(13:35:19)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>jkp:
yes, it's supposed to<br>
<font size="2"><font color="#af7f00">(13:39:07)
</font></font><span
style="font-weight:bold;color:rgb(175,127,0)">jkp:
</span>sbonazzo,
still gives me the : OSError: [Errno 2] No such file or directory:
'/var/run/vdsm/svdsm.sock'<br>
<font size="2"><font color="#204a87">(13:39:35)
</font></font><span
style="font-weight:bold;color:rgb(32,74,135)">sbonazzo:
</span>jkp
does /var/run/vdsm/ exist?<br>
<font size="2"><font color="#af7f00">(13:40:55)
</font></font><span
style="font-weight:bold;color:rgb(175,127,0)">jkp:
</span>sbonazzo,
yes it contains [root@kvm1 ~]# ls /var/run/vdsm/ lvm sourceRoutes
trackedInterfaces v2v<br>
<br>
Later I received a email <br>
<pre class="moz-signature" cols="72">Mar 9 10:41:21 kvm1
journal: Module /usr/lib64/libvirt/connection-driver/libvirt_driver_lxc.so not accessible
Mar 9 10:41:21 kvm1 journal: The server certificate /etc/pki/vdsm/certs/vdsmcert.pem is
not yet active
Mar 9 10:41:21 kvm1 systemd: libvirtd.service: main process exited, code=exited,
status=6/NOTCONFIGURED
Mar 9 10:41:21 kvm1 systemd: Failed to start Virtualization daemon.
Mar 9 10:41:21 kvm1 systemd: Dependency failed for Virtual Desktop Server Manager.
Mar 9 10:41:21 kvm1 systemd: Dependency failed for MOM instance configured for VDSM
purposes.
Mar 9 10:41:21 kvm1 systemd: Job mom-vdsm.service/start failed with result
'dependency'.
Mar 9 10:41:21 kvm1 systemd: Job vdsmd.service/start failed with result
'dependency'.
Mar 9 10:41:21 kvm1 systemd: Dependency failed for Virtual Desktop Server Manager network
restoration.
Mar 9 10:41:21 kvm1 systemd: Job vdsm-network.service/start failed with result
'dependency'.
Mar 9 10:41:21 kvm1 systemd: Unit libvirtd.service entered failed state.
Mar 9 10:41:21 kvm1 systemd: libvirtd.service failed.
Mar 9 10:41:21 kvm1 systemd-logind: Removed session 4.
Mar 9 10:41:21 kvm1 systemd: libvirtd.service holdoff time over, scheduling restart.
I see that libvirtd fails to start.
It might be due to Engine system clock being deep in the future?
</pre>
What I had failed to notice was that the vdsmcert.pem that was not
active.<br>
The ntp service running on the Engine was out of sync with a year
resulting in that of cause the certificate did not work and then the
vdsm would not start. <br>
I have a fairly new engine so I removed it and fixed the time issue
and all was perfect<br>
<br>
Thanks for a great help on the chat and on email<br>
<pre class="moz-signature" cols="72">
</pre>
<pre class="moz-signature" cols="72">--
Jonas Kirk Pedersen
ASOM-Net
Systemadministrator
</pre>
</body>
</html>
--------------080709040101080905010803--