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

[IDD #GBL-286949]: CONDUIT down?

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: [IDD #GBL-286949]: CONDUIT down?
  • Date: Fri, 06 Oct 2006 11:09:05 -0600
Art,

> Upon restart, things seem to be running normally.
> 
> Any idea what these errors (from below) mean?
> 
> Oct 05 16:58:23 idd-ingest idd.unidata.ucar.edu[13779] ERROR:
> pq_del_oldest: signature 00000000000000000000000000005080: Not Found

The "pq_del_oldest" message means that there was no entry in the signature list 
corresponding to the signature of the data-product that was just deleted from 
the region list of the product-queue (I know this sounds like gobbledygook).  I 
don't think it should have happened, however, and it might indicate a problem 
with your product-queue.  I'll investigate more.

> Oct 05 16:58:23 idd-ingest idd.unidata.ucar.edu[13779] ERROR: pq_insert()
> failed: Invalid argument: 8e1efb2f5322d97b4503cb8900f14bd4    
> 4242220061005164806.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_$
> !grib/ncep/RUC2/#252/200610051600/F001/VVEL/hybrid_lev_46! 000345

The "pq_insert()" message isn't formatted correctly: there should be a space 
between the product-size (42422) and the timestamp (20061005164806.699).  Was 
it miscopied?

In any case, the message means that the given data-product couldn't be inserted 
into the product-queue because a function in the product-queue library 
determined that it was given an invalid argument.  This should not have 
occurred and might indicate corruption of the product-queue.

> Oct 05 16:58:24 idd-ingest rpc.ldmd[13773] NOTE: child 13779 exited with 
> status 10

The "child ... exited" message means that the downstream LDM that was receiving 
the CONDUIT data-feed terminated due to the previously described problems with 
the product-queue.  This is the reason you stopped receiving CONDUIT data.

> They seem to be the first errors that ocurred around the time that we quit
> getting CONDUIT data.  Could there be a queue corruption issue?

All things considered, I think your product-queue was corrupted.

Regards,
Steve Emmerson

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