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

[TIGGE #BGR-338705]: A problem when perform LDM tests

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: [TIGGE #BGR-338705]: A problem when perform LDM tests
  • Date: Thu, 07 Jun 2007 08:30:24 -0600
Hi Yangxin,

This is a quick note to let you know that:

- I have configured yakov.unidata.ucar.edu with a 4 GB LDM queue

- yakov.unidata.ucar.edu is now receiving the full CONDUIT datastream

- I have added an entry into /etc/hosts on yakov that assigns the
  fictitious name 'yangxin.cma.gov.cn' to the IP address 210.73.54.25

- I allowed machines whose names match the pattern \.cma\.gov\.cn$ to
  receive CONDUIT data from yakov

So far, I see no connection requests from your machine to yakov for
CONDUIT data.  If your machine is up and running and currently requesting
CONDUIT data from yakov, it would mean that there is some sort of a problem.
Please check your LDM log file (~ldm/logs/ldmd.log) to see if there are
any messages related to your request of CONDUIT data from yakov.


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: BGR-338705
Department: Support IDD TIGGE
Priority: High
Status: Closed