Re: [Gluster-users] SSL support is NOT enabled

[Atin Mukherjee]

On 02/29/2016 01:49 AM, Steven Fisher wrote:
> Hi,
> 
> I have been using gluster successfully for a while on a couple of
> Raspberry Pi2s where I have external USB devices. I used the following
> article to get me up and running very
> quickly: 
> http://banoffeepiserver.com/glusterfs/set-up-glusterfs-on-two-nodes.html
> 
> I mount that gluster volumes on my RPis where I don’t have external
> storage.  This is useful to move files between the machines easily. All
> was fine but then I added a new RPI2 which runs the new Linux kernel
> (4.1.18) by default and I get the error SSL support is NOT enabled  when
> trying to mount the cluster volume from this machine.
> 
>  The versions installed on my existing RPIs set-up are:
> 
> *gluster*fs-client  3.2.7-3+deb7u1 
> armhfclustered file-system (client package)
> ii  *gluster*fs-common  3.2.7-3+deb7u1 
> armhfGlusterFS common libraries and translator modules
> ii  *gluster*fs-server  3.2.7-3+deb7u1 
> armhfclustered file-system (server package)
> 
3.2.7 is way too old and probably that's the reason why TLS (SSL)
implementation is not there in the same.

Can you please upgrade your bits to at least 3.5 if not 3.6/3.7 to check
the functionality?
> They run: Linux rpi2 3.18.6-v7+ #3 SMP PREEMPT Mon Feb 9 15:39:54 UTC
> 2015 armv7l GNU/Linux
> 
> My new RPI comes with the new Rasbian OS: 
> 
> Linux raspberrypi 4.1.18-v7+ #845 SMP Thu Feb 18 19:45:28 GMT 2016
> armv7l GNU/Linux
> 
> On this version when I install the glusterfs-clinet I end up with the
> following version:
> 
> ii  glusterfs-client  3.5.2-2+deb8u1   
> armhfclustered file-system (client package)
> ii  glusterfs-common  3.5.2-2+deb8u1
> 
> For some reason I can’t install the earlier version and when I try the
> command to mount 'sudo mount -t glusterfs glus1:/glusv0 /mnt -o
> backupvolfile-server=glus2’ I end up with an error.
> 
> What I would like to do is to use what I have seen is the
> option client.ssl=off , but the existing gluster volume servers don’t
> recognise that option and I can’t find the option to cause the mount on
> the new RPI2 to not use ssl.
> 
> Since I don’t want to have to set-up this volume with SSL how can I
> get access to it on the new RPI2?
> 
> Regards
> 
> Steve
> 
> 
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
> 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] What I noticed while upgrading 3.7.6 to 3.7.8

[Atin Mukherjee]

On 02/28/2016 11:06 PM, ML mail wrote:
> Thanks for explaining why the ping-timeout option has been disabled. Now in 
> my case of a small replicate volume of 2 physical nodes with one brick per 
> node, does it mean that if one node goes down the FUSE client mount will not 
> respond at all? In the past it would simply block for 42 seconds and after 
> this timeout respond again.
No, that still applies. ping timer logic still holds true for connection
between client & bricks and by default it should be 42 seconds. Only its
disabled between GlusterD to GlusterD connection.

> 
> By the way is there a ChangeLog somewhere for 3.7.8?
Please refer [1]

[1]
https://github.com/gluster/glusterfs/blob/release-3.7/doc/release-notes/3.7.8.md
> 
> Regards
> ML
> 
> 
> 
> 
> On Sunday, February 28, 2016 5:50 PM, Atin Mukherjee  
> wrote:
> 
> 
> On 02/28/2016 04:48 PM, ML mail wrote:
>> Hi,
>>
>> I just upgraded from 3.7.6 to 3.7.8 and noticed the following 2 points:
>>
>> 1) As others on the mailing list I am also affected by a massive performance 
>> drop on my FUSE mount. I used to have around 10 MB/s transfer, which is 
>> already quite slow, but now since the upgrade I am at around 2 MB/s as you 
>> can see below:
>>
>>
>> $ sudo dd if=/dev/zero of=bwtest bs=1M count=64
>> 64+0 records in
>> 64+0 records out
>> 67108864 bytes (67 MB) copied, 37.9311 s, 1.8 MB/s
>>
>>
>> I know there is a bug (#1309462) already opened for that but just thought I 
>> would mention it too and hope that it will be fixed in 3.7.9.
>>
>>
>> 2) I noticed that the ping-timeout option in /etc/glusterfs/glusterd.vol 
>> changed from 30 seconds to 0 seconds. Can someone comment on that change? 
>> and does this mean that with 0 seconds it never times out?
> This indicates that there is no ping mechanism between GlusterDs now. We
> have had some issues from snapshot use cases when we tried to enable
> ping timer in glusterd, the solution to it was multi threaded epoll and
> when we enabled it then we got to see some corruption and crashes which
> are yet to be RCAed. So we decided to turn both these features off till
> we get to the root cause.
> 
> HTH,
> Atin
> 
>>
>> Regards
>> ML
>> ___
>> Gluster-users mailing list
>> Gluster-users@gluster.org
>> http://www.gluster.org/mailman/listinfo/gluster-users
> 
>>
> 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] faied start the glusterd after reboot

