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

19990408: LDM troubles

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 19990408: LDM troubles
  • Date: Thu, 08 Apr 1999 08:08:26 -0600
>From: Anthony Rockwood - MSCD Meteorology <address@hidden>
>Organization: Metropolitan State College of Denver
>Keywords: 199904072154.PAA22612 LDM queue

Tony-

>No, I haven't made any changes to the system, so I don't know what's going
>on.  I'm expecting it to happen again by tomorrow morning, so I'll pay
>attention to which file it is and let you know.

I logged on this morning and everything looks to be okay.  I noticed that
the disk is 91% full by 8AM, at which point mcscour.sh runs and reduces it
back to 83%.  It could be that for some reason, the disk was getting full
and when the ldm tried to write to the queue, it would be corrupted.  When
you come in at 8 and restart the LDM, mcscour.sh has run.  Although, I
don't see anything errors indicating this in your /var/adm/messages files.

>You ready for us next week ?  

Oh, sure.  We have to move out of our offices tomorrow for the rewiring,
but I'll be upstairs for most of the time and working at home some
of the time.  See you next week.

Don