[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #ISK-264773]: RCP Connection Timeout

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #ISK-264773]: RCP Connection Timeout
  • Date: Tue, 07 Feb 2017 12:57:05 -0700
Robert,

On the system on which rpcinfo(1) doesn't show the LDM, is the file
"~ldm/bin/ldmd" owned by root and setuid?

> Yeah, rpcbind is definitely running on both servers (the one that works and 
> the one that doesn't work).
> 
> On the server that works, rpcinfo returns:
> 
> program version netid     address                service    owner
> 100000    4    tcp6      ::.0.111               portmapper superuser
> 100000    3    tcp6      ::.0.111               portmapper superuser
> 100000    4    udp6      ::.0.111               portmapper superuser
> 100000    3    udp6      ::.0.111               portmapper superuser
> 100000    4    tcp       0.0.0.0.0.111          portmapper superuser
> 100000    3    tcp       0.0.0.0.0.111          portmapper superuser
> 100000    2    tcp       0.0.0.0.0.111          portmapper superuser
> 100000    4    udp       0.0.0.0.0.111          portmapper superuser
> 100000    3    udp       0.0.0.0.0.111          portmapper superuser
> 100000    2    udp       0.0.0.0.0.111          portmapper superuser
> 100000    4    local     /var/run/rpcbind.sock  portmapper superuser
> 100000    3    local     /var/run/rpcbind.sock  portmapper superuser
> 100024    1    udp       0.0.0.0.219.178        status     29
> 100024    1    tcp       0.0.0.0.206.245        status     29
> 100024    1    udp6      ::.214.208             status     29
> 100024    1    tcp6      ::.135.101             status     29
> 300029    6    tcp       0.0.0.0.1.132          ldmd       superuser
> 300029    5    tcp       0.0.0.0.1.132          ldmd       superuser
> 
> On the server that DOES NOT work, rpcinfo returns:
> 
> program version netid     address                service    owner
> 100000    4    tcp6      ::.0.111               portmapper superuser
> 100000    3    tcp6      ::.0.111               portmapper superuser
> 100000    4    udp6      ::.0.111               portmapper superuser
> 100000    3    udp6      ::.0.111               portmapper superuser
> 100000    4    tcp       0.0.0.0.0.111          portmapper superuser
> 100000    3    tcp       0.0.0.0.0.111          portmapper superuser
> 100000    2    tcp       0.0.0.0.0.111          portmapper superuser
> 100000    4    udp       0.0.0.0.0.111          portmapper superuser
> 100000    3    udp       0.0.0.0.0.111          portmapper superuser
> 100000    2    udp       0.0.0.0.0.111          portmapper superuser
> 100000    4    local     /var/run/rpcbind.sock  portmapper superuser
> 100000    3    local     /var/run/rpcbind.sock  portmapper superuser
> 100024    1    udp       0.0.0.0.212.181        status     29
> 100024    1    tcp       0.0.0.0.201.153        status     29
> 100024    1    udp6      ::.193.11              status     29
> 100024    1    tcp6      ::.144.59              status     29

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ISK-264773
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.