date:20190719

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

2019-07-19 Thread Gabriel Beims Bräscher

Congrats Nathan!

Em sex, 19 de jul de 2019 às 15:58, Sven Vogel  escreveu:

> Congrats Nathan!
>
> Von meinem iPhone gesendet
>
>
> __
>
> Sven Vogel
> Teamlead Platform
>
> EWERK RZ GmbH
> Brühl 24, D-04109 Leipzig
> P +49 341 42649 - 11
> F +49 341 42649 - 18
> s.vo...@ewerk.com
> www.ewerk.com
>
> Geschäftsführer:
> Dr. Erik Wende, Hendrik Schubert, Frank Richter
> Registergericht: Leipzig HRB 17023
>
> Zertifiziert nach:
> ISO/IEC 27001:2013
> DIN EN ISO 9001:2015
> DIN ISO/IEC 2-1:2011
>
> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook
>
> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.
>
> Disclaimer Privacy:
> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist
> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der
> bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,
> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte
> informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie
> die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.
> Vielen Dank.
>
> The contents of this e-mail (including any attachments) are confidential
> and may be legally privileged. If you are not the intended recipient of
> this e-mail, any disclosure, copying, distribution or use of its contents
> is strictly prohibited, and you should please notify the sender immediately
> and then delete it (including any attachments) from your system. Thank you.
> > Am 19.07.2019 um 19:45 schrieb Suresh Kumar Anaparti <
> sureshkumar.anapa...@gmail.com>:
> >
> > Congratulations Nathan...
> >
> >> On Fri, Jul 19, 2019 at 8:29 PM Paul Angus  wrote:
> >>
> >> Fellow CloudStackers,
> >>
> >>
> >>
> >> It gives me great pleasure to say that Nathan has been invited to join
> the
> >> PMC and has gracefully accepted.
> >>
> >>
> >> Please join me in congratulating Nathan!
> >>
> >>
> >>
> >>
> >> Kind regards,
> >>
> >>
> >>
> >> Paul Angus
> >>
> >> CloudStack PMC
> >>
>

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

2019-07-19 Thread Sven Vogel

Congrats Nathan!

Von meinem iPhone gesendet

__

Sven Vogel
Teamlead Platform

EWERK RZ GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.
> Am 19.07.2019 um 19:45 schrieb Suresh Kumar Anaparti 
> :
>
> Congratulations Nathan...
>
>> On Fri, Jul 19, 2019 at 8:29 PM Paul Angus  wrote:
>>
>> Fellow CloudStackers,
>>
>>
>>
>> It gives me great pleasure to say that Nathan has been invited to join the
>> PMC and has gracefully accepted.
>>
>>
>> Please join me in congratulating Nathan!
>>
>>
>>
>>
>> Kind regards,
>>
>>
>>
>> Paul Angus
>>
>> CloudStack PMC
>>

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

2019-07-19 Thread Suresh Kumar Anaparti

Congratulations Nathan...

On Fri, Jul 19, 2019 at 8:29 PM Paul Angus  wrote:

> Fellow CloudStackers,
>
>
>
> It gives me great pleasure to say that Nathan has been invited to join the
> PMC and has gracefully accepted.
>
>
> Please join me in congratulating Nathan!
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
> CloudStack PMC
>

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

2019-07-19 Thread Andrija Panic

Cheers Nathan!

On Fri, 19 Jul 2019 at 16:59, Paul Angus  wrote:

> Fellow CloudStackers,
>
>
>
> It gives me great pleasure to say that Nathan has been invited to join the
> PMC and has gracefully accepted.
>
>
> Please join me in congratulating Nathan!
>
>
>
>
> Kind regards,
>
>
>
> Paul Angus
>
> CloudStack PMC
>


-- 

Andrija Panić

[ANNOUNCE] Nathan Johnson has joined the PMC

2019-07-19 Thread Paul Angus

