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

Re: The product-queue is corrupt.

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: Re: The product-queue is corrupt.
  • Date: Tue, 14 Sep 2004 19:04:49 +0000
Steve,

Did the trick . . . takes a bit longer for the stop to occur, but no more 
corrupt queue.  I have changed our init scripts to use the feedback and 
remake the queue if anything other than "O.K." . . . we had some safety nets 
before - checking for the PID file and comparing it to the existence of said 
process . . . but this should be better.

Thanks!

Stonie

On Tuesday 14 September 2004 18:53, Steve Chiswell wrote:
> Stonie,
>
> You need to close the queue (eg call pq_close in your atexit routine)
> when you are finished writing so that when the LDM is restarted,
> the queue counter is properly decremented. Otherwise, the ldm will
> assume that the state is not clean.
>
> Without calling pq_close, you would have to reset the counter with
> pqcheck -F to avoid remaking the queue.
>
> Steve Chiswell
> Unidata User Support
>
> On Tue, 2004-09-14 at 12:47, Stonie Cooper wrote:
> > Steve and Steve,
> >
> > Ported our stuff to 6.1.0, and I have noticed something bothersome.
> >
> > If I do an ldmadmin stop, and then an ldmadmin start . . . the ldmadmin
> > start always comes up with "The product-queue is corrupt."  So, I do the
> > ldmadmin delqueue && ldmadmin mkqueue . . . and we're back running - just
> > inconvenient to have to rebuild the queue every time.
> >
> > Is this normal?

-- 
Stonie R. Cooper
Planetary Data, Incorporated
(402) 727-6599