search for: glus

On 13/09/17 20:47, Ben Werthmann wrote: > These symptoms appear to be the same as I've recorded in > this post: > > http://lists.gluster.org/pipermail/gluster-users/2017-September/032435.html > > On Wed, Sep 13, 2017 at 7:01 AM, Atin Mukherjee > <atin.mukherjee83 at gmail.com > <mailto:atin.mukherjee83 at gmail.com>> wrote: > > Additionally the brick log file of the same brick > would be...

On 13/09/17 06:21, Gaurav Yadav wrote: > Please provide the output of gluster volume info, gluster > volume status and gluster peer status. > > Apart? from above info, please provide glusterd logs, > cmd_history.log. > > Thanks > Gaurav > > On Tue, Sep 12, 2017 at 2:22 PM, lejeczek > <peljasz at yahoo.co.uk <mailto:peljasz at yahoo.c...

Additionally the brick log file of the same brick would be required. Please look for if brick process went down or crashed. Doing a volume start force should resolve the issue. On Wed, 13 Sep 2017 at 16:28, Gaurav Yadav <gyadav at redhat.com> wrote: > Please send me the logs as well i.e glusterd.logs and cmd_history.log. > > > On Wed, Sep 13, 2017 at 1:45 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > >> >> >> On 13/09/17 06:21, Gaurav Yadav wrote: >> > Please provide the output of gluster volume info, gluster volume status >>> and...

These symptoms appear to be the same as I've recorded in this post: http://lists.gluster.org/pipermail/gluster-users/2017-September/032435.html On Wed, Sep 13, 2017 at 7:01 AM, Atin Mukherjee <atin.mukherjee83 at gmail.com> wrote: > Additionally the brick log file of the same brick would be required. > Please look for if brick process went down or crashed. Doing a volu...

Please send me the logs as well i.e glusterd.logs and cmd_history.log. On Wed, Sep 13, 2017 at 1:45 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > > > On 13/09/17 06:21, Gaurav Yadav wrote: > >> Please provide the output of gluster volume info, gluster volume status >> and gluster peer status. >> &gt...

1) one peer, out of four, got separated from the network, from the rest of the cluster. 2) that unavailable(while it was unavailable) peer got detached with "gluster peer detach" command which succeeded, so now cluster comprise of three peers 3) Self-heal daemon (for some reason) does not start(with an attempt to restart glusted) on the peer which probed that fourth peer. 4) fourth unavailable peer is still up & running but is inaccessible to ot...

...statstics heal-count command work? On Mon, Sep 4, 2017 at 7:24 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > 1) one peer, out of four, got separated from the network, from the rest of > the cluster. > 2) that unavailable(while it was unavailable) peer got detached with > "gluster peer detach" command which succeeded, so now cluster comprise of > three peers > 3) Self-heal daemon (for some reason) does not start(with an attempt to > restart glusted) on the peer which probed that fourth peer. > 4) fourth unavailable peer is still up & running but is in...

...o get it work with a free daemon like nut, but are there some hints using it? In my ups.conf I tried: [apc001] driver = apcsmart port = auto desc = "Smart APC" And I get broadcast messages when I connect/disconnect the device like: Broadcast Message from root at glus (somewhere) at 14:24 ... Communications restored with UPS glustersv001 (glustersv001 is the machine I connect it to) Thank you for support, Gregor -- --

This means shd client is not able to establish the connection with the brick on port 49155. Now this could happen if glusterd has ended up providing a stale port back which is not what brick is listening to. If you had killed any brick process using sigkill signal instead of sigterm this is expected as portmap_signout is not received by glusterd in the former case and the old portmap entry is never wiped off. Please...

how critical is above? I get plenty of these on all three peers. hi guys I've recently upgraded from 3.8 to 3.10 and I'm seeing weird behavior. I see: $gluster vol status $_vol detail; takes long timeand mostly times out. I do: $ gluster vol heal $_vol info and I see: Brick 10.5.6.32:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER-CYTO-DATA Status: Transport endpoint is not connected Number of entries: - Brick 10.5.6.49:/__.aLocalStorages/0/0-GLUSTERs/0GL...