Fellow CloudStackers,



It gives me great pleasure to say that Nathan has been invited to join the
PMC and has gracefully accepted.


Please join me in congratulating Nathan!




Kind regards,



Paul Angus

CloudStack PMC

答复: Agent LB for CloudStack failed

2019-07-19 Thread li jerry

In order to facilitate tracking, I created a new issue.



https://github.com/apache/cloudstack/issues/3505



Welcome to update, thank you








发件人: li jerry 
发送时间: Friday, July 19, 2019 8:25:27 PM
收件人: dev@cloudstack.apache.org ; 
us...@cloudstack.apache.org 
主题: 答复: Agent LB for CloudStack failed

Thank you, look forward to your reply.



发送自 Windows 10 版邮件应用




发件人: Nicolas Vazquez 
发送时间: Friday, July 19, 2019 8:16:40 PM
收件人: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
主题: Re: Agent LB for CloudStack failed

Ok, I'll try replicating and get back to you.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Thursday, July 18, 2019 4:41 AM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: 答复: Agent LB for CloudStack failed


I added host.lb.check.interval = 0 to all agent.properties and restarted the 
cloudstack-agent


The following is the connection status of the agent after reboot.

mysql> select host.id ,host.name,host.mgmt_server_id,host.status,mshost.name 
from host,mshost where host.mgmt_server_id=mshost.msid;
+++++--+
| id | name   | mgmt_server_id | status | name |
+++++--+
|  1 | test-ceph-node01.cs2cloud.internal |  2200502468634 | Up | acs-mn01 |
|  3 | s-8-VM |  2200502468634 | Up | acs-mn01 |
|  5 | test-ceph-node03.cs2cloud.internal |  2200502468634 | Up | acs-mn01 |
|  2 | v-9-VM |  2199950196764 | Up | acs-mn02 |
|  4 | test-ceph-node02.cs2cloud.internal |  2199950196764 | Up | acs-mn02 |
|  6 | test-ceph-node04.cs2cloud.internal |  2199950196764 | Up | acs-mn02 |
+++++--+
6 rows in set (0.00 sec)

2019-07-18 15:10 Forced power off to close acs-mn02

wait

After the 15th minute (2019-07-18 15:26:23), the agent found that the 
management node failed and began to switch.
So, add host.lb.check.interval=0 to agent. properties doesn't solve the problem.

Below is the log




2019-07-18 15:26:23,414 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket 
Socket[addr=/172.17.1.142,port=8250,localport=33190] closed on read.  Probably 
-1 returned: No route to host
2019-07-18 15:26:23,416 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Closing socket 
Socket[addr=/172.17.1.142,port=8250,localport=33190]
2019-07-18 15:26:23,417 DEBUG [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Clearing watch list: 2
2019-07-18 15:26:23,417 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Lost connection to host: 172.17.1.142. Attempting reconnection while 
we still have 0 commands in progress.
2019-07-18 15:26:23,420 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) NioClient connection closed
2019-07-18 15:26:23,420 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Reconnecting to host:172.17.1.142
2019-07-18 15:26:23,420 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) Connecting to 172.17.1.142:8250
2019-07-18 15:26:26,427 ERROR [utils.nio.NioConnection] (Agent-Handler-2:null) 
(logid:) Unable to initialize the threads.
java.net.NoRouteToHostException: No route to host
  at sun.nio.ch.Net.connect0(Native Method)
  at sun.nio.ch.Net.connect(Net.java:454)
  at sun.nio.ch.Net.connect(Net.java:446)
  at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
  at com.cloud.utils.nio.NioClient.init(NioClient.java:56)
  at com.cloud.utils.nio.NioConnection.start(NioConnection.java:95)
  at com.cloud.agent.Agent.reconnect(Agent.java:517)
  at com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:1091)
  at com.cloud.utils.nio.Task.call(Task.java:83)
  at com.cloud.utils.nio.Task.call(Task.java:29)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at java.lang.Thread.run(Thread.java:748)
