<div dir="ltr">This is from the messages:<br>, respawning slave<br><br>Feb 10 13:16:13 ovirthyp02dev respawn: slave '/usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock --pidfile /var/run/vdsm/supervdsmd.pid' died too quickly, respawning slave<br>Feb 10 13:16:13 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave<br>Feb 10 13:16:13 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave<br>Feb 10 13:16:14 ovirthyp02dev respawn: slave '/usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock --pidfile /var/run/vdsm/supervdsmd.pid' died too quickly, respawning slave<br>Feb 10 13:16:14 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave<br>Feb 10 13:16:14 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave<br>Feb 10 13:16:14 ovirthyp02dev respawn: slave '/usr/share/vdsm/supervdsmServer --sockfile /var/run/vdsm/svdsm.sock --pidfile /var/run/vdsm/supervdsmd.pid' died too quickly, respawning slave<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-10 12:57 GMT+01:00 Koen Vanoppen <span dir="ltr"><<a href="mailto:vanoppen.koen@gmail.com" target="_blank">vanoppen.koen@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">OK... Damn... Still not solved...<br><br>ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-27) [1c3008a9] Command GetCapabilitiesVDSCommand(HostName = ovirthyp02dev, HostId = 30d9b657-89ba-4514-94ae-78d8d7135fab, vds=Host[ovirthyp02dev,30d9b657-89ba-4514-94ae-78d8d7135fab]) execution failed. Exception: VDSNetworkException: VDSGenericException: VDSNetworkException: Message timeout which can be caused by communication issues<br>2015-02-10 12:56:04,676 WARN [org.ovirt.engine.core.vdsbroker.VdsManager] (DefaultQuartzScheduler_Worker-27) [1c3008a9] Host ovirthyp02dev is not responding. It will stay in Connecting state for a grace period of 60 seconds and after that an attempt to fence the host will be issued.<br><br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2015-02-10 7:15 GMT+01:00 Koen Vanoppen <span dir="ltr"><<a href="mailto:vanoppen.koen@gmail.com" target="_blank">vanoppen.koen@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Found the problem...<br></div>Because of the fact that we are working with local repos, we didn't update the vdsm version due dependency errors with the CentOS-Base and updates repos.<br></div>I pulled the new rpms for these 2 repos and now everything works fine.<br></div><div>Thanks for the help!<br></div>[SOLVED]<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-10 6:10 GMT+01:00 Koen Vanoppen <span dir="ltr"><<a href="mailto:vanoppen.koen@gmail.com" target="_blank">vanoppen.koen@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So, which package should I install where in our <b>oVirt</b> <b>3.5.1</b> environment? <br><pre>rhevm-3.5.0-0.31.el6ev.noarch?<br></pre><pre>It sure looks like this bug... But as I said, we are on 3.5.1...<br></pre><br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-02-09 22:22 GMT+01:00 Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Mon, Feb 09, 2015 at 06:53:11AM +0100, Koen Vanoppen wrote:<br>
> We are already on oVirt 3.5.1... So this shouldn't be the problem...<br>
> We also have network issues for the moment here, so if it wouldn't be<br>
> solved when these issues disappear, I come back to this.<br>
<br>
><br>
> 2015-02-06 12:43 GMT+01:00 Piotr Kliczewski <<a href="mailto:piotr.kliczewski@gmail.com" target="_blank">piotr.kliczewski@gmail.com</a>>:<br>
><br>
> > Koen,<br>
> ><br>
> > It seems that you hit [1] bug. The fix is part of async release so<br>
> > please update and the problem will disappear.<br>
> ><br>
> > Thanks,<br>
> > Piotr<br>
> ><br>
> > [1] <a href="https://bugzilla.redhat.com/1185818" target="_blank">https://bugzilla.redhat.com/1185818</a><br>
> ><br>
> > On Thu, Feb 5, 2015 at 3:19 PM, Koen Vanoppen <<a href="mailto:vanoppen.koen@gmail.com" target="_blank">vanoppen.koen@gmail.com</a>><br>
> > wrote:<br>
> > > Back again... Already...<br>
<br>
</span>Are you sure that this is indeed a reincarnation of<br>
<br>
Bug 1185818 - [engine-backend] requests don't reach vdsm<br>
<br>
? Is vdsm running? Does it show something interesting in its logs?<br>
<div><div><br>
> > ><br>
> > > So, the hypervisor got his packages...<br>
> > > But when I tried to setup the network config I get this:<br>
> > > INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]<br>
> > > (ajp--127.0.0.1-8702-15) [21da92a6] FINISH, SetupNetworksVDSCommand, log<br>
> > id:<br>
> > > 13932de5<br>
> > > 2015-02-05 15:04:28,604 INFO<br>
> > > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp<br>
> > Reactor)<br>
> > > Connecting to <a href="http://ovirthyp01dev.brusselsairport.aero/10.110.56.23" target="_blank">ovirthyp01dev.brusselsairport.aero/10.110.56.23</a><br>
> > > 2015-02-05 15:04:59,040 WARN<br>
> > > [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker)<br>
> > > Exception thrown during message processing<br>
> > > 2015-02-05 15:04:59,041 ERROR<br>
> > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand]<br>
> > > (ajp--127.0.0.1-8702-15) [21da92a6]<br>
> > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:<br>
> > > VDSGenericException: VDSNetworkException: Vds timeout occured<br>
> > > 2015-02-05 15:04:59,103 ERROR<br>
> > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand]<br>
> > > (ajp--127.0.0.1-8702-15) [21da92a6] Command PollVDSCommand(HostName =<br>
> > > ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952) execution<br>
> > > failed. Exception: VDSNetworkException: VDSGenericException:<br>
> > > VDSNetworkException: Vds timeout occured<br>
> > > 2015-02-05 15:04:59,111 ERROR<br>
> > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]<br>
> > > (ajp--127.0.0.1-8702-15) [21da92a6]<br>
> > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException:<br>
> > > VDSGenericException: VDSNetworkException: Message timeout which can be<br>
> > > caused by communication issues<br>
> > > 2015-02-05 15:04:59,128 ERROR<br>
> > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand]<br>
> > > (ajp--127.0.0.1-8702-15) [21da92a6] Command<br>
> > SetupNetworksVDSCommand(HostName<br>
> > > = ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952,<br>
> > force=false,<br>
> > > checkConnectivity=true, conectivityTimeout=120,<br>
> > ><br>
> > ><br>
> > > _______________________________________________<br>
> > > Users mailing list<br>
> > > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
> > > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
> > ><br>
> ><br>
<br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>