thr3ads.net - Gluster users - [Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state" [Mar 2016]

If this information is useful, please help other people find it:
Share via:

Joshua J. Kugler

2016-Mar-19 19:41 UTC

[Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state"

So, I'm trying to set up a new cluster.  I set up Host A, get gluster up and
running. That works. Then I set up Host B.
>From Host B, I run the peer probe, and the command and logs tell me that worked. I then try to run the 'volume create' command, I get the error

failed: Host 192.168.122.10 is not in 'Peer in Cluster' state

So...if the peer probe worked, why won't the volume create? What am I
missing?
This is from an ansible playbook that was working, but now it seems something 
broke. Maybe a change in a recent version?

The full log from Host B is below. Any pointers would be greatly appreciated. 
Until now, I've found setting up Gluster clusters really easy...this one has
be stumped. :)

CentOS 6
No iptables rules between hosts
Gluster 3.7.8-4
Packages from download.gluster.org

Thanks!

j

[2016-03-19 18:55:15.918243]  : peer probe 192.168.122.10 : SUCCESS    
[2016-03-19 18:55:16.057827]  : peer probe 192.168.122.11 : SUCCESS : Probe on 
localhost not needed
[2016-03-19 18:55:16.090987]  : volume create email replica 2 transport tcp 
192.168.122.10:/export/email/brick 192.168.122.11:/export/email/brick force : 
FAILED : Host 192.168.122.10 is not in 'Peer in Cluster' state
[2016-03-19 18:55:16.634652]  : peer probe 192.168.122.11 : SUCCESS : Probe on 
localhost not needed
[2016-03-19 18:55:16.681337]  : volume create list_archive replica 2 transport 
tcp 192.168.122.10:/export/list_archive/brick 
192.168.122.11:/export/list_archive/brick force : FAILED : Host 192.168.122.10 
is not in 'Peer in Cluster' state
[2016-03-19 19:26:55.805651]  : volume create list_archive replica 2 transport 
tcp 192.168.122.10:/export/list_archive/brick 
192.168.122.11:/export/list_archive/brick force : FAILED : Host 192.168.122.10 
is not in 'Peer in Cluster' state
[2016-03-19 19:27:28.260941]  : peer probe 192.168.122.10 : SUCCESS : Host 
192.168.122.10 port 24007 already in peer list
[2016-03-19 19:27:34.629895]  : volume create list_archive replica 2 transport 
tcp 192.168.122.10:/export/list_archive/brick 
192.168.122.11:/export/list_archive/brick force : FAILED : Host 192.168.122.10 
is not in 'Peer in Cluster' state
-- 
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua at azariah.com - Jabber: pedahzur at gmail.com
PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A

Atin Mukherjee

2016-Mar-20 09:04 UTC

head link

[Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state"

What does gluster peer status output say?

-Atin
Sent from one plus one
On 20-Mar-2016 1:16 pm, "Joshua J. Kugler" <joshua at
azariah.com> wrote:
> So, I'm trying to set up a new cluster.  I set up Host A, get gluster
up
> and
> running. That works. Then I set up Host B.
>
> From Host B, I run the peer probe, and the command and logs tell me that
> worked. I then try to run the 'volume create' command, I get the
error
>
> failed: Host 192.168.122.10 is not in 'Peer in Cluster' state
>
> So...if the peer probe worked, why won't the volume create? What am I
> missing?
> This is from an ansible playbook that was working, but now it seems
> something
> broke. Maybe a change in a recent version?
>
> The full log from Host B is below. Any pointers would be greatly
> appreciated.
> Until now, I've found setting up Gluster clusters really easy...this
one
> has
> be stumped. :)
>
> CentOS 6
> No iptables rules between hosts
> Gluster 3.7.8-4
> Packages from download.gluster.org
>
> Thanks!
>
> j
>
> [2016-03-19 18:55:15.918243]  : peer probe 192.168.122.10 : SUCCESS
> [2016-03-19 18:55:16.057827]  : peer probe 192.168.122.11 : SUCCESS :
> Probe on
> localhost not needed
> [2016-03-19 18:55:16.090987]  : volume create email replica 2 transport tcp
> 192.168.122.10:/export/email/brick 192.168.122.11:/export/email/brick
> force :
> FAILED : Host 192.168.122.10 is not in 'Peer in Cluster' state
> [2016-03-19 18:55:16.634652]  : peer probe 192.168.122.11 : SUCCESS :
> Probe on
> localhost not needed
> [2016-03-19 18:55:16.681337]  : volume create list_archive replica 2
> transport
> tcp 192.168.122.10:/export/list_archive/brick
> 192.168.122.11:/export/list_archive/brick force : FAILED : Host
> 192.168.122.10
> is not in 'Peer in Cluster' state
> [2016-03-19 19:26:55.805651]  : volume create list_archive replica 2
> transport
> tcp 192.168.122.10:/export/list_archive/brick
> 192.168.122.11:/export/list_archive/brick force : FAILED : Host
> 192.168.122.10
> is not in 'Peer in Cluster' state
> [2016-03-19 19:27:28.260941]  : peer probe 192.168.122.10 : SUCCESS : Host
> 192.168.122.10 port 24007 already in peer list
> [2016-03-19 19:27:34.629895]  : volume create list_archive replica 2
> transport
> tcp 192.168.122.10:/export/list_archive/brick
> 192.168.122.11:/export/list_archive/brick force : FAILED : Host
> 192.168.122.10
> is not in 'Peer in Cluster' state
> --
> Joshua J. Kugler - Fairbanks, Alaska
> Azariah Enterprises - Programming and Website Design
> joshua at azariah.com - Jabber: pedahzur at gmail.com
> PGP Key: http://pgp.mit.edu/  ID 0x73B13B6A
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160320/507e294f/attachment.html>

Gluster users - Mar 2016 - Peer probe succeeded, but "not in 'Peer in Cluster' state"

[Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state"

[Gluster-users] Peer probe succeeded, but "not in 'Peer in Cluster' state"