Displaying 20 results from an estimated 400 matches similar to: "glusterd service fails to start from AWS AMI"
2011 Dec 14
1
glusterfs crash when the one of replicate node restart
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
2011 Jul 08
1
Possible to bind to multiple addresses?
I am trying to run GlusterFS on only my internal interfaces. I have
setup two bricks and have a replicated volume that is started.
Everything works fine when I run with no transport.socket.bind-address
defined in the /etc/glusterfs/glusterd.vol file, but when I add it I get:
Transport endpoint is not connected
My configuration looks like this:
volume management
type mgmt/glusterd
2011 Jul 11
0
Instability when using RDMA transport
I've run into a problem with Gluster stability with the RDMA transport. Below is a description of the environment, a simple script that can replicate the problem, and log files from my test system.
I can work around the problem by using the TCP transport over IPoIB but would like some input onto what may be making the RDMA transport fail in this case.
=====
Symptoms
=====
- Error from test
2017 May 09
1
Empty info file preventing glusterd from starting
Hi Atin/Team,
We are using gluster-3.7.6 with setup of two brick and while restart of
system I have seen that the glusterd daemon is getting failed from start.
At the time of analyzing the logs from etc-glusterfs.......log file I have
received the below logs
[2017-05-06 03:33:39.798087] I [MSGID: 100030] [glusterfsd.c:2348:main]
0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version
2013 Oct 07
1
glusterd service fails to start on one peer
I'm hoping that someone here can point me the right direction to help me
solve a problem I am having.
I've got 3 gluster peers and for some reason glusterd sill not start on one
of them. All are running glusterfs version 3.4.0-8.el6 on Centos 6.4
(2.6.32-358.el6.x86_64).
In /var/log/glusterfs/etc-glusterfs-glusterd.vol.log I see this error
repeated 36 times (alternating between brick-0
2017 Aug 21
0
Glusterd not working with systemd in redhat 7
On Mon, Aug 21, 2017 at 2:49 AM, Cesar da Silva <thunderlight1 at gmail.com>
wrote:
> Hi!
> I am having same issue but I am running Ubuntu v16.04.
> It does not mount during boot, but works if I mount it manually. I am
> running the Gluster-server on the same machines (3 machines)
> Here is the /tc/fstab file
>
> /dev/sdb1 /data/gluster ext4 defaults 0 0
>
>
2017 Aug 20
2
Glusterd not working with systemd in redhat 7
Hi!
I am having same issue but I am running Ubuntu v16.04.
It does not mount during boot, but works if I mount it manually. I am
running the Gluster-server on the same machines (3 machines)
Here is the /tc/fstab file
/dev/sdb1 /data/gluster ext4 defaults 0 0
web1.dasilva.network:/www /mnt/glusterfs/www glusterfs
defaults,_netdev,log-level=debug,log-file=/var/log/gluster.log 0 0
2017 Jun 01
0
[Gluster-devel] Empty info file preventing glusterd from starting
On Thu, Jun 01, 2017 at 01:03:25PM +0530, ABHISHEK PALIWAL wrote:
> Hi Niels,
>
> No problem we wil try to backport that patch on 3.7.6.
>
> Could you please let me know in which release Gluster community is going to
> provide this patch and date of that release?
It really depends on when someone has time to work on it. Our releases
are time based, and will happen even when a
2017 Aug 21
1
Glusterd not working with systemd in redhat 7
Hi!
Please see bellow. Note that web1.dasilva.network is the address of the
local machine where one of the bricks is installed and that ties to mount.
[2017-08-20 20:30:40.359236] I [MSGID: 100030] [glusterfsd.c:2476:main]
0-/usr/sbin/glusterd: Started running /usr/sbin/glusterd version 3.11.2
(args: /usr/sbin/glusterd -p /var/run/glusterd.pid)
[2017-08-20 20:30:40.973249] I [MSGID: 106478]
2014 Sep 30
1
geo-replication 3.5.2 not working on Ubuntu 12.0.4 - transport.address-family not specified
Hi,
I am testing geo-replication 3.5.2 by following the instruction from https://github.com/gluster/glusterfs/blob/master/doc/admin-guide/en-US/markdown/admin_distributed_geo_rep.md
All commands are executed successfully without returning any error, but no replication is done from master to the slave.
Enclosed please find the logs when starting the geo-replication volume. At the end of the log,
2017 Jun 01
2
[Gluster-devel] Empty info file preventing glusterd from starting
Hi Niels,
No problem we wil try to backport that patch on 3.7.6.
Could you please let me know in which release Gluster community is going to
provide this patch and date of that release?
Regards,
Abhishek
On Wed, May 31, 2017 at 10:05 PM, Niels de Vos <ndevos at redhat.com> wrote:
> On Wed, May 31, 2017 at 04:08:06PM +0530, ABHISHEK PALIWAL wrote:
> > We are using 3.7.6 and on
2013 May 13
0
Fwd: Seeing non-priv port + auth issue in the gluster brick log
Fwd.ing to Gluster users, in the hope that many more people can see this
and hopefully can provide any clues
thanx,
deepak
-------- Original Message --------
Subject: [Gluster-devel] Seeing non-priv port + auth issue in the
gluster brick log
Date: Sat, 11 May 2013 12:43:20 +0530
From: Deepak C Shetty <deepakcs at linux.vnet.ibm.com>
Organization: IBM India Pvt. Ltd.
To: Gluster
2017 Jun 18
0
gluster peer probe failing
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]
2017 Jun 15
1
peer probe failures
Hi,
I'm having a similar issue, were you able to solve it?
Thanks.
Hey all,
I've got a strange problem going on here. I've installed glusterfs-server
on ubuntu 16.04:
glusterfs-client/xenial,now 3.7.6-1ubuntu1 amd64 [installed,automatic]
glusterfs-common/xenial,now 3.7.6-1ubuntu1 amd64 [installed,automatic]
glusterfs-server/xenial,now 3.7.6-1ubuntu1 amd64 [installed]
I can
2013 Jul 02
1
RDMA Volume Mount Not Functioning for Debian 3.4.beta4
Anyone ele having these issues mounting RDMA only volumes under Ubuntu? Install of Gluster via: https://launchpad.net/~semiosis/+archive/ubuntu-glusterfs-3.4
I'm guessing this build is looking for an include somewhere that is just misplaced?
glusterfs 3.4.0beta4 built on Jun 28 2013 16:16:07
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc.
2017 Jun 20
0
gluster peer probe failing
Hi,
I am able to recreate the issue and here is my RCA.
Maximum value i.e 32767 is being overflowed while doing manipulation on it
and it was previously not taken care properly.
Hence glusterd was crashing with SIGSEGV.
Issue is being fixed with "
https://bugzilla.redhat.com/show_bug.cgi?id=1454418" and being backported
as well.
Thanks
Gaurav
On Tue, Jun 20, 2017 at 6:43 AM, Gaurav
2017 Jun 20
1
gluster peer probe failing
Thanks Gaurav!
1. Any time estimation on to when this fix would be released?
2. Any recommended workaround?
Best,
Guy.
From: Gaurav Yadav [mailto:gyadav at redhat.com]
Sent: Tuesday, June 20, 2017 9:46 AM
To: Guy Cukierman <guyc at elminda.com>
Cc: Atin Mukherjee <amukherj at redhat.com>; gluster-users at gluster.org
Subject: Re: [Gluster-users] gluster peer probe failing
2017 Jun 20
2
gluster peer probe failing
Hi,
I have tried on my host by setting corresponding ports, but I didn't see
the issue on my machine locally.
However with the logs you have sent it is prety much clear issue is related
to ports only.
I will trying to reproduce on some other machine. Will update you as s0on
as possible.
Thanks
Gaurav
On Sun, Jun 18, 2017 at 12:37 PM, Guy Cukierman <guyc at elminda.com> wrote:
>
2017 Dec 01
0
Problems joining new gluster 3.10 nodes to existing 3.8
On Fri, Dec 1, 2017 at 1:55 AM, Ziemowit Pierzycki <ziemowit at pierzycki.com>
wrote:
> Hi,
>
> I have a problem joining four Gluster 3.10 nodes to an existing
> Gluster 3.8 nodes. My understanding that this should work and not be
> too much of a problem.
>
> Peer robe is successful but the node is rejected:
>
> gluster> peer detach elkpinfglt07
> peer
2017 Nov 30
2
Problems joining new gluster 3.10 nodes to existing 3.8
Hi,
I have a problem joining four Gluster 3.10 nodes to an existing
Gluster 3.8 nodes. My understanding that this should work and not be
too much of a problem.
Peer robe is successful but the node is rejected:
gluster> peer detach elkpinfglt07
peer detach: success
gluster> peer probe elkpinfglt07
peer probe: success.
gluster> peer status
Number of Peers: 6
Hostname: elkpinfglt02