Ok, the saga of the hung console proxy VM continues, and I really need
to get this cleaned up. After a hard reboot and having to force the
hypervisor online via the database, my consol proxy VM is still hung in
migrating state, so CS essentially ignores it:
2013-01-16 23:03:38,763 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-492:null) Seq 3-1375993858: Executing request
2013-01-16 23:03:39,155 WARN [xen.resource.CitrixResourceBase]
(DirectAgent-492:null) The VM is now missing marking it as Stopped v-11-VM
2013-01-16 23:03:39,155 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-492:null) Seq 3-1375993858: Response Received:
2013-01-16 23:03:39,155 DEBUG [agent.transport.Request]
(DirectAgent-492:null) Seq 3-1375993858: Processing: { Ans: , MgmtId:
130577622632, via: 3, Ver: v1, Flags: 10,
[{"ClusterSyncAnswer":{"_clusterId":1,"_newStates":{"v-11-VM":{"t":"4bafdf37-d0e7-4652-90dd-afa6f9099598","u":"Stopped"}},"_isExecuted":false,"result":true,"wait":0}}]
}
2013-01-16 23:03:39,160 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-492:null) VM v-11-VM: cs state = Migrating and realState =
Stopped
2013-01-16 23:03:39,160 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-492:null) VM v-11-VM: cs state = Migrating and realState =
Stopped
2013-01-16 23:03:39,160 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-492:null) Skipping vm in migrating state:
VM[ConsoleProxy|v-11-VM]
2013-01-16 23:03:44,793 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) Ping from 13
How do I get this VM back online, and do any developers need anything to
try and dtermine what is wrong? The status of system VMs and hosts is
VERY fragile in CS, and there seems to be little error recovery in
place. CS shoudl not just ignore a VM in a migrating state. I have a
migratewait setting of 3600 seconds, but this VM has been in this state
> 24 hours, after multiple management restarts.
--
Regards,
Nik
Nik Martin
nfina Technologies, Inc.
+1.251.243.0043 x1003
http://nfinausa.com
Relentless Reliability
