[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20020103: Meaning of a ldmd.log statement and need for alternatefailover site
- Subject: Re: 20020103: Meaning of a ldmd.log statement and need for alternatefailover site
- Date: Thu, 3 Jan 2002 12:42:50 -0700 (MST)
HI James,
All looks in order, even the traceroute to sunny89.
After you are connected to sunny89 for a period of time (say a couple of
hours) are you still seeing the one hour latency?
As the LDM re-starts it will begin looking for data an hour old, or less,
and fill your queue until it catches up...so if you were off of aeolus for
an hour, we would expect to see hour latencies for awhile until your
machine got current. How often are you running ldmfail out of cron..or
are you?
Thanks,
-Jeff
____________________________ _____________________
Jeff Weber address@hidden
Unidata Support PH:303-497-8676
NWS-COMET Case Study Library FX:303-497-8690
University Corp for Atmospheric Research 3300 Mitchell Ln
http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000
________________________________________ ______________________
On Thu, 3 Jan 2002, James Murakami wrote:
> Jeff Weber wrote:
>
> > HI James,
> >
> > The message:
> >
> > > Jan 03 07:40:31 typhoon ldmping[5522]: SVC_UNAVAIL 29.995430 0
> > > aeolus.ucsd.edu h_clnt_create(aeolus.ucsd.edu): Timed out while
> >
> > Indicates the ldm on aeolus is not running, and your ldm timed out after
> > not being able to make a connection..
> >
> > I continue to be amazed at your hour of latency coming from Washington,
> > their products are timely, and you seem to have a good connection...most
> > peculiar. I am in agreement with you that this would necessitate a new
> > failover, or more diagnosis as to why Wash is so slow to you, other feeds
> > from Wash do not experience this.
> >
> > Please perform traceroutes to both:
> >
> > sunny89.atmos.washington.edu
> >
> > and
> >
> > nimbus.atmo.arizona.edu
> >
> > and attach them in an e-mail back to me please..
> >
> > Thank you,
> >
> > PS : perhaps you could also attach your ldmd.conf file as well..thanks
> >
> > -Jeff
> > ____________________________ _____________________
> > Jeff Weber address@hidden
> > Unidata Support PH:303-497-8676
> > NWS-COMET Case Study Library FX:303-497-8690
> > University Corp for Atmospheric Research 3300 Mitchell Ln
> > http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000
> > ________________________________________ ______________________
> >
>
> Jeff,
>
> I have attached a copy of the ldmd.conf (for Sunny89).
> The traceroute for Sunny89 and Nimbus follow (taken at 1825 UTC):
>
> > traceroute sunny89.atmos.washington.edu
> traceroute to sunny89.atmos.washington.edu (128.95.89.38), 30 hops max, 40
> byte
> packets
> 1 psnet-ms77.atmos.ucla.edu (128.97.77.231) 1 ms 1 ms 1 ms
> 2 164.67.160.1 (164.67.160.1) 1 ms 2 ms 2 ms
> 3 cbn5-ci7200-1msa.cbn.ucla.edu (169.232.3.1) 2 ms 1 ms 1 ms
> 4 gsr-cbn5.calren2.ucla.edu (169.232.1.17) 2 ms 2 ms 2 ms
> 5 ISI--UCLA.POS.calren2.net (198.32.248.29) 3 ms 2 ms 3 ms
> 6 USC--ISI.POS.calren2.net (198.32.248.25) 3 ms 3 ms 2 ms
> 7 Abilene--USC.ATM.calren2.net (198.32.248.86) 3 ms 3 ms 4 ms
> 8 scrm-losa.abilene.ucaid.edu (198.32.8.17) 10 ms 10 ms 11 ms
> 9 sttl-snva.abilene.ucaid.edu (198.32.8.9) 28 ms 29 ms 29 ms
> 10 hnsp1-wes-so-5-0-0-0.pnw-gigapop.net (198.48.91.77) 29 ms 28 ms 29 ms
> 11 uwbr2-GE0-0.cac.washington.edu (198.107.150.52) 29 ms 29 ms 28 ms
> 12 dustbuster-V23.cac.washington.edu (140.142.153.2) 30 ms 29 ms 29 ms
> 13 sunny.atmos.washington.edu (128.95.89.38) 29 ms 29 ms 29 ms
>
> > traceroute nimbus.atmo.arizona.edu
> traceroute to nimbus.atmo.arizona.edu (128.196.30.175), 30 hops max, 40 byte
> packets
> 1 psnet-ms77.atmos.ucla.edu (128.97.77.231) 1 ms 1 ms 1 ms
> 2 164.67.160.1 (164.67.160.1) 1 ms 1 ms 2 ms
> 3 cbn5-ci7200-1msa.cbn.ucla.edu (169.232.3.1) 1 ms 2 ms 1 ms
> 4 gsr-cbn5.calren2.ucla.edu (169.232.1.17) 2 ms 2 ms 1 ms
> 5 ISI--UCLA.POS.calren2.net (198.32.248.29) 2 ms 2 ms 2 ms
> 6 USC--ISI.POS.calren2.net (198.32.248.25) 3 ms 3 ms 2 ms
> 7 Abilene--USC.ATM.calren2.net (198.32.248.86) 3 ms 3 ms 3 ms
> 8 scrm-losa.abilene.ucaid.edu (198.32.8.17) 11 ms 10 ms 10 ms
> 9 dnvr-snva.abilene.ucaid.edu (198.32.8.2) 35 ms 35 ms 35 ms
> 10 virgil-pos6-0-0.telcom.arizona.edu (192.80.43.21) 53 ms 54 ms 53 ms
> 11 tuco-fa9-1-virgil.telcom.arizona.edu (192.80.43.33) 53 ms 53 ms 53 ms
> 12 woody-vl911-tuco.telcom.arizona.edu (192.80.43.26) 54 ms 55 ms 54 ms
> 13 bullseye-vlan996-woody.telcom.Arizona.EDU (150.135.250.14) 54 ms 53 ms
> 53
> ms
> 14 nimbus.atmo.arizona.edu (128.196.30.175) 54 ms 54 ms 53 ms
>
> As of this writing, we're still "catching up" on data (hour latency).
> If we weren't missing so much model output and some mcidas products, the hour
> delay isn't that bad.
>
> James
>
> --------------------------------------
> James Murakami
> Staff Meteorologist/Student Affairs
> Department of Atmospheric Sciences
> University of California, Los Angeles
> 405 Hilgard Ave.
> Los Angeles, CA 90095-1565
>
>
> e-mail: address@hidden
> telephone: 310-825-2418
> Fax: 310-206-5219
> ---------------------------------------
>
>