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

[TIGGE #YIO-560538]: Reuse CONDUIT scripts in TIGGE

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: [TIGGE #YIO-560538]: Reuse CONDUIT scripts in TIGGE
  • Date: Mon, 10 Apr 2006 15:50:07 -0600
David,

> I am mystified why the dataportal LDM seems not to have received any
> data from
> tigge-ldm.ecmwf.int since about 22 hours UTC on the 9th. Judging from
> the web stats pages,
> tigge-ldm is producing data, but from dataportal currently I cannot
> successfully do an
> ldmping or contact tigge-ldm in any way.
> The dataportal ldm logfile has been producing endless iterations of
> 
> Apr 10 21:00:21 dataportal tigge-ldm[5142] NOTE: nullproc_6 failure to
> tigge-ldm.ecmwf.int; RPC: Timed out
> Apr 10 21:00:21 dataportal tigge-ldm[5142] NOTE: LDM-6 desired
> product-class: 20060410200021.383 TS_ENDT {{ANY,
> "^z_tigge_c_ecmf.*\.grib:.*(02|22|42|62|82)$"}}
> Apr 10 21:00:25 dataportal tigge-ldm[5144] NOTE: nullproc_6 failure to
> tigge-ldm.ecmwf.int; RPC: Timed out
> Apr 10 21:00:25 dataportal tigge-ldm[5144] NOTE: LDM-6 desired
> product-class: 20060410200025.103 TS_ENDT {{ANY,
> "^z_tigge_c_ecmf.*\.grib:.*(04|24|44|64|84)$"}}
> Apr 10 21:00:26 dataportal tigge-ldm[5147] NOTE: nullproc_6 failure to
> tigge-ldm.ecmwf.int; RPC: Timed out
> Apr 10 21:00:26 dataportal tigge-ldm[5147] NOTE: LDM-6 desired
> product-class: 20060410200026.973 TS_ENDT {{ANY,
> "^z_tigge_c_ecmf.*\.grib:.*(07|27|47|67|87)$"}}
> 
> Any know what's going on?
> -dave

The LDM log messages are consistent with the inability to an ldmping(1)  (or 
even a ping(1)?) on host Dataportal to host tigge-ldm.ecmwf.int.  This could be 
a routing problem or a firewall problem.  We suggest that you try a 
traceroute(1) to tigge-ldm.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: YIO-560538
Department: Support IDD TIGGE
Priority: Normal
Status: On Hold