Gluster users - Dec 2015 - unable to mount gluster volume on client - Resolved

I am now able to mount the Gluster volume on the client:

The problem was corrected by setting

#gluster volume set gtower auth.allow "*"

Instead of

#gluster volume set gtower auth.allow  *


This fixed the problem!!

Thanks,
Uthra

From: Rao, Uthra R. (GSFC-672.0)[ADNET SYSTEMS INC]
Sent: Tuesday, December 01, 2015 10:14 AM
To: gluster-users at gluster.org
Subject: unable to mount gluster volume on client

I am having difficulty mounting the glusterfs volume on my client. I had mounted
it earlier but after the performance tuning I did I man seeing a problem

In the server  /var/log/glusterfs/bricks/ tower7-gluster1-brick.log I see the
following message when I try to mount on the client:

[2015-12-01 14:58:31.276123] E [MSGID: 115004]
[authenticate.c:229:gf_authenticate] 0-auth: no authentication module is
interested in accepting remote-client (null)
[2015-12-01 14:58:31.276145] E [MSGID: 115001]
[server-handshake.c:623:server_setvolume] 0-gtower-server: Cannot authenticate
client from ***.***.***.***-15951-2015/12/01-14:58:29:637694-gtower-client-0-0-0
3.7.6 [Permission denied]
[2015-12-01 14:58:31.280258] I [MSGID: 115036] [server.c:552:server_rpc_notify]
0-gtower-server: disconnecting connection from
aster.sci.gsfc.nasa.gov-15951-2015/12/01-14:58:29:637694-gtower-client-0-0-0
[2015-12-01 14:58:31.280276] I [MSGID: 101055] [client_t.c:419:gf_client_unref]
0-gtower-server: Shutting down connection
aster.sci.gsfc.nasa.gov-15951-2015/12/01-14:58:29:637694-gtower-client-0-0-0


# gluster volume info gtower

Volume Name: gtower
Type: Replicate
Volume ID: ***********************
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: ************:/tower7/gluster1/brick
Brick2: ************:/tower8/gluster2/brick
Options Reconfigured:
cluster.readdir-optimize: on
cluster.lookup-optimize: on
server.allow-insecure: on
features.trash-max-filesize: 1GB
features.trash: on
performance.write-behind-window-size: 10MB
nfs.disable: on
server.root-squash: ON
server.event-threads: 4
client.event-threads: 4
performance.io-thread-count: 64
performance.io-cache: on
performance.client-io-threads: on
nfs.export-volumes: off
nfs.addr-namelookup: off
performance.readdir-ahead: enable
performance.cache-size: 2GB
auth.allow: all

I am not sure if any of the above volume properties I have set is causing this
mount problem on the client. I am able to mount the gluster volume locally on
the server but not on the remote client.
I would appreciate any help to solve this issue.

Thank you.
Uthra

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20151201/466d863f/attachment.html>