NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Charles O'Brien wrote:
>
> Anne,
>
> We have always told our clients to use both accept AND allow lines
> for our feed. This has always worked.
>
> As for identifying the problem... I have no idea. Like I said
> in a previous email, we send the data to all clients the same
> way. Thus far only Purdue saw the problem (without any changes
> on their end). In the end, I believe it was a DNS issue. Our
> name service changed slightly around that time. So I don't
> believe it is a coincidence. The strange part is why did
> Purdue's LDM have such a problem with it, even after adding the
> appropriate additional lines to their ldmd.conf file? All of our
> other clients that experienced the same problem (6 or 7) were
> back up online in less than 30 seconds after adding the extra
> allow/accept lines.
>
> Oh well, after all is said and done, it is good to see data are flowing
> as "normal" again.
>
> Charlie
>
Charlie,
Oh well, another mystery, but at least we have a happy ending. Thanks
for info.
Anne
--
***************************************************
Anne Wilson UCAR Unidata Program
address@hidden P.O. Box 3000
Boulder, CO 80307
----------------------------------------------------
Unidata WWW server http://www.unidata.ucar.edu/
****************************************************