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.
>From: Anthony Rockwood - MSCD Meteorology <address@hidden> >Organization: Metropolitan State College of Denver >Keywords: 199904071842.MAA17661 LDM queue problems Tony- >For the past week, my LDM quits sometime shortly after 12Z each day. A >big core file gets written. I delete the core file, stop and restart the >LDM, but that doesn't seem to fix it. Rebooting works till the next >morning when the same thing happens again. It sounds like your queue is getting corrupted for some unknown reason. If the queue is corrupt and you try to restart the ldm, it will not work. On you system, when you reboot, /etc/init.d/ldmd is set up to delete and remake the queue. If you want to avoid a reboot, just run: ldmadmin delqueue ldmadmin mkqueue ldmadmin start if it doesn't start after failing. The next question is why is this happening and why did it start all of a sudden. I don't see that any of your ldm configuration files have been modified recently, so have there been any other changes made to the system? If this happens again, check which program is dumping core. In the directory where the core file is, run: file core and part of the output is the program that created the core file. Let us know which program has the problem. Don **************************************************************************** < Unidata User Support UCAR Unidata Program < (303)497-8644 P.O. Box 3000 < address@hidden Boulder, CO 80307 < ---------------------------------------------------------------------------- < Unidata WWW Service http://www.unidata.ucar.edu/ < **************************************************************************** <