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

20010910: cant get data from ARM sites

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: 20010910: cant get data from ARM sites
  • Date: Tue, 11 Sep 2001 16:49:16 -0600
>From: Teresa Van Hove <address@hidden>
>Organization: GST
>Keywords: 200109110136.f8B1aR120890 LDM portmapper

Teresa,

>Do you have any thoughts on why there might be portmapper problems
>for the ARM sites? I get the following error message in the
>ldmd.log 
>
>
>Sep 11 01:03:36 suomildm1 198.124.97.216[23794]:
>FEEDME(198.124.97.216): can't contact portmapper: RPC: Timed out. 

This indicates that the LDM can't contact the portmapper on your system,
not the remote one.  If it is a solaris system, then check to make sure
that nsbind is running.  When all else fails, try rebooting your machine.

>I ran traceroute from here to both of these sites and get the
>following
>
>traceroute to 198.124.99.58 (198.124.99.58), 30 hops max, 40 byte
>packets
> 1  flra-n29 (128.117.29.252)  0.507 ms  0.212 ms  0.201 ms
> 2  vbnsr-n2.ucar.edu (128.117.2.252)  0.674 ms  0.722 ms  0.660 ms
> 3  internetr-n243-104.ucar.edu (128.117.243.106)  1.018 ms  0.636
>ms  0.809 ms
> 4  denv-abilene.ucar.edu (128.117.243.126)  1.889 ms  1.785 ms 
>1.824 ms
> 5  kscy-dnvr.abilene.ucaid.edu (198.32.8.14)  12.995 ms  12.507 ms 
>12.176 ms
> 6  ipls-kscy.abilene.ucaid.edu (198.32.8.6)  21.596 ms  21.494 ms 
>21.422 ms
> 7  chicago-abilene.es.net (198.124.254.169)  26.228 ms  26.089 ms 
>26.499 ms
> 8  nyc-s-chi.es.net (134.55.205.105)  45.888 ms  45.846 ms  46.175
>ms
> 9  orn-s-nyc.es.net (134.55.205.110)  87.192 ms  87.355 ms  86.773
>ms
>10  ornl-orn.es.net (134.55.208.62)  105.702 ms  106.240 ms  106.259
>ms
>11  lamont-ornl3.es.net (198.124.254.154)  142.050 ms  142.208 ms 
>140.863 ms
>12  198.124.99.58 (198.124.99.58)  141.323 ms  140.914 ms  140.691
>ms
>
>But it actually takes up to a minute or more of actual time for step
>11 to 12 to happen.  (Same thing for 198.128.97.216)  
>
>I think this might be too long for ldm (or possibly too long for
>some system setting on suomildm1) so it times out before the
>connection is established.
>
>Thanks for any thoughts on solving this, 

Tom Yoksas