Re: 20051111: Need help on LDM setup

Jayne,

> To: address@hidden
> From: "Jayne Hirakawa" <address@hidden>
> Subject: Need help on LDM setup
> Organization: NOAA
> Keywords: 200511112059.jABKxE7s007770 LDM

The above message contained the following:

> I am trying to setup LDM 6-4.1between 2 linux RH ES4 systems.

I assume you mean LDM 6.4.1.

> For mcidas 
> area files in a server directory, how do we automatically send these 
> areafiles to the client machine's 
> /home/nadata/images/satellite/G10/4km/IR directory.  (for testing, 
> attempting to put data in /usr/local/ldm/save/IR)
> 
> dude-pc = server
> gracie-pc = client

I assume that you're trying to send McIDAS AREA files from host
"dude-pc" to host "gracie_pc".

> * I get no errors when starting ldm  on both machines (see attached).  
> At current, put new data on the server and nothing happens.

I'm afraid that I don't know what you mean by the phrase "put new data
on the server".

> Ran  following command on server where the data is located:
> 
>  ldmsend   -x -v -h gracie-pc.hfo.noaa.gov -f ANY IR_051111_2000
> 
> 
> * Got the following reply:
> 
> [ldm@dude-pc data]$  ldmsend -x -v -h gracie-pc.hfo.noaa.gov -f ANY 
> IR_051111_2000
>         version 6
>         max_hereis = 4294967295
> ldmsend INFO: Sending IR_051111_2000, 1952928 bytes
>         Sending file via HEREIS
> 
> Don't know where the data went.  `ldmadmin watch` on both machines 
> displayed nothing when ran ldmsend.

An "ldmadmin watch" on host "dude-pc" shouldn't display anything because
the ldmsend(1) utility sent the file to the LDM on host "gracie-pc" and
not to the LDM on host "dude-pc".

A default "ldmadmin watch" on host "gracie-pc" should have indicated
that the data-product was received, however -- providing it was executed
before the ldmsend(1) on host "dude-pc".

> Also `notifyme ...` did not display 
> anything on gracie-pc.

Does the LDM configuration-file on host "dude-pc" contain an ACCEPT
entry for everything from host "gracie-pc"?

> How does the client know where the data directory on the server is?

It doesn't.  What the downstream LDM does with the incoming data-product
is up to the downstream LDM and is not under the control of the upstream
LDM.

> Also 
> need help with understanding architecture of pqact.conf and ldmd.conf

Have you read the "LDM Basics" webpages for your release at

    http://www.unidata.ucar.edu/software/ldm/

> Attached startup log on dude-pc and gracie-pc. Also the "NOTE: hiya6" in 
> gracie-ldmd.log is when I ran the ldmdsend command on dude-pc.
> 
> jayne
> 
> Nov 11 20:39:55 dude-pc pqcheck[28295] NOTE: Starting Up (28287) 
> Nov 11 20:39:55 dude-pc pqcheck[28295] INFO: The writer-counter of the 
> product-queue is 0 
> Nov 11 20:39:55 dude-pc pqcheck[28295] NOTE: Exiting 
> Nov 11 20:39:55 dude-pc rpc.ldmd[28306] NOTE: Starting Up (version: 6.4.1; 
> built: Oct  2 2005 02:38:12) 
> Nov 11 20:39:55 dude-pc rpc.ldmd[28306] NOTE: Using local address 0.0.0.0:388 
> Nov 11 20:39:55 dude-pc pqact[28307] NOTE: Starting Up 
> Nov 11 20:40:27 dude-pc gracie-pc[28317] NOTE: Data-product with signature 
> bca4bcaa2aa52b6466c13aceff2b6d66 wasn't found in product-queue 
> Nov 11 20:40:27 dude-pc gracie-pc(feed)[28317] NOTE: Starting Up(6.4.1/6): 
> 20051111202449.951 TS_ENDT {{ANY,  ".*"}}, Primary 
> Nov 11 20:40:27 dude-pc gracie-pc(feed)[28317] NOTE: topo:  
> gracie-pc.hfo.noaa.gov {{ANY, (.*)}} 

> Nov 11 20:40:26 gracie-pc rpc.ldmd[7957] NOTE: Starting Up (version: 6.4.1; 
> built: Nov  8 2005 13:18:43) 
> Nov 11 20:40:26 gracie-pc rpc.ldmd[7957] NOTE: Using local address 
> 0.0.0.0:388 
> Nov 11 20:40:26 gracie-pc dude-pc[7960] NOTE: Starting Up(6.4.1): 
> dude-pc.hfo.noaa.gov:388 20051111194026.510 TS_ENDT {{ANY,  ".*"}} 
> Nov 11 20:40:26 gracie-pc dude-pc[7960] NOTE: LDM-6 desired product-class: 
> 20051111202449.951 TS_ENDT {{ANY,  ".*"},{NONE,  
> "SIG=bca4bcaa2aa52b6466c13aceff2b6d66"}} 
> Nov 11 20:40:26 gracie-pc pqact[7958] NOTE: Starting Up 
> Nov 11 20:40:26 gracie-pc dude-pc[7960] NOTE: Upstream LDM-6 on 
> dude-pc.hfo.noaa.gov is willing to be a primary feeder 
> Nov 11 20:42:15 gracie-pc dude-pc[7984] NOTE: hiya6: 20051111204215.582 
> TS_ENDT {{ANY,  ".*"}} 
> Nov 11 20:42:23 gracie-pc dude-pc[7985] NOTE: hiya6: 20051111204223.961 
> TS_ENDT {{ANY,  ".*"}} 
> Nov 11 20:45:14 gracie-pc dude-pc[8020] NOTE: hiya6: 20051111204514.388 
> TS_ENDT {{ANY,  ".*"}} 

The last three lines indicate that the upstream LDM on host "dude-pc"
(the ldmsend(1) utility) was able to connect to a downstream LDM on host
"gracie-pc".

Regards,
Steve Emmerson

> NOTE: All email exchanges with Unidata User Support are recorded in the
> Unidata inquiry tracking system and then made publicly available
> through the web.  If you do not want to have your interactions made
> available in this way, you must let us know in each email you send to us.