[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

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 #CUA-629523]: Re: dataportal not receiving data from tigge-ldm.ecmwf.int
  • Date: Thu, 13 Apr 2006 12:38:13 -0600
David,

> It appears that the TIGGE connection between tigge-ldm and dataportal
> has reverted to a
> state where the problem of a few days ago is recurring. The dataportal
> logs are again
> continuously reporting messages like:
> 
> Apr 13 17:43:59 dataportal tigge-ldm[15199] NOTE: nullproc_6 failure
> to tigge-ldm.ecmwf.int; RPC: Timed out
> Apr 13 17:43:59 dataportal tigge-ldm[15199] NOTE: LDM-6 desired
> product-class: 20060413164359.510 TS_ENDT {{ANY,
> "^z_tigge_c_ecmf.*\.grib:.*(13|33|53|73|93)$"}}
> 
> I am wondering if perhaps the number of streams might play a role in
> the stability of the system.
> Currently dataportal is setup (somewhat arbitrarily) with 20 streams.
> Is it possible that this is too many and
> occasionally causes problems given other fluctuations in the state of
> the network?

While the number of TCP connections can affect total throughput (some TCP 
implementations are affected this way) problems like the one you describe 
should, very definitely, be independent of the number of TCP connections.

What does a traceroute(1) show?  ping(1)?  ldmping(1)?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: CUA-629523
Department: Support IDD TIGGE
Priority: Normal
Status: On Hold