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

[LDM #AET-991057]: LDM 6.4.4: upstream connection closed for unknown reason

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: [LDM #AET-991057]: LDM 6.4.4: upstream connection closed for unknown reason
  • Date: Tue, 04 Apr 2006 10:25:05 -0600
Robert,

> The same errors occur even with the hub out of the loop.  I also installed 
> the same beta version of LDM on a Linux box as is on psnldm..and switched the 
> feed to that box.  I get the same exact error, and have the same missing 
> chunks of data.  I have our machine in New Mexico getting data from 
> idd.unidata.ucar.edu as a test.  Even though latencies in the CONDUIT feed 
> are about 5 minutes greater than in Palestine (30 min. vs. 35 minutes) that 
> machine gets each forecast hour and all parameters with no errors.  The 
> difference is that in New Mexico it is connected to a single T1 on the NASA 
> network.  Here we were forced to move to a Sprint commercial line (dual 
> T-1's).  I am beginning to wonder if the Sprint commercial networm is the 
> problem.  If it is, then this is hopeless as we were kicked off the NASA line 
> due to our bandwidth usage.
> 
> May have to go to some fort of ftp.

Is the LDM on host Psnldm getting the same CONDUIT data-products from a single, 
upstream LDM or from multiple, upstream LDM-s?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: AET-991057
Department: Support LDM
Priority: High
Status: On Hold