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

[Support #MFF-300564]: TCP tuning for TIGGE tuning

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: [Support #MFF-300564]: TCP tuning for TIGGE tuning
  • Date: Thu, 29 Mar 2007 09:59:20 -0600
Manuel,

> YangXin has allowed me to login their system (Thanks!).
> Looking at the ldm log, I can see messages that don't seem very healthy:
> 
> Mar 29 10:38:48 tgn01 tigge-ldm.ecmwf.int[28268] ERROR: readtcp(): EOF
> on socket 4
> Mar 29 10:38:48 tgn01 tigge-ldm.ecmwf.int[28268] ERROR: one_svc_run():
> RPC layer closed connection
> Mar 29 10:38:48 tgn01 tigge-ldm.ecmwf.int[28268] ERROR: Disconnecting
> due to LDM failure; Connection to upstream LDM closed
> 
> Mar 29 10:39:11 tgn01 ultrazone.ucar.edu[28305] ERROR: readtcp(): EOF on
> socket 4
> Mar 29 10:39:11 tgn01 ultrazone.ucar.edu[28305] ERROR: one_svc_run():
> RPC layer closed connection
> Mar 29 10:39:11 tgn01 ultrazone.ucar.edu[28305] ERROR: Disconnecting due
> to LDM failure; Connection to upstream LDM closed

The error messages mean that a read on the socket returned due to an
end-of-file condition.  This means that the TCP layer decided that
the connection was broken.  Because the LDM uses TCP, there's
nothing that the LDM can do about this other than reconnect.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: MFF-300564
Department: Support IDD TIGGE
Priority: Normal
Status: Closed