[songxin]

Hi,
Thank you for reply.


The file .nfs01722f42 is a file but not a directory.
And I found that it is there when the gluster is running.


root@128:/# ls -al /var/lib/glusterd/snaps/ total 8 drwxr-xr-x 2 root root 4096 
Feb 26 2016 . drwxr-xr-x 14 root root 4096 Feb 26 2016 .. -rw--- 1 root 
root 0 Feb 26 2016 .nfs06c02b09000c -rw--- 1 root root 0 Feb 26 
2016 missed_snaps_list


If I abnormal shutdown the my board， the file will be there when the board 
reboot.And some error will happened as below.
...
316] E [MSGID: 106043] [glusterd-store.c:3589:glusterd_store_retrieve_snaps] 
0-management: Unable to restore snapshot: .nfs01722f2c0001 348] D 
[MSGID: 0] [glusterd-store.c:3607:glusterd_store_retrieve_snaps] 0-management: 
Returning with -1 389] D [MSGID: 0] [glusterd-store.c:4339:glusterd_restore] 
0-management: Returning -1 469] E [MSGID: 101019] [xlator.c:428:xlator_init] 
0-management: Initialization of volume 'management' failed, review your volfile 
again 501] E [graph.c:322:glusterfs_graph_init] 0-management: initializing 
translator failed
...


Do you know why is that？


Thanks,
Xin






