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

20001207: missing SAO data

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: 20001207: missing SAO data
  • Date: Thu, 07 Dec 2000 12:59:10 -0700
>From: Anthony Rockwood - MSCD Meteorology <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200012071839.eB7Idgo00814

>Chiz,
>
>Thanks.  I didn't find anything in the log files, but I did find a big
>core file that was written at about the time the surface obs quit.  I
>deleted it, re-started the LDM, and I'm now getting obs again.  I know
>that my disk space is getting low, so maybe the core file was enough to
>put it over the top?
>
>Anyway, I think I'm ok now.
>
>Tony
>
> ****************************************************************************
>   Anthony A. Rockwood              Metropolitan State College of Denver    
>   Meteorology Program              Dept.of Earth and Atmospheric Sciences 
>   303.556.8399                     P.O. Box 173362, Campus Box 22
>   address@hidden                Denver, CO  80217-3362                  
>   fax: 303.556.4436                www.mscd.edu/~eas
> ****************************************************************************
>
>


Tony,
Yes, a core file, combined with when scouring actually occurs could
mean that disk space was not available and the GEMPAK file couldn't
be written.

You can always check your disk partition usage with: df -k
Also, if the core file appears frequently, you can determine
which program created it with the command "file core".
If a decoder is frequently core dumping, then that is something
that should be fixed (or upgraded).

Steve Chiswell