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

20030806: LDM issue

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: 20030806: LDM issue
  • Date: Wed, 06 Aug 2003 16:00:14 -0600
>From: William C Klein <address@hidden>
>Organization: Valparaiso
>Keywords: 200308062130.h76LUALd017442 LDM ldmadmin

Bill,

>We can run the ldmadmin watch command, but we cannot ctrl-d, ctrl-c out of
>it.  Just keeps on running.

I just logged onto aeolus; ran 'ldmadmin watch'; and _was_ able to kill
it with a ctrl-c.  Given that I had no problems, I would think that
your problem has something to do with the terminal setting in the
window in which you were logged onto aeolus.  Check these with
'stty -a'.  When I do this, I see the expected 'intr' setting:

[ 7 ] > stty -a
speed 9600 baud; 
rows = 55; columns = 80; ypixels = 774; xpixels = 579;
csdata ?
eucw 1:0:0:0, scrw 1:0:0:0
intr = ^c; quit = ^\; erase = ^?; kill = ^u;

 ...

>Just thought you would like to know.

There is no problem as far as I can tell.


aeolus' LDM seems to be running nicely and data scouring is working as
it should.  You can keep an eye on the data ingestion on aeolus online
at:

http://www.unidata.ucar.edu/staff/chiz/rtstats

Click on the 'Statistics by Host' link, and then on the
aeolus.valpo.edu [ 6.0.14 ] link.  You will get a page that shows what
datastreams you are ingesting along with various links for different
kinds of plots: latency, log(latency), volume, products, topology.

Clicking on the 'latency' link for IDS|DDPLUS will show you a plot of
the most current two days of latencies for that feed.  The 'topology'
link will show you who aeolus is requesting data from, and the link to
the upstream machine will show the differential latency from the
upstream to you for the particular stream.

Tom