I have restarted multiple times but it is not changing I am not able to see
nfs_acl in my
environment.
To file the bug what I need to do?
Regards,
Abhishek
On Wed, May 4, 2016 at 1:28 PM, Soumya Koduri wrote:
> Even on my setup if I change nfs.port, all the other services also started
> regist
Even on my setup if I change nfs.port, all the other services also
started registering on those ports. Can you please file a bug for it.
That seems like a bug (or is it intentional..Niels?).
153 tcp 2049 mountd
151 tcp 2049 mountd
133 tcp 2049 n
i am changing the nfs.port using gluster volume set gv0 nfs.port 2049 but
it automatically changing MOUNTD as well
and nfs.disable is also off
gluster volume get gv0 nfs.disable
Option
Value
--
-
nfs.disable off
On Wed, May 4, 2016 at 12:25 PM, Soumya Koduri
Not sure why mountd is registering on 2049 port number. Please try
resetting volume options (if its fine) using "gluster v reset
force" and enable only nfs and verify the behavior.
"gluster v set nfs.disable off"
Thanks,
Soumya
On 05/04/2016 12:17 PM, ABHISHEK PALIWAL wrote:
still having
> nfs.port
> 38465
Is there any reason behind choosing this port for NFS protocol? This
port number seems to be used for MOUNT (V3) protocol as well and that
may have resulted in port registration failures. Could you please change
nfs port to default (2049) or some other port (other than 38465
Hi Soumya,
Please find attached nfs.log file.
Regards,
Abhishek
On Wed, May 4, 2016 at 11:45 AM, ABHISHEK PALIWAL
wrote:
> HI Soumya,
>
> Thanks for reply.
>
> Yes, I am getting following error in /var/log/glusterfs/nfs.log file
>
> [2016-04-25 06:27:23.721851] E [MSGID: 112109] [nfs.c:1482:i
HI Soumya,
Thanks for reply.
Yes, I am getting following error in /var/log/glusterfs/nfs.log file
[2016-04-25 06:27:23.721851] E [MSGID: 112109] [nfs.c:1482:init] 0-nfs:
Failed to initialize protocols
Please suggest me how can I resolve it.
Regards,
Abhishek
On Wed, May 4, 2016 at 11:33 AM, S
Hi Abhishek,
Below 'rpcinfo' output doesn't list 'nfsacl' protocol. That must be the
reason client is not able set ACLs. Could you please check the log file
'/var/lib/glusterfs/nfs.log' if there are any errors logged with respect
protocol registration failures.
Thanks,
Soumya
On 05/04/2016
Hi Niels,
Please reply it is really urgent.
Regards,
Abhishek
On Tue, May 3, 2016 at 11:36 AM, ABHISHEK PALIWAL
wrote:
> Hi Niels,
>
> Do you require more logs...
>
> Regards,
> Abhishek
>
> On Mon, May 2, 2016 at 4:58 PM, ABHISHEK PALIWAL
> wrote:
>
>> Hi Niels,
>>
>>
>> Here is the output o
Hi Niels,
Do you require more logs...
Regards,
Abhishek
On Mon, May 2, 2016 at 4:58 PM, ABHISHEK PALIWAL
wrote:
> Hi Niels,
>
>
> Here is the output of rpcinfo -p $NFS_SERVER
>
> root@128:/# rpcinfo -p $NFS_SERVER
>program vers proto port service
> 104 tcp111 portmapp
Hi Niels,
Here is the output of rpcinfo -p $NFS_SERVER
root@128:/# rpcinfo -p $NFS_SERVER
program vers proto port service
104 tcp111 portmapper
103 tcp111 portmapper
102 tcp111 portmapper
104 udp111 portmapper
On Mon, May 02, 2016 at 04:14:01PM +0530, ABHISHEK PALIWAL wrote:
> HI Team,
>
> I am exporting gluster volume using GlusterNFS with ACL support but at NFS
> client while running 'setfacl' command getting "setfacl: /tmp/e: Remote I/O
> error"
>
>
> Following is the NFS option status for Volume:
12 matches
Mail list logo
