[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 20001115: IDD delivery of Unidata-Wisconsin imagery for 11/10 - 11/13
- Subject: Re: 20001115: IDD delivery of Unidata-Wisconsin imagery for 11/10 - 11/13
- Date: Thu, 16 Nov 2000 16:54:34 -0500 (EST)
All,
I did some further sleuthing to try and diagnose this outage and found
that one of our administrators had restarted our ldm Monday morning and it
was then that our McIDAS data started flowing again, so apparently the
stream was there and ready, but a connection was not established and we
were not feeding data. Our other data streams during the McIDAS outage
appear to have been nominal. I checked our system logs and didn't see any
aberrations, and then checked my email for messages about network outages,
etc... and found this on the idd-relay mailing list:
> From address@hidden Thu Nov 16 16:37:41 2000
> Date: Fri, 10 Nov 2000 10:11:37 -0600
> From: Pete Pokrandt <address@hidden>
> To: Harry Edmon <address@hidden>
> Cc: address@hidden
> Subject: Re: No McIDAS
>
>
> In a previous message to me, you wrote:
>
> >I am getting no McIDAS data. The server is up, but sending nothing.
> >--
> >Dr. Harry Edmon E-MAIL: address@hidden
> >(206) 543-0547 FAX: (206) 543-0308
> >Dept of Atmospheric Sciences
> >University of Washington, Box 351640, Seattle, WA 98195-1640
>
> All,
>
> Something was bogus with the routing for some UW-Madison sites
> from about 11:PM until about 4:AM overnight. From outside, sites
> were ping-able, but I couldn't slogin to any of my machines, and
> I couldn't get a response from our web server or SSEC's. Both
> .meteor.wisc.edu and .ssec.wisc.edu domains were affected.
>
> Pete
>
>
> --
> +>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+
> ^ Pete Pokrandt V 1447 AOSS Bldg 1225 W Dayton St^
> ^ Systems Programmer V Madison, WI 53706 ^
> ^ V address@hidden ^
> ^ Dept of Atmos & Oceanic Sciences V (608) 262-3086 (Phone/voicemail) ^
> ^ University of Wisconsin-Madison V 262-0166 (Fax) ^
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<+>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>+
Apparently, whatever happened during the network break from here to
Wisconsin, it caused the ldm rpc on our machine to Wisconsin to hang and
when the network connectivity was reestablished, it didn't fix itself.
Perhaps this is something that needs to be fixed in the ldm? Or is there
something I can set relating to the networking?
Art.
Arthur A. Person
Research Assistant, System Administrator
Penn State Department of Meteorology
email: address@hidden, phone: 814-863-1563
On Thu, 16 Nov 2000, Jennie L. Moody wrote:
> On Nov 16, 7:57, Tom Yoksas wrote:
> > Subject: 20001115: IDD delivery of Unidata-Wisconsin imagery for 11/10 - 1
> > >From: "Jennie L. Moody" <address@hidden>
> > >Organization: UVa
> > >Keywords: 200011151652.eAFGqio23078 IDD Unidata-Wisconsin ADDE
> >
> > Jennie and Art,
> >
> > Previously, Jennie wrote:
> >
> > >Thanks for clarifying my faulty recollection of the
> > >change in ldm-administration.
> > >
> > >Well, since others on the ldm were receiving McIDAS
> > >imagery, it does seem strange. I had a brief exchange
> > >about this with Tom Yoksas at Unidata, so I am going
> > >to forward your note to him. Perhaps we can find out
> > >of Wisconsin was down during that time (we had the same
> > >outage as you 3-4UTC Friday until 16UTC Monday, the 13th.
> > >I actually assumed you had seen my message and has "fixed"
> > >things.
> >
> > Wisconsin was not down during this or any other period in the past two
> > weeks. I verified this by looking at the online, realtime imagery
> > available from motherlode (adde.ucar.edu):
> >
> > <snippit of imglist.k RTIMAGES/GE-IR.ALL while pointing McIDAS ADDE at
> > adde.ucar.edu for RTIMAGES>
> >
> > 203 G-8 IMG 10 NOV 00315 00:15:00 23 71 4
> > 204 G-8 IMG 10 NOV 00315 01:15:00 23 71 4
> > 205 G-8 IMG 10 NOV 00315 02:15:00 23 71 4
> > 206 G-8 IMG 10 NOV 00315 03:15:00 23 71 4
> > 207 G-8 IMG 10 NOV 00315 04:15:00 23 71 4
> > 208 G-8 IMG 10 NOV 00315 09:15:00 23 71 4
> > 209 G-8 IMG 10 NOV 00315 10:15:00 23 71 4
> > 210 G-8 IMG 10 NOV 00315 11:15:00 23 71 4
> > 211 G-8 IMG 10 NOV 00315 12:15:00 23 71 4
> > 212 G-8 IMG 10 NOV 00315 13:15:00 23 71 4
> > 213 G-8 IMG 10 NOV 00315 14:15:00 23 71 4
> > 214 G-8 IMG 10 NOV 00315 15:15:00 23 71 4
> > 215 G-8 IMG 10 NOV 00315 16:15:00 23 71 4
> > 216 G-8 IMG 10 NOV 00315 17:15:00 23 71 4
> > 217 G-8 IMG 10 NOV 00315 18:15:00 23 71 4
> > 218 G-8 IMG 10 NOV 00315 19:15:00 23 71 4
> > 219 G-8 IMG 10 NOV 00315 20:15:00 23 71 4
> > 220 G-8 IMG 10 NOV 00315 21:15:00 23 71 4
> > 221 G-8 IMG 10 NOV 00315 22:15:00 23 71 4
> > 222 G-8 IMG 10 NOV 00315 23:15:00 23 71 4
> > 223 G-8 IMG 11 NOV 00316 00:15:00 23 71 4
> > 224 G-8 IMG 11 NOV 00316 01:15:00 23 71 4
> > 225 G-8 IMG 11 NOV 00316 02:15:00 23 71 4
> > 226 G-8 IMG 11 NOV 00316 03:15:00 23 71 4
> > 227 G-8 IMG 11 NOV 00316 04:15:00 23 71 4
> > 228 G-8 IMG 11 NOV 00316 05:15:00 23 71 4
> > 229 G-8 IMG 11 NOV 00316 06:15:00 23 71 4
> > 230 G-8 IMG 11 NOV 00316 07:15:00 23 71 4
> > 231 G-8 IMG 11 NOV 00316 08:15:00 23 71 4
> > 232 G-8 IMG 11 NOV 00316 09:15:00 23 71 4
> > 233 G-8 IMG 11 NOV 00316 10:15:00 23 71 4
> > 234 G-8 IMG 11 NOV 00316 11:15:00 23 71 4
> > 235 G-8 IMG 11 NOV 00316 12:15:00 23 71 4
> > 236 G-8 IMG 11 NOV 00316 13:15:00 23 71 4
> > 237 G-8 IMG 11 NOV 00316 14:15:00 23 71 4
> > 238 G-8 IMG 11 NOV 00316 15:15:00 23 71 4
> > 239 G-8 IMG 11 NOV 00316 16:15:00 23 71 4
> > 240 G-8 IMG 11 NOV 00316 17:15:00 23 71 4
> > 241 G-8 IMG 11 NOV 00316 18:15:00 23 71 4
> > 242 G-8 IMG 11 NOV 00316 19:15:00 23 71 4
> > 243 G-8 IMG 11 NOV 00316 20:15:00 23 71 4
> > 244 G-8 IMG 11 NOV 00316 21:15:00 23 71 4
> > 245 G-8 IMG 11 NOV 00316 22:15:00 23 71 4
> > 246 G-8 IMG 11 NOV 00316 23:15:00 23 71 4
> > 247 G-8 IMG 12 NOV 00317 00:15:00 23 71 4
> > 248 G-8 IMG 12 NOV 00317 01:15:00 23 71 4
> > 249 G-8 IMG 12 NOV 00317 02:15:00 23 71 4
> > 250 G-8 IMG 12 NOV 00317 03:15:00 23 71 4
> > 251 G-8 IMG 12 NOV 00317 04:15:00 23 71 4
> > 252 G-8 IMG 12 NOV 00317 05:15:00 23 71 4
> > 253 G-8 IMG 12 NOV 00317 06:15:00 23 71 4
> > 254 G-8 IMG 12 NOV 00317 07:15:00 23 71 4
> > 255 G-8 IMG 12 NOV 00317 08:15:00 23 71 4
> > 256 G-8 IMG 12 NOV 00317 09:15:00 23 71 4
> > 257 G-8 IMG 12 NOV 00317 10:15:00 23 71 4
> > 258 G-8 IMG 12 NOV 00317 11:15:00 23 71 4
> > 259 G-8 IMG 12 NOV 00317 12:15:00 23 71 4
> > 260 G-8 IMG 12 NOV 00317 13:15:00 23 71 4
> > 261 G-8 IMG 12 NOV 00317 14:15:00 23 71 4
> > 262 G-8 IMG 12 NOV 00317 15:15:00 23 71 4
> > 263 G-8 IMG 12 NOV 00317 16:15:00 23 71 4
> > 264 G-8 IMG 12 NOV 00317 17:15:00 23 71 4
> > 265 G-8 IMG 12 NOV 00317 18:15:00 23 71 4
> > 266 G-8 IMG 12 NOV 00317 19:15:00 23 71 4
> > 267 G-8 IMG 12 NOV 00317 20:15:00 23 71 4
> > 268 G-8 IMG 12 NOV 00317 21:15:00 23 71 4
> > 269 G-8 IMG 12 NOV 00317 22:15:00 23 71 4
> > 270 G-8 IMG 12 NOV 00317 23:15:00 23 71 4
> > 271 G-8 IMG 13 NOV 00318 00:15:00 23 71 4
> > 272 G-8 IMG 13 NOV 00318 01:15:00 23 71 4
> >
> > As you can see, the GOES-East IR (10.7 um channel) ingestion on
> > motherlode was complete during the period when you were both reporting
> > dropouts. Since motherlode feeds directly from SSEC, I can safely say
> > that SSEC was not down at any point during the same period.
> >
> > The current topology for the LDM MCIDAS feed indicates that navier should
> > be feeding directly from the same machine that motherlode is:
> >
> > unidata.ssec.wisc.edu MCIDAS
> > navier.meteo.psu.edu 0.4 Minutes
> > bjerknes.earth.uni.edu unknown
> > ...
> >
> > I _assume_ that this was the case over the weekend as well. If it is
> > the case, I would suspect that the network connection to Penn State was
> > either down or degraded over the entire weekend. However, if this was
> > true, then all of the Penn State feeds should have been affected. The
> > question is "were they"?
> >
> > If not, please tell us what version of the LDM both of you are using.
> > I believe that Jennie is still running LDM 5.0.8 or 5.0.9 (true?), and
> > I think that Art is running 5.1.2 (true?). If these are both true,
> > then it may be time to upgrade Jennie's machine to the current release
> > of the LDM. Anne and I were talking about this either yesterday
> > morning or the day before. If need be, we can jump in and lend a
> > hand. This upgrade, however, would not cure any problems that Art is
> > seeing, so that warrants further investigation.
> >
> > >Thanks for getting back to me.
> >
> > Sorry I couldn't get to this last night.
> >
> > Tom
> > --
> > +-----------------------------------------------------------------------------+
> > * Tom Yoksas UCAR Unidata
> > Program *
> > * (303) 497-8642 (last resort) P.O. Box
> > 3000 *
> > * address@hidden Boulder, CO 80307 *
> > * Unidata WWW Service
> > http://www.unidata.ucar.edu/*
> > +-----------------------------------------------------------------------------+
> > -- End of excerpt from Tom Yoksas <address@hidden>
>
>
>
> Tom and Anne,
>
> Well, I guess it is time to try to upgrade the ldm. Actually,
> I think its worse than 5.08 or 5.09, I believe I am running
> V5.05 of the ldm. I have a readme file for a newer version that
> I pulled over when I was upgrading the ldm (and ldm-mcidas), but
> I guess I put off upgrading when I realized it wasn't imperative.
>
> However, I do think there must be another problem, since
> I understood Arthur to say that they continued to receive all
> their other products, and I continued to receive these products
> from Arthur (text products, and I think model grids were coming
> in too, but I better go back and look at the archive). It
> must be something else?
>
> Jennie
>
>