Gluster users - Dec 2015 - removing peers manually

I seem to have a peer that I cannot detach, network seems fine,  I assume I
dont have to bare metal rebuild it to clean it up?

=========[root at ipa1 salt]#  salt 'glusterp3.graywitch.co.nz' cmd.run
"gluster peer
status"

glusterp3.graywitch.co.nz:
    Number of Peers: 1

    Hostname: glusterp1.graywitch.co.nz
    Uuid: 4ece8509-033e-48d1-809f-2079345caea2
    State: Accepted peer request (Connected)
[root at ipa1 salt]#  salt 'glusterp2.graywitch.co.nz' cmd.run
"gluster peer
detach glusterp3.graywitch.co.nz"

glusterp2.graywitch.co.nz:
    peer detach: failed: One of the peers is probably down. Check with
'peer status'
ERROR: Minions returned with non-zero exit code
[root at ipa1 salt]#  salt 'glusterp2.graywitch.co.nz' cmd.run
"ping -c 2
glusterp3.graywitch.co.nz"

glusterp2.graywitch.co.nz:
    PING glusterp3.graywitch.co.nz (192.168.1.33) 56(84) bytes of data.
    64 bytes from glusterp3.graywitch.co.nz (192.168.1.33): icmp_seq=1
ttl=63 time=0.441 ms
    64 bytes from glusterp3.graywitch.co.nz (192.168.1.33): icmp_seq=2
ttl=63 time=0.415 ms

    --- glusterp3.graywitch.co.nz ping statistics ---
    2 packets transmitted, 2 received, 0% packet loss, time 1001ms
    rtt min/avg/max/mdev = 0.415/0.428/0.441/0.013 ms
[root at ipa1 salt]#

=============
How can I clean up glusterp2???
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151214/afe92eda/attachment.html>

On 12/14/2015 07:45 AM, Thing wrote:
> I seem to have a peer that I cannot detach, network seems fine,  I
> assume I dont have to bare metal rebuild it to clean it up?
> 
> =========> [root at ipa1 salt]#  salt 'glusterp3.graywitch.co.nz
> <http://glusterp3.graywitch.co.nz>' cmd.run "gluster peer
status"
> 
> glusterp3.graywitch.co.nz <http://glusterp3.graywitch.co.nz>:
>     Number of Peers: 1
> 
>     Hostname: glusterp1.graywitch.co.nz
<http://glusterp1.graywitch.co.nz>
>     Uuid: 4ece8509-033e-48d1-809f-2079345caea2
>     State: Accepted peer request (Connected)
> [root at ipa1 salt]#  salt 'glusterp2.graywitch.co.nz
> <http://glusterp2.graywitch.co.nz>' cmd.run "gluster peer
detach
> glusterp3.graywitch.co.nz <http://glusterp3.graywitch.co.nz>"
> 
> glusterp2.graywitch.co.nz <http://glusterp2.graywitch.co.nz>:
>     peer detach: failed: One of the peers is probably down. Check with
> 'peer status'
This indicates that one of the other node(s) are also down in the
cluster. If glusterp2 doesn't host any bricks you can safely detach it
with 'gluster peer detach glusterp2 force'
> ERROR: Minions returned with non-zero exit code
> [root at ipa1 salt]#  salt 'glusterp2.graywitch.co.nz
> <http://glusterp2.graywitch.co.nz>' cmd.run "ping -c 2
> glusterp3.graywitch.co.nz <http://glusterp3.graywitch.co.nz>"
> 
> glusterp2.graywitch.co.nz <http://glusterp2.graywitch.co.nz>:
>     PING glusterp3.graywitch.co.nz <http://glusterp3.graywitch.co.nz>
> (192.168.1.33) 56(84) bytes of data.
>     64 bytes from glusterp3.graywitch.co.nz
> <http://glusterp3.graywitch.co.nz> (192.168.1.33): icmp_seq=1 ttl=63
> time=0.441 ms
>     64 bytes from glusterp3.graywitch.co.nz
> <http://glusterp3.graywitch.co.nz> (192.168.1.33): icmp_seq=2 ttl=63
> time=0.415 ms
> 
>     --- glusterp3.graywitch.co.nz <http://glusterp3.graywitch.co.nz>
> ping statistics ---
>     2 packets transmitted, 2 received, 0% packet loss, time 1001ms
>     rtt min/avg/max/mdev = 0.415/0.428/0.441/0.013 ms
> [root at ipa1 salt]#
> 
> =============> 
> How can I clean up glusterp2???
> 
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
>