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

Re: 20050512: Routing from winderground to idd and rtstats



Jeff,

I failed to mention that we've also made some changes on our end.
Starting last week, our local change should have reduced if not eliminated
the rtstats nullproc_6 failure errors.

mike

On Jun 16,  3:11pm, Jeff Masters wrote:
> Subject: Re: 20050512: Routing from winderground to idd and rtstats
>
> Hi Mike, this appears to be fixed now. We had a DNS/IP conflict on our end
> that was the apparent cause of the trouble. No error messages the past 24
> hours. Thanks for working on this for us!
>
> Jeff
>
> On Thu, 19 May 2005, Mike Schmidt wrote:
>
> > Jeff,
> >
> > On May 19,  2:19pm, Jeff Masters wrote:
> > > Subject: Re: 20050512: Routing from wunderground to idd and rtstats
> > >
> > > Hi Mike, I am running ldm 6.2.1, do I need to upgrade?
> >
> > There's no compelling reason to that with regard to these concerns.
> >
> > > the ldmd.log file for the machine n8.wunderground.com is available via:
> > >
> > > ftp ftp.wunderground.com
> > > Name (ftp.wunderground.com:root): ftp
> > > 331 Anonymous login ok, send your complete email address as your
password.
> > > Password:
> > > ftp> cd auto
> > > ftp> get ldmd.log
> >
> > Thanks
> >
> > > You won't be able to get a directory listing for security reasons, you
> > > have to know the file name and dir.
> > >
> > > It's curious about the "No route to host" thing, I just did some
> > > traceroutes, and one to rtstats.unidata.ucar.edu failed at the last hop
> > > (flrb.ucar.edu), but succeeded to idd.unidata.ucar.edu. I was able to
ping
> > > both machines.
> > >
> > >  Thanks, Jeff
> >
> > >From our end, I now see the same problem.  It looks like all the
> > authoratative name servers for wunderground.com are giving out a
> > private address for n8.wunderground.com (ie 10.0.10.91)?
> >
> > mike
> >
>-- End of excerpt from Jeff Masters