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

Re: Re-insert into the LDM queue

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: Re-insert into the LDM queue
  • Date: Mon, 27 Jun 2005 09:22:03 -0600
Angel,

>Date: Fri, 24 Jun 2005 23:10:39 +0000
>From: "Angel Corona" <address@hidden>
>Organization: NOAA/NWS
>To: Steve Emmerson <address@hidden>
>Subject: Re-insert into the LDM queue

The above message contained the following:

> What is the best way to get something back into the LDM queue to be 
> processed on a machine listening to my machine. 
> 
> For example:  a forecaster runs a program that creates a text forecast. 
> This forecast is put into the LDM queue that another machine takes and 
> runs a script that sends it out. Say something goes wrong with the 
> script so it doesn't go out. I then fix the script. The forecaster then 
> runs the program again. Now the forecast will not be inserted into the 
> queue because it says it was already inserted into the queue (it matched 
> the previous one exactly). Now we can not send the product out because 
> we can't get the product into the queue so it can run on the other 
> machine again.
> 
> How do I avoid this problem and get the queue to accept another 
> insertion of the same thing?

The problem isn't that the LDM product-queue won't accept a duplicate
data-product; rather, then problem is that you need to reprocess
the data-product that's already in the product-queue.  Deleting the
data-product in question and then re-inserting it would be one solution
to this problem.  I believe that the pqexpire(1) utility could be used
to delete a single data-product by very careful specification of the
feedtype and pattern.  You should test this.

Another possibility -- assuming that the "other" machine receives the
data-product via the LDM -- would be to manually execute the pqact(1)
utility on that other system.  Again, the feedtype and pattern would have
to be carefully specified to ensure that the desired data-product was
the only one acted upon.

You should be able to get more information on the pqexpire(1) and
pqact(1) utilities by executing the man(1) utility as the LDM user.

> Thanks
> Angel Corona
> 
> --------------020502040201020705050106
> Content-Type: text/x-vcard; charset=utf-8;
>  name="angel.corona.vcf"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment;
>  filename="angel.corona.vcf"
> 
> begin:vcard
> fn:Angel Corona
> n:Corona;Angel
> org:National Weather Service - Alaska Region;Systems Integration Branch
> adr;dom:;;222 W. 7th Ave. #23 Rm. 517;Anchorage;AK;99513-7575
> email;internet:address@hidden
> title:Special Applications Program Manager
> tel;work:(907)271-4428
> tel;fax:(907)271-3711
> tel;cell:(907)229-5614
> x-mozilla-html:FALSE
> url:http://www.arh.noaa.gov
> version:2.1
> end:vcard
> 
> 
> --------------020502040201020705050106--

Regards,
Steve Emmerson