Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

g down for system halt > > > > Broadcast message from root@r-687-VM (Tue Dec 20 01:46:22 2016): > > > > The system is going down for system halt NOW! > > Dec 20 01:46:22 r-687-VM shutdown[3962]: shutting down for system halt > > > > Broadcast message fro

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

sion, nchannels 1 > Connection to 169.254.0.197 closed by remote host. > Connection to 169.254.0.197 closed. > Transferred: sent 4336, received 93744 bytes, in 180.3 seconds > Bytes per second: sent 24.0, received 519.8 > debug1: Exit status -1 > > Looks like the config script didn't get p

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

ir <sa...@pulasan.my> > Sent: Monday, December 19, 2016 2:09 AM > To: users@cloudstack.apache.org > Subject: Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks > > On Tue, Dec 13, 2016 at 7:26 PM, Syahrul Sazli Shaharir > <sa...@pulasan.my> wrote: >&

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

Shaharir <sa...@pulasan.my> Sent: Monday, December 19, 2016 2:09 AM To: users@cloudstack.apache.org Subject: Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks On Tue, Dec 13, 2016 at 7:26 PM, Syahrul Sazli Shaharir <sa...@pulasan.my> wrote: > Hi Simon, > >

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

On Tue, Dec 13, 2016 at 7:26 PM, Syahrul Sazli Shaharir wrote: > Hi Simon, > > On Tue, Dec 13, 2016 at 10:31 AM, Simon Weller wrote: >> Can you turn on agent debug mode and take a look at the debug level logs? >> >> >> You can do that by running sed -i

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

On Fri, Dec 16, 2016 at 5:16 PM, Dag Sonstebo wrote: > Hi Syahrul, > > It just struck me we had similar issues with patchviasocket.py and > python-argparse with one of our clients a while back, I believe our fix is > going into 4.9.1.0: > >

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

Hi Syahrul, It just struck me we had similar issues with patchviasocket.py and python-argparse with one of our clients a while back, I believe our fix is going into 4.9.1.0: https://github.com/apache/cloudstack/pull/1634 Regards, Dag Sonstebo Cloud Architect ShapeBlue On 15/12/2016, 23:09,

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

Hi Ilya, I've looked at the patch suggested, looks like it has been committed into qemu 2.4.0, and I can see the modified parts in the latest qemu 2.6.0 code. So I went ahead and installed qemu-kvm-ev-2.6.0-27.1 on one of the hosts. But the problem still persists. Perhaps I should bring this

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

This will explain a bit more on how this issue came about and how to fix it.. https://www.mail-archive.com/dev@cloudstack.apache.org/msg71559.html On 12/12/16 6:31 PM, Simon Weller wrote: > Can you turn on agent debug mode and take a look at the debug level logs? > > > You can do that by

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

Hi Simon, On Tue, Dec 13, 2016 at 10:31 AM, Simon Weller wrote: > Can you turn on agent debug mode and take a look at the debug level logs? > > > You can do that by running sed -i 's/INFO/DEBUG/g' > /etc/cloudstack/agent/log4j-cloud.xml on the host and then restarting the >

Re: Router VM: patchviasocket.py timeout issue on 1 out of 4 networks

Can you turn on agent debug mode and take a look at the debug level logs? You can do that by running sed -i 's/INFO/DEBUG/g' /etc/cloudstack/agent/log4j-cloud.xml on the host and then restarting the agent. - Si From: Syahrul Sazli Shaharir