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.
Gilbert Sebenste wrote: > Here's a follow up. It wasn't the hard drive, but... > > ******************************************************************************* > Gilbert Sebenste ******** > Internet: address@hidden (My opinions only!) ****** > Staff Meteorologist, Northern Illinois University **** > E-mail: address@hidden *** > web: http://weather.admin.niu.edu ** > Work phone: 815-753-5492 * > ******************************************************************************* > > From: David B. Bukowski <address@hidden> > To: Gilbert Sebenste <address@hidden> > Subject: It stopped the same time newlog was run > > I'm turning off the newlog off the crontab so I can see what actually > happenes. Doesn't help if the log file is not being made when it crashes > :), but it looks like a corrupt queue again. > -dave > > -- Hi Gilbert, Does this mean you were able to build the queue avoiding the bad blocks you found and it still crashed? Is this the only time the running of newlog coincided with the crash? Keep me posted. Anne -- *************************************************** Anne Wilson UCAR Unidata Program address@hidden P.O. Box 3000 Boulder, CO 80307 ---------------------------------------------------- Unidata WWW server http://www.unidata.ucar.edu/ ****************************************************