[PVE-User] Problems with Proxmox 2.0 HA

[Gusek, Michael]

I'll kill it via ipmi. But I think I found the problem:

fence_ipmilan -a xxxx -p xxxx -l xxx -M onoff  -v
Rebooting machine @ IPMI:xxxx...Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power off'...
Spawning: '/usr/bin/ipmitool -I lan -H 'xxxx' -U 'XXXX' -P '[set]' -v chassis power status'...
ipmilan: Power still on
Failed

The server turns itself off  too late.  The problems seems to be with too<http://www.dict.cc/englisch-deutsch/too.html> narrowly<http://www.dict.cc/englisch-deutsch/narrowly.html> considered<http://www.dict.cc/englisch-deutsch/considered.html> timeouts, so I'm going to investigate this thoroughly. If I have the right numbers, there can I define them in cluster.conf ?

Michael


Von: José Román Bilbao [mailto:jrbcast at gmail.com]
Gesendet: Dienstag, 21. Februar 2012 12:28
An: Gusek, Michael
Cc: pve-user at pve.proxmox.com
Betreff: Re: [PVE-User] Problems with Proxmox 2.0 HA

Hi,

How did you "kill" your first machine?. Take into account that the power coord must be properly pluged in order to enable fencing. If no response is obtained from the fencing mechanism (i.e. it is powered-off), the alive machine won't try/allow to restart the dead VM to prevent simultaneous running.

Hope this helps.

Jose.
El 21 de febrero de 2012 12:15, Gusek, Michael <Michael.Gusek at vanguard-healthcare.com<mailto:Michael.Gusek at vanguard-healthcare.com>> escribió:
Hi,

after creating my cluster of two nodes, I've added a VM to HA. The VM is hosted on the first Node. After killing this node the HA-managed VM isn't restarted on the second node. Offline migration to Node 2 isn't possible (Can't connect to ip_of_node_1:8006 (connect: No route to host)). I think it's not functional at the moment ?

Next, if I shutting down first Node with HA-enabled VM, the VM will also shutdown, better is to migrate to an available cluster member.

Regards,

Michael

michael.gusek at vanguard-healthcare.com<mailto:michael.gusek at vanguard-healthcare.com>
T  +49 (0)30 80 484 - 116<tel:%2B49%20%280%2930%2080%20484%20-%20116>
F  +49 (0)30 80 484 - 335<tel:%2B49%20%280%2930%2080%20484%20-%20335>
M  +49 (0)151 180 50 - 362<tel:%2B49%20%280%29151%20180%2050%20-%20362>

VANGUARD AG
Friedrichstraße 78, 10117 Berlin, Deutschland
www.vanguard-healthcare.com<http://www.vanguard-healthcare.com>

Sitz/Registergericht: Berlin/AG Charlottenburg, HRB 80368 B
Vorstand: Dr. Ralf Berscheid, Dr. Kordt Griepenkerl
Vorsitzender des Aufsichtsrates: Herr Marcus Bracklo

Hinweis: Diese Nachricht enthält vertrauliche Informationen. Diese sind ausdrücklich nur für den/die Empfänger/in dieser Nachricht bestimmt. Sollten Sie nicht der beabsichtigte Empfänger sein, so nehmen Sie bitte zur Kenntnis, dass jede Weiterleitung, jede Kopie oder die Verwendung der in dieser Nachricht enthaltenen Informationen untersagt ist. Sollten Sie diese Nachricht fälschlicherweise erhalten haben, löschen Sie bitte diese Nachricht und sämtliche Kopien bzw. Ausdrucke. Vielen Dank!

Confidentiality Notice: This mail contains information which is confidential and may also be privileged. It is for exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this mail or the contained information is strictly prohibited. If you have received this mail in error, please delete this email and any copies of it. Thank you!


_______________________________________________
pve-user mailing list
pve-user at pve.proxmox.com<mailto:pve-user at pve.proxmox.com>
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20120222/255e98fe/attachment.htm>