Greetings, Grasscutters:
There are signs of growth all around us. One of which is that we are beginning
to outgrow some of our infrastructure services, including our gluster.org web
host, documentation wiki, and even our IRC channel. The first two require
longer-term solutions and will be flesh
The fix for this issue is merged in the master branch -
review.gluster.com/3619. This should be backported to release-3.3 and make
it into 3.3.1.
Avati
On Mon, Jul 2, 2012 at 8:18 AM, Whit Blauvelt wrote:
> Hi,
>
> We've several systems running 3.1.5 since it was new, happily without
> incident.
Awesome! Glad it worked out :)
-JM
- Original Message -
> Hi Everyone,
> Problem has been SOLVED.
> My colleague was playing with hearbeat on this machine and didn't
> forget to reset net.ipv4.ip_nonlocal_bind = 0. I fixed it, did
> sysctl -p and now:
> # gluster peer probe 192.168.
Hi,
We've several systems running 3.1.5 since it was new, happily without
incident. The time has come to upgrade to 3.3.0, so I want to make sure I
have the instructions right to minimize downtime. From here:
http://gluster.org/community/documentation//index.php/Main_Page
I'm sent to here:
Yep, Marcelo, all worked fine. All, but Gluster.
See my previous message about the root cause.
Closing this topic.
Thanks again.
On Mon, Jul 2, 2012 at 6:53 PM, Marcelo Roccasalva wrote:
> On Mon, Jul 2, 2012 at 11:16 AM, Vladimir Yakovlev
> wrote:
> > Thanks, Brian, for the hint.
> > I've ch
Hi Everyone,
Problem has been SOLVED.
My colleague was playing with hearbeat on this machine and didn't forget to
reset net.ipv4.ip_nonlocal_bind = 0. I fixed it, did sysctl -p and now:
# gluster peer probe 192.168.1.193
Probe successful
Thanks, guys, for great support and sorry for keep you bus
On Mon, Jul 2, 2012 at 11:16 AM, Vladimir Yakovlev wrote:
> Thanks, Brian, for the hint.
> I've changed /etc/hosts with respect to your comment, but it didn't help
> either.
>
> The problem (from my perspective) in smth else, e.g. why, when I try to do
> the following, I see the blank response in
Hi Philip,
I tried IPs instead of hostnames at the beginning, but it didn't help:
[root@host1 ~]# gluster peer probe 192.168.1.193
Probe on localhost not needed
My assumption is smth wrong smwhere else. Donno where - no ideas at all;
the worst is i have a set of test machines, where everything w
Hi Vladimir
To circumvent any remaining /etc/hosts abnormalities, try with IPs
only. if that doesn't work either, you have a problem outside name
resolution. If it works with IPs, the problem is the resolver.
Note that nscd caches answers, also the "host" command uses DNS
responses, /not/ the /et
Thanks, Brian, for the hint.
I've changed /etc/hosts with respect to your comment, but it didn't help
either.
The problem (from my perspective) in smth else, e.g. why, when I try to do
the following, I see the blank response in tcpdump:
[root@host1 ~]# ip a
1: lo: mtu 16436 qdisc noqueue state UN
On Mon, Jul 02, 2012 at 05:54:46PM +0400, Vladimir Yakovlev wrote:
>I tried different configurations, the latest follows:
>[root@host1 ~]# cat /etc/hosts
>127.0.0.1 localhost localhost.localdomain localhost4
>localhost4.localdomain4
>127.0.0.1 host1 host1.fqdn
>192.168.1
On Mon, Jul 2, 2012 at 10:54 AM, Vladimir Yakovlev wrote:
> Hi Marcelo, Everyone,
>
> I tried different configurations, the latest follows:
>
> [root@host1 ~]# cat /etc/hosts
> 127.0.0.1 localhost localhost.localdomain localhost4
> localhost4.localdomain4
> 127.0.0.1 host1 host1.fqdn
I would
Hi Marcelo, Everyone,
I tried different configurations, the latest follows:
[root@host1 ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4
localhost4.localdomain4
127.0.0.1 host1 host1.fqdn
192.168.1.193 host2 host2.fqdn
[root@host2 ~]# cat /etc/hosts
127.0.0.1 local
On Mon, Jul 2, 2012 at 8:32 AM, Vladimir Yakovlev wrote:
> Hi Everyone,
>
> I'm trying to set up Gluster 3.3.0 on a fresh CentOS 6.2 with selinux &
> firewall disabled, hosts can see each other (they are present in DNS and one
> can ping/telnet to gluster port each other), there seems to be nothin
Hi Everyone,
I'm trying to set up Gluster 3.3.0 on a fresh CentOS 6.2 with selinux &
firewall disabled, hosts can see each other (they are present in DNS and
one can ping/telnet to gluster port each other), there seems to be nothing
suspicious in sysctl, but whatever I put in peer probe refers to
Hi Mitsue,
I have a report from a colleague that his company was using Gluster for storing
mailboxes and they end up with many issues. I think it was something related to
number of small files which is known to not perform well.
Needless to say for you to test the performance, specially the writ
16 matches
Mail list logo