2019-07-18 15:26:26,432 INFO  [utils.exception.CSExceptionErrorCode] 
(Agent-Handler-2:null) (logid:) Could not find exception: 
com.cloud.utils.exception.NioConnectionException in error code list for 
exceptions
2019-07-18 15:26:26,432 WARN  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) NIO Connection Exception  
com.cloud.utils.exception.NioConnectionException: No route to host
2019-07-18 15:26:26,432 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Attempted to connect to the server, but received an unexpected

Re: Latest Qemu KVM EV appears to be broken with ACS #3278

2019-07-19 Thread Simon Weller

Hi Sven,

We're still using 2.10 right now and we haven't tested the patches yet for 
2.12. Having said that, we're currently trying to get our internal ACS release 
up to a more recent mainline version, so I'd suspect we'll have to dive into 
this fairly soon.

-Si


From: Sven Vogel 
Sent: Friday, July 19, 2019 6:48 AM
To: dev 
Subject: Re: Latest Qemu KVM EV appears to be broken with ACS #3278

Hi Guys,

Sorry that I formal reopen this issue.

We tested the actual system with this patch #3278

We use CentOS 1805 or 1810 and OVS and QEMU 2.12. It seems the first agent 
contact will not work so that the agent know the virtual machine is running. 
With 2.10 and the old agent, SystemVM it works.

2019-07-19 00:17:30,571 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:8ad14091) Executing: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patch.sh -n v-1728-VM -c 
 template=domP type=consoleproxy host=10.24.48.46 port=8250 name=v-1728-VM 
premium=true zone=4 pod=4 guid=Proxy.1728 proxy_vm=1728 disable_rp_filter=true 
eth2ip=185.232.219.237 eth2mask=255.255.255.248 gateway=185.232.219.233 
eth0ip=169.254.0.193 eth0mask=255.255.0.0 eth1ip=10.24.48.124 
eth1mask=255.255.255.0 mgmtcidr=10.24.48.0/24 localgw=10.24.48.1 
internaldns1=10.24.48.33 internaldns2=10.24.48.34 dns1=217.69.224.73 
dns2=85.232.28.146
2019-07-19 00:17:30,573 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:8ad14091) Executing while with timeout : 
30
2019-07-19 00:17:30,616 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Unable to logon to 169.254.2.189
2019-07-19 00:17:30,616 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Trying to connect to 
169.254.2.189
2019-07-19 00:17:31,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Could not connect to 169.254.1.21
2019-07-19 00:17:33,622 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Could not connect to 
169.254.2.189
2019-07-19 00:17:36,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Unable to logon to 169.254.1.21
2019-07-19 00:17:36,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Trying to connect to 169.254.1.21
2019-07-19 00:17:38,622 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Trying to connect to 
169.254.2.189

@simonweller you encountered the same problem?

@rohit maybe there is something what we forget or what’s wrong?

@wido do you have ideas?

thanks

Sven


__

Sven Vogel
Teamlead Platform

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

EWERK-Blog | 
LinkedIn | 
Xing | 
Twitter | 
Facebook

Mit Handelsregistereintragung vom 10.07.2019 ist die EWERK RZ GmbH auf die 
EWERK IT GmbH verschmolzen und firmiert zukünftig gemeinsam unter dem Namen: 
EWERK DIGITAL GmbH, für weitere Informationen klicken Sie 
hier.

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.

Am 22.04.2019 um 21:29 schrieb Simon Weller 
mailto:swel...@ena.com.INVALID>>:

In our case the SystemVMs were booting fine, but ACS wasn't able to inject the 
payload via the socket.

答复: Agent LB for CloudStack failed

2019-07-19 Thread li jerry

Thank you, look forward to your reply.



发送自 Windows 10 版邮件应用




