Replacing Failed Server Failing

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

 



Hi All (and Happy New Year),

We had to replace one of our Gluster Servers in our Trusted Pool this week (node1).

The new server is now built, with empty folders for the bricks, peered to the old Nodes (node2 & node3).

We basically followed this guide: https://docs.rackspace.com/docs/recover-from-a-failed-server-in-a-glusterfs-array

We are using the same/old IP address.

So when we try to do a `gluster volume sync node2 all` we get a `volume sync node2 all : FAILED : Staging failed on node2. Please check log file for details.`

The logs all *seem* to be complaining the there are no volumes on node1 - which makes sense (I think) because there *are* no volumes on node1.

If we try to create a volume on node1 the system complains that the volume already exists (on nodes 2& 3) - again, yes, this is correct.

So, what are we doing wrong?

Thanks in advance

Dulux-Oz

________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux