Yes it seems likely you have a duplicate conflicting gluster configuration. Fixing it should be fairly easy: clear out /var/lib/glusterd, and then reinstall the glusterfs packages. You will also have to clear all the extended attributes and files from any brick directories, it may be easier to reformat the file system if they are on separate bock devices. I assume the system has a different host name? You should then be able to peer probe the new server from one of the cluster members.
On 29 September 2015 at 01:00, Sreejith K B <sreejith@xxxxxxxxxxxx> wrote:
sreejith.regards,Hi all,While i am trying to add a new brick in to an existing cluster it fails, our servers are on linode, i think the problem occurs because, we created new server by copying/cloning an existing server that already part of that cluster in to a new server space. So i think the already existing gluster configuration causes this issue, i need to find-out a solution for this situation. please confirm the error reason and a working solution.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