发件人: Nicolas Vazquez 
发送时间: Friday, July 19, 2019 8:16:40 PM
收件人: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
主题: Re: Agent LB for CloudStack failed

Ok, I'll try replicating and get back to you.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Thursday, July 18, 2019 4:41 AM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: 答复: Agent LB for CloudStack failed


I added host.lb.check.interval = 0 to all agent.properties and restarted the 
cloudstack-agent


The following is the connection status of the agent after reboot.

mysql> select host.id ,host.name,host.mgmt_server_id,host.status,mshost.name 
from host,mshost where host.mgmt_server_id=mshost.msid;
+++++--+
| id | name   | mgmt_server_id | status | name |
+++++--+
|  1 | test-ceph-node01.cs2cloud.internal |  2200502468634 | Up | acs-mn01 |
|  3 | s-8-VM |  2200502468634 | Up | acs-mn01 |
|  5 | test-ceph-node03.cs2cloud.internal |  2200502468634 | Up | acs-mn01 |
|  2 | v-9-VM |  2199950196764 | Up | acs-mn02 |
|  4 | test-ceph-node02.cs2cloud.internal |  2199950196764 | Up | acs-mn02 |
|  6 | test-ceph-node04.cs2cloud.internal |  2199950196764 | Up | acs-mn02 |
+++++--+
6 rows in set (0.00 sec)

2019-07-18 15:10 Forced power off to close acs-mn02

wait

After the 15th minute (2019-07-18 15:26:23), the agent found that the 
management node failed and began to switch.
So, add host.lb.check.interval=0 to agent. properties doesn't solve the problem.

Below is the log




2019-07-18 15:26:23,414 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket 
Socket[addr=/172.17.1.142,port=8250,localport=33190] closed on read.  Probably 
-1 returned: No route to host
2019-07-18 15:26:23,416 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Closing socket 
Socket[addr=/172.17.1.142,port=8250,localport=33190]
2019-07-18 15:26:23,417 DEBUG [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Clearing watch list: 2
2019-07-18 15:26:23,417 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Lost connection to host: 172.17.1.142. Attempting reconnection while 
we still have 0 commands in progress.
2019-07-18 15:26:23,420 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) NioClient connection closed
2019-07-18 15:26:23,420 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Reconnecting to host:172.17.1.142
2019-07-18 15:26:23,420 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) Connecting to 172.17.1.142:8250
2019-07-18 15:26:26,427 ERROR [utils.nio.NioConnection] (Agent-Handler-2:null) 
(logid:) Unable to initialize the threads.
java.net.NoRouteToHostException: No route to host
  at sun.nio.ch.Net.connect0(Native Method)
  at sun.nio.ch.Net.connect(Net.java:454)
  at sun.nio.ch.Net.connect(Net.java:446)
  at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
  at com.cloud.utils.nio.NioClient.init(NioClient.java:56)
  at com.cloud.utils.nio.NioConnection.start(NioConnection.java:95)
  at com.cloud.agent.Agent.reconnect(Agent.java:517)
  at com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:1091)
  at com.cloud.utils.nio.Task.call(Task.java:83)
  at com.cloud.utils.nio.Task.call(Task.java:29)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at java.lang.Thread.run(Thread.java:748)
2019-07-18 15:26:26,432 INFO  [utils.exception.CSExceptionErrorCode] 
(Agent-Handler-2:null) (logid:) Could not find exception: 
com.cloud.utils.exception.NioConnectionException in error code list for 
exceptions
2019-07-18 15:26:26,432 WARN  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) NIO Connection Exception  
com.cloud.utils.exception.NioConnectionException: No route to host
2019-07-18 15:26:26,432 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Attempted to connect to the server, but received an unexpected 
exception, trying again...
2019-07-18 15:26:26,432 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) NioClient connection closed
2019-07-18 15:26:31,433 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Reconnecting to host:172.17.1.141
2019-07-18 15:26:31,434 INFO  [utils.nio.NioClient] (Agent-Handler-2:null)

