Node is unable to mount a GFS or GFS2 file systems after a fence or reboot with the error "node not a member of the default fence domain" in RHEL 4, 5, or 6

Issue

• When the GFS filesystem is mounted on any cluster node, running mount -a produces the following messages in /var/log/messages:

/sbin/mount.gfs: node not a member of the default fence domain  
/sbin/mount.gfs: error mounting lockproto lock_dlm

/sbin/mount.gfs: can't connect to gfs_controld: Connection refused  
/sbin/mount.gfs: can't connect to gfs_controld: Connection refused  
/sbin/mount.gfs: gfs_controld not running  
/sbin/mount.gfs: error mounting lockproto lock_dlm

• The GFS filesystem will not mount automatically when booting the system, and produces an error when attempting to mount it manually.