[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2017-10-31 Thread Rajani Karuturi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226481#comment-16226481
 ] 

Rajani Karuturi commented on CLOUDSTACK-9590:
-

Hi @sven.vogel and @dag.Sonstebo 
I am facing a similar issue with adding KVM host.
Which java is downgraded? The MS java version or host java version? Do you know 
any reason for this to happen? Is it java issue or cloudstack issue?

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Fix For: 4.9.1.0
>
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-12-01 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711922#comment-15711922
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


i found the solution with help of Dag Sonstebo. I used Java 1.8 and changed it 
to 1.7. After this Agent comes up fast.

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-14 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15664298#comment-15664298
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


in Management Server i see always things like

{code}
2016-11-14 16:44:56,034 WARN  [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Monitor 
NetworkOrchestrator says there is an error in the connect process for 70 due to 
Unable to get an answer to the Check
NetworkCommand from agent: 70
2016-11-14 16:44:56,034 INFO  [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Host 70 is 
disconnecting with event AgentDisconnected
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) The next status of 
agent 70is Alert, current status is Connecting
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Deregistering link for 
70 with state Alert
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Remove Agent : 70
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.ConnectedAgentAttache] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Processing Disconnect.
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.hypervisor.xenserver.discoverer.XcpServerDiscoverer
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.hypervisor.hyperv.discoverer.HypervServerDiscoverer
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.storage.secondary.SecondaryStorageListener
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.storage.listener.StoragePoolMonitor
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.vm.ClusteredVirtualMachineManagerImpl
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.network.security.SecurityGroupListener
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.deploy.DeploymentPlanningManagerImpl
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: org.apache.cloudstack.engine.orchestration.NetworkOrchestrator
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.network.SshKeysDistriMonitor
2016-11-14 16:44:56,040 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.storage.LocalStoragePoolListener
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.capacity.StorageCapacityListener
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.capacity.ComputeCapacityListener
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.network.SshKeysDistriMonitor
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.storage.upload.UploadListener
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Sending Disconnect to 
listener: com.cloud.network.NetworkUsageManagerImpl$DirectNetworkStatsListener
2016-11-14 16:44:56,041 DEBUG [c.c.n.NetworkUsageManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) Disconnected called on 
70 with status Alert
2016-11-14 16:44:56,041 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentConnectTaskPool-15:ctx-f99e936f) (logid:6cdf713e) 

