You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kal Torak (JIRA)" <ji...@apache.org> on 2014/06/10 00:49:02 UTC
[jira] [Commented] (CLOUDSTACK-5452) KVM - Agent is not able to
connect back if management server was restarted when there are pending
tasks to this host.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025877#comment-14025877 ]
Kal Torak commented on CLOUDSTACK-5452:
---------------------------------------
And if you restarted the agent and still doesn't work ?
I've restarted the agent, the management, the both hosts, disable iptables, running in circles and crying like a cow and STILL DOESN'T WORK,
Then my workaround was, drop the database, and restart the process then it works ( I should tell you was in front my teachers, in our test)
> KVM - Agent is not able to connect back if management server was restarted when there are pending tasks to this host.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5452
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5452
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Build from 4.3
> Reporter: Sangeetha Hariharan
> Assignee: edison su
> Priority: Critical
> Fix For: Future
>
>
> KVM - Agent is not able to connect back if management server was restarted when there are pending tasks to this host.
> Steps to reproduce the problem:
> Set up - Advanced zone with 2 KVM ( RHEL 6.3) hosts.
> Deployed few Vms.
> Started snapshot for ROOT volume of the VMs.
> When the snapshot processes are still in progress , restart management server.
> When the management sever started , the KVM hosts remain in disconnected state.
> Attempt to stop Vms /start Vms fails because of having no connection to the host.
> Following is seen in agent logs:
> 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:56:46,640 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:56:51,641 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:56:51,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:56:56,642 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:56:56,643 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:01,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:06,644 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:06,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:11,645 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:11,646 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:16,647 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:21,648 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:26,649 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:26,675 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:31,676 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:31,677 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> 2013-12-10 20:57:36,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Cannot connect because we still have 1 commands in progress.
> 2013-12-10 20:57:41,678 INFO [cloud.agent.Agent] (Agent-Handler-2:null) Lost connection to the server. Dealing with the remaining commands...
> :
--
This message was sent by Atlassian JIRA
(v6.2#6252)