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

[IDD #UJU-198299]: Problem receiving CONDUIT/NIMAGE data

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 #UJU-198299]: Problem receiving CONDUIT/NIMAGE data
  • Date: Mon, 27 Apr 2009 18:22:51 -0600
Hi James,

re:
> I wasn't sure which department to contact(ldm or idd support). So, I'm
> writing to the old general contact.

address@hidden would be the correct department, but
your thinking is virtually identical to what mine would have been
(e.g., is it an LDM problem, or a relay problem, etc.).  Your sending
the inquiry to address@hidden was the _exact_ right thing
to do in this kind of situation!  We thank you for this!!

> I'm no longer receiving  a data feed  from CONDUIT nor NIMAGE(NGRID
> too).  It suddenly started Sunday morning(26 Apr). The other
> feeds(UNIDATA,NNEXRAD,CRAFT) are fine.
> When I restart the ldm,  the "missing" feed resumes for a short time.
> Then it appears to stop. The ldmd.log file doesn't show anything unusual.
> 
> I get the feed for CONDUIT and NIMAGE from idd.unidata.ucar.edu  and
> thelma.ucar.edu(latter is back-up feed). My primary feed from
> aeolus.ucsd.edu doesn't seem to provide the above.

One thing:  please remove any requests to thelma.ucar.edu.  That
machine has not existed for several years now.  idd.unidata.ucar.edu
is actually a high performance Linux cluster that is handling just
over 500 downstream connections at the moment.

> I'm able to get the necessary data manually, but it would nice if I
> could get the feed automatically again(for convenience).

It is unclear why your feeds would start upon an 'ldmadmin restart' on
your side, but we restarted the LDM on each of our cluster nodes to
see if that would "fix" the problem you are experiencing.

> Thank you in advance for your help.

No worries.  Please let us know if your problem persists or goes away.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: UJU-198299
Department: Support IDD
Priority: Normal
Status: Closed