namirda
commented
1 year ago I have exactly the same problem - Glusterfs 10.3, Debian 12, ARM
Open redhyper9 opened 1 year ago
namirda
commented
1 year ago I have exactly the same problem - Glusterfs 10.3, Debian 12, ARM
namirda
commented
1 year ago In my case, the problem was that on one node in the cluster there were some old files remaining from previous glusterfs version. That node was not even in my trusted pool!
To fix, I had to delete all gluster volumes and then
sudo systemctl stop glusterd - on ALL nodes in the cluster, even those not in the peer group sudo rm -rf /var/lib/glusterd - on ALL nodes in the cluster, even those not in the peer group sudo systemctl start glusterd - on ALL nodes in the cluster, even those not in the peer group
Then build your trusted pool and create the volume.
@redhyper9 - hope that helps
NathanEid
commented
8 months ago i have the same problem: volume create: volumes: failed: Host manager is not in 'Peer in Cluster' state i tried some solution but it dosn't work GlusterFS version 10.5 running on Ubuntu 18.04.3 LTS how can i solve this problem? @redhyper9 @namirda @manveru @dev-zero
cs35-owncloud
commented
8 months ago Hello,
I had that kind of problem on Debian 12 aswell. To fix it, you have to peer the first node from one of the other nodes:
root@node2 # gluster peer probe node1Then you will be able to create your volume. It seems that when you probe all the others nodes from the first node, the first node will be added but with the "wrong" hostname.
Hope this helps, it took me a while to figure this out :exploding_head: Cheers.
EDIT: some doc
aravindavk
commented
8 months ago [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 Looking at the logs, Gluster is failing to understand de-fra-01 is the local address in de-fra-01 and similarly in de-fra-02. Update the /etc/hosts like below and try again.
Server 1:
127.0.0.1 de-fra-01
<server2PublicIP> de-fra-02Server 2:
<server1PublicIP> de-fra-01
127.0.0.1 de-fra-02
thebigbone
commented
1 week ago For some reason, the host names in /etc/hosts are not properly mapped with the IPs. Just specifying the server IP (instead of host names) solved that issue for me.
Description of problem: I'm getting
Host <host> is not in 'Peer in Cluster' statewhen attempting to create a gluster volume.The exact command to reproduce the issue:
gluster volume create myvolume de-fra-01:/mnt/storage de-fra-02:/mnt/storageThe full output of the command that failed:
volume create: myvolume: failed: Host de-fra-02 is not in 'Peer in Cluster' stateExpected results: I expected the volume to successfully create.
Mandatory info: - The output of the
gluster volume infocommand:No volumes present- The output of the
gluster volume statuscommand:No volumes present- The output of the
gluster volume healcommand:Usage: volume heal <VOLNAME> [enable | disable | full |statistics [heal-count [replica <HOSTNAME:BRICKNAME>]] |info [summary | split-brain] |split-brain {bigger-file <FILE> | latest-mtime <FILE> |source-brick <HOSTNAME:BRICKNAME> [<FILE>]} |granular-entry-heal {enable | disable}]**- Provide logs present on following locations of client and server nodes -
Server 1:
/var/log/glusterfs/cli.log:
/var/log/glusterfs/cmd_history.log
/var/log/glusterfs/glusterd.log:
Server 2:
/var/log/glusterfs/cli.log
/var/log/glusterfs/cmd_history.log
/var/log/glusterfs/glusterd.log
**- Is there any crash ? Provide the backtrace and coredump No.
Additional info:
The servers have no firewall activated, all ports are open.
I have the following in
/etc/hostson both servers:Output of
gluster peer statuson Server 1:Output of
gluster peer statuson Server 2:- The operating system / glusterfs version: GlusterFS version 10.3 running on Debian 12 ARM, installed from main Debian 12 repo.