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

Re: 20020103: Meaning of a ldmd.log statement and need for (fwd)

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: Re: 20020103: Meaning of a ldmd.log statement and need for (fwd)
  • Date: Thu, 3 Jan 2002 13:42:15 -0700 (MST)

Hi James, 

Can you tail -40 your ldmd.log file

and maybe the same for ldmd.log1 so I can see what may be going on with
sunny89..WSI and NLDN come from different sources, so this is not a
surprise, I just cannot figure out why sunny89 is late to you..

-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,
> 
> It's been over 12 hours since we failed over, and the
> latency is still about one hour. However, not all 
> products are late. WSI radar (we're still subscribing
> mosaic images for now) and NLDN data come in fine.
> 
> Even when I delete and make a new queue (using
> "ldmadmin delqueue" and "ldmadmin mkqueue" commands),
> unidata products are an hour old. The new ldmd.log
> file (stopped ldmadmin before remaking a new queue),
> continues to show "reclass" for sunny89.
> 
> As far as the cron is concerned, ldm pings for
> aeolus.ucsd.edu every 20 minutes. So, when aeolus
> comes back, we should back up to speed.
> 
> 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
> ---------------------------------------
> 
> > 
> > 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
> > ________________________________________      ______________________
>