[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[IDV #WDJ-710360]: nexradcomp data from motherlode
- Subject: [IDV #WDJ-710360]: nexradcomp data from motherlode
- Date: Sat, 23 Oct 2010 10:40:20 -0600
Hi Bill,
Tom here...
I just wanted to jump in to let you know that there were problems
with the THREDDS server on motherlode.ucar.edu yesterday for a good
fraction of the morning (our time). The problems you ran into
might have been a result of those THREDDS problems.
If this sort of thing happens in the future, please check data
access via an ADDE server on motherlode (the Imagery tab in the
IDV). If that is working fine, then the problem could be something
happening with THREDDS; if it also does not work, the problem may
be something more general with motherlode, or with the network
connection between your machine and motherlode.
Cheers,
Tom
> I've been trying a few things, and I might be on to something.
>
> When I request the radar composite data from motherlode, I get the
> connection timeout message about half the time. If I request these
> data from thredds.cise-nsf.gov, I do not get the message.
>
> Next, I tried pinging the 2 servers.
>
> C:\Documents and Settings\Bill>ping motherlode.ucar.edu
>
> Pinging motherlode.ucar.edu [128.117.114.119] with 32 bytes of data:
>
> Reply from 128.117.114.119: bytes=32 time=101ms TTL=241
> Reply from 128.117.114.119: bytes=32 time=101ms TTL=241
> Reply from 128.117.114.119: bytes=32 time=101ms TTL=241
> Reply from 128.117.114.119: bytes=32 time=101ms TTL=241
>
> Ping statistics for 128.117.114.119:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 101ms, Maximum = 101ms, Average = 101ms
>
> C:\Documents and Settings\Bill>ping thredds.cise-nsf.gov
>
> Pinging thredds.cise-nsf.gov [192.12.209.64] with 32 bytes of data:
>
> Reply from 192.12.209.64: bytes=32 time=63ms TTL=244
> Reply from 192.12.209.64: bytes=32 time=64ms TTL=244
> Reply from 192.12.209.64: bytes=32 time=63ms TTL=244
> Reply from 192.12.209.64: bytes=32 time=64ms TTL=244
>
> Ping statistics for 192.12.209.64:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 63ms, Maximum = 64ms, Average = 63ms
>
> I'm not an expert at communication, but it appears that responses
> from motherlode are longer than from nsf. And this is on a
> Saturday morning when business traffic should be low.
>
> Feeling brave, I did a tracert to motherlode:
>
> C:\Documents and Settings\Bill>tracert motherlode.ucar.edu
>
> Tracing route to motherlode.ucar.edu [128.117.114.119]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.0.1
> 2 37 ms 35 ms 33 ms 10.19.13.1
> 3 70 ms 34 ms 37 ms
> static-64-222-84-40.burl.east.myfairpoint.net [64.222.84.40]
> 4 48 ms 49 ms 49 ms POS4-0-1.GW16.NYC9.ALTER.NET
> [208.192.176.205]
> 5 49 ms 61 ms 49 ms 0.ge-3-0-0.XT1.NYC9.ALTER.NET
> [152.63.22.138]
> 6 49 ms 47 ms 49 ms 0.so-1-0-1.XL3.NYC4.ALTER.NET
> [152.63.0.213]
> 7 50 ms 48 ms 48 ms 0.ae3.BR3.NYC4.ALTER.NET [152.63.16.181]
> 8 67 ms 79 ms 49 ms te-7-3-0.edge2.NewYork2.level3.net
> [4.68.111.137]
> 9 50 ms 47 ms 49 ms vlan52.ebr2.NewYork2.Level3.net
> [4.69.138.254]
> 10 73 ms 69 ms 71 ms ae-2-2.ebr1.Chicago1.Level3.net
> [4.69.132.65]
> 11 71 ms 73 ms 72 ms ae-6-6.ebr1.Chicago2.Level3.net
> [4.69.140.190]
> 12 116 ms 106 ms 109 ms ae-3-3.ebr2.Denver1.Level3.net
> [4.69.132.61]
> 13 100 ms 101 ms 102 ms ge-9-2.hsa1.Denver1.Level3.net
> [4.68.107.163]
> 14 103 ms 101 ms 99 ms UNIVERSITY.hsa1.Denver1.Level3.net
> [209.245.16.54]
> 15 102 ms 101 ms 101 ms flra.ucar.edu [128.117.243.82]
> 16 101 ms 102 ms 103 ms motherlode.ucar.edu [128.117.114.119]
>
> Trace complete.
>
> At hop 12, the times jump up. So, what might this mean ?
>
> You might check communication east to my isp and see what shows up ?
>
> Bill
>
> On 10/18/2010 4:00 PM, Unidata IDV Support wrote:
> > Hi Bill
> >
> > Yuan and I are having trouble reproducing the connection problem.
> >
> > We were able to load your bundle and see
> >
> > + US Metar data
> > + Canadian Metar data
> > + Radar composite data
> >
> > (We are getting errors originating from not being able to load local
> > resource, e.g. C:\IdvWxIcon\radarColBar9.gif, but that is expected.)
> >
> > In order to better diagnosis this connection problem, do not use this
> > bundle, but start from a clean slate. Then try to load the radar composite
> > from the Unidata adde server. Are you seeing a connect problem? This test
> > will hopefully better isolate the problem.
> >
> >
> > Thanks.
> >
> > -Julien
> >
> >
> >> Julien,
> >>
> >> I don't believe it is. The metar data displayed fine, but the area file
> >> did not.
> >> The error message is: ERROR: connect
> >>
> >> Bill
> >>
> >> On 10/18/2010 1:59 PM, Unidata IDV Support wrote:
> >>> Hi Bill,
> >>>
> >>> We recently had some data server issues which we believe are resolved.
> >>>
> >>> Can you confirm that your expected data is present?
> >>>
> >>> Thanks.
> >>>
> >>> -Julien
> >>>
> >>>> Good morning,
> >>>>
> >>>> I think I need to describe my problem/symptoms in more detail, to help
> >>>> you
> >>>> zero in on the cause.
> >>>>
> >>>> I am trying to load a bundle, that worked fine until recently. It has
> >>>> several
> >>>> data sources, that include metars and nexradcomp data from motherlode.
> >>>> The metar data source occurs twice; one is used for US stations and
> >>>> the other is used for Canadian stations. Thus, I can filter each
> >>>> separately.
> >>>>
> >>>> The problem is that 'usually' 2 of the data sources appear and are
> >>>> displayed
> >>>> while the third is not. The omitted source varies! After it fails, I
> >>>> find error messages
> >>>> that include:
> >>>>
> >>>> error opening areafile: java.net.connection exception: connection timed
> >>>> out
> >>>>
> >>>> and
> >>>>
> >>>> error: reading point data
> >>>> problem accessing data
> >>>> visad.visadexception: problem accessing data
> >>>>
> >>>> So, each works okay some of the time, but rarely do all work at the same
> >>>> time.
> >>>>
> >>>> I hope this helps you, Bill
> >>>>
> >>>> On 10/17/2010 10:00 AM, Unidata IDV Support wrote:
> >>>>> address@hidden,
> >>>>>
> >>>>> Your Ticket has been received, and a Unidata staff member will review
> >>>>> it and reply accordingly. Listed below are details of this new Ticket.
> >>>>> Please make sure the Ticket ID remains in the Subject: line on all
> >>>>> correspondence related to this Ticket.
> >>>>>
> >>>>> Ticket ID: WDJ-710360
> >>>>> Subject: nexradcomp data from motherlode
> >>>>> Department: Support IDV
> >>>>> Priority: Normal
> >>>>> Status: Open
> >>>>>
> >>>>>
> >>>>>
> >>>>> Please let us know how we can assist you further.
> >>>>>
> >>>>> Unidata User Support
> >>>>>
> >>>>>
> >>>> --
> >>>> The Fingerhuts
> >>>> Saint Johnsbury, Vt, 05819
> >>>>
> >>>> email: address@hidden
> >>>>
> >>>>
> >>> Ticket Details
> >>> ===================
> >>> Ticket ID: WDJ-710360
> >>> Department: Support IDV
> >>> Priority: Normal
> >>> Status: Open
> >>>
> >>>
> >>
> >> --
> >> The Fingerhuts
> >> Saint Johnsbury, Vt, 05819
> >>
> >> email: address@hidden
> >>
> >>
> >
> > Ticket Details
> > ===================
> > Ticket ID: WDJ-710360
> > Department: Support IDV
> > Priority: Normal
> > Status: Open
> >
> >
>
>
> --
> The Fingerhuts
> Saint Johnsbury, Vt, 05819
>
> email: address@hidden
>
>
Cheers,
Tom
--
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
address@hidden Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: WDJ-710360
Department: Support IDV
Priority: Normal
Status: Open