[IDD #GBL-286949]: CONDUIT down?

Art,

> Yes... that's my fault.  Sometimes when I cut/paste I'll join lines for
> readability, which had negative results in this case :(   Here's the
> unedited cut/paste:
> 
> Oct 05 16:58:23 idd-ingest idd.unidata.ucar.edu[13779] ERROR: pq_insert()
> failed: Invalid argument: 8e1efb2f5322d97b4503cb8900f14bd4    42422
> 20061005164806.699 CONDUIT 345 
> /afs/.nwstg.nws.noaa.gov/ftp/SL.us008001/ST.opnl/MT.ruc_CY.16/RD.20061005/PT.grid_DF.gr1/fh.0001_tl.press_gr.bgrib20
> !grib/ncep/RUC2/#252/200610051600/F001/VVEL/hybrid_lev_46! 000345

The "pq_insert()" message looks OK now.

> When a child LDM process like this aborts, can that cause queue corruption
> too?

A child LDM should only be able to corrupt the product-queue if its process 
terminates abnormally (e.g., due to a SIGSEGV).  In this case, the child LDM 
process terminated normally, so it shouldn't have corrupted the product-queue.

> Okay... I'm still running with that queue now.  Would you recommend I
> stop/remake queue/start to make sure things are okay?

Yes, I recommend that you recreate the product-queue.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GBL-286949
Department: Support LDM
Priority: Normal
Status: Closed