search for: glusterd

Hi again, I'm having trouble testing the add-brick feature. I'm using a replicate 2 setup with currently 2 nodes in and am trying to add 2 more. The command blocks for a bit until i get an "Add Brick unsuccessful" message. According to etc-glusterfs-glusterd.vol.log below i can't seem to find anything : [2011-04-20 12:55:06.944593] I [glusterd-handler.c:1050:glusterd_handle_add_brick] glusterd: Received add brick req [2011-04-20 12:55:06.944725] I [glusterd-utils.c:2140:glusterd_friend_find_by_hostname] glusterd: Friend bebr0lbr6 found.. state: 3...

...4baff5cf-6e81-4b2e-b31f-be725b2da4b3 State: Peer Rejected (Connected) The node where I'm probing from complains about not able to find information on elkpinfglt07 but then it's found anyway and checksums on data0 volume aren't the same: [2017-11-30 20:12:24.278996] I [MSGID: 106487] [glusterd-handler.c:1241:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req elkpinfglt07 24007 [2017-11-30 20:12:24.279999] I [MSGID: 106129] [glusterd-handler.c:3670:glusterd_probe_begin] 0-glusterd: Unable to find peerinfo for host: elkpinfglt07 (24007) [2017-11-30 20:12:24.281020] I [rpc-clnt...

...biter or Replica 3 to avoid this. See: https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Split%20brain%20and%20ways%20to%20deal%20with%20it/. Do you still want to continue? (y/n) y volume create: myvol1: failed: Host pri.ostechnix.lan is not in 'Peer in Cluster' state node 1 glusterd.log is here root at pri:/var/log/glusterfs# cat glusterd.log [2018-02-06 13:28:37.638373] W [glusterfsd.c:1331:cleanup_and_exit] (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f0232faa6ba] -->/usr/sbin/glusterd(glusterfs_sigwaiter+0xe5) [0x55e17938a8c5] -->/usr/sbin/glusterd(clea...

...re on one of my volumes: gluster volume set date01 features.trash on I also limited the max file size to 500MB: gluster volume set data01 features.trash-max-filesize 500MB 3 hours after that I enabled this, this specific gluster volume went down: [2017-06-16 16:08:14.410905] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-management: quotad already stopped [2017-06-16 16:08:14.412027] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0-management: quotad service is stopped [2017-06-16 16:08:14.412217] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0-...

...nd 163.172.151.120 from? > 51.15.77.14 > So here itself you have 3 node cluster, after all this you are going > on node 2 and again peer probing 51.15.77.14. > ?Ideally it should work, with above steps, but due to some address > resolution volume create is getting failed, and from glusterd logs its > not clear. Given 163.172.151.120 is on a different subnet I'd guess routing issues. Can it be pinged from both the other nodes? -- Lindsay

...ee: https://gluster.readthedocs.io/en/latest/Administrator% > 20Guide/Split%20brain%20and%20ways%20to%20deal%20with%20it/. > Do you still want to continue? > (y/n) y > volume create: myvol1: failed: Host pri.ostechnix.lan is not in 'Peer in > Cluster' state > > node 1 glusterd.log is here > > root at pri:/var/log/glusterfs# cat glusterd.log > [2018-02-06 13:28:37.638373] W [glusterfsd.c:1331:cleanup_and_exit] > (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f0232faa6ba] > -->/usr/sbin/glusterd(glusterfs_sigwaiter+0xe5) [0x55e17938a8c5] > -...

...ed_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 gluster packages (glusterfs-3.12.6-1.el7.x86_64) than the others (glusterfs-3.12.5-2.el7.x86_64). The guide told me to create /var/lib/glusterd/glusterd.info with the UUID from the old host. Then I copied /var/lib/glusterd/peers/<uuid> files from the two other hosts to the new (except the uuid file from the old host). I created all the brick directories as present on the other machines. Empty of course. And I set the volume-id extend...

...> State: Peer Rejected (Connected) > > The node where I'm probing from complains about not able to find > information on elkpinfglt07 but then it's found anyway and checksums > on data0 volume aren't the same: > > [2017-11-30 20:12:24.278996] I [MSGID: 106487] > [glusterd-handler.c:1241:__glusterd_handle_cli_probe] 0-glusterd: > Received CLI probe req elkpinfglt07 24007 > [2017-11-30 20:12:24.279999] I [MSGID: 106129] > [glusterd-handler.c:3670:glusterd_probe_begin] 0-glusterd: Unable to > find peerinfo for host: elkpinfglt07 (24007) > [2017-11-30 20:...

