[
https://issues.apache.org/jira/browse/AMBARI-10280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392038#comment-14392038
]
Hudson commented on AMBARI-10280:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2173 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2173/])
AMBARI-10280. Need to check if rpcbind or portmap is started before starting
NFS Gateway (Brandon Li via alejandro) (afernandez:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d331e853295e60928174cf0a7c4ffa558b65813a)
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/status_params.py
* ambari-server/src/test/python/stacks/2.0.6/HDFS/test_nfsgateway.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/utils.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/params.py
*
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py
> Need to check if rpcbind or portmap is started before starting NFS Gateway
> --------------------------------------------------------------------------
>
> Key: AMBARI-10280
> URL: https://issues.apache.org/jira/browse/AMBARI-10280
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Brandon Li
> Assignee: Brandon Li
> Fix For: 2.1.0
>
> Attachments: AMBARI-10280.001.patch, AMBARI-10280.003.patch,
> AMBARI-10280.004.patch
>
>
> On some platform, rpcbind is not started by default. The script should try to
> start rpcbind(or portmap) when starting the Gateway.
> {noformat}
> 2015-03-30 12:03:18,835 FATAL mount.MountdBase (MountdBase.java:start(86)) -
> Failed to start the server. Cause:
> java.lang.RuntimeException: Registration failure
> at org.apache.hadoop.oncrpc.RpcProgram.register(RpcProgram.java:135)
> at org.apache.hadoop.oncrpc.RpcProgram.register(RpcProgram.java:101)
> at org.apache.hadoop.mount.MountdBase.start(MountdBase.java:83)
> at
> org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.startServiceInternal(Nfs3.java:56)
> at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.startService(Nfs3.java:69)
> at org.apache.hadoop.hdfs.nfs.nfs3.Nfs3.main(Nfs3.java:73)
> Caused by: java.net.SocketTimeoutException: Receive timed out
> at java.net.PlainDatagramSocketImpl.receive0(Native Method)
> at
> java.net.AbstractPlainDatagramSocketImpl.receive(AbstractPlainDatagramSocketImpl.java:145)
> at java.net.DatagramSocket.receive(DatagramSocket.java:786)
> at
> org.apache.hadoop.oncrpc.SimpleUdpClient.run(SimpleUdpClient.java:66)
> at org.apache.hadoop.oncrpc.RpcProgram.register(RpcProgram.java:130)
> ... 5 more
> 2015-03-30 12:03:18,839 INFO util.ExitUtil (ExitUtil.java:terminate(124)) -
> Exiting with status 1
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)