We are already on oVirt 3.5.1... So this shouldn't be the problem... We also have network issues for the moment here, so if it wouldn't be solved when these issues disappear, I come back to this.

2015-02-06 12:43 GMT+01:00 Piotr Kliczewski <piotr.kliczewski(a)gmail.com&gt;: > Koen, > > It seems that you hit [1] bug. The fix is part of async release so > please update and the problem will disappear. > > Thanks, > Piotr > > [1] https://bugzilla.redhat.com/1185818 > > On Thu, Feb 5, 2015 at 3:19 PM, Koen Vanoppen <vanoppen.koen(a)gmail.com&gt; > wrote: > > Back again... Already...

> > > > So, the hypervisor got his packages... > > But when I tried to setup the network config I get this: > > INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] > > (ajp--127.0.0.1-8702-15) [21da92a6] FINISH, SetupNetworksVDSCommand, log > id: > > 13932de5 > > 2015-02-05 15:04:28,604 INFO > > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp > Reactor) > > Connecting to ovirthyp01dev.brusselsairport.aero/10.110.56.23 > > 2015-02-05 15:04:59,040 WARN > > [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] (ResponseWorker) > > Exception thrown during message processing > > 2015-02-05 15:04:59,041 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] > > (ajp--127.0.0.1-8702-15) [21da92a6] > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: > > VDSGenericException: VDSNetworkException: Vds timeout occured > > 2015-02-05 15:04:59,103 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] > > (ajp--127.0.0.1-8702-15) [21da92a6] Command PollVDSCommand(HostName = > > ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952) execution > > failed. Exception: VDSNetworkException: VDSGenericException: > > VDSNetworkException: Vds timeout occured > > 2015-02-05 15:04:59,111 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] > > (ajp--127.0.0.1-8702-15) [21da92a6] > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: > > VDSGenericException: VDSNetworkException: Message timeout which can be > > caused by communication issues > > 2015-02-05 15:04:59,128 ERROR > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] > > (ajp--127.0.0.1-8702-15) [21da92a6] Command > SetupNetworksVDSCommand(HostName > > = ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952, > force=false, > > checkConnectivity=true, conectivityTimeout=120, > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > > >

_______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

So, which package should I install where in our *oVirt* *3.5.1* environment? rhevm-3.5.0-0.31.el6ev.noarch? It sure looks like this bug... But as I said, we are on 3.5.1... 2015-02-09 22:22 GMT+01:00 Dan Kenigsberg <danken(a)redhat.com&gt;: > On Mon, Feb 09, 2015 at 06:53:11AM +0100, Koen Vanoppen wrote: > > We are already on oVirt 3.5.1... So this shouldn't be the problem... > > We also have network issues for the moment here, so if it wouldn't be > > solved when these issues disappear, I come back to this. > > > > > 2015-02-06 12:43 GMT+01:00 Piotr Kliczewski <piotr.kliczewski(a)gmail.com > >: > > > > > Koen, > > > > > > It seems that you hit [1] bug. The fix is part of async release so > > > please update and the problem will disappear. > > > > > > Thanks, > > > Piotr > > > > > > [1] https://bugzilla.redhat.com/1185818 > > > > > > On Thu, Feb 5, 2015 at 3:19 PM, Koen Vanoppen < > vanoppen.koen(a)gmail.com&gt; > > > wrote: > > > > Back again... Already... > > Are you sure that this is indeed a reincarnation of > > Bug 1185818 - [engine-backend] requests don't reach vdsm > > ? Is vdsm running? Does it show something interesting in its logs? > > > > > > > > > So, the hypervisor got his packages... > > > > But when I tried to setup the network config I get this: > > > > INFO > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] > > > > (ajp--127.0.0.1-8702-15) [21da92a6] FINISH, > SetupNetworksVDSCommand, log > > > id: > > > > 13932de5 > > > > 2015-02-05 15:04:28,604 INFO > > > > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp > > > Reactor) > > > > Connecting to ovirthyp01dev.brusselsairport.aero/10.110.56.23 > > > > 2015-02-05 15:04:59,040 WARN > > > > [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] > (ResponseWorker) > > > > Exception thrown during message processing > > > > 2015-02-05 15:04:59,041 ERROR > > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] > > > > (ajp--127.0.0.1-8702-15) [21da92a6] > > > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: > > > > VDSGenericException: VDSNetworkException: Vds timeout occured > > > > 2015-02-05 15:04:59,103 ERROR > > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] > > > > (ajp--127.0.0.1-8702-15) [21da92a6] Command PollVDSCommand(HostName > = > > > > ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952) > execution > > > > failed. Exception: VDSNetworkException: VDSGenericException: > > > > VDSNetworkException: Vds timeout occured > > > > 2015-02-05 15:04:59,111 ERROR > > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] > > > > (ajp--127.0.0.1-8702-15) [21da92a6] > > > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: > > > > VDSGenericException: VDSNetworkException: Message timeout which can > be > > > > caused by communication issues > > > > 2015-02-05 15:04:59,128 ERROR > > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] > > > > (ajp--127.0.0.1-8702-15) [21da92a6] Command > > > SetupNetworksVDSCommand(HostName > > > > = ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952, > > > force=false, > > > > checkConnectivity=true, conectivityTimeout=120, > > > > > > > > > > > > _______________________________________________ > > > > Users mailing list > > > > Users(a)ovirt.org > > > > http://lists.ovirt.org/mailman/listinfo/users > > > > > > > > > > _______________________________________________ > > Users mailing list > > Users(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/users > >

OK... Damn... Still not solved... 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 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. 2015-02-10 7:15 GMT+01:00 Koen Vanoppen <vanoppen.koen(a)gmail.com&gt;: > Found the problem... > 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. > I pulled the new rpms for these 2 repos and now everything works fine. > Thanks for the help! > [SOLVED] > > 2015-02-10 6:10 GMT+01:00 Koen Vanoppen <vanoppen.koen(a)gmail.com&gt;: > >> So, which package should I install where in our *oVirt* *3.5.1* >> environment? >> >> rhevm-3.5.0-0.31.el6ev.noarch? >> >> It sure looks like this bug... But as I said, we are on 3.5.1... >> >> >> >> 2015-02-09 22:22 GMT+01:00 Dan Kenigsberg <danken(a)redhat.com&gt;: >> >>> On Mon, Feb 09, 2015 at 06:53:11AM +0100, Koen Vanoppen wrote: >>> > We are already on oVirt 3.5.1... So this shouldn't be the problem... >>> > We also have network issues for the moment here, so if it wouldn't be >>> > solved when these issues disappear, I come back to this. >>> >>> > >>> > 2015-02-06 12:43 GMT+01:00 Piotr Kliczewski < >>> piotr.kliczewski(a)gmail.com&gt;: >>> > >>> > > Koen, >>> > > >>> > > It seems that you hit [1] bug. The fix is part of async release so >>> > > please update and the problem will disappear. >>> > > >>> > > Thanks, >>> > > Piotr >>> > > >>> > > [1] https://bugzilla.redhat.com/1185818 >>> > > >>> > > On Thu, Feb 5, 2015 at 3:19 PM, Koen Vanoppen < >>> vanoppen.koen(a)gmail.com&gt; >>> > > wrote: >>> > > > Back again... Already... >>> >>> Are you sure that this is indeed a reincarnation of >>> >>> Bug 1185818 - [engine-backend] requests don't reach vdsm >>> >>> ? Is vdsm running? Does it show something interesting in its logs? >>> >>> > > > >>> > > > So, the hypervisor got his packages... >>> > > > But when I tried to setup the network config I get this: >>> > > > INFO >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] >>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] FINISH, >>> SetupNetworksVDSCommand, log >>> > > id: >>> > > > 13932de5 >>> > > > 2015-02-05 15:04:28,604 INFO >>> > > > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL Stomp >>> > > Reactor) >>> > > > Connecting to ovirthyp01dev.brusselsairport.aero/10.110.56.23 >>> > > > 2015-02-05 15:04:59,040 WARN >>> > > > [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] >>> (ResponseWorker) >>> > > > Exception thrown during message processing >>> > > > 2015-02-05 15:04:59,041 ERROR >>> > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] >>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] >>> > > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>> > > > VDSGenericException: VDSNetworkException: Vds timeout occured >>> > > > 2015-02-05 15:04:59,103 ERROR >>> > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] >>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] Command >>> PollVDSCommand(HostName = >>> > > > ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952) >>> execution >>> > > > failed. Exception: VDSNetworkException: VDSGenericException: >>> > > > VDSNetworkException: Vds timeout occured >>> > > > 2015-02-05 15:04:59,111 ERROR >>> > > > >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] >>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] >>> > > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>> > > > VDSGenericException: VDSNetworkException: Message timeout which >>> can be >>> > > > caused by communication issues >>> > > > 2015-02-05 15:04:59,128 ERROR >>> > > > >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] >>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] Command >>> > > SetupNetworksVDSCommand(HostName >>> > > > = ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952, >>> > > force=false, >>> > > > checkConnectivity=true, conectivityTimeout=120, >>> > > > >>> > > > >>> > > > _______________________________________________ >>> > > > Users mailing list >>> > > > Users(a)ovirt.org >>> > > > http://lists.ovirt.org/mailman/listinfo/users >>> > > > >>> > > >>> >>> > _______________________________________________ >>> > Users mailing list >>> > Users(a)ovirt.org >>> > http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >

And this : https://mail.google.com/mail/u/0/#search/vds+daemon+is+not+running%2C+and... won't work... [root@ovirthyp02dev ~]# vdsm-tool configure --force Checking configuration status... libvirt is already configured for vdsm Running configure... Reconfiguration of sebool is done. Reconfiguration of libvirt is done. Done configuring modules to VDSM. 2015-02-10 13:18 GMT+01:00 Koen Vanoppen <vanoppen.koen(a)gmail.com&gt;: > This is from the messages: > , respawning slave > > 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 > Feb 10 13:16:13 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm > --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave > Feb 10 13:16:13 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm > --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave > 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 > Feb 10 13:16:14 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm > --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave > Feb 10 13:16:14 ovirthyp02dev respawn: slave '/usr/share/vdsm/vdsm > --pidfile /var/run/vdsm/vdsmd.pid' died too quickly, respawning slave > 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 > > > 2015-02-10 12:57 GMT+01:00 Koen Vanoppen <vanoppen.koen(a)gmail.com&gt;: > >> OK... Damn... Still not solved... >> >> 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 >> 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. >> >> >> 2015-02-10 7:15 GMT+01:00 Koen Vanoppen <vanoppen.koen(a)gmail.com&gt;: >> >>> Found the problem... >>> 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. >>> I pulled the new rpms for these 2 repos and now everything works fine. >>> Thanks for the help! >>> [SOLVED] >>> >>> 2015-02-10 6:10 GMT+01:00 Koen Vanoppen <vanoppen.koen(a)gmail.com&gt;: >>> >>>> So, which package should I install where in our *oVirt* *3.5.1* >>>> environment? >>>> >>>> rhevm-3.5.0-0.31.el6ev.noarch? >>>> >>>> It sure looks like this bug... But as I said, we are on 3.5.1... >>>> >>>> >>>> >>>> 2015-02-09 22:22 GMT+01:00 Dan Kenigsberg <danken(a)redhat.com&gt;: >>>> >>>>> On Mon, Feb 09, 2015 at 06:53:11AM +0100, Koen Vanoppen wrote: >>>>> > We are already on oVirt 3.5.1... So this shouldn't be the problem... >>>>> > We also have network issues for the moment here, so if it wouldn't >>>>> be >>>>> > solved when these issues disappear, I come back to this. >>>>> >>>>> > >>>>> > 2015-02-06 12:43 GMT+01:00 Piotr Kliczewski < >>>>> piotr.kliczewski(a)gmail.com&gt;: >>>>> > >>>>> > > Koen, >>>>> > > >>>>> > > It seems that you hit [1] bug. The fix is part of async release >>>>> so >>>>> > > please update and the problem will disappear. >>>>> > > >>>>> > > Thanks, >>>>> > > Piotr >>>>> > > >>>>> > > [1] https://bugzilla.redhat.com/1185818 >>>>> > > >>>>> > > On Thu, Feb 5, 2015 at 3:19 PM, Koen Vanoppen < >>>>> vanoppen.koen(a)gmail.com&gt; >>>>> > > wrote: >>>>> > > > Back again... Already... >>>>> >>>>> Are you sure that this is indeed a reincarnation of >>>>> >>>>> Bug 1185818 - [engine-backend] requests don't reach vdsm >>>>> >>>>> ? Is vdsm running? Does it show something interesting in its logs? >>>>> >>>>> > > > >>>>> > > > So, the hypervisor got his packages... >>>>> > > > But when I tried to setup the network config I get this: >>>>> > > > INFO >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] >>>>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] FINISH, >>>>> SetupNetworksVDSCommand, log >>>>> > > id: >>>>> > > > 13932de5 >>>>> > > > 2015-02-05 15:04:28,604 INFO >>>>> > > > [org.ovirt.vdsm.jsonrpc.client.reactors.ReactorClient] (SSL >>>>> Stomp >>>>> > > Reactor) >>>>> > > > Connecting to ovirthyp01dev.brusselsairport.aero/10.110.56.23 >>>>> > > > 2015-02-05 15:04:59,040 WARN >>>>> > > > [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] >>>>> (ResponseWorker) >>>>> > > > Exception thrown during message processing >>>>> > > > 2015-02-05 15:04:59,041 ERROR >>>>> > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] >>>>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] >>>>> > > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>>>> > > > VDSGenericException: VDSNetworkException: Vds timeout occured >>>>> > > > 2015-02-05 15:04:59,103 ERROR >>>>> > > > [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] >>>>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] Command >>>>> PollVDSCommand(HostName = >>>>> > > > ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952) >>>>> execution >>>>> > > > failed. Exception: VDSNetworkException: VDSGenericException: >>>>> > > > VDSNetworkException: Vds timeout occured >>>>> > > > 2015-02-05 15:04:59,111 ERROR >>>>> > > > >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] >>>>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] >>>>> > > > org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>>>> > > > VDSGenericException: VDSNetworkException: Message timeout which >>>>> can be >>>>> > > > caused by communication issues >>>>> > > > 2015-02-05 15:04:59,128 ERROR >>>>> > > > >>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] >>>>> > > > (ajp--127.0.0.1-8702-15) [21da92a6] Command >>>>> > > SetupNetworksVDSCommand(HostName >>>>> > > > = ovirthyp01dev, HostId = cdf4e467-9cab-4032-bc90-aed6a04d6952, >>>>> > > force=false, >>>>> > > > checkConnectivity=true, conectivityTimeout=120, >>>>> > > > >>>>> > > > >>>>> > > > _______________________________________________ >>>>> > > > Users mailing list >>>>> > > > Users(a)ovirt.org >>>>> > > > http://lists.ovirt.org/mailman/listinfo/users >>>>> > > > >>>>> > > >>>>> >>>>> > _______________________________________________ >>>>> > Users mailing list >>>>> > Users(a)ovirt.org >>>>> > http://lists.ovirt.org/mailman/listinfo/users >>>>> >>>>> >>>> >>> >> >