[Bugs] [Bug 1451937] New: Cannot probe nodes on ubuntu 16.04 and not on centos 7.3
bugzilla at redhat.com
bugzilla at redhat.com
Wed May 17 23:23:40 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1451937
Bug ID: 1451937
Summary: Cannot probe nodes on ubuntu 16.04 and not on centos
7.3
Product: GlusterFS
Version: 3.10
Component: glusterd
Severity: urgent
Assignee: bugs at gluster.org
Reporter: alexei at virtuman.com
CC: bugs at gluster.org
Created attachment 1279831
--> https://bugzilla.redhat.com/attachment.cgi?id=1279831&action=edit
/var/lib/glusterd/cli.log
Description of problem:
Trying to setup glusterfs cluster on centos7.3 machines and a separate cluster
on ubuntu 16.04 and getting the same failure when trying to probe a node
Version-Release number of selected component (if applicable):
so far tried 3.7.*, 3.8.*, 3.10.*
How reproducible:
Trying to get new cluster(s) deployed but can't get it to work on CentOS 7 and
not on Ubuntu 16.04
Steps to Reproduce:
1. Install glusterfs-server using yum or apt repository
2. start "service glusterd restart" or "service glusterfs-server restart"
3. attempt to probe a peer with "gluster peer probe srv-eu1"
Actual results:
getting an immediate glusterfs server shut-down and this message in cli
"Connection failed. Please check if gluster daemon is operational."
file in /var/lib/glusterd/peers/* is create with the following content:
==============
> # cat /var/lib/glusterd/peers/srv-eu1
> uuid=00000000-0000-0000-0000-000000000000
> state=0
> hostname1=srv-eu1
==============
Unless file is deleted from this folder - service will not restart. After the
restart - if i try the same steps - it will continue to fail and will never
succeed in creating a cluster.
Expected results:
expected to see peer added to the cluster and the cluster start up.
Additional info:
All host nodes act as kubernetes nodes and have been configured using "kargo"
utility.
I already specified local hostname as 127.0.0.1 in /etc/hosts file. iptables is
fully open for communication between our hosts on all ports and telnet is able
to connect on port 24007 without any issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list