Actions
Bug #5631
closedrpcinfo(1M) is unable to connect to localhost
Start date:
2015-02-16
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:
Description
The rpcinfo(1M) is unable to connect to localhost over TCP or UDP in a case the host parameter is not specified and the machine's hostname is not resolvable:
# hostname test # getent hosts test # rpcinfo -p rpcinfo: test: n2a: hostname not found # rpcinfo -T tcp rpcinfo: can't contact rpcbind: RPC: Name to address translation failed - n2a: hostname not found # rpcinfo -T udp rpcinfo: can't contact rpcbind: RPC: Name to address translation failed - n2a: hostname not found #
To fix this, we should change rpcinfo(1M) to explicitly connect to localhost, instead of obtaining the hostname of the localhost, resolve it, and then attemp to connect to it.
Updated by Marcel Telka over 7 years ago
- Status changed from In Progress to Pending RTI
Updated by Electric Monk over 7 years ago
- Status changed from Pending RTI to Closed
- % Done changed from 0 to 100
git commit 20d0ade92f2ccd1095364cf9ca5807ad3dee6081
commit 20d0ade92f2ccd1095364cf9ca5807ad3dee6081 Author: Marcel Telka <marcel.telka@nexenta.com> Date: 2015-02-19T19:17:35.000Z 5631 rpcinfo(1M) is unable to connect to localhost Reviewed by: Gordon Ross <gordon.w.ross@gmail.com> Reviewed by: Richard Elling <richard.elling@richardelling.com> Reviewed by: Josef 'Jeff' Sipek <josef.sipek@nexenta.com> Reviewed by: Bayard Bell <buffer.g.overflow@gmail.com> Approved by: Dan McDonald <danmcd@omniti.com>
Actions