Re: Two-node cluster GFS2 confusing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I reproduced my cluster problem again and got this error from /var/log/message

So, I think the reason is fencing wrongly configured. And I may have to focus on Configure Fencing Device.

Here is my log:

Jun 17 22:32:36 server2 fenced[6559]: fenced 3.0.12.1 started
Jun 17 22:32:36 server2 dlm_controld[6573]: dlm_controld 3.0.12.1 started
Jun 17 22:32:37 server2 gfs_controld[6634]: gfs_controld 3.0.12.1 started
Jun 17 22:33:29 server2 fenced[6559]: fencing node server1
Jun 17 22:33:29 server2 fenced[6559]: fence server1 dev 0.0 agent none result: error config agent
Jun 17 22:33:29 server2 fenced[6559]: fence server1 failed
Jun 17 22:33:32 server2 fenced[6559]: fencing node server1
Jun 17 22:33:32 server2 fenced[6559]: fence server1 dev 0.0 agent none result: error config agent
Jun 17 22:33:32 server2 fenced[6559]: fence server1 failed
Jun 17 22:33:35 server2 fenced[6559]: fencing node server1
Jun 17 22:33:35 server2 fenced[6559]: fence server1 dev 0.0 agent none result: error config agent
Jun 17 22:33:35 server2 fenced[6559]: fence server1 failed

-----Original Message-----
From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Bob Peterson
Sent: Tuesday, June 17, 2014 7:09 PM
To: linux clustering
Subject: Re:  Two-node cluster GFS2 confusing

----- Original Message -----
> Hi, here is my dmesg after failed:
> 
> GFS2: fsid=: Trying to join cluster "lock_dlm", "mycluster:web"
> dlm: Using TCP for communications
> GFS2: fsid=mycluster:web.0: Joined cluster. Now mounting FS...
> GFS2: fsid=mycluster:web.0: jid=0, already locked for use
> GFS2: fsid=mycluster:web.0: jid=0: Looking at journal...
> GFS2: fsid=mycluster:web.0: jid=0: Acquiring the transaction lock...
> GFS2: fsid=mycluster:web.0: jid=0: Replaying journal...
> GFS2: fsid=mycluster:web.0: jid=0: Replayed 1 of 1 blocks
> GFS2: fsid=mycluster:web.0: jid=0: Found 0 revoke tags
> GFS2: fsid=mycluster:web.0: jid=0: Journal replayed in 1s
> GFS2: fsid=mycluster:web.0: jid=0: Done
> GFS2: fsid=mycluster:web.0: jid=1: Trying to acquire journal lock...
> GFS2: fsid=mycluster:web.0: jid=1: Looking at journal...
> GFS2: fsid=mycluster:web.0: jid=1: Done
> hrtimer: interrupt took 4149483 ns
> dlm: closing connection to node 2
> dlm: closing connection to node 1
> GFS2: fsid=: Trying to join cluster "lock_dlm", "mycluster:web"
> dlm: Using TCP for communications
> 

Hi,

If there was a GFS2 problem, you would ordinarily see errors there, and these messages are all pretty normal.

Regards,

Bob Peterson
Red Hat File Systems

--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster




[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux