similar to: glusterfs 3.13 repo unavailable and downgrade to 3.12.9 fails

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

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

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

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

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

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 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 , 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

The backport just got merged few minutes back and this fix should be available in next update of 3.10. On Fri, Sep 15, 2017 at 2:08 PM, ismael mondiu <mondiu at hotmail.com> wrote: > Hello Team, > > Do you know when the backport to 3.10 will be available ? > > Thanks > > > > > ------------------------------ > *De :* Atin Mukherjee <amukherj at

On Fri, Aug 18, 2017 at 12:22:33PM +0530, Atin Mukherjee 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: We still maintain 3.10 for at least 6 months. It

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

On Wed, Oct 4, 2017 at 9:26 PM, ismael mondiu <mondiu at hotmail.com> wrote: > 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 >

So I have the root cause. Basically as part of the patch we write the brickinfo->uuid in to the brickinfo file only when there is a change in the volume. As per the brickinfo files you shared the uuid was not saved as there is no new change in the volume and hence the uuid was always NULL in the resolve brick because of which glusterd went for local address resolution. Having this done with a

Are you shure about possibility to resolve all node names on all other nodes? You need to use names used previously in Gluster - check their by ?gluster peer status? or ?gluster pool list?. Regards, Bartosz > Wiadomo?? napisana przez Ludwig Gamache <ludwig at elementai.com> w dniu 24.10.2017, o godz. 03:13: > > All, > > I am trying to add a third peer to my gluster

All, I am trying to add a third peer to my gluster install. The first 2 nodes are running since many months and have gluster 3.10.3-1. I recently installed the 3rd node and gluster 3.10.6-1. I was able to start the gluster daemon on it. After, I tried to add the peer from one of the 2 previous server (gluster peer probe IPADDRESS). That first peer started the communication with the 3rd peer. At

Hello list, I have an issue on my Gluster cluster. It is composed of two data nodes and an arbiter for all my volumes. After having upgraded my bricks to gluster 3.12.9 (Fedora 27), this is what I get : ??? - on node 1, volumes won't start, and glusterd.log shows a lot of : ??? ??? [2018-05-02 09:46:06.267817] W [glusterd-locks.c:843:glusterd_mgmt_v3_unlock]