You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Tomasz Zięba <t....@gmail.com> on 2014/02/05 17:40:26 UTC
CloudStack stops the machine for no reason
Hello,
Today I've submitted this bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-6036
Could someone confirm the existence of the problems after the migration
from 3.0.2 to 4.2.1.
--
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/<http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/>
Fwd: CloudStack stops the machine for no reason
Posted by Tomasz Zięba <t....@gmail.com>.
if someone could help......
After the upgrade from version 3.0.2 to 4.2.1 appeared very strange error
associated with self-stopping machine after changing the offering.
Steps to reproduce:
1. Running instance of the machine
2. Stop with the operating system
3. Change offering of machine
4. Start the machine
5. Waiting for 10 minutes
6. CloudStack stops the machine for no reason
7. Restart the machine
8. Sometimes this situation repeats few times
In the logs you can find information:
2014-02-05 06:27:00,974 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-316:null) 11. The VM i-41-824-VM is in Running state
2014-02-05 06:27:00,974 DEBUG [agent.transport.Request]
(DirectAgent-316:null) Seq 50-1756626952: Processing: { Ans: , MgmtId:
160544475005497, via: 50, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":2,"_newStates":{"i-41-824-VM":{"t":"f32a4fee-b64e-4868-9c52-2a27e32d4c0e","u":"Running","v":"viridian:true;acpi:true;apic:true;pae:true;nx:false;timeoffset:0;cores-per-socket:4"}},"_isExecuted":false,"result":true,"wait":0}}]
}
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Sending { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-41-824-VM","wait":0}}]
}
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Executing: { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-41-824-VM","wait":0}}]
}
2014-02-05 06:36:01,383 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 9. The VM i-41-824-VM is in Stopping state
2014-02-05 06:36:27,625 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 10. The VM i-41-824-VM is in Stopped state
You will notice that the stop of the machine corresponds to the component
HA-Worker.
Such operation after the upgrade is complicating work of users.
---------- Forwarded message ----------
From: Tomasz Zięba <t....@gmail.com>
Date: 2014-02-05 17:40 GMT+01:00
Subject: CloudStack stops the machine for no reason
To: dev@cloudstack.apache.org, users@cloudstack.apache.org
Hello,
Today I've submitted this bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-6036
Could someone confirm the existence of the problems after the migration
from 3.0.2 to 4.2.1.
--
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/<http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/>
--
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/<http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/>
Fwd: CloudStack stops the machine for no reason
Posted by Tomasz Zięba <t....@gmail.com>.
if someone could help......
After the upgrade from version 3.0.2 to 4.2.1 appeared very strange error
associated with self-stopping machine after changing the offering.
Steps to reproduce:
1. Running instance of the machine
2. Stop with the operating system
3. Change offering of machine
4. Start the machine
5. Waiting for 10 minutes
6. CloudStack stops the machine for no reason
7. Restart the machine
8. Sometimes this situation repeats few times
In the logs you can find information:
2014-02-05 06:27:00,974 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-316:null) 11. The VM i-41-824-VM is in Running state
2014-02-05 06:27:00,974 DEBUG [agent.transport.Request]
(DirectAgent-316:null) Seq 50-1756626952: Processing: { Ans: , MgmtId:
160544475005497, via: 50, Ver: v1, Flags: 10,
[{"com.cloud.agent.api.ClusterSyncAnswer":{"_clusterId":2,"_newStates":{"i-41-824-VM":{"t":"f32a4fee-b64e-4868-9c52-2a27e32d4c0e","u":"Running","v":"viridian:true;acpi:true;apic:true;pae:true;nx:false;timeoffset:0;cores-per-socket:4"}},"_isExecuted":false,"result":true,"wait":0}}]
}
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:27:00,981 DEBUG [cloud.vm.VirtualMachineManagerImpl]
(DirectAgent-316:null) VM i-41-824-VM: cs state = Running and realState =
Running
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Sending { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-41-824-VM","wait":0}}]
}
2014-02-05 06:36:01,240 DEBUG [agent.transport.Request]
(HA-Worker-1:work-1511) Seq 51-1374970375: Executing: { Cmd , MgmtId:
160544475005497, via: 51, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":true,"vmName":"i-41-824-VM","wait":0}}]
}
2014-02-05 06:36:01,383 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 9. The VM i-41-824-VM is in Stopping state
2014-02-05 06:36:27,625 DEBUG [xen.resource.CitrixResourceBase]
(DirectAgent-150:null) 10. The VM i-41-824-VM is in Stopped state
You will notice that the stop of the machine corresponds to the component
HA-Worker.
Such operation after the upgrade is complicating work of users.
---------- Forwarded message ----------
From: Tomasz Zięba <t....@gmail.com>
Date: 2014-02-05 17:40 GMT+01:00
Subject: CloudStack stops the machine for no reason
To: dev@cloudstack.apache.org, users@cloudstack.apache.org
Hello,
Today I've submitted this bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-6036
Could someone confirm the existence of the problems after the migration
from 3.0.2 to 4.2.1.
--
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/<http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/>
--
Regards,
Tomasz Zięba
Twitter: @TZieba
LinkedIn: pl.linkedin.com/pub/tomasz-zięba-ph-d/3b/7a8/ab6/<http://pl.linkedin.com/pub/tomasz-zi%C4%99ba-ph-d/3b/7a8/ab6/>