similar to: Error after removing/reinstall gluster

hi, i noticed that this repo for glusterfs 3.13 does not exists anymore at: http://mirror.centos.org/centos/7/storage/x86_64/ i knew was not going to be long term supported however the downgrade to 3.12 breaks the server node i believe the issue is with: *[2018-05-15 08:54:39.981101] E [MSGID: 101019] [xlator.c:503:xlator_init] 0-management: Initialization of volume 'management'

Hi, Unable to do peer probe... and unable to figure out whats the reason from the gluster log. can someone help ? 1) This is what i was trying... gluster> peer probe llm19.in.ibm.com Probe unsuccessful Probe returned with unknown errno 107 gluster> peer probe 9.124.111.25 Probe unsuccessful Probe returned with unknown errno 107 gluster> peer status Number of Peers: 1 Hostname:

You can still get them from https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.13/ (I don't know how much longer they'll be there. I suggest you copy them if you think you're going to need them in the future.) n 05/15/2018 04:58 AM, Davide Obbi wrote: > hi, > > i noticed that this repo for glusterfs 3.13 does not exists anymore at: > >

Thanks Kaleb, any chance i can make the node working after the downgrade? thanks On Tue, May 15, 2018 at 2:02 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > You can still get them from > https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.13/ > > (I don't know how much longer they'll be there. I suggest you copy them > if you think

On 05/15/2018 08:08 AM, Davide Obbi wrote: > Thanks Kaleb, > > any chance i can make the node working after the downgrade? > thanks Without knowing what doesn't work, I'll go out on a limb and guess that it's an op-version problem. Shut down your 3.13 nodes, change their op-version to one of the valid 3.12 op-versions (e.g. 31203) and restart. Then the 3.12 nodes should

Hi Team, I noticed that glusterd is never starting when i reboot my Redhat 7.1 server. Service is enabled but don't works. I tested with gluster 3.10.4 & gluster 3.10.5 and the problem still exists. When i started the service manually this works. I'va also tested on Redhat 6.6 server and gluster 3.10.4 and this works fine. The problem seems to be related to Redhat 7.1 This is

Hello everyone, So this is my first email here. Recently I have downloaded glusterfs-3.1 and tried to install it on my four servers. I did not have any problems with the installation, but the configuration is a little bit unclear to me. I would like to ask you, if perhaps you had the same problems as I encountered and if yes, then how did you resolve your problem ? My configuration : 5 servers

You're hitting a race here. By the time glusterd tries to resolve the address of one of the remote bricks of a particular volume, the n/w interface is not up by that time. We have fixed this issue in mainline and 3.12 branch through the following commit: commit 1477fa442a733d7b1a5ea74884cac8f29fbe7e6a Author: Gaurav Yadav <gyadav at redhat.com> Date: Tue Jul 18 16:23:18 2017 +0530

On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > You're hitting a race here. By the time glusterd tries to resolve the > address of one of the remote bricks of a particular volume, the n/w > interface is not up by that time. We have fixed this issue in mainline and > 3.12 branch through the following commit: > Correction. This patch is

Hi all, I have downloaded and installed the following: [root at compute-0-0 ~]# rpm -qa | grep gluster glusterfs-rdma-3.3beta2-1 glusterfs-fuse-3.3beta2-1 glusterfs-core-3.3beta2-1 I have also compiled all those from source but they didn't work either. The problem I'm having is that when I start glusterd I get the following and I'm not sure how to fix it: [2012-01-26

On Fri, Aug 18, 2017 at 1:38 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > > > On Fri, Aug 18, 2017 at 12:22 PM, Atin Mukherjee <amukherj at redhat.com> > wrote: >> >> You're hitting a race here. By the time glusterd tries to resolve the >> address of one of the remote bricks of a particular volume, the n/w >> interface is not up by that

Hello, I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is the correct way to upgrade from 3.10.5 to 3.10.6. It's hard to find upgrade guides for a minor release. Can you help me please ? Thanks in advance Ismael ________________________________ De : Atin Mukherjee <amukherj at redhat.com> Envoy? : dimanche 17 septembre 2017 14:56 ? : ismael

On Wed, Oct 04, 2017 at 09:44:44AM +0000, ismael mondiu wrote: > Hello, > > I'd like to test if 3.10.6 version fixes the problem . I'm wondering which is the correct way to upgrade from 3.10.5 to 3.10.6. > > It's hard to find upgrade guides for a minor release. Can you help me please ? Packages for GlusterFS 3.10.6 are available in the testing repository of the

Thanks Niels, We want to install it on redhat 7. We work on a secured environment with no internet access. We download the packages here https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.10/ and then, we push the package to the server and install them via rpm command . Do you think this is a correct way to upgrade gluster when working without internet access? Thanks in advance

Hello , it seems the problem still persists on 3.10.6. I have a 1 x (2 + 1) = 3 configuration. I upgraded the first server and then launched a reboot. Gluster is not starting. Seems that gluster starts before network layer. Some logs here: Thanks [2017-10-04 15:33:00.506396] I [MSGID: 106143] [glusterd-pmap.c:277:pmap_registry_bind] 0-pmap: adding brick /opt/glusterfs/advdemo on port

Could you share the following information: 1. gluster --version 2. output of gluster volume status 3. glusterd log and all brick log files from the node where bricks didn't come up. On Wed, Mar 21, 2018 at 12:35 PM, Richard Neuboeck <hawk at tbi.univie.ac.at> wrote: > Hi all, > > our systems have suffered a host failure in a replica three setup. > The host needed a

Hi all, our systems have suffered a host failure in a replica three setup. The host needed a complete reinstall. I followed the RH guide to 'replace a host with the same hostname' (https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3/html/administration_guide/sect-replacing_hosts). The machine has the same OS (CentOS 7). The new machine got a minor version number newer

On Wed, Oct 04, 2017 at 12:17:23PM +0000, ismael mondiu wrote: > > Thanks Niels, > > We want to install it on redhat 7. We work on a secured environment > with no internet access. > > We download the packages here > https://buildlogs.centos.org/centos/7/storage/x86_64/gluster-3.10/ and > then, we push the package to the server and install them via rpm > command .

Hello Atin, Please find below the requested informations: [root at dvihcasc0r ~]# cat /var/lib/glusterd/vols/advdemo/bricks/* hostname=dvihcasc0r path=/opt/glusterfs/advdemo real_path=/opt/glusterfs/advdemo listen-port=49152 rdma.listen-port=0 decommissioned=0 brick-id=advdemo-client-0 mount_dir=/advdemo snap-status=0 hostname=dvihcasc0s path=/opt/glusterfs/advdemo

Hi, Below please find the reserved ports and log, thanks. sysctl net.ipv4.ip_local_reserved_ports: net.ipv4.ip_local_reserved_ports = 30000-32767 glusterd.log: [2017-06-18 07:04:17.853162] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007 [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr]