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

20000313: LDM queue corruption

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: 20000313: LDM queue corruption
  • Date: Mon, 13 Mar 2000 12:32:04 -0700
>From: "Ka Kit Lai" <address@hidden>
>Organization: .
>Keywords: 200003131901.MAA08039

>Robb:
>    This is Ka Kit from CCNY. Our machine Halo is not getting data from 
>Albany and I use the ldmadmin watch and the output said something like QUEUE 
>corrupt and I think it is related to a file called something like pquilt. I 
>try to reboot the machine but it is waiting forever for the LDM server to 
>start. What can I do now? Do I need to turn off the LDM server first at the 
>single user mode?
>
>                                                       Ka Kit Lai
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>


Ka Kit,

I logged in to halo and restarted the ldm after making a new product queue.

When the LDM has a corrupted queue, you need to delete the current queue
with "ldmadmin delqueue" and then recreate the queue with "ldmadmin mkqueue".

After making the new queue, you can restart the LDM with "ldmadmin start".

Typically, a queue can become corrupted if the machine is rebooted while the 
LDM is writing data into the queue. Because of this, you should always try to
shut down the LDM gracefully with "ldmadmin stop" before rebooting your
computer if possible. 

Steve Chiswell