Hi,we have use glusterfs for two years. After upgraded to 3.2.5,we discover that when one of replicate node reboot and startup the glusterd daemon,the gluster will crash cause by the other replicate node cpu usage reach 100%. Our gluster info: Type: Distributed-Replicate Status: Started Number of Bricks: 5 x 2 = 10 Transport-type: tcp Options Reconfigured: performance.cache-size: 3GB performance.cache-max-file-size: 512KB network.fr...

...misspelled the volume name. Is it data01 or date01? > I also limited the max file size to 500MB: > gluster volume set data01 features.trash-max-filesize 500MB > 3 hours after that I enabled this, this specific gluster volume went down: > [2017-06-16 16:08:14.410905] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:glusterd_proc_stop] 0- > management: quotad already stopped > [2017-06-16 16:08:14.412027] I [MSGID: 106568] [glusterd-svc-mgmt.c:228:glusterd_svc_stop] 0- > management: quotad service is stopped > [2017-06-16 16:08:14.412217] I [MSGID: 106132] [glusterd-proc-mgmt.c:83:gl...

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 complete reinstall...

...See: > https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Split%20brain%20and%20ways%20to%20deal%20with%20it/. > Do you still want to continue? > (y/n) y > volume create: myvol1: failed: Host pri.ostechnix.lan is not in 'Peer in > Cluster' state > > node 1 glusterd.log is here > > root at pri:/var/log/glusterfs# cat glusterd.log > [2018-02-06 13:28:37.638373] W [glusterfsd.c:1331:cleanup_and_exit] > (-->/lib/x86_64-linux-gnu/libpthread.so.0(+0x76ba) [0x7f0232faa6ba] > -->/usr/sbin/glusterd(glusterfs_sigwaiter+0xe5) [0x55e17938a8c5] > -...

...ge, sometimes while executing a simple command like "gluster volume status vm-images-repo" as a response I got "Another transaction is in progress for vm-images-repo. Please try again after sometime.". This situation does not get solved simply waiting for but I've to restart glusterd on the node that hold (and does not release) the lock, this situation occur randomly after some days. In the meanwhile, prior and after the issue appear, everything is working as expected. I'm using gluster 3.8.12 on CentOS 7.3, the only relevant information that I found on the log file (etc-g...

...ed_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 gluster packages (glusterfs-3.12.6-1.el7.x86_64) than the others (glusterfs-3.12.5-2.el7.x86_64). The guide told me to create /var/lib/glusterd/glusterd.info with the UUID from the old node. Then I copied /var/lib/glusterd/peers/<uuid> files from the two other nodes to the new (except the uuid file from the old host). I created all the brick directories as present on the other machines. Empty of course. And I set the volume-id extend...

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 wo...

...de:/glusterfs/sde1enc/brick Status: Connected Number of entries: 0 Brick gluster3.linova.de:/glusterfs/sde1enc/brick Status: Connected Number of entries: 0 root at gluster1:~# This are the warnings and errors I've found in the logs on our three servers... * Warnings on gluster1.linova.de: glusterd.log:[2023-05-31 23:56:00.032233 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x...

Hello, So I'm seeing a rejected peer with 3.12.6. This is with a replica 3 volume. It actually began as the same problem with a different peer. I noticed with (call it) gluster-2, when I couldn't make a new volume. I compared /var/lib/glusterd between them, and found that somehow the options in one of the vols differed. (I suspect this was due to attempting to create the volume via the Ovirt GUI; suffice to say I'm not using it for things like this in the future.) So I stopped the daemons and corrected that (gluster-2 had a tiering e...

...le command like "gluster volume > status vm-images-repo" as a response I got "Another transaction is > in progress for vm-images-repo. Please try again after sometime.". > This situation does not get solved simply waiting for but I've to > restart glusterd on the node that hold (and does not release) the > lock, this situation occur randomly after some days. In the > meanwhile, prior and after the issue appear, everything is working > as expected. > > I'm using gluster 3.8.12 on CentOS 7.3, the only relevant >...

I changed /etc/hosts 127.0.0.1 pri.ostechnix.lan pri 51.15.90.60 sec.ostechnix.lan sec 163.172.151.120 third.ostechnix.lan third on every node matching hostname to 127.0.0.1 then root at pri:~# apt-get purge glusterfs-server root at pri:~# rm -rf /var/lib/glusterd/ root at pri:~# rm -rf /var/log/glusterfs/ root at pri:~# apt-get install glusterfs-server root at pri:~# apt-mark hold glusterfs* root at pri:~# reboot now root at pri:~# gluster peer probe sec.ostechnix.lan peer probe: success. root at pri:~# gluster peer probe third.ostechnix.lan peer probe: suc...

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.co...