Re: Agent LB for CloudStack failed

2019-07-19 Thread Nicolas Vazquez

Ok, I'll try replicating and get back to you.


Regards,

Nicolas Vazquez


From: li jerry 
Sent: Thursday, July 18, 2019 4:41 AM
To: us...@cloudstack.apache.org ; 
dev@cloudstack.apache.org 
Subject: 答复: Agent LB for CloudStack failed


I added host.lb.check.interval = 0 to all agent.properties and restarted the 
cloudstack-agent


The following is the connection status of the agent after reboot.

mysql> select host.id ,host.name,host.mgmt_server_id,host.status,mshost.name 
from host,mshost where host.mgmt_server_id=mshost.msid;
+++++--+
| id | name   | mgmt_server_id | status | name |
+++++--+
|  1 | test-ceph-node01.cs2cloud.internal |  2200502468634 | Up | acs-mn01 |
|  3 | s-8-VM |  2200502468634 | Up | acs-mn01 |
|  5 | test-ceph-node03.cs2cloud.internal |  2200502468634 | Up | acs-mn01 |
|  2 | v-9-VM |  2199950196764 | Up | acs-mn02 |
|  4 | test-ceph-node02.cs2cloud.internal |  2199950196764 | Up | acs-mn02 |
|  6 | test-ceph-node04.cs2cloud.internal |  2199950196764 | Up | acs-mn02 |
+++++--+
6 rows in set (0.00 sec)

2019-07-18 15:10 Forced power off to close acs-mn02

wait

After the 15th minute (2019-07-18 15:26:23), the agent found that the 
management node failed and began to switch.
So, add host.lb.check.interval=0 to agent. properties doesn't solve the problem.

Below is the log




2019-07-18 15:26:23,414 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Location 1: Socket 
Socket[addr=/172.17.1.142,port=8250,localport=33190] closed on read.  Probably 
-1 returned: No route to host
2019-07-18 15:26:23,416 DEBUG [utils.nio.NioConnection] 
(Agent-NioConnectionHandler-1:null) (logid:) Closing socket 
Socket[addr=/172.17.1.142,port=8250,localport=33190]
2019-07-18 15:26:23,417 DEBUG [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Clearing watch list: 2
2019-07-18 15:26:23,417 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Lost connection to host: 172.17.1.142. Attempting reconnection while 
we still have 0 commands in progress.
2019-07-18 15:26:23,420 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) NioClient connection closed
2019-07-18 15:26:23,420 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Reconnecting to host:172.17.1.142
2019-07-18 15:26:23,420 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) Connecting to 172.17.1.142:8250
2019-07-18 15:26:26,427 ERROR [utils.nio.NioConnection] (Agent-Handler-2:null) 
(logid:) Unable to initialize the threads.
java.net.NoRouteToHostException: No route to host
  at sun.nio.ch.Net.connect0(Native Method)
  at sun.nio.ch.Net.connect(Net.java:454)
  at sun.nio.ch.Net.connect(Net.java:446)
  at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
  at com.cloud.utils.nio.NioClient.init(NioClient.java:56)
  at com.cloud.utils.nio.NioConnection.start(NioConnection.java:95)
  at com.cloud.agent.Agent.reconnect(Agent.java:517)
  at com.cloud.agent.Agent$ServerHandler.doTask(Agent.java:1091)
  at com.cloud.utils.nio.Task.call(Task.java:83)
  at com.cloud.utils.nio.Task.call(Task.java:29)
  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
  at java.lang.Thread.run(Thread.java:748)
