Technical article 126085

ERROR MESSAGE: "rpcbind: ERROR: could not find any loopback transport. Exiting", Error displayed during bootup and in syslog.

OpenServer 6.0.0

Written · Last revised

Problem

I see the message "rpcbind: ERROR: could not find any loopback transport. Exiting" during bootup and in syslog.

Neither RCP or NFS are not working properly.

The command `rpcinfo -p` fails with the error message:

rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused

Cause

This message indicates that the hostnames in the files: /etc/net/*/hosts does not match the current hostname.

This problem happens when the hostname is set outside of
the netconfig utility, with either `hostname` or `uname -S`.

Solution

To correct this problem you can either reset the hostname using the netconfig utility, when adding a network card, or manually edit the files:

/etc/net/ticots/hosts
/etc/net/ticlts/hosts
/etc/net/ticotsord/hosts

Also check to make certain that each file has the current hostname listed (twice).

<hostname> <hostname>
Similar to:
scosysv scosysv

In addition, check that there is the correct hostname entry in:

/etc/hosts
192.168.192.168  scosysv  scosysv.mydomain.com

Once the hostname is properly defined in the /etc/net/*/hosts files and /etc/hosts, you can restart RPC and NFS using:

nfs stop
rpcinit stop
rpcinit start
nfs start

From the Xinuos technical article database, record 126085. Reproduced with permission. The original is at www.sco.com/ta/126085, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.