[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[TIGGE #CUA-629523]: Re: dataportal not receiving data from tigge-ldm.ecmwf.int
- Subject: [TIGGE #CUA-629523]: Re: dataportal not receiving data from tigge-ldm.ecmwf.int
- Date: Thu, 13 Apr 2006 13:19:42 -0600
David,
> I can't reach tigge-ldm by any means.
>
> ldmping:
> $ ldmping tigge-ldm.ecmwf.int
> Apr 13 18:46:27 INFO: State Elapsed Port Remote_Host
> rpc_stat
> Apr 13 18:46:37 ERROR: H_CLNTED 10.006497 388 tigge-ldm.ecmwf.int
> select: RPC: Timed out
> Apr 13 18:47:12 ERROR: ADDRESSED 9.999620 0 tigge-ldm.ecmwf.int
> RPC: Timed out
> Apr 13 18:47:47 ERROR: NAMED 10.019453 0 tigge-ldm.ecmwf.int
> can't contact portmapper: RPC: Timed out
> Apr 13 18:48:22 ERROR: H_CLNTED 10.009302 388 tigge-ldm.ecmwf.int
> select: RPC: Timed out
> Apr 13 18:48:57 ERROR: ADDRESSED 9.999582 0 tigge-ldm.ecmwf.int
> RPC: Timed out
> Apr 13 18:49:32 ERROR: NAMED 10.019423 0 tigge-ldm.ecmwf.int
> can't contact portmapper: RPC: Timed out
> Apr 13 18:50:07 ERROR: SVC_UNAVAIL 9.999576 0
> tigge-ldm.ecmwf.int h_clnt_create(tigge-ldm.ecmwf.int): Timed out
> while creating connection
> Apr 13 18:50:32 ERROR: ADDRESSED 0.000006 0 tigge-ldm.ecmwf.int
> h_clnt_create(tigge-ldm.ecmwf.int): Timed out while creating
> connection
> Apr 13 18:51:07 ERROR: NAMED 10.019305 0 tigge-ldm.ecmwf.int
> can't contact portmapper: RPC: Timed out
>
> traceroute:
> traceroute tigge-ldm.ecmwf.int
> traceroute: Warning: Multiple interfaces found; using 128.117.12.2 @ ge1
> traceroute to tigge-ldm.ecmwf.int (193.61.196.74), 30 hops max, 40 byte
> packets
> 1 mlr-n12.ucar.edu (128.117.12.251) 0.376 ms 0.234 ms 0.223 ms
> 2 gin-n243-72.ucar.edu (128.117.243.73) 11.704 ms 0.711 ms 0.469 ms
> 3 frgp-gw-1.ucar.edu (128.116.254.250) 1.451 ms 1.377 ms 1.393 ms
> 4 192.43.217.130 (192.43.217.130) 1.505 ms 1.503 ms 1.523 ms
> 5 kscyng-dnvrng.abilene.ucaid.edu (198.32.8.14) 12.203 ms 22.868 ms
> 31.512 ms
> 6 iplsng-kscyng.abilene.ucaid.edu (198.32.8.80) 21.688 ms 21.423 ms
> 21.332 ms
> 7 chinng-iplsng.abilene.ucaid.edu (198.32.8.76) 25.406 ms 27.241 ms
> 32.783 ms
> 8 nycmng-chinng.abilene.ucaid.edu (198.32.8.83) 45.318 ms 49.575 ms
> 45.477 ms
> 9 198.32.11.51 (198.32.11.51) 88.964 ms 45.426 ms 45.440 ms
> 10 ny.uk1.uk.geant.net (62.40.96.170) 114.195 ms 114.065 ms 114.050
> ms
> 11 po2-0-0.gn2-gw1.ja.net (62.40.124.198) 113.978 ms 113.960 ms
> 113.901 ms
> 12 po1-1.lond-scr3.ja.net (146.97.35.97) 113.986 ms 114.101 ms
> 113.934 ms
> 13 po0-0.read-scr.ja.net (146.97.33.38) 115.168 ms 115.309 ms
> 115.165 ms
> 14 po2-0.read-bar4.ja.net (146.97.35.158) 115.293 ms 115.238 ms
> 115.262 ms
> 15 * * *
> 16 * *^Z
> Stopped (user)
>
> I believe that tigge-ldm has disabled ping, but for whatever reason it
> just returns:
> no answer from tigge-ldm.ecmwf.int
It looks like Tigge-ldm's subnet has become a "black hole": packets go in, but
they're never head from again.
Is there a network administrator over there with whom you can communicate?
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: CUA-629523
Department: Support IDD TIGGE
Priority: Normal
Status: On Hold