Atin Mukherjee [2016-05-25 18:30 +0530] :
> It seems like 24007 port is blocked by firewall. Also brick process
> starts binding from port 49152, so you may have to open up those ports too.
I can confirm that it was related to some firewall/network related
issue. I could eventually solve the prob
On 05/25/2016 05:29 PM, Niklaas Baudet von Gersdorff wrote:
> Atin Mukherjee [2016-05-25 15:50 +0530] :
>
>> Could you check the brick log?
>
> Sorry, I was not aware of the fact that there is an additional log. Here
> it is:
>
> [2016-05-25 08:26:11.830795] I [MSGID: 100030] [glusterfsd.c
Niklaas Baudet von Gersdorff [2016-05-25 13:59 +0200] :
> To me it looks like a firewall issue since there's a problem
> establishing a connection (see line 2 and three). Yet, IP 10.1.0.1 is
> on an internal interface that is not protected by firewall:
I just figured out that it's indeed a proble
Atin Mukherjee [2016-05-25 15:50 +0530] :
> Could you check the brick log?
Sorry, I was not aware of the fact that there is an additional log. Here
it is:
[2016-05-25 08:26:11.830795] I [MSGID: 100030] [glusterfsd.c:2318:main]
0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/gl
On 05/25/2016 02:07 PM, Niklaas Baudet von Gersdorff wrote:
> Hello,
>
> on a FreeBSD 10.3 machine I get the following error if I try to start
> a volume with `gluster volume start volume1`:
>
> [2016-05-25 08:26:11.807056] W [common-utils.c:1685:gf_string2boolean]
> (-->0x8048d84e4 at
>
Hello,
on a FreeBSD 10.3 machine I get the following error if I try to start
a volume with `gluster volume start volume1`:
[2016-05-25 08:26:11.807056] W [common-utils.c:1685:gf_string2boolean]
(-->0x8048d84e4 at
/usr/local/lib/glusterfs/3.7.6/xlator/mgmt/glusterd.so -->0x800870f6b
at /u
