Rohit Yadav created CLOUDSTACK-7291:
---------------------------------------
Summary: LXC: Mgmt server/agent keeps killing systemvms
Key: CLOUDSTACK-7291
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7291
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.3.0, 4.3.1
Reporter: Rohit Yadav
Assignee: Kishan Kavala
Fix For: 4.3.1
Followed installation and setup docs of 4.3, was unable to get LXC to work on
Ubuntu 14.04/trusty. The systemvms kept coming up and result from ssvm_check.sh
was good and it was able to reach mgmt server /host, even then mgmt server
complained that it was unable to contact agent on the systemvm (ping), while
the agent would gracefully shutdown the systemvm (by killing them).
Relevant log:
2014-08-07 19:52:26,294 INFO [c.c.u.e.CSExceptionErrorCode]
(secstorage-1:ctx-fc57ef43) Could not find exception:
com.cloud.exception.OperationTimedoutException in error code list for exceptions
2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl]
(consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host
Host[-1-Routing]
2014-08-07 19:52:26,295 DEBUG [c.c.a.m.AgentAttache]
(consoleproxy-1:ctx-e123fa9c) Seq 1-51249205: Cancelling.
2014-08-07 19:52:26,295 DEBUG [c.c.v.VirtualMachineManagerImpl]
(consoleproxy-1:ctx-e123fa9c) Unable to send the start command to host
Host[-1-Routing]
2014-08-07 19:52:26,303 DEBUG [c.c.h.Status] (AgentTaskPool-13:ctx-0b35e679)
Transition:[Resource state = Enabled, Agent event = ShutdownRequested, Host id
= 1, name = bluebox1.bhaisaab.org]
2014-08-07 19:52:26,311 DEBUG [c.c.h.HighAvailabilityManagerImpl]
(secstorage-1:ctx-fc57ef43) Scheduled HAWork[12-CheckStop-2-Starting-Scheduled]
2014-08-07 19:52:26,314 WARN [c.c.s.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-fc57ef43) Exception while trying to start secondary storage vm
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is
unreachable: Host 1: Unable to start s-2-VM
>---at
>com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:1051)
>---at
>com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:761)
>---at
>com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:745)
>---at
>com.cloud.storage.secondary.SecondaryStorageManagerImpl.startSecStorageVm(SecondaryStorageManagerImpl.java:261)
>---at
>com.cloud.storage.secondary.SecondaryStorageManagerImpl.allocCapacity(SecondaryStorageManagerImpl.java:694)
>---at
>com.cloud.storage.secondary.SecondaryStorageManagerImpl.expandPool(SecondaryStorageManagerImpl.java:1278)
>---at
>com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:123)
>---at
>com.cloud.secstorage.PremiumSecondaryStorageManagerImpl.scanPool(PremiumSecondaryStorageManagerImpl.java:50)
>---at com.cloud.vm.SystemVmLoadScanner.loadScan(SystemVmLoadScanner.java:111)
>
...
...
...
Caused by: com.cloud.exception.OperationTimedoutException: Commands 51249206 to
Host 1 timed out after 3600
>---at com.cloud.agent.manager.AgentAttache.send(AgentAttache.java:439)
>
>---at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:394)
>
>---at com.cloud.agent.manager.AgentManagerImpl.send(AgentManagerImpl.java:920)
>
>---at
>com.cloud.vm.VirtualMachineManagerImpl.orchestrateStart(VirtualMachineManagerImpl.java:989)
>---... 24 more
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