2019-07-18 15:26:26,432 INFO  [utils.exception.CSExceptionErrorCode] 
(Agent-Handler-2:null) (logid:) Could not find exception: 
com.cloud.utils.exception.NioConnectionException in error code list for 
exceptions
2019-07-18 15:26:26,432 WARN  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) NIO Connection Exception  
com.cloud.utils.exception.NioConnectionException: No route to host
2019-07-18 15:26:26,432 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Attempted to connect to the server, but received an unexpected 
exception, trying again...
2019-07-18 15:26:26,432 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) NioClient connection closed
2019-07-18 15:26:31,433 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
(logid:) Reconnecting to host:172.17.1.141
2019-07-18 15:26:31,434 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) Connecting to 172.17.1.141:8250
2019-07-18 15:26:31,435 INFO  [utils.nio.Link] (Agent-Handler-2:null) (logid:) 
Conf file found: /etc/cloudstack/agent/agent.properties
2019-07-18 15:26:31,545 INFO  [utils.nio.NioClient] (Agent-Handler-2:null) 
(logid:) SSL: Handshake done
2019-07-18 15:26:31,546 INFO

Re: Latest Qemu KVM EV appears to be broken with ACS #3278

2019-07-19 Thread Sven Vogel

Hi Guys,

Sorry that I formal reopen this issue.

We tested the actual system with this patch #3278

We use CentOS 1805 or 1810 and OVS and QEMU 2.12. It seems the first agent 
contact will not work so that the agent know the virtual machine is running. 
With 2.10 and the old agent, SystemVM it works.

2019-07-19 00:17:30,571 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:8ad14091) Executing: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patch.sh -n v-1728-VM -c 
 template=domP type=consoleproxy host=10.24.48.46 port=8250 name=v-1728-VM 
premium=true zone=4 pod=4 guid=Proxy.1728 proxy_vm=1728 disable_rp_filter=true 
eth2ip=185.232.219.237 eth2mask=255.255.255.248 gateway=185.232.219.233 
eth0ip=169.254.0.193 eth0mask=255.255.0.0 eth1ip=10.24.48.124 
eth1mask=255.255.255.0 mgmtcidr=10.24.48.0/24 localgw=10.24.48.1 
internaldns1=10.24.48.33 internaldns2=10.24.48.34 dns1=217.69.224.73 
dns2=85.232.28.146
2019-07-19 00:17:30,573 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:8ad14091) Executing while with timeout : 
30
2019-07-19 00:17:30,616 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Unable to logon to 169.254.2.189
2019-07-19 00:17:30,616 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Trying to connect to 
169.254.2.189
2019-07-19 00:17:31,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Could not connect to 169.254.1.21
2019-07-19 00:17:33,622 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Could not connect to 
169.254.2.189
2019-07-19 00:17:36,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Unable to logon to 169.254.1.21
2019-07-19 00:17:36,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Trying to connect to 169.254.1.21
2019-07-19 00:17:38,622 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Trying to connect to 
169.254.2.189

@simonweller you encountered the same problem?

@rohit maybe there is something what we forget or what’s wrong?

@wido do you have ideas?

thanks

Sven


__

Sven Vogel
Teamlead Platform

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
s.vo...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

EWERK-Blog | 
LinkedIn | 
Xing | 
Twitter | 
Facebook

Mit Handelsregistereintragung vom 10.07.2019 ist die EWERK RZ GmbH auf die 
EWERK IT GmbH verschmolzen und firmiert zukünftig gemeinsam unter dem Namen: 
EWERK DIGITAL GmbH, für weitere Informationen klicken Sie 
hier.

Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.

Am 22.04.2019 um 21:29 schrieb Simon Weller 
mailto:swel...@ena.com.INVALID>>:

In our case the SystemVMs were booting fine, but ACS wasn't able to inject the 
payload via the socket.

Re: Latest Qemu KVM EV appears to be broken with ACS #3278

2019-07-19 Thread Sven Vogel

xHi Guys,

Sorry that I formal reopen this issue.

We tested the actual system with this patch #3278

We use CentOS 1805 or 1810 and OVS and QEMU 2.12. It seems the first agent 
contact will not work so that the agent know the virtual machine is running. 
With 2.10 and the old agent, SystemVM it works.

