gluster / glusterdocs

This repo contains the source of official Gluster documentation rendered at https://docs.gluster.org
MIT License
353 stars 279 forks source link

Host is not in 'Peer in Cluster' state #780

Closed redhyper9 closed 1 year ago

redhyper9 commented 1 year ago

I have GlusterFS installed on two Debian 12 VMs, installed the glusterfs-server package from the main Debian 12 repo. GlusterFS version is 10.3 as reported by glusterfs --version. The servers have no firewall activated, all ports are open.

I have the following in /etc/hosts on both servers:

<server1PublicIP>   de-fra-01
<server2PublicIP>   de-fra-02

I have peered the two servers: Server 1:

root@de-fra-01:~# gluster peer status
Number of Peers: 1

Hostname: de-fra-02
Uuid: 0a43f531-dff3-42a8-a7b0-aba584cb1245
State: Peer in Cluster (Connected)

Server 2:

root@de-fra-02:~# gluster peer status
Number of Peers: 1

Hostname: de-fra-01
Uuid: 08eae420-3aef-4604-9f45-4c518739706a
State: Peer in Cluster (Connected)

Whenever I try to create a volume, I get the following depending on the server: Server 1:

root@de-fra-01:~# gluster volume create myvolume de-fra-01:/mnt/storage de-fra-02:/mnt/storage
volume create: myvolume: failed: Host de-fra-01 is not in 'Peer in Cluster' state

Server 2:

root@de-fra-02:~# gluster volume create myvolume de-fra-01:/mnt/storage de-fra-02:/mnt/storage
volume create: myvolume: failed: Host de-fra-02 is not in 'Peer in Cluster' state

Relevant logs from Server 1, /var/log/glusterfs/glusterfs.log:

[2023-07-03 20:13:09.002901 +0000] E [MSGID: 106301] [glusterd-syncop.c:1328:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host de-fra-01 is not in 'Peer in Cluster' state 
[2023-07-03 20:12:53.707244 +0000] E [MSGID: 106408] [glusterd-peer-utils.c:214:glusterd_peerinfo_find_by_hostname] 0-management: error in getaddrinfo: Name or service not known
 [Unknown error -2]
[2023-07-03 20:15:12.140502 +0000] I [MSGID: 106487] [glusterd-handler.c:1388:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req 
[2023-07-03 20:15:39.887680 +0000] E [MSGID: 106429] [glusterd-utils.c:1306:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname de-fra-01 to uuid 
[2023-07-03 20:15:39.887706 +0000] E [MSGID: 106301] [glusterd-syncop.c:1328:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host de-fra-01 is not in 'Peer in Cluster' state 
[2023-07-03 20:18:27.579440 +0000] E [MSGID: 106429] [glusterd-utils.c:1306:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname de-fra-01 to uuid 
[2023-07-03 20:18:27.579469 +0000] E [MSGID: 106301] [glusterd-syncop.c:1328:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host de-fra-01 is not in 'Peer in Cluster' state

Relevant logs from Server 2, /var/log/glusterfs/glusterfs.log:

The message "E [MSGID: 106429] [glusterd-utils.c:1306:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname de-fra-02 to uuid" repeated 2 times between [2023-07-03 20:08:51.855923 +0000] and [2023-07-03 20:09:28.872057 +0000]
The message "E [MSGID: 106301] [glusterd-syncop.c:1328:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host de-fra-02 is not in 'Peer in Cluster' state" repeated 2 times between [2023-07-03 20:08:51.855948 +0000] and [2023-07-03 20:09:28.872060 +0000]
The message "I [MSGID: 106487] [glusterd-handler.c:1388:__glusterd_handle_cli_list_friends] 0-glusterd: Received cli list req" repeated 2 times between [2023-07-03 20:08:54.362086 +0000] and [2023-07-03 20:10:15.658696 +0000]
[2023-07-03 20:18:49.879953 +0000] E [MSGID: 106429] [glusterd-utils.c:1306:glusterd_brickinfo_new_from_brick] 0-management: Failed to convert hostname de-fra-02 to uuid 
[2023-07-03 20:18:49.879980 +0000] E [MSGID: 106301] [glusterd-syncop.c:1328:gd_stage_op_phase] 0-management: Staging of operation 'Volume Create' failed on localhost : Host de-fra-02 is not in 'Peer in Cluster' state 

What could cause the issue? I've searched for hours to no avail. I really hope someone can shed some light and fix this issue, maybe I'm doing something wrong?

Thanks in advance to everyone.

redhyper9 commented 1 year ago

Oops, opened issue in wrong repository, sorry!