[PVE-User] Proxmox VE 4.1 released!
Patrick Kaiser
pk at argonius.de
Wed Mar 30 14:59:26 CEST 2016
I am the only one who is facing this problem on iDRAC 8 BMC??
On 29 Mar 2016, at 20:40, Patrick Kaiser <pk at argonius.de> wrote:
> Hi all,
>
> i’ve also running a 3 node DELL server cluster like Albert.
>
> I have a ha enabled vm running on pve server 1.
>
> i receive also the following error in kernel ring buffer:
> kernel: [ 2838.041628] ipmi_si ipmi_si.0: Could not set the global enables: 0xcc.
>
>
> ever 2 seconds …. :/
>
>
> i completely followed https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x
> but it does not seem to work for me.
>
> any idea where to go next?
>
>
> additonal info:
>
> i am running 2 dell servers with iDRAC 8 enterprise and 1 dell server with iDRAC 6 enterprise.
>
> iDRAC6 server does not prints this error, iDRAC8 servers do :/
>
> so i am not the only one: https://forum.proxmox.com/threads/kernel-ipmi_si-ipmi_si-0-could-not-set-the-global-enables-0xcc.24920/
> known bug? https://sourceforge.net/p/openipmi/mailman/message/34383470/
>
>
>
>
>
> On 12 Dec 2015, at 07:43, Alexandre DERUMIER <aderumier at odiso.com> wrote:
>
>>>> 3x DELL R620 Servers, with full iDRAC
>>>> running current pve from the enterprise repository
>>
>> Do you have openmanage installed ?
>> if yes, please read :
>> https://pve.proxmox.com/wiki/High_Availability_Cluster_4.x
>>
>> I have wrote some notes , because by default openmanage change watchdog timeout and action.
>>
>> ----- Mail original -----
>> De: "Albert Dengg" <albert at fsfe.org>
>> À: "proxmoxve" <pve-user at pve.proxmox.com>
>> Envoyé: Vendredi 11 Décembre 2015 19:59:34
>> Objet: Re: [PVE-User] Proxmox VE 4.1 released!
>>
>> hi,
>> On Fri, Dec 11, 2015 at 12:24:16PM +0100, Martin Maurer wrote:
>>> Hi all,
>>>
>>> we are proud to announce the final release of our Proxmox VE 4.1!
>> :)
>>
>> i have a slight problem however and i'm wondering if anybody else
>> has this problem:
>> while i had fencing working fine using the iTCO watchdog in 4.0, in
>> 4.1 i cannot get pve to fence a node.
>>
>> my setup is the following:
>>
>> 3x DELL R620 Servers, with full iDRAC
>> running current pve from the enterprise repository
>>
>>
>> when i try to force a node to fence itself by setting all links to
>> down using this simple command
>> for i in $(seq 0 5); do ip l s eth$i down; done
>> to set all links to down, the node will not reboot itself even
>> though pvecm status correctly displays that quorum has been lost
>>
>> i have tried:
>> iTCO_wdt
>> ipmi_watchdog
>> both with and without nmi_watchdog=0
>>
>> the only differnece is that if i use ipmi_watchdog, i get a message
>> in the kernel ring buffer every 5 secondds like that:
>> Dec 11 18:59:29 pve2 kernel: [ 361.067004] ipmi_si ipmi_si.0: Could not set the global enables: 0xcc.
>>
>> fencing was working before (in fact it seems all nodes where fencing
>> themselves on the upgrade from 4.0 to 4.1...)
>>
>> does somebody have an idea whats going wrong here or to be more
>> exact, where to search next?
>>
>> thx
>>
>> regards,
>> albert
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> _______________________________________________
>> pve-user mailing list
>> pve-user at pve.proxmox.com
>> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
More information about the pve-user
mailing list