NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
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