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

[LDM #NWS-711897]: Problem with ldm 6.6.4 in 64 bit Linux

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: [LDM #NWS-711897]: Problem with ldm 6.6.4 in 64 bit Linux
  • Date: Mon, 04 Jun 2007 17:08:09 -0600
Harry,

> The trouble is, the only way to stop this is a "kill -9".

Hmm... Bit of a catch-22.  Can't investigate corruption unless
the LDM is stopped and, because the product-queue module is
being executed, can't stop the LDM without causing corruption.

At this point I think I'd recreate the product-queue:

    ldmadmin stop && ldmadmin delqueue && ldmadmin mkqueue -f && ldmadmin start

Because of the new persistent-state files, you shouldn't loose 
much (if any) data.

> Here is the
> output from "pqcheck -vl - " after the kill -9 on all the rpc.ldmd
> processes:
> 
> Jun 04 22:49:38 pqcheck NOTE: Starting Up (18820)
> Jun 04 22:49:38 pqcheck INFO: The writer-counter of the product-queue is 4
> Jun 04 22:49:38 pqcheck NOTE: Exiting
> 
> When I reset the writer counter to zero I get:
> 
> Jun 04 22:50:53 pqcheck NOTE: Starting Up (18822)
> Jun 04 22:50:53 pqcheck INFO: The writer-counter of the product-queue is 0
> Jun 04 22:50:53 pqcheck NOTE: Exiting
> 
> I have enclosed the config.log from my build.

Generally, the "config.log" file is only useful if the package
can't be built.

How often has this occurred?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NWS-711897
Department: Support LDM
Priority: Normal
Status: On Hold