Re: 20020103: Meaning of a ldmd.log statement and need for alternate failover site

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
________________________________________      ______________________

On Thu, 3 Jan 2002, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >cc: address@hidden
> >From: James Murakami <address@hidden>
> >Subject: Meaning of a ldmd.log statement
> >Organization: UCLA
> >Keywords: 200201031541.g03Ff5N07448 IDD failover ldmping
> 
> Hi,
> 
> Can someone tell me the meaning of the following line I saw
> in the ldmd.log file?
> 
> 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
> 
> 
> 
> We're currently failed over to U.of Washington (since 740 UTC) with the usual
> hour latency. I've seen "unable to connect" statements before, but the above
> statement is a first to me. 
> 
> Although we've had the occasional failover in past years, they mostly
> lasted only a hour or less. In recent months, they seem to last nearly
> 24 hours. UCSD has a new server running (Aeolus), and it seems to have
> cut down on switch overs. However, failing over is lasting longer than 
> in the past. Is there something we (our Dept) can do, or is this something
> we have to live with? Of course, if it means big expense, we'll just
> live with this occasional headache.
> 
> 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
> ---------------------------------------
> 
> 
> ------- End of Forwarded Message
> 
>