Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

First installation. 3rd node will not finish deploy


jamesrleu
3 Posts
January 10, 2021, 8:28 pm

Hello,

I'm new to petasan, I'm trying my first install on a set of VMs.  During the 'join existing cluster' step for the 3rd node, the process never seems to finish.  I'm seeing what I perceive as errors in the gluster log, but I'm not sure.  Are there any kind souls willing to help out his newbie?  If so, what information should I provide to to be helpful?

Here is what I see in the gluster.log

 

[2021-01-10 20:15:07.429014] E [MSGID: 106451] [glusterd-utils.c:7368:glusterd_is_path_in_use] 0-management: /opt
/petasan/config/gfs-brick is already part of a volume [No data available]
[2021-01-10 20:15:07.429052] E [MSGID: 106301] [glusterd-syncop.c:1352:gd_stage_op_phase] 0-management: Staging o
f operation 'Volume Create' failed on localhost : /opt/petasan/config/gfs-brick is already part of a volume
[2021-01-10 20:15:12.557837] E [MSGID: 106525] [glusterd-op-sm.c:4347:glusterd_dict_set_volid] 0-management: Volu
me gfs-vol does not exist
[2021-01-10 20:15:12.557864] E [MSGID: 106117] [glusterd-mgmt.c:2189:glusterd_mgmt_v3_initiate_all_phases] 0-mana
gement: Failed to build payload for operation 'Volume Start'
The message "E [MSGID: 106451] [glusterd-utils.c:7368:glusterd_is_path_in_use] 0-management: /opt/petasan/config/
gfs-brick is already part of a volume [No data available]" repeated 3 times between [2021-01-10 20:15:07.429014]
and [2021-01-10 20:16:08.190239]

I would really appreciate any help someone can provide,

Thank you for your time,

James

#1

jamesrleu
3 Posts
January 10, 2021, 8:43 pm

Reading infor from another thread I think my issue is related to my networking
here is the route table on node3
192.168.200.0/24 dev eth0 proto kernel scope link src 192.168.200.103
192.168.200.0/24 dev eth1 proto kernel scope link src 192.168.200.203

 

I will retry will different subnets

#2

jamesrleu
3 Posts
January 10, 2021, 9:46 pm

Just for posterity.

Once I fixed my network allocations, joining node3 to the cluster finished after 15 minutes.

#3