2019-07-19 00:17:30,571 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:8ad14091) Executing: 
/usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patch.sh -n v-1728-VM -c 
 template=domP type=consoleproxy host=10.24.48.46 port=8250 name=v-1728-VM 
premium=true zone=4 pod=4 guid=Proxy.1728 proxy_vm=1728 disable_rp_filter=true 
eth2ip=185.232.219.237 eth2mask=255.255.255.248 gateway=185.232.219.233 
eth0ip=169.254.0.193 eth0mask=255.255.0.0 eth1ip=10.24.48.124 
eth1mask=255.255.255.0 mgmtcidr=10.24.48.0/24 localgw=10.24.48.1 
internaldns1=10.24.48.33 internaldns2=10.24.48.34 dns1=217.69.224.73 
dns2=85.232.28.146
2019-07-19 00:17:30,573 DEBUG [kvm.resource.LibvirtComputingResource] 
(agentRequest-Handler-5:null) (logid:8ad14091) Executing while with timeout : 
30
2019-07-19 00:17:30,616 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Unable to logon to 169.254.2.189
2019-07-19 00:17:30,616 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Trying to connect to 
169.254.2.189
2019-07-19 00:17:31,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Could not connect to 169.254.1.21
2019-07-19 00:17:33,622 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Could not connect to 
169.254.2.189
2019-07-19 00:17:36,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Unable to logon to 169.254.1.21
2019-07-19 00:17:36,874 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-3:null) (logid:04b4d6ce) Trying to connect to 169.254.1.21
2019-07-19 00:17:38,622 DEBUG [resource.virtualnetwork.VirtualRoutingResource] 
(agentRequest-Handler-2:null) (logid:7577151e) Trying to connect to 
169.254.2.189

@simonweller you encountered the same problem?

@rohit maybe there is something what we forget.

@wido do you have ideas?

thanks

Sven


__

Sven Vogel
Teamlead Platform

EWERK DIGITAL GmbH
Br?hl 24, D-04109 Leipzig
P +49 341 42649 - 11
F +49 341 42649 - 18
s.vo...@ewerk.com
www.ewerk.com

Gesch?ftsf?hrer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 17023

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

EWERK-Blog | 
LinkedIn | 
Xing | 
Twitter | 
Facebook

Mit Handelsregistereintragung vom 10.07.2019 ist die EWERK RZ GmbH auf die 
EWERK IT GmbH verschmolzen und firmiert zuk?nftig gemeinsam unter dem Namen: 
EWERK DIGITAL GmbH, f?r weitere Informationen klicken Sie 
hier.

Ausk?nfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschlie?lich etwaiger beigef?gter Dateien) ist 
vertraulich und nur f?r den Empf?nger bestimmt. Sollten Sie nicht der 
bestimmungsgem??e Empf?nger sein, ist Ihnen jegliche Offenlegung, 
Vervielf?ltigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverz?glich den Absender und l?schen Sie die 
E-Mail (einschlie?lich etwaiger beigef?gter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential and 
may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.

Am 22.04.2019 um 21:29 schrieb Simon Weller 
mailto:swel...@ena.com.INVALID>>:

In our case the SystemVMs were booting fine, but ACS wasn't able to inject the 
payload via the socket.

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

Re: [ANNOUNCE] Nathan Johnson has joined the PMC

[ANNOUNCE] Nathan Johnson has joined the PMC

答复: Agent LB for CloudStack failed

Re: Latest Qemu KVM EV appears to be broken with ACS #3278

答复: Agent LB for CloudStack failed

Re: Agent LB for CloudStack failed

Re: Latest Qemu KVM EV appears to be broken with ACS #3278

Re: Latest Qemu KVM EV appears to be broken with ACS #3278

11 matches

Site Navigation

Mail list logo

Footer information