Re: [ClusterLabs] Antw: Alert notes

On 06/24/2016 09:16 AM, Ulrich Windl wrote: Ferenc Wágner schrieb am 15.06.2016 um 18:11 in Nachricht > <87vb1a5t4k@lant.ki.iif.hu>: >> Hi, >> > [...] >> The SNMP agent seems to have a problem with hrSystemDate, which should >> be an OCTETSTR with strict format, not some

[ClusterLabs] Antw: restarting pacemakerd

>>> Ferenc Wágner schrieb am 18.06.2016 um 12:15 in Nachricht <8760t66bwn@lant.ki.iif.hu>: > Hi, > > Could somebody please elaborate a little why the pacemaker systemd > service file contains "Restart=on-failure"? I mean that a failed node > gets fenced anyway, so most of the

Re: [ClusterLabs] DLM standalone without crm ?

Yes, technically. I've not played with it stand-alone, and I believe it will still need corosync for internode communication and membership. Also, if a node fails and can't be fenced, I believe it will block. Others here might be able to speak more authoritatively than I. madi On 24/06/16 11:34

[ClusterLabs] Antw: Alert notes

>>> Ferenc Wágner schrieb am 15.06.2016 um 18:11 in Nachricht <87vb1a5t4k@lant.ki.iif.hu>: > Hi, > [...] > The SNMP agent seems to have a problem with hrSystemDate, which should > be an OCTETSTR with strict format, not some plain textual timestamp. ??? snmptranslate -M+.

Re: [ClusterLabs] Cluster reboot fro maintenance

Maintenance worked perfectly: - cluster in maintenance: crm configure property maintenance-mode=true - update vm os etc - stop corosync/pacemaker - reboot - start corosync/pacemaker - cluster out of maintenance: crm configure property maintenance-mode=false - all resources went up ok Best

[ClusterLabs] Pacemaker and Corosync versions compatibility

Hello, I've been following a tutorial to set up a simple HA cluster using Pacemaker and Corosync on CentOS 6.x while I have noticed that in the original documentation it is stated that: "Since pcs has the ability to manage all aspects of the cluster (both corosync and pacemaker), it requires a