Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

single node error : Unable to associate brick with a peer in the cluster #26

Closed
gpavinteractiv opened this issue Feb 4, 2020 · 3 comments

Comments

@gpavinteractiv
Copy link

gpavinteractiv commented Feb 4, 2020

Hi, I have a single node gluster server, as setup by oVirt in single node hyperconverged mode.
When running gstatus 0.66, I get :

~]# gstatus --all
 
Unable to associate brick server.fqdn:/gluster_bricks/engine/engine with a peer in the cluster, possibly dueto name lookup failures. If the nodes are not registered (fwd & rev)to dns, add local entries for your cluster nodes in the the /etc/hosts file

No such error on a 3 node cluster

@aravindavk
Copy link
Member

Please provide the output of hostname, gluster pool list and gluster volume info

@gpavinteractiv
Copy link
Author

~]# hostname 
server.fqdn

 ~]# gluster pool list
UUID					Hostname 	State
fe5c10f2-2599-44b1-8763-c382f6710fb2	localhost	Connected 

~]# gluster volume info
 
Volume Name: engine
Type: Distribute
Volume ID: f1ffcff6-ea3e-403b-8b47-7c4e134eb8d9
Status: Started
Snapshot Count: 0
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: server.fqdn:/gluster_bricks/engine/engine
Options Reconfigured:
performance.low-prio-threads: 32
storage.owner-gid: 36
performance.read-ahead: off
user.cifs: off
storage.owner-uid: 36
performance.io-cache: off
performance.quick-read: off
network.ping-timeout: 30
features.shard: on
network.remote-dio: off
cluster.eager-lock: enable
performance.strict-o-direct: on
transport.address-family: inet
nfs.disable: on
 
Volume Name: vmstore
Type: Distribute
Volume ID: 20752e3b-0587-46a0-8d42-66d1c81cb5d7
Status: Started
Snapshot Count: 0
Number of Bricks: 1
Transport-type: tcp
Bricks:
Brick1: server.fqdn:/gluster_bricks/vmstore/vmstore
Options Reconfigured:
performance.low-prio-threads: 32
storage.owner-gid: 36
performance.read-ahead: off
user.cifs: off
storage.owner-uid: 36
performance.io-cache: off
performance.quick-read: off
network.ping-timeout: 30
features.shard: on
network.remote-dio: off
cluster.eager-lock: enable
performance.strict-o-direct: on
transport.address-family: inet
nfs.disable: on

@sac
Copy link
Member

sac commented Aug 12, 2020

Please try: https://github.com/gluster/gstatus/releases/download/v1.0.0/gstatus let us know if it fixes the issue.

@sac sac closed this as completed Aug 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants