Re: CloudStack HA

2016-03-30 Thread Dag Sonstebo
Hi Martins, yes this is a typical example of host self fencing, where a host will reboot when losing connectivity to a primary storage pool. As you have already found this is controlled by the xenheartbeat.sh script. Dag Sonstebo Cloud Architect ShapeBlue On 30/03/2016, 10:04, "Mārtiņš

Re: CloudStack HA

2016-03-30 Thread Mārtiņš Jakubovičs
Looks like I found issue, it is /opt/cloud/bin/xenheartbeat.sh script which is running in all hosts. On 2016.03.30. 11:14, Mārtiņš Jakubovičs wrote: Hello, This morning I faced unexpected problem, one of XenServer hosts rebooted. I checked logs and it looks like due network issue, but

AW: CloudStack HA

2016-03-30 Thread S . Brüseke - proIO GmbH
- Von: Mārtiņš Jakubovičs [mailto:martins-li...@hostnet.lv] Gesendet: Mittwoch, 30. März 2016 10:14 An: users@cloudstack.apache.org Betreff: CloudStack HA Hello, This morning I faced unexpected problem, one of XenServer hosts rebooted. I checked logs and it looks like due network issue

CloudStack HA

2016-03-30 Thread Mārtiņš Jakubovičs
Hello, This morning I faced unexpected problem, one of XenServer hosts rebooted. I checked logs and it looks like due network issue, but question is why host rebooted it self? CloudStack's XS Pool is not HA enabled. And as I know, in ACS 4.3.2 CloudStack did not manage Host's HA or am I

CloudStack HA & One VM startup failure

2015-10-20 Thread giraffeg forestg
Hi all. My environment: CloudStack 4.3.0 (CentOS6) XenServer 6.2 SP1 1. One host failure. 2. VM is started on another host by CloudStack HA. (VM001,VM002,VM004,VM005) 3. VM003 only startup failure. I want to know the cause of VM003 did not start by CloudStack HA. Resources of the host