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

Re: 20001003: Can't Contact Portmapper Problem

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: Re: 20001003: Can't Contact Portmapper Problem
  • Date: Tue, 3 Oct 2000 16:07:52 -0600 (MDT)
On Tue, 3 Oct 2000, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >From: "Ken Waters" <address@hidden>
> >Subject: Can't Contact Portmapper Problem
> >Organization: UCAR/Unidata
> >Keywords: 200010031806.e93I6Wb25056
> 
> This is a multi-part message in MIME format.
> --------------51E214D1D703F799F0502279
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> Hello again,
> 
> Once again I am befuddled with the mysterious "FEEDME: Can't contact
> portmapper: RPC: Timed out" error.  What exactly does this error mean
> and what can I do to resolve the problem?
> 
> I scoured through your online archives and searched for portmapper.  I
> found several other instances where people were having this error in
> their log files, but I wasn't able to find what the fix is for it.

Ken,

Look at message http://www.unidata.ucar.edu/glimpse/ldm/3670.  Ask your
sysadmin if port 111 is open and if the portmapper is running on run-time
level 3 on the remote machine.  One could also test the remote machine if
it can contact your machine via ldmping. 

Robb...

> 
> We are running version 5.1.2 of LDM on a Redhat 6.2 Linux box.  I
> continue to supect a firewall problem but our network specialist says it
> couldn't be.
> 
> I hope you can help me. I have attached a copy of my ldmd.log file as
> well as the output from the "rpcinfo -p" command.   Thanks!
> 
> Ken
> 
> 
> --------------51E214D1D703F799F0502279
> Content-Type: text/plain; charset=us-ascii;
>  name="ldmd.log"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline;
>  filename="ldmd.log"
> 
> Oct 03 15:32:44 wwwldm rpc.ldmd[12020]: Starting Up (built: Sep  6 2000 
> 06:48:45) 
> Oct 03 15:32:45 wwwldm 192.168.2.12[12022]: run_requester: Starting Up: 
> 192.168.2.12 
> Oct 03 15:32:45 wwwldm 192.168.2.12[12022]: run_requester: 20001003143245.077 
> TS_ENDT {{AFOS,  ".*"}} 
> Oct 03 15:32:45 wwwldm pqact[12021]: Starting Up 
> Oct 03 15:32:47 wwwldm localhost[12030]: Connection from 
> localhost.localdomain 
> Oct 03 15:32:47 wwwldm localhost[12030]: Connection reset by peer 
> Oct 03 15:32:47 wwwldm localhost[12030]: Exiting 
> Oct 03 15:33:10 wwwldm 192.168.2.12[12022]: FEEDME(192.168.2.12): can't 
> contact portmapper: RPC: Timed out 
> 
> --------------51E214D1D703F799F0502279
> Content-Type: text/plain; charset=us-ascii;
>  name="rpcinfo.txt"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline;
>  filename="rpcinfo.txt"
> 
>    program vers proto   port
>     100000    2   tcp    111  portmapper
>     100000    2   udp    111  portmapper
>     100021    1   udp   1024  nlockmgr
>     100021    3   udp   1024  nlockmgr
>     100021    1   tcp   1024  nlockmgr
>     100021    3   tcp   1024  nlockmgr
>     100024    1   udp    964  status
>     100024    1   tcp    966  status
>     300029    5   tcp    388  ldmd
>     300029    4   tcp    388  ldmd
> 
> --------------51E214D1D703F799F0502279--
> 
> 
> ------- End of Forwarded Message
> 

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================