[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-14 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15664147#comment-15664147
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


1. first of all i add the host from cs management
2. Management Host 
--  {code} cloudstack-setup-agent  -m 192.168.85.25 -z 3 -p 3 -c 9 -g 
6e6cff15-3183-3cca-9389-ed1a78f6236a -a --pubNic=cloudbr2 --prvNic=cloudbr0 
--guestNic=cloudbr1 --hypervisor=kvm {code}
3. agent will be dead after add the host
4. restart agent
6. agent reconnect to server and wait with alert

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-14 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15664111#comment-15664111
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


no maintenance mode. the host are fresh installed and added to cs. after that 
they stay for lime in alert mode.

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-14 Thread Wei Zhou (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15663308#comment-15663308
 ] 

Wei Zhou commented on CLOUDSTACK-9590:
--

is the host in Maintenance ?

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-11 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656691#comment-15656691
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


a how i fix this??!?

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-11 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656668#comment-15656668
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


Hi Wei,

what does this say to me?

thanks

Sven

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-11 Thread Wei Zhou (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656573#comment-15656573
 ] 

Wei Zhou commented on CLOUDSTACK-9590:
--

key logs
{code}
2016-11-10 13:23:06,568 DEBUG [c.c.a.t.Request] (AgentManager-Handler-15:null) 
(logid:) Seq -1-4: Scheduling the first command  { Cmd , MgmtId: -1, via: -1, 
Ver: v1, Flags: 1, 
[{"com.cloud.agent.api.StartupRoutingCommand":{"cpuSockets":2,"cpus":8,"speed":2261,"memory":100092813312,"dom0MinMemory":1073741824,"poolSync":false,"supportsClonedVolumes":false,"caps":"hvm,snapshot","pool":"/root","hypervisorType":"KVM","hostDetails":{"Host.OS.Kernel.Version":"3.10.0-327.36.3.el7.x86_64","com.cloud.network.Networks.RouterPrivateIpStrategy":"HostLocal","Host.OS.Version":"7.2.1511","Host.OS":"CentOS"},"hostTags":[],"groupDetails":{},"type":"Routing","dataCenter":"3","pod":"3","cluster":"9","guid":"71773d35-5679-34fe-9b15-7e2736d0dd28-LibvirtComputingResource","name":"kvm02.oscloud.local","version":"4.9.0","iqn":"iqn.1994-05.com.redhat:eedee56bd952","privateIpAddress":"192.168.85.14","privateMacAddress":"52:80:f7:fc:af:42","privateNetmask":"255.255.255.0","storageIpAddress":"192.168.85.14","storageNetmask":"255.255.255.0","storageMacAddress":"52:80:f7:fc:af:42","resourceName":"LibvirtComputingResource","gatewayIpAddress":"192.168.85.254","wait":0}},{"com.cloud.agent.api.StartupStorageCommand":{"totalSize":0,"poolInfo":{"uuid":"b3b9ef96-18b1-4136-8a69-5b316c6dc123","host":"192.168.85.14","localPath":"/var/lib/libvirt/images","hostPath":"/var/lib/libvirt/images","poolType":"Filesystem","capacityBytes":30866534400,"availableBytes":29248552960},"resourceType":"STORAGE_POOL","hostDetails":{},"type":"Storage","dataCenter":"3","pod":"3","guid":"71773d35-5679-34fe-9b15-7e2736d0dd28-LibvirtComputingResource","name":"kvm02.oscloud.local","version":"4.9.0","resourceName":"LibvirtComputingResource","wait":0}}]
 }
2016-11-10 13:23:06,570 INFO  [c.c.a.m.AgentManagerImpl] 
(AgentManager-Handler-13:null) (logid:) Connection from /192.168.85.14 closed 
but no cleanup was done.
2016-11-10 13:23:06,582 DEBUG [c.c.a.m.AgentManagerImpl] 
(AgentManager-Handler-15:null) (logid:) Failed to send startupanswer: 
java.nio.channels.ClosedChannelException
2016-11-10 13:23:06,605 DEBUG [c.c.a.t.Request] 
(AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Seq -1-4: Processing 
the first command  { Cmd , MgmtId: -1, via: -1, Ver: v1, Flags: 1, 
[{"com.cloud.agent.api.StartupRoutingCommand":{"cpuSockets":2,"cpus":8,"speed":2261,"memory":100092813312,"dom0MinMemory":1073741824,"poolSync":false,"supportsClonedVolumes":false,"caps":"hvm,snapshot","pool":"/root","hypervisorType":"KVM","hostDetails":{"Host.OS.Kernel.Version":"3.10.0-327.36.3.el7.x86_64","com.cloud.network.Networks.RouterPrivateIpStrategy":"HostLocal","Host.OS.Version":"7.2.1511","Host.OS":"CentOS"},"hostTags":[],"groupDetails":{},"type":"Routing","dataCenter":"3","pod":"3","cluster":"9","guid":"71773d35-5679-34fe-9b15-7e2736d0dd28-LibvirtComputingResource","name":"kvm02.oscloud.local","version":"4.9.0","iqn":"iqn.1994-05.com.redhat:eedee56bd952","privateIpAddress":"192.168.85.14","privateMacAddress":"52:80:f7:fc:af:42","privateNetmask":"255.255.255.0","storageIpAddress":"192.168.85.14","storageNetmask":"255.255.255.0","storageMacAddress":"52:80:f7:fc:af:42","resourceName":"LibvirtComputingResource","gatewayIpAddress":"192.168.85.254","wait":0}},{"com.cloud.agent.api.StartupStorageCommand":{"totalSize":0,"poolInfo":{"uuid":"b3b9ef96-18b1-4136-8a69-5b316c6dc123","host":"192.168.85.14","localPath":"/var/lib/libvirt/images","hostPath":"/var/lib/libvirt/images","poolType":"Filesystem","capacityBytes":30866534400,"availableBytes":29248552960},"resourceType":"STORAGE_POOL","hostDetails":{},"type":"Storage","dataCenter":"3","pod":"3","guid":"71773d35-5679-34fe-9b15-7e2736d0dd28-LibvirtComputingResource","name":"kvm02.oscloud.local","version":"4.9.0","resourceName":"LibvirtComputingResource","wait":0}}]
 }
2016-11-10 13:23:06,626 DEBUG [c.c.r.ResourceManagerImpl] 
(AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Dispatching resource 
state event CREATE_HOST_VO_FOR_CONNECTED to BareMetalDiscoverer
2016-11-10 13:23:06,626 DEBUG [c.c.r.ResourceManagerImpl] 
(AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Dispatching resource 
state event CREATE_HOST_VO_FOR_CONNECTED to NetscalerElement
2016-11-10 13:23:06,626 DEBUG [c.c.r.ResourceManagerImpl] 
(AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Dispatching resource 
state event CREATE_HOST_VO_FOR_CONNECTED to HypervServerDiscoverer
2016-11-10 13:23:06,626 DEBUG [c.c.r.ResourceManagerImpl] 
(AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Dispatching resource 
state event CREATE_HOST_VO_FOR_CONNECTED to BaremetalPxeManagerImpl
2016-11-10 13:23:06,626 DEBUG [c.c.r.ResourceManagerImpl] 
(AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Dispatching resource 

[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15655167#comment-15655167
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


i upload the management-server.log

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log, management-server.zip
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Wei Zhou (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654860#comment-15654860
 ] 

Wei Zhou commented on CLOUDSTACK-9590:
--

no.

Can you paste the management logs just before 2016-11-10 13:23:06 ?


> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654266#comment-15654266
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


ip upload the agent.log

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654195#comment-15654195
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


i dont see anything like an error. you?

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: agent.log, cloudstack-startup.log
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Wei Zhou (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654132#comment-15654132
 ] 

Wei Zhou commented on CLOUDSTACK-9590:
--

any error in agent.log near 2016-11-10 13:23:06 ?

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: cloudstack-startup.log
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Sven Vogel (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654097#comment-15654097
 ] 

Sven Vogel commented on CLOUDSTACK-9590:


Hi Wei,

thanks for answer.

when you look the startup it looks good. the agent starts and host are very 
long in alert mode.

what could be the problem?

thanks

Sven

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
> Attachments: cloudstack-startup.log
>
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CLOUDSTACK-9590) KVM + CentOS 7.2 + Agent in Alert State for long time

2016-11-10 Thread Wei Zhou (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15654040#comment-15654040
 ] 

Wei Zhou commented on CLOUDSTACK-9590:
--

any error in /var/log/cloudstack/agent/agent.log ?

> KVM + CentOS 7.2 + Agent in Alert State for long time
> -
>
> Key: CLOUDSTACK-9590
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9590
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: cloudstack-agent
>Affects Versions: 4.9.0
> Environment: entOS Linux release 7.2.1511 (Core)
> cloudstack-agent-4.9.0-1.el7.centos.x86_64
>Reporter: Sven Vogel
>
> Hi,
> When i add a new host to cloudstack management server it take some time to 
> get host out from alert state.
> 1. i add the host and host add not possible
> 2. values are correct set to agent.properties, restart cloustack agent
> 3. agent says connected to server
> 4. management server says "alert"
> management-server.log
> 2016-11-10 13:23:06,783 DEBUG [c.c.h.Status] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Transition:[Resource 
> state = Enabled, Agent event = AgentDisconnected, Host
> id = 51, name = kvm02.oscloud.local]
> 2016-11-10 13:23:06,798 DEBUG [c.c.a.m.ClusteredAgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Notifying other nodes 
> of to disconnect
> 2016-11-10 13:23:06,806 DEBUG [c.c.a.m.AgentManagerImpl] 
> (AgentConnectTaskPool-49:ctx-c3b72839) (logid:5a86e1fb) Failed to handle host 
> connection: com.cloud.exception.Connection
> Exception: Unable to get an answer to the CheckNetworkCommand from agent: 51
> is there any way to speed up the alert state? is it normal that it take so 
> long?
> thanks
> Sven



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)