similar to: error "Not able to add to index" in brick logs

Yes indeed it is probably what's going on. what filesystem are you using and what are the mount options? ? Original Message ? From: lists at bago.org Sent: November 22, 2017 4:26 PM To: gluster-users at gluster.org Subject: [Gluster-users] error "Not able to add to index" in brick logs in my /var/log/gluster/bricks/mybrick-path.log I get thousands of those errors: ------

Hi all, i had a replica 2 gluster 3.12 between S1 and S2 (1 brick per node) geo-replicated to S5 where both S1 and S2 were visible in the geo-replication status and S2 "active" while S1 "passive". I had to replace S1 with S3, so I did an "add-brick replica 3 S3" and then "remove-brick replica 2 S1". Now I have again a replica 2 gluster between S3 and S2

Hi, When S3 is added to master volume from new node, the following cmd should be run to generate and distribute ssh keys 1. Generate ssh keys from new node #gluster system:: execute gsec_create 2. Push those ssh keys of new node to slave #gluster vol geo-rep <mastervol> <slavehost>::<slavevol> create push-pem force 3. Stop and start geo-rep But note that

Recently we updated a Gluster replicated setup from 3.6 to 3.12 (stepping through 3.8 first before going to 3.12). Afterwards I noticed the brick logs were filling at an alarming rate on the server we have the NFS service running from: $ sudo tail -20 /var/log/glusterfs/bricks/export-gluster-shared.log [2018-05-23 06:22:12.405240] I [MSGID: 139001] [posix-acl.c:269:posix_acl_log_permit_denied]

I have a setup with 3 nodes running GlusterFS. gluster volume create myBrick replica 3 node01:/mnt/data/myBrick node02:/mnt/data/myBrick node03:/mnt/data/myBrick Unfortunately node1 seemed to stop syncing with the other nodes, but this was undetected for weeks! When I noticed it, I did a "service glusterd restart" on node1, hoping the three nodes would sync again. But this did not

Clients using W2k Sp2 are randomly no longer connecting to my Samba PDC server running 2.2.5 so i thought to upgrading to 2.2.6 but the problem still remains. What can be appened? Just a few days ago all was running very very fine!! THE ERROR IS: THE DOMAIN IS NOT DISPOSABLE AT THE MOMENT! =============================================================== I only have activated Bind9 and DHCP but I

Hello, I have the same problems outlined in this old thread... Only difference the original poster was on RHEL6.X, I am on RHEL7, he compiled samba on its own, I used Sernet Samba (latest)... Unfortunately there is no solution on this thread. Suggestions? Thank you

Il 22/06/2017 15:30, Rowland Penny via samba ha scritto: > On Thu, 22 Jun 2017 14:47:36 +0200 > Marco Coli via samba <samba at lists.samba.org> wrote: > >> Hello, >> >> I have the same problems outlined in this old thread... >> Only difference the original poster was on RHEL6.X, I am on RHEL7, he >> compiled samba on its own, I used Sernet Samba

Hi to everyone, Something quite strange occured to me this weekend as we wanted to switch our network to w2k ads structure with a sambaserver as main fileserver running winbind. The windowsprofiles are supposed to reside on the sambaserver and the client successfully loads the initial profile. The first time the user logs on to his machine, he gets some default .msi-softwarepackages assigned by

Please see inline comments. On Fri, 23 Jun 2017 07:09:47 +0200 Marco Coli <marco.coli at isolettaelba.eu> wrote: > cat /etc/resolv.conf > # Generated by NetworkManager > search niccolai.local > nameserver 10.0.0.253 Only thing wrong there is that you may be using the '.local' domain (unless it is has been changed to hide the real domain). If it is the real domain,

I am getting the following build break on changeset 13662. I am compiling on x86_64 SLES10 with gcc 4.1.0. Is there a fix for this? Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA make[1]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware'' make[2]: Entering directory `/root/xen/xen-unstable.hg/tools/firmware/rombios'' gcc -o biossums

Hi, It seems that master user login does not work with the 'pass=yes' option as recommended and documented. I defined a master user passdb as documented. In addition, I have a passdb sql. If 'pass=yes' is defined then it seems that dovecot recognizes the master login, verifies the master password but then attempts to verify the ***master*** password again with the ***user***

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp