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

Re: 20040920: Possible pqact issue in LDM?

Everyone,
Well... sigh. Looks like I found the problem and of course it has nothing to do with LDM, which is a very good thing. The upstream ntp server was rebuilt recently and configured incorrectly, causing all the downstream ntpd clients to do 'bad' things, like continually slide time back a little at a time. So, while everything was synchronized with the same time, and ntpd on the clients looked right, all the clients had to constantly make adjustments backwards to keep right with the ntp server, causing the pqact problems I was seeing. Fixing the upstream ntp and restarting everything, and all is right with 
at least this part the world.

Sorry for the wild goose chase...  thanks for all the help!

Steven

Steve Emmerson wrote:


Steven,


Date: Mon, 20 Sep 2004 17:45:30 -0500
From: "Steven Danz" <address@hidden>
Organization: Aviation Weather Center
To: Steve Emmerson <address@hidden>
Subject: Re: 20040920: Possible pqact issue in LDM?
Keywords: 200409091803.i89I3pnJ023109


The above message contained the following:


Just out of curiosity, are the data-products that cause the insertion of
the EXEC-generated data-products also relayed to LDM clients on other,
internal systems?  If so, is a missed data-product, nevertheless,
successfully relayed?


I knew this one was coming. :-) I can't tell. The downstream clients
have multiple upstream sources that are faster to arrive so the
NOAAPort data ends up getting dup-eliminated, if it gets there.


Too bad.

Regards,
Steve Emmerson



--
Steven Danz
Senior Software Development Engineer
Aviation Weather Center (NOAA/NWS/NCEP)
7220 NW 101st Terrace, Room 101
Kansas City, MO 64153-2371

Email: address@hidden
Phone: 816.584.7251
Fax:   816.880.0650
URL:   http://aviationweather.gov/
The opinions expressed in this message do not necessarily reflect those of the National Weather Service, or the Aviation Weather Center.