Support Questions

Find answers, ask questions, and share your expertise
Announcements

Problem report HDP 2.4 User that is tunning NFSGateway doesn't have proxy rights

avatar
New Contributor

These lines should come with HDP image in core-site.xml , if one wish to have working NFSGateway out of the box

    <property>
      <name>hadoop.proxyuser.hdfs.groups</name>
      <value>*</value>
    </property>
    <property>
      <name>hadoop.proxyuser.hdfs.hosts</name>
      <value>*</value>
    </property>

Without them this is the result in /var/log/hadoop/root/hadoop-hdfs-nfs3-sandbox.hortonworks.com.log

2016-06-10 10:22:21,763 WARN  nfs3.RpcProgramNfs3 (RpcProgramNfs3.java:fsinfo(1982)) - Exception
org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException): User: hdfs is not allowed to imperson
ate root
        at org.apache.hadoop.ipc.Client.call(Client.java:1427)
        at org.apache.hadoop.ipc.Client.call(Client.java:1358)
        at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
        at com.sun.proxy.$Proxy11.getFileLinkInfo(Unknown Source)
        at org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getFileLinkInfo(ClientNamenodeProtocolTranslatorPB.java:7
84)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:187)
        at org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
        at com.sun.proxy.$Proxy12.getFileLinkInfo(Unknown Source)
        at org.apache.hadoop.hdfs.DFSClient.getFileLinkInfo(DFSClient.java:2156)
        at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3Utils.getFileStatus(Nfs3Utils.java:58)
        at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3Utils.getFileAttr(Nfs3Utils.java:82)
        at org.apache.hadoop.hdfs.nfs.nfs3.RpcProgramNfs3.fsinfo(RpcProgramNfs3.java:1969)
        at org.apache.hadoop.hdfs.nfs.nfs3.RpcProgramNfs3.fsinfo(RpcProgramNfs3.java:1925)
        at org.apache.hadoop.hdfs.nfs.nfs3.RpcProgramNfs3.handleInternal(RpcProgramNfs3.java:2251)
        at org.apache.hadoop.oncrpc.RpcProgram.messageReceived(RpcProgram.java:167)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:281)
        at org.apache.hadoop.oncrpc.RpcUtil$RpcMessageParserStage.messageReceived(RpcUtil.java:132)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
        at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:787)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)
        at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462)
        at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443)
        at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)
        at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:560)
        at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:555)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268)
        at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255)
        at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107)
        at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312)
        at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88)
        at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)
        at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
        at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

with mount failing without useful error message

mount -t nfs -o vers=3,proto=tcp,nolock 127.0.0.1:/ /media/
mount.nfs: mount system call failed
1 ACCEPTED SOLUTION

avatar
Contributor

@Ventseslav Vat, BUG-60085 has been resolved, so this update will be in the next version (HDP-2.5) of the Sandbox.

View solution in original post

9 REPLIES 9

avatar

This may require a bug or at least documentation of the above

avatar
Contributor

@Ali Bajwa, I'm from the Tech Docs team. I'm happy to work with you, assuming that you need documentation assistance. Please file a bug and/or contact me directly.

avatar
Contributor

@Ventseslav Vat:

This appears to be documented already in Step 1 of this topic in our documentation:

http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.4.2/bk_hdfs_nfs_gateway/content/user-guide-hdfs-...

You can also find it documented in the Apache docs:

https://hadoop.apache.org/docs/r2.7.2/hadoop-project-dist/hadoop-hdfs/HdfsNfsGateway.html

Hope this helps,

Pattie

avatar
New Contributor

That is correct, but I'm talking about HDP 2.4 and 2.3.2 sandboxes. NfsGateway should work in those VM images. If you do a plain Ambari cluster from start, the NfsGateway is properly configured.

avatar
Contributor
@Ventseslav Vat

We in Tech Docs have no control over the sandbox. You should file a bug against the HDP-2.3.2 and HDP-2.4 Sandbox (Project: Bug DB, Issue Type: Bug, Component: Sandbox). Provide a description of the problem in the bug, and also a link to this HCC post.

avatar
Contributor

Hopefully, that will fix your issue and help others in the future.

avatar
Contributor
@Ventseslav Vat

Sorry, about that. Mistakenly assumed you were a Hortonworks employee and could file a bug. https://hortonworks.jira.com/browse/BUG-60085 has been filed on this issue. Hopefully, the problem will be fixed very soon.

avatar
Contributor

@Ventseslav Vat, I filed a JIRA against the Sandbox for this issue (https://hortonworks.jira.com/browse/BUG-60085), so the Sandbox team will take it from here. Thanks very much for letting us know about this issue.

avatar
Contributor

@Ventseslav Vat, BUG-60085 has been resolved, so this update will be in the next version (HDP-2.5) of the Sandbox.