Please provide the output of gluster volume info, gluster volume status and gluster peer status. Apart from above info, please provide glusterd logs, cmd_history.log. Thanks Gaurav On Tue, Sep 12, 2017 at 2:22 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > hi everyone > > I have 3-peer cluster with all vols in...

hi everyone I have 3-peer cluster with all vols in replica mode, 9 vols. What I see, unfortunately, is one brick fails in one vol, when it happens it's always the same vol on the same brick. Command: gluster vol status $vol - would show brick not online. Restarting glusterd with systemclt does not help, only system reboot seem to help, until it happens, next time. How to troubleshoot this weird misbehaviour? many thanks, L. .

Please provide the output of gluster volume info, gluster volume status and gluster peer status. On Mon, Sep 4, 2017 at 4:07 PM, lejeczek <peljasz at yahoo.co.uk> wrote: > hi all > > this: > $ vol heal $_vol info > outputs ok and exit code is 0 > But if I want to see statistics: > $ gluster vol heal $_v...

for all three nodes:=0A= =0A= Brick1: gluster-0-0:/mseas-data-0-0=0A= Brick2: gluster-0-1:/mseas-data-0-1=0A= Brick3: gluster-data:/data=0A= =0A= =0A= Which node are you trying to mount to /data? If it is not the=0A= gluster-data node, then it will fail if there is not a /data directory.=0A= In this case, it is a good thing, since mounting...

hi all this: $ vol heal $_vol info outputs ok and exit code is 0 But if I want to see statistics: $ gluster vol heal $_vol statistics Gathering crawl statistics on volume GROUP-WORK has been unsuccessful on bricks that are down. Please check if all brick processes are running. I suspect - gluster inability to cope with a situation where one peer(which is not even a brick for a single vol on the c...

...o get it work with a free daemon like nut, but are there some hints using it? In my ups.conf I tried: [apc001] driver = apcsmart port = auto desc = "Smart APC" And I get broadcast messages when I connect/disconnect the device like: Broadcast Message from root at glus (somewhere) at 14:24 ... Communications restored with UPS glustersv001 (glustersv001 is the machine I connect it to) Thank you for support, Gregor --

...onnects over the serial port, so under Linux, you would need to pass something like "port = /dev/ttyS0". To connect over USB, change to "driver = usbhid-ups". > > And I get broadcast messages when I connect/disconnect the device like: > Broadcast Message from root at glus > (somewhere) at 14:24 ... > > Communications restored with UPS glustersv001 Not sure I understand what you did here. Are you disconnecting the USB or AC connection? Also, apcsmart shouldn't have connected at all with "por...

Hi All, I'm having an issue with connecting Gluster with NFS. When I do gluster volume status. It shows the ports aren't opened. NFS Server on localhost N/A N/A N N/A the /var/log/glusterfs/etc-glusterfs-glusterd.vol.log file states this: [2017-07-10 15:48:25.214618] I [MSGID: 106006] [glusterd-svc-mgmt...

Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I went ahead and created a new share in the samba server which is on a local filesystem where the OS is installed, not part of gluster: # mount | grep home ]# ls -ld /home drwxr-xr-x. 14 root root 4096 Jun 2 17:21 /home This...

On 03-Jun-2017 3:27 AM, "Diego Remolina" <dijuremo at gmail.com> wrote: Hi everyone, Is there anything else we could do to check on this problem and try to fix it? The issue is definitively related to either the samba vfs gluster plugin or gluster itself. I am not sure how to pin it down futher. I don't think it is vfs plugin because you haven't updated samba packages and vfs plugin is same as before. It is either gfapi in Gluster or one of the lower xlators. Changing to fuse based shares might make the probl...