Yes dig and ping works fine. I used first the short hostname gfs1 and then I
also tried gfs1.intra.domain.com. That did not change anything.
Currently for testing I only have a single node setup so my gluster peer
status output would be empty.
Now I had a closed look at the brick logfile and
Yes, so I added a sleep 5 in the init script right before the startup of the
daemon here:
start-stop-daemon --start --quiet --oknodo --pidfile $PIDFILE --startas $DAEMON
-- -p $PIDFILE $GLUSTERD_OPTS
and yes it works. So this is a workaround but IMHO this should get fixed into
the Debian
Hi all,
This meeting is scheduled for anyone that is interested in learning more
about, or assisting with the Bug Triage.
Meeting details:
- location: #gluster-meeting on Freenode IRC
( https://webchat.freenode.net/?channels=gluster-meeting )
- date: every Tuesday
- time: 12:00 UTC,
Hi ML,
Here's what I have noted down in my personal documentation when I installed
GlusterFS the first time in 2013 (also on Debian Wheezy with 3.5.2):
All cluster nodes MUST resolve each other through DNS (preferred) or
/etc/hosts.
An entry in /etc/hosts is probably even more safe because you
So that would sound like the boot order is messed up. Sounds a bit like
this:
http://joejulian.name/blog/glusterfs-volumes-not-mounting-in-debian-squeeze-at-boot-time/
As I said before, I also run glusterfs 3.5.2 on Debian Wheezy and I don't
have issues after a reboot. But unfortunately I don't
I tried Claudio's advice by renaming /etc/rc2.d/S12glusterfs-server to
/etc/rc2.d/S99glusterfs-server but it did not change anything. It looks like
that even at the S99 stage the network is just not ready by something like 1
second (based on the log files of gluster and my switch).
Any other
Hi everyone.
I'm disappointed to announce that our application to be a mentoring
organization for GSoC-2015 has been rejected. Google has accepted 137
organizations [1] this year (down from 190 last year) and couldn't find
place to accommodate us.
The main reason behind the rejection was the
On Mon, Feb 23, 2015 at 11:43 AM, Manju Nath manjubs.m...@gmail.com wrote:
Hi,
We have installed glusterFS 3.5.1 on a docker container. Container is
installed with RHEL7.
We have executed following commands, but after mount if i check the
mounted partition we are getting Input/output
Hi,
[environment]
1. gluster version: 3.5.3
2. os: redhat6.5
3. volume info shown below:
Volume Name: gv0
Type: Replicate
Volume ID: 37742c27-9f6b-4a38-821f-ea68d1ec8950
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1:
Thanks for the tip but Debian wheezy does not use systemd at all, it's still
old sysV style init scripts.
On Tuesday, March 3, 2015 2:43 PM, Jeremy Young jrm16...@gmail.com wrote:
I know that you mention the script in init.d but want to ask to make sure that
you're not using systemd. Are
Can you resolve the other gluster peers with dig?
Are you able to ping the other peers, too?
On Tue, Mar 3, 2015 at 12:38 PM, ML mail mlnos...@yahoo.com wrote:
Well the weird thing is that my DNS resolver servers are configured
correctly and working fine. Here below is the exact error message
Well the weird thing is that my DNS resolver servers are configured correctly
and working fine. Here below is the exact error message from the brick log file:
[2015-03-03 11:34:21.731639] E [common-utils.c:223:gf_resolve_ip6] 0-resolver:
getaddrinfo failed (Name or service not known)
While probing new nodes have you used mixed flavour of fqdn like short
names, long names?
Can you please paste peer status output here?
~Atin
On 03/03/2015 05:08 PM, ML mail wrote:
Well the weird thing is that my DNS resolver servers are configured correctly
and working fine. Here below is
Probably a stupid workaround but what if you just add a sleep n line into
the init script?
Glusterfs is working fine if it was launched manually, did I understand
that right? It's only the automatic startup at boot which causes the lookup
failure?
On Tue, Mar 3, 2015 at 2:54 PM, ML mail
14 matches
Mail list logo
