20040722: 20040722: 20040720: 20040719: 20040719: sending EXP data to another LDM server

Ying,

the PIPE action in pqact.conf is used to send the data to input of another 
process, which could be "cat" for instance, but wouldn't be a great way to 
accomplish the process.
.
The FILE action is used to send to a disk file. You could PIPE to the "cat"

Check your clock on both machines to ensure that they are both correct.
By now, the file you inserted this morning has aged out of your queue, 
so you will need to reinsert it to for your test. I was able to run
notifyme to your unidata.scs computer but there is no EXP data at this time.

Your mail host clock time was 30 minutes different from your system,
which is one reason I was concerned about your system time. If the
times are off, then the downstrean feeder with request to the upstream 
may not have the window that the product was inserted.

Steve Chiswell
Unidata User Support



>From: address@hidden
>Organization: UCAR/Unidata
>Keywords: 200407221918.i6MJIwaW014258

>
>Steve
>
>> 
>> Ying,
>> 
>> The pqinsert suceeded in entering the data into the queue. The 
>> sequencenumber is 000. The file is 7MB. It will take a few seconds 
>> for 7MB to get to 
>> your downstream. Your test.exp file would have its timestamp 
>> changed if
>> the data arrived and was processed.
>> 
>> You did not show the notifyme command, but you must use the -o 
>> option, unless it
>> is already connected before you run pqinsert.
>
>Yeah, I used -o 3600, by notifyme I can find the data in product queue on unid
> ata(upstream), both from unidata itself and from spring.
>
>> 
>> On spring.scs you would run "notifyme -vxl - -o 3600 -f EXP -h 
>> unidata.scs.gmu.edu"to see the data on unidata.scsjjjjjjjj. 
>> 
>> Check you ldmd.log file on unidata.scs amd verify that you see the 
>> connectionfrom spring.scs when the ldm is started up (remember, 
>> you have to restart your
>> ldm on the machine if you edit its ldmd.conf before changes will 
>> take effect). 
>
>The ldmd.log says:
>Jul 22 18:18:26 unidata spring(noti)[2829]: Starting Up(6.0.14/5): 20040722180
> 645.877 TS_ENDT {{EXP,  ".*"}}
>Jul 22 18:18:26 unidata spring(noti)[2829]: topo:  spring.scs.gmu.edu EXP
>Jul 22 18:22:44 unidata localhost(noti)[2828]: nullproc5(localhost.localdomain
> ): RPC: Unable to receive
>Jul 22 18:23:09 unidata localhost(noti)[2833]: Starting Up(6.0.14/5): 20040722
> 180645.877 TS_ENDT {{EXP,  ".*"}}
>Jul 22 18:23:09 unidata localhost(noti)[2833]: topo:  localhost.localdomain EX
> P
>Jul 22 18:23:32 unidata spring(noti)[2829]: nullproc5(spring.scs.gmu.edu): RPC
> : Unable to receive
>Jul 22 18:23:57 unidata spring(noti)[2834]: Starting Up(6.0.14/5): 20040722180
> 645.877 TS_ENDT {{EXP,  ".*"}}
>Jul 22 18:23:57 unidata spring(noti)[2834]: topo:  spring.scs.gmu.edu EXP
>...
>
>> Check your ldmd.conf file on spring to see if it has any trouble 
>> connectingto the upstream.
>> 
>> You can also run "ldmadmin watch -f EXP" on spring to watch data 
>> arrivingin your queue.
>> 
>> Also, if you edit your pqact.conf file to add the FILE action, you 
>> have to
>> run "ldmadmin pqactHUP" to reread theconf file into a running 
>> pqact process.
>I'm a bit confused about this. any more info I can get from you or from web? C
> an I use PIPE instead, with -close ?
>
>Thanks a lot,
>
>Ying
>
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically 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.