在 2016-02-25 19:46:40，"Avra Sengupta"  写道：
>Hi,
>
>/var/lib/glusterd/snaps/ contains only 1 file called missed_snaps_list. Apart 
>from it, there are only directories created with
>the snap names. Is .nfs01722f42, that you saw in 
>/var/lib/glusterd a file or a directory. If it's a file, then it
>was not placed there as part of snapshotting any volume. If it's a directory, 
>then did you try creating a snapshot with such a name.
>
>Regards,
>Avra
>
>On 02/25/2016 05:10 PM, songxin wrote:
>> If I run "reboot" on the a node��there are not .snap files on A node after 
>> reboot.
>> Does the snap file only appear after unexpect reboot��
>> Why its size is 0 byte��
>> In this situation ��is a right method to solve this problem removing the 
>> snap file?
>>
>> thanks
>> xin
>>
>> �ҵ� iPhone
>>
>>> �� 2016��2��25�գ�19:05��Atin Mukherjee  д
>>>
>>> + Rajesh , Avra
>>>
 On 02/25/2016 04:12 PM, songxin wrote:
 Thanks for your reply.

 Do I need check all files in /var/lib/glusterd/*?
 Must all files be same in A node and B node?
>>> Yes, they should be identical.
 I found that the size of
 file /var/lib/glusterd/snaps/.nfs01722f42 is 0 bytes
 after A board reboot.
 So glusterd can't restore by this snap file on A node.
 Is it right?
>>> Yes, looks like that.





 At 2016-02-25 18:25:50, "Atin Mukherjee"  wrote:
> I believe you and Abhishek are from the same group and sharing the
> common set up. Could you check the content of /var/lib/glusterd/* in
> board B (post reboot and before starting glusterd) matches with
> /var/lib/glusterd/* from board A?
>
> ~Atin
>
>> On 02/25/2016 03:48 PM, songxin wrote:
>> Hi,
>> I have a problem as below when I start the gluster after reboot a board.
>>
>> precondition:
>> I use two boards do this test.
>> The version of glusterfs is 3.7.6.
>>
>> A board ip:128.224.162.255
>> B board ip:128.224.95.140
>>
>> reproduce steps£º
>>
>> 1.systemctl start glusterd (A board)
>> 2.systemctl start glusterd (B board)
>> 3.gluster peer probe 128.224.95.140 (A board)
>> 4.gluster volume create gv0 replica 2 128.224.95.140:/tmp/brick1/gv0
>> 128.224.162.255:/data/brick/gv0 force (local board)
>> 5.gluster volume start gv0 (A board)
>> 6.press the reset button on the A board.It is a develop board so it has
>> a reset button that is similar to reset button on pc (A board)
>> 7.run command "systemctl start glusterd" after A board reboot. And
>> command failed because the file /var/lib/glusterd/snaps/.nfsx
>> (local board) .
>> Log is as below.
>> [2015-12-07 07:55:38.260084] E [MSGID: 101032]
>> [store.c:434:gf_store_handle_retrieve] 0-: Path corresponding to
>> /var/lib/glusterd/snaps/.nfs01722f42
>> [2015-12-07 07:55:38.260120] D [MSGID: 0]
>> [store.c:439:gf_store_handle_retrieve] 0-: Returning -1
>>
>> [2015-12-07 07:55:38.260152] E [MSGID: 106200]
>> [glusterd-store.c:3332:glusterd_store_update_snap] 0-management: snap
>> handle is NULL
>> [2015-12-07 07:55:38.260180] E [MSGID: 106196]
>> [glusterd-store.c:3427:glusterd_store_retrieve_snap] 0-management:
>> Failed to update snapshot for .nfs01722f40
>> [2015-12-07 07:55:38.260208] E [MSGID: 106043]
>> [glusterd-store.c:3589:glusterd_store_retrieve_snaps] 0-management:
>> Unable to restore snapshot: .nfs01722f400
>> [2015-12-07 07:55:38.260241] D [MSGID: 0]
>> [glusterd-store.c:3607:glusterd_store_retrieve_snaps] 0-management:
>> Returning with -1
>> [2015-12-07 07:55:38.260268] D [MSGID: 0]
>> [glusterd-store.c:4339:glusterd_restore] 0-management: Retur

[Gluster-users] SSL support is NOT enabled

[Steven Fisher]

Hi,

I have been using gluster successfully for a while on a couple of Raspberry 
Pi2s where I have external USB devices. I used the following article to get me 
up and running very quickly: 
http://banoffeepiserver.com/glusterfs/set-up-glusterfs-on-two-nodes.html 


I mount that gluster volumes on my RPis where I don’t have external storage.  
This is useful to move files between the machines easily. All was fine but then 
I added a new RPI2 which runs the new Linux kernel (4.1.18) by default and I 
get the error SSL support is NOT enabled  when trying to mount the cluster 
volume from this machine.

 The versions installed on my existing RPIs set-up are:

glusterfs-client  3.2.7-3+deb7u1  
armhfclustered file-system (client package)
ii  glusterfs-common  3.2.7-3+deb7u1
  armhfGlusterFS common libraries and translator modules
ii  glusterfs-server  3.2.7-3+deb7u1
  armhfclustered file-system (server package)

They run: Linux rpi2 3.18.6-v7+ #3 SMP PREEMPT Mon Feb 9 15:39:54 UTC 2015 
armv7l GNU/Linux

My new RPI comes with the new Rasbian OS: 

Linux raspberrypi 4.1.18-v7+ #845 SMP Thu Feb 18 19:45:28 GMT 2016 armv7l 
GNU/Linux

On this version when I install the glusterfs-clinet I end up with the following 
version:

ii  glusterfs-client  3.5.2-2+deb8u1
armhfclustered file-system (client package)
ii  glusterfs-common  3.5.2-2+deb8u1

For some reason I can’t install the earlier version and when I try the command 
to mount 'sudo mount -t glusterfs glus1:/glusv0 /mnt -o 
backupvolfile-server=glus2’ I end up with an error.

What I would like to do is to use what I have seen is the option client.ssl=off 
, but the existing gluster volume servers don’t recognise that option and I 
can’t find the option to cause the mount on the new RPI2 to not use ssl.

Since I don’t want to have to set-up this volume with SSL how can I get access 
to it on the new RPI2?

Regards

Steve___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] What I noticed while upgrading 3.7.6 to 3.7.8

[ML mail]

Thanks for explaining why the ping-timeout option has been disabled. Now in my 
case of a small replicate volume of 2 physical nodes with one brick per node, 
does it mean that if one node goes down the FUSE client mount will not respond 
at all? In the past it would simply block for 42 seconds and after this timeout 
respond again.

By the way is there a ChangeLog somewhere for 3.7.8?

Regards
ML




On Sunday, February 28, 2016 5:50 PM, Atin Mukherjee  
wrote:


On 02/28/2016 04:48 PM, ML mail wrote:
> Hi,
> 
> I just upgraded from 3.7.6 to 3.7.8 and noticed the following 2 points:
> 
> 1) As others on the mailing list I am also affected by a massive performance 
> drop on my FUSE mount. I used to have around 10 MB/s transfer, which is 
> already quite slow, but now since the upgrade I am at around 2 MB/s as you 
> can see below:
> 
> 
> $ sudo dd if=/dev/zero of=bwtest bs=1M count=64
> 64+0 records in
> 64+0 records out
> 67108864 bytes (67 MB) copied, 37.9311 s, 1.8 MB/s
> 
> 
> I know there is a bug (#1309462) already opened for that but just thought I 
> would mention it too and hope that it will be fixed in 3.7.9.
> 
> 
> 2) I noticed that the ping-timeout option in /etc/glusterfs/glusterd.vol 
> changed from 30 seconds to 0 seconds. Can someone comment on that change? and 
> does this mean that with 0 seconds it never times out?
This indicates that there is no ping mechanism between GlusterDs now. We
have had some issues from snapshot use cases when we tried to enable
ping timer in glusterd, the solution to it was multi threaded epoll and
when we enabled it then we got to see some corruption and crashes which
are yet to be RCAed. So we decided to turn both these features off till
we get to the root cause.

HTH,
Atin

> 
> Regards
> ML
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

> 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] What I noticed while upgrading 3.7.6 to 3.7.8

[Atin Mukherjee]

On 02/28/2016 04:48 PM, ML mail wrote:
> Hi,
> 
> I just upgraded from 3.7.6 to 3.7.8 and noticed the following 2 points:
> 
> 1) As others on the mailing list I am also affected by a massive performance 
> drop on my FUSE mount. I used to have around 10 MB/s transfer, which is 
> already quite slow, but now since the upgrade I am at around 2 MB/s as you 
> can see below:
> 
> 
> $ sudo dd if=/dev/zero of=bwtest bs=1M count=64
> 64+0 records in
> 64+0 records out
> 67108864 bytes (67 MB) copied, 37.9311 s, 1.8 MB/s
> 
> 
> I know there is a bug (#1309462) already opened for that but just thought I 
> would mention it too and hope that it will be fixed in 3.7.9.
> 
> 
> 2) I noticed that the ping-timeout option in /etc/glusterfs/glusterd.vol 
> changed from 30 seconds to 0 seconds. Can someone comment on that change? and 
> does this mean that with 0 seconds it never times out?
This indicates that there is no ping mechanism between GlusterDs now. We
have had some issues from snapshot use cases when we tried to enable
ping timer in glusterd, the solution to it was multi threaded epoll and
when we enabled it then we got to see some corruption and crashes which
are yet to be RCAed. So we decided to turn both these features off till
we get to the root cause.

HTH,
Atin
> 
> Regards
> ML
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users
> 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] What I noticed while upgrading 3.7.6 to 3.7.8

[ML mail]

Hi,

I just upgraded from 3.7.6 to 3.7.8 and noticed the following 2 points:

1) As others on the mailing list I am also affected by a massive performance 
drop on my FUSE mount. I used to have around 10 MB/s transfer, which is already 
quite slow, but now since the upgrade I am at around 2 MB/s as you can see 
below:


$ sudo dd if=/dev/zero of=bwtest bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB) copied, 37.9311 s, 1.8 MB/s


I know there is a bug (#1309462) already opened for that but just thought I 
would mention it too and hope that it will be fixed in 3.7.9.


2) I noticed that the ping-timeout option in /etc/glusterfs/glusterd.vol 
changed from 30 seconds to 0 seconds. Can someone comment on that change? and 
does this mean that with 0 seconds it never times out?

Regards
ML
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users