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

20050428: Hello from UNCA and aksing for help

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: 20050428: Hello from UNCA and aksing for help
  • Date: Thu, 28 Apr 2005 07:57:54 -0600
>From: "Alex Huang" <address@hidden>
>Organization: UNCA
>Keywords: 200504281338.j3SDckP3001435 LDM corrupt queue

Hi Alex,

>How are you?

I am doing well, thank you.  By the way, I am answering this from my hotel
room in Vienna, Austria!  You have to love the Internet -- it has made
the world a much smaller place...

>It has been a while since I contacted you, it means we are
>doing just fine.

Very good.  I am glad to hear that you are well.

>Unfortunately, we had a big power surge at UNCA yesterday, every PC
>seems to be fine, but the LDM machine (storm2.atms.unca.edu) stopped at
>Testing LDM queue integrity: while rebooting.  I tried a few times of
>cold boot, but it didn't work.
>
>Can you tell me what I should do?

The fix is easy.  All you have to do is delete and remake the LDM
queue.  Here are the steps you should follow:

<as 'ldm'>

ldmadmin delqueue
ldmadmin mkqueue -f
ldmadmin clean
ldmadmin start

>We only have a few days left in this
>semester, so the timing is not good.  We may replace this old PC with a
>newer one in summer.

You should easily be up and ingesting data within 5 minutes of receiving
this email.

>Thank you so much.

No worries.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.