Looking at the logs I see that some calls timeout due to reconnect because other calls timeout before.
This behavior seems to create a loop. I do not see original issue in the logs.

Is it possible that you could send logs from the time it started to occur?

As workaround you could restart the engine which should break the loop but this won't fix the issue
which caused it.

Thanks,
Piotr

On Tue, Aug 30, 2016 at 9:25 AM, Piotr Kliczewski <pkliczew@redhat.com> wrote:
Please make sure that we can access the logs.

On Tue, Aug 30, 2016 at 9:23 AM, knarra <knarra@redhat.com> wrote:
On 08/30/2016 12:36 PM, Nir Soffer wrote:
On Tue, Aug 30, 2016 at 9:20 AM, knarra <knarra@redhat.com> wrote:
On 08/30/2016 11:47 AM, knarra wrote:
Hi,

    I have installed the latest bits of ovirt and i see that my events tab in the UI is flodded with the following error messages for all the hosts in the cluster. Can some help me understand why are these ?

VDSM <host> command failed: Message timeout which can be caused by communication issues

VDSM command failed: Vds timeout occured

Thanks

kasturi

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

I am monitoring some vms and i see there are warnings related to these saying "Vm not responding" though my vms are up and running fine.

We will need engine and vdsm logs to check this.

Nir

Hi Nir,

    I have uploaded the logs to google drive and shared it with you.  Below is the link

https://drive.google.com/drive/u/0/folders/0B1PSZZ4Ki3DnWTdsazZwUWhfdWc

Thanks

kasturi