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

[LDM #GTE-652670]: problems with SCOOP IDD data: ELCIRC on dc-ldm2

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: [LDM #GTE-652670]: problems with SCOOP IDD data: ELCIRC on dc-ldm2
  • Date: Wed, 02 Apr 2008 10:21:40 -0600
Gerry,

> 6.6.5 is installed and ldm restarted.  After awhile I started seeing
> this as a result of ldmadmin tail:
> 
> Apr 02 15:22:34 dc-ldm2 localhost.localdomain(noti)[8426] NOTE: Starting
> Up(6.6.5/5): 20080402134214.012 TS_ENDT {{EXP,  "^[DSW]"}}
> Apr 02 15:22:34 dc-ldm2 localhost.localdomain(noti)[8426] NOTE: topo:
> localhost.localdomain EXP
> Apr 02 15:22:34 dc-ldm2 localhost.localdomain(noti)[8427] NOTE: Starting
> Up(6.6.5/5): 20080402045107.730 TS_ENDT {{EXP,  "SELC"}}
> Apr 02 15:22:34 dc-ldm2 localhost.localdomain(noti)[8427] NOTE: topo:
> localhost.localdomain EXP
> Apr 02 15:22:44 dc-ldm2 sasquatch.tamu.edu(feed)[8434] NOTE: Starting
> Up(6.6.5/6): 20080402142243.185 TS_ENDT {{EXP,  "wrfout"}}, SIG=NONE,
> Primary
> Apr 02 15:22:44 dc-ldm2 sasquatch.tamu.edu(feed)[8434] NOTE: topo:
> sasquatch.tamu.edu {{EXP, (.*)}}
> Apr 02 15:22:44 dc-ldm2 sasquatch.tamu.edu[8435] NOTE: Data-product with
> signature 6c0ab96898347c8a4bc4b81d1b3b58a5 wasn't found in product-queue
> Apr 02 15:22:44 dc-ldm2 sasquatch.tamu.edu(feed)[8435] NOTE: Starting
> Up(6.6.5/6): 20080402142243.185 TS_ENDT {{EXP,  "^W"}},
> SIG=6c0ab96898347c8a4bc4b81d1b3b58a5, Alternate
> Apr 02 15:22:44 dc-ldm2 sasquatch.tamu.edu(feed)[8435] NOTE: topo:
> sasquatch.tamu.edu {{EXP, (.*)}}
> Apr 02 15:27:36 dc-ldm2 localhost.localdomain(noti)[8427] ERROR:
> nullproc5(localhost.localdomain): RPC: Unable to receive
> Apr 02 15:27:36 dc-ldm2 localhost.localdomain(noti)[8427] NOTE: Exiting

I assume that you're concerned about the ERROR messages.  They
are probably due to the termination of the "notifyme" process.
When an upstream LDM notices that its downstream process no
longer exists, it logs an ERROR-level message.

> gc
> --
> Gerry Creager -- address@hidden
> Texas Mesonet -- AATLT, Texas A&M University
> Cell: 979.229.5301 Office: 979.862.3982 FAX: 979.862.3983
> Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: GTE-652670
Department: Support LDM
Priority: Normal
Status: Closed