- Who we are
- What we know
- What we've created
- Hints and Kinks
- Checking Corosync cluster membership
- Configuring radosgw to behave like Amazon S3
- Downgrading to DRBD 8.3
- Fencing in Libvirt/KVM virtualized cluster nodes
- Fencing in VMware virtualized Pacemaker nodes
- GFS2 in Pacemaker (Debian/Ubuntu)
- Interleaving in Pacemaker clones
- Maintenance in active Pacemaker clusters
- Managing cron jobs with Pacemaker
- Mandatory and advisory ordering in Pacemaker
- Migrating virtual machines from block-based storage to RADOS/Ceph
- Network connectivity check in Pacemaker
- OCFS2 in Pacemaker (Debian/Ubuntu)
- Solid-state drives and Ceph OSD journals
- Solve a DRBD split-brain in 4 steps
- Testing Pacemaker clusters
- Totem "Retransmit List" in Corosync
- Turning Ceph RBD Images into SAN Storage Devices
- Which OSD stores a specific RADOS object?
- Presentations
- Ceph Tutorial (LCA 2013)
- Ceph: The Storage Stack for OpenStack (OpenStack Israel 2013)
- Die eigene Cloud mit OpenStack Essex (German, LinuxTag 2012)
- Fencing (LCE 2011)
- GlusterFS in HA Clusters (LCEU 2012)
- GlusterFS und Ceph (German, CeBIT 2012)
- Hands-On With Ceph (LCEU 2012)
- High Availability Update (OpenStack Summit Fall 2012)
- High Availability in OpenStack (CloudOpen 2012)
- High Availability in OpenStack (OpenStack Conference Spring 2012)
- Highly Available Cloud: Pacemaker integration with OpenStack (OSCON 2012)
- Mit OpenStack zur eigenen Cloud (German, CLT 2012)
- Mit OpenStack zur eigenen Cloud (German, OSDC 2012)
- More Reliable, More Resilient, More Redundant (OpenStack Summit April 2013)
- MySQL HA Deep Dive (MySQL Conference 2012)
- MySQL High Availability Deep Dive (PLUK 2012)
- MySQL High Availability Sprint (PLUK 2011)
- OpenStack Essex im Praxistest (German, Linuxwochen Wien 2012)
- OpenStack High Availability Update (Grizzly and Havana)
- Roll Your Own Cloud (LCA 2011)
- Storage Replication in HPHA (LCA 2012)
- Zen of Pacemaker (LCA 2012)
- hastexo in 100 Seconds
- Technical documentation
- News releases
- Hints and Kinks
- What we do
- What we charge
- What others say

About our blogs
All hastexo blog posts represent the opinion of the post's author, and do not necessarily reflect hastexo's corporate policy or point of view.
The Debian logo is Copyright (c) 1999 Software in the Public Interest
More Blog Posts
cluster-glue in Squeeze backports updated
Submitted by martin on Mon, 2012-03-12 11:34
I'm happy to announce that cluster-glue 1.0.9+hg2665-1~bpo60+1 is available in the backports repository for Debian GNU/Linux 6.0 ("Squeeze"). I uploaded the backport-version right after the package got migrated from unstable to testing last night.
This version of cluster-glue fixes a nasty bug in the IPMI STONITH resource agent, so everybody is highly advised to update to this version to make sure that STONITH via IPMI works as expected.
- martin's blog
- Login or register to post comments

Comments
I have installed this package
I have installed this package on three different clusters and i am experiencing major problems while using standard commands e.g. "crm configure verify" or "crm configure edit".
The problem seems to be related to this thread:
http://www.gossamer-threads.com/lists/linuxha/dev/68372#68372
Testing output: http://pastebin.com/qDKA80gK
libglib2.0
Can you give us your exact libglib2.0 package version please?
libglib2.0-0 Version
My currently installed libglib2.0-0 version is: 2.24.2-1. Thank you for the immediate package update! I'll try the new version and give you some feedback if things are working as expected.
cluster-glue_1.0.9+hg2665-1~bpo60+2
It appears that a necessary fix to libglib2 wasn't pushed from Ubuntu to the Debian maintainer. Please keep your eyes peeled for
cluster-glue_1.0.9+hg2665-1~bpo60+2which should hit thesqueeze-backportsarchive within the next few hours, which disables the lrmd upstart plugin and should thus fix your issue.cluster-glue_1.0.9+hg2665-1~bpo60+2 is fine
The package cluster-glue_1.0.9+hg2665-1~bpo60+2 is now working as expected. Thanks to the hastexo team and their immediate response to this issue :-)