[
https://issues.apache.org/jira/browse/AMBARI-19567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Onischuk updated AMBARI-19567:
-------------------------------------
Status: Patch Available (was: Open)
> NFS Gateway start fails during EU to HDP-2.5.3 with portmap error
> -----------------------------------------------------------------
>
> Key: AMBARI-19567
> URL: https://issues.apache.org/jira/browse/AMBARI-19567
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.5.0
>
> Attachments: AMBARI-19567.patch
>
>
> **Steps**
> 1. Deploy cluster with Ambari version: 2.2.2.0 and HDP version: 2.4.3.0-227
> 2. Upgrade Ambari to Target Version: 2.5.0.0-513 (Hash:
> 4f01102c087344f9aca78574756741ac190f9b19)
> 3. Register HDP-2.5.3.0 and install the bits
> 4. Start Express Upgrade to HDP-2.5.3.0
> **Result**
> NFS gateway start failed with error:
>
>
>
> Traceback (most recent call last):
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py",
> line 147, in <module>
> NFSGateway().execute()
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 287, in execute
> method(env)
> File
> "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py",
> line 729, in restart
> self.start(env, upgrade_type=upgrade_type)
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/nfsgateway.py",
> line 58, in start
> nfsgateway(action="start")
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py",
> line 61, in nfsgateway
> prepare_rpcbind()
> File
> "/var/lib/ambari-agent/cache/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_nfsgateway.py",
> line 52, in prepare_rpcbind
> raise Fail("Failed to start rpcbind or portmap")
> resource_management.core.exceptions.Fail: Failed to start rpcbind or
> portmap
>
> Checked on one of the hosts:
>
>
>
> [root@natr76-utrs-dgm20tofnmlevelsecha-r7-1 ~]# systemctl status
> rpcbind.service
> ● rpcbind.service - RPC bind service
> Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; enabled;
> vendor preset: enabled)
> Active: failed (Result: exit-code) since Sun 2017-01-01 14:37:45 UTC;
> 20h ago
> Process: 31808 ExecStart=/sbin/rpcbind -w $RPCBIND_ARGS (code=exited,
> status=127)
> Main PID: 925 (code=exited, status=2)
>
> Jan 01 14:37:45 natr76-utrs-dgm20tofnmlevelsecha-r7-1 systemd[1]:
> Starting RPC bind service...
> Jan 01 14:37:45 natr76-utrs-dgm20tofnmlevelsecha-r7-1 rpcbind[31808]:
> /sbin/rpcbind: symbol lookup error: /sbin/rpcbind: undefined symbol:
> libtirpc_set_debug
> Jan 01 14:37:45 natr76-utrs-dgm20tofnmlevelsecha-r7-1 systemd[1]:
> rpcbind.service: control process exited, code=exited status=127
> Jan 01 14:37:45 natr76-utrs-dgm20tofnmlevelsecha-r7-1 systemd[1]: Failed
> to start RPC bind service.
> Jan 01 14:37:45 natr76-utrs-dgm20tofnmlevelsecha-r7-1 systemd[1]: Unit
> rpcbind.service entered failed state.
> Jan 01 14:37:45 natr76-utrs-dgm20tofnmlevelsecha-r7-1 systemd[1]:
> rpcbind.service failed.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)