RE: 20060221: 20060216: problems with CONDUIT feed from idd.unidata.ucar.edu

Robert,

Your latencies on the CONDUIT feed are really bad. I did some
pings and at best you are 80ms to idd.unidata.ucar.edu, and
as bad as 120ms.

http://www.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?CONDUIT+newpsn.balloonfacility.org

I believe that you see data ending at 39 hours because at that
point you have fallen so far bahind, that the data is no longer in
the queue (which can hold 3-4 hours on our end).

The data set you are trying to receive is about 1.3GB, which is probably going to
require a data rate of 2 T-1's. Do you know what your capacity is?
We tried a few pings from closer IDD sites, slightly better than idd.unidata,
but still about 60ms.

You might try splitting your requests into several again to see if that helps,
but if your pipe is saturated, then trying to get that much data through is
probably not going to be satisfactory.

Steve Chiswell
Unidata User Support

>From: "Robert Mullenax" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200602211720.k1LHKnO7026346

>This is a multi-part message in MIME format.
>
>------_=_NextPart_001_01C6370B.2CBADED0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
>Steve,
>
>At least here nslookup shows that both forward and reverse DNS are =
>working now yet we still are having issues, although not a total lack of =
>data like before. We got 39 hours worth of the Global 1x1 GFS and then =
>it stopped and the log shows:
>
>Feb 21 17:16:28 newpsn idd[5918]: Upstream LDM is willing to feed
>Feb 21 17:17:05 newpsn idd[5918]: ERROR: requester6.c:206: Connection to =
>upstream LDM closed
>Feb 21 17:17:35 newpsn idd[5918]: Desired product class: =
>20060221154207.716 TS_ENDT {{CONDUIT, "MT\.gfs.*DF.gr1"}}
>Feb 21 17:17:36 newpsn idd[5918]: Connected to upstream LDM-6
>Feb 21 17:17:36 newpsn idd[5918]: Upstream LDM is willing to feed
>
>Any ideas?
>
>Thanks,
>Robert Mullenax
>
>
>
>
>-----Original Message-----
>From: Unidata Support [mailto:address@hidden]
>Sent: Thu 2/16/2006 12:48 PM
>To: Robert Mullenax
>Cc: address@hidden
>Subject: 20060216: problems with CONDUIT feed from idd.unidata.ucar.edu=20
>=20
>
>Robert,
>
>There appears to be a name service problem (I believe on your end).
>Your machine is connecting here as:
>host93.balloonfacility.org
>rather than=20
>newpsn.balloonfacility.org
>
>I can't reverse lookup "host93" on other machines as well as the =
>idd.unidata host.
>
>There are 150 other downstreams on the node that are sucessfully =
>resolved on uni4.
>I'll ask our Sys-admins for suggestions.
>
>Steve Chiswell
>Unidata User Support
>
>
>>From: "Robert Mullenax" <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200602161652.k1GGqGO7012285
>
>>This is a multi-part message in MIME format.
>>
>>------_=3D_NextPart_001_01C63319.5BFB4752
>>Content-Type: text/plain;
>> charset=3D"iso-8859-1"
>>Content-Transfer-Encoding: quoted-printable
>>
>>
>>We got things switched over and I got about 48 hours worth of the GFS =
>=3D
>>from CONDUIT this morning and then it stopped. I see this in my =3D
>>ldmd.log:
>>
>>Feb 16 16:47:43 newpsn idd[5918]: ERROR: requester6.c:206: Connection =
>to =3D
>>upstream LDM closed
>>Feb 16 16:48:13 newpsn idd[5918]: Desired product class: =3D
>>20060216154848.718 TS_ENDT {{CONDUIT, "MT\.gfs.*DF.gr1"}}
>>Feb 16 16:48:13 newpsn idd[5918]: Connected to upstream LDM-6
>>
>>This repeats over and over. I am connecting to idd.unidata.ucar.edu. =
>=3D
>>Any ideas?
>>
>>Thanks,
>>Robert Mullenax
>>NMSU/CSBF
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>------_=3D_NextPart_001_01C63319.5BFB4752
>>Content-Type: text/html;
>> charset=3D"iso-8859-1"
>>Content-Transfer-Encoding: quoted-printable
>>
>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
>><HTML>
>><HEAD>
>><META HTTP-EQUIV=3D3D"Content-Type" CONTENT=3D3D"text/html; =3D
>>charset=3D3Diso-8859-1">
>><META NAME=3D3D"Generator" CONTENT=3D3D"MS Exchange Server version =3D
>>6.5.7638.1">
>><TITLE>problems with CONDUIT feed from idd.unidata.ucar.edu</TITLE>
>></HEAD>
>><BODY>
>>
>> 
>>
>>We got things switched over and I got about 48 =
>hours =3D
>>worth of the GFS from CONDUIT this morning and then it stopped.  I =
>=3D
>>see this in my ldmd.log: 
>> 
>>Feb 16 16:47:43 newpsn idd[5918]: ERROR: requester6.c:206: Connection =
>to =3D
>>upstream LDM closed 
>>Feb 16 16:48:13 newpsn idd[5918]: Desired product class: =3D
>>20060216154848.718 TS_ENDT {{CONDUIT,  =3D
>>"MT\.gfs.*DF.gr1"}} 
>>Feb 16 16:48:13 newpsn idd[5918]: Connected to upstream LDM-6 
>> 
>>This repeats over and over.  I am connecting to =3D
>>idd.unidata.ucar.edu.  Any ideas? 
>> 
>>Thanks, 
>>Robert Mullenax 
>>NMSU/CSBF 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>>
>></BODY>
>></HTML>
>>------_=3D_NextPart_001_01C63319.5BFB4752--
>>
>--
>*************************************************************************=
>*** <
>Unidata User Support UCAR Unidata =
>Program <
>(303)497-8643 P.O. Box =
>3000 <
>address@hidden Boulder, CO =
>80307 <
>-------------------------------------------------------------------------=
>--- <
>Unidata WWW Service =
>http://my.unidata.ucar.edu/content/support <
>-------------------------------------------------------------------------=
>--- <
>NOTE: All email exchanges with Unidata User Support are recorded in the
>Unidata inquiry tracking system and then made publicly available
>through the web. If you do not want to have your interactions made
>available in this way, you must let us know in each email you send to =
>us.
>
>
>------_=_NextPart_001_01C6370B.2CBADED0
>Content-Type: text/html;
> charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
><HTML>
><HEAD>
><META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
>charset=3Diso-8859-1">
><META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
>6.5.7638.1">
><TITLE>RE: 20060216: problems with CONDUIT feed from =
>idd.unidata.ucar.edu </TITLE>
></HEAD>
><BODY>
>
>
>Steve, 
> 
>At least here nslookup shows that both forward and reverse DNS are =
>working now yet we still are having issues, although not a total lack of =
>data like before.  We got 39 hours worth of the Global 1x1 GFS and =
>then it stopped and the log shows: 
> 
>Feb 21 17:16:28 newpsn idd[5918]: Upstream LDM is willing to feed 
>Feb 21 17:17:05 newpsn idd[5918]: ERROR: requester6.c:206: Connection to =
>upstream LDM closed 
>Feb 21 17:17:35 newpsn idd[5918]: Desired product class: =
>20060221154207.716 TS_ENDT {{CONDUIT,  =
>"MT\.gfs.*DF.gr1"}} 
>Feb 21 17:17:36 newpsn idd[5918]: Connected to upstream LDM-6 
>Feb 21 17:17:36 newpsn idd[5918]: Upstream LDM is willing to feed 
> 
>Any ideas? 
> 
>Thanks, 
>Robert Mullenax 
> 
> 
> 
> 
>-----Original Message----- 
>From: Unidata Support [<A =
>HREF="" href="mailto:address@hidden">mailto:address@hidden">mailto:address@hidden<=
>/A>] 
>Sent: Thu 2/16/2006 12:48 PM 
>To: Robert Mullenax 
>Cc: address@hidden 
>Subject: 20060216: problems with CONDUIT feed from =
>idd.unidata.ucar.edu 
> 
> 
>Robert, 
> 
>There appears to be a name service problem (I believe on your end). 
>Your machine is connecting here as: 
>host93.balloonfacility.org 
>rather than 
>newpsn.balloonfacility.org 
> 
>I can't reverse lookup "host93" on other machines as well as =
>the idd.unidata host. 
> 
>There are 150 other downstreams on the node that are sucessfully =
>resolved on uni4. 
>I'll ask our Sys-admins for suggestions. 
> 
>Steve Chiswell 
>Unidata User Support 
> 
> 
>>From: "Robert Mullenax" =
><address@hidden> 
>>Organization: UCAR/Unidata 
>>Keywords: 200602161652.k1GGqGO7012285 
> 
>>This is a multi-part message in MIME format. 
>> 
>>------_=3D_NextPart_001_01C63319.5BFB4752 
>>Content-Type: text/plain; 
>>       =
>charset=3D"iso-8859-1" 
>>Content-Transfer-Encoding: quoted-printable 
>> 
>> 
>>We got things switched over and I got about 48 hours worth of the =
>GFS =3D 
>>from CONDUIT this morning and then it stopped.  I see this in =
>my =3D 
>>ldmd.log: 
>> 
>>Feb 16 16:47:43 newpsn idd[5918]: ERROR: requester6.c:206: =
>Connection to =3D 
>>upstream LDM closed 
>>Feb 16 16:48:13 newpsn idd[5918]: Desired product class: =3D 
>>20060216154848.718 TS_ENDT {{CONDUIT,  =
>"MT\.gfs.*DF.gr1"}} 
>>Feb 16 16:48:13 newpsn idd[5918]: Connected to upstream LDM-6 
>> 
>>This repeats over and over.  I am connecting to =
>idd.unidata.ucar.edu.  =3D 
>>Any ideas? 
>> 
>>Thanks, 
>>Robert Mullenax 
>>NMSU/CSBF 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>------_=3D_NextPart_001_01C63319.5BFB4752 
>>Content-Type: text/html; 
>>       =
>charset=3D"iso-8859-1" 
>>Content-Transfer-Encoding: quoted-printable 
>> 
>><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML =
>3.2//EN"> 
>><HTML> 
>><HEAD> 
>><META HTTP-EQUIV=3D3D"Content-Type" =
>CONTENT=3D3D"text/html; =3D 
>>charset=3D3Diso-8859-1"> 
>><META NAME=3D3D"Generator" CONTENT=3D3D"MS =
>Exchange Server version =3D 
>>6.5.7638.1"> 
>><TITLE>problems with CONDUIT feed from =
>idd.unidata.ucar.edu</TITLE> 
>></HEAD> 
>><BODY> 
>> 
>> 
>> 
>>We got things switched over and I =
>got about 48 hours =3D 
>>worth of the GFS from CONDUIT this morning and then it =
>stopped.&nbsp; I =3D 
>>see this in my ldmd.log: 
>> 
>>Feb 16 16:47:43 newpsn idd[5918]: ERROR: requester6.c:206: =
>Connection to =3D 
>>upstream LDM closed 
>>Feb 16 16:48:13 newpsn idd[5918]: Desired product class: =3D 
>>20060216154848.718 TS_ENDT {{CONDUIT,&nbsp; =3D 
>>&quot;MT\.gfs.*DF.gr1&quot;}} 
>>Feb 16 16:48:13 newpsn idd[5918]: Connected to upstream =
>LDM-6 
>> 
>>This repeats over and over.&nbsp; I am connecting to =3D 
>>idd.unidata.ucar.edu.&nbsp; Any ideas? 
>> 
>>Thanks, 
>>Robert Mullenax 
>>NMSU/CSBF 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>></BODY> 
>></HTML> 
>>------_=3D_NextPart_001_01C63319.5BFB4752-- 
>> 
>-- 
>*************************************************************************=
>*** < 
>Unidata User =
>Support           =
>            &=
>nbsp;            =
>UCAR Unidata Program < 
>(303)497-8643          =
>            &=
>nbsp;           &n=
>bsp;           &nb=
>sp;   P.O. Box 3000 < 
>address@hidden        &=
>nbsp;           &n=
>bsp;           &nb=
>sp;  Boulder, CO 80307 < 
>-------------------------------------------------------------------------=
>--- < 
>Unidata WWW =
>Service           =
>   <A =
>HREF="" href="http://my.unidata.ucar.edu/content/support">http://my.unidata.ucar.edu/content/support">http://my.unidata.uca=
>r.edu/content/support</A>  < 
>-------------------------------------------------------------------------=
>--- < 
>NOTE: All email exchanges with Unidata User Support are recorded in =
>the 
>Unidata inquiry tracking system and then made publicly available 
>through the web.  If you do not want to have your interactions =
>made 
>available in this way, you must let us know in each email you send to =
>us. 
> 
>
>
>
></BODY>
></HTML>
>------_=_NextPart_001_01C6370B.2CBADED0--
>
--
**************************************************************************** <
Unidata User Support UCAR Unidata Program <
(303)497-8643 P.O. Box 3000 <
address@hidden Boulder, CO 80307 <
---------------------------------------------------------------------------- <
Unidata WWW Service http://my.unidata.ucar.edu/content/support <
---------------------------------------------------------------------------- <
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web. If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.