[IDD #CXN-285845]: could you inspect dc-ldm1.tamu.edu and help us figure out a feed/sink problem?

Hi Gerry,

re: could you inspect dc-ldm1.tamu.edu and help us figure out a feed/sink 
problem?
> It's behind the firewall; access via bigbird, ernie or sasquatch.

Hmm...  I was able to SSH as 'ldm' directly to dc-ldm1.tamu.edu.  You may want
to check the machine's firewall setup if it is really supposed to only be
accessible from bigbird, ernie, or sasquatch.

> Trying to set this up as a downstream from sasquatch, loking for
> products in EXP starting wiht D,S, or W.  I think we've fixed the
> various broken pipes.

I used the following 'notifyme' command as 'ldm' on dc-ldm1.tamu.edu:

notifyme -vxl- -f EXP -h sasquatch.tamu.edu -p '^[DSW]' -o 10000

Jul 19 19:43:12 notifyme[8278] NOTE: Starting Up: sasquatch.tamu.edu: 
20060719165632.506 TS_ENDT {{EXP,  "^[DSW]"}}
Jul 19 19:43:12 notifyme[8278] NOTE: LDM-5 desired product-class: 
20060719165632.506 TS_ENDT {{EXP,  "^[DSW]"}}
Jul 19 19:43:12 notifyme[8278] INFO: Resolving sasquatch.tamu.edu to 
165.91.140.32 took 0.000288 seconds
Jul 19 19:43:12 DEBUG: NOTIFYME(sasquatch.tamu.edu) returns OK
Jul 19 19:43:12 notifyme[8278] NOTE: NOTIFYME(sasquatch.tamu.edu): OK
Jul 19 19:43:13 notifyme[8278] INFO: 9fadb03b043941dbbdf1ef7fb3061cb8 22737900 
20060719180510.667     EXP 000  
WGFD0000-GFD_20060719T0600_20060724T0600_20060724T0600_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: 0a52bf1d7fe6b4aa0db2d782fb35f8cb 22421255 
20060719180540.702     EXP 000  
WGFD0000-GFD_20060719T0600_20060724T1200_20060724T1200_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: e0cf2258e1d70e61586a4bb78c2a2fef 22261768 
20060719180610.734     EXP 000  
WGFD0000-GFD_20060719T0600_20060720T0000_20060720T0000_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: b815fb1425ccbc2edfb96981d0e8ccd3 22389600 
20060719180640.760     EXP 000  
WGFD0000-GFD_20060719T0600_20060720T0600_20060720T0600_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: 1b977e877ed1df25dcbcb6121beeb576 22085824 
20060719180710.799     EXP 000  
WGFD0000-GFD_20060719T0600_20060720T1200_20060720T1200_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: edfb2d7bba852478939a9a8563156da8 22211734 
20060719180725.825     EXP 000  
WGFD0000-GFD_20060719T0600_20060720T1800_20060720T1800_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: b5fe60c19494206ec9e0119481bee405 22141764 
20060719180755.857     EXP 000  
WGFD0000-GFD_20060719T0600_20060721T0000_20060721T0000_026th_Z.grb.gz
Jul 19 19:43:13 notifyme[8278] INFO: 92ba38b10af9333a0fc4215ac81c06f1 22237369 
20060719180825.913     EXP 000  
WGFD0000-GFD_20060719T0600_20060721T0600_20060721T0600_026th_Z.grb.gz

So, you are able to feed EXP products beginning with D, S, or W from sasquatch.

Given the 'notifyme' success, I modified the ~ldm/etc/ldmd.conf requests for
EXP data from sasquatch, restarted the LDM, and watched for EXP products:

ldmadmin watch -f EXP

(Type ^D when finished)
Jul 19 19:47:00 pqutil INFO: 131739922 20060719191103.071     EXP 000  
SELC0004-VMS_WNAMAW12-NCP_20060719T1200_20060719T1200_20060722T1200_00femCB41_Z.nc.gz
Jul 19 19:47:00 pqutil INFO:    45615 20060719191103.401     EXP 000  
SELC0004-VMS_WNAMAW12-NCP_20060719T1200_20060719T1200_20060722T1200_00staCB41_Z.nc.gz
Jul 19 19:47:00 pqutil INFO:    33703 20060719191511.784     EXP 000  
DTRK0AAL-NHC_20060717T1200_20060719T1906_02_Z.txt.gz
Jul 19 19:47:00 pqutil INFO:      729 20060719191556.831     EXP 000  
WANAFe07-UFL_20060719T1200_20060719T1200_20060725T1200_02trk_Z.txt.gz
Jul 19 19:47:00 pqutil INFO:      729 20060719191556.840     EXP 000  
WANAFe07-UFL_20060719T0600_20060719T0600_20060725T0600_02trk_Z.txt.gz
 ...

The ~ldm/etc/ldmd.conf request line now looks like:

request         EXP     "^[DSW]"        sasquatch.tamu.edu

This is more efficient than the 3 separate request lines that you had 
originally,
but is otherwise not significantly different.

I guess at this point I am not sure what you are asking for.  You are receiving 
the
EXP products you are requesting from sasquatch.  I see lots of broken pipe 
messages
in ~ldm/logs/ldmd.log that I assume are related to the Perl script you are 
trying to run.  
Is this what you want us to look into?
College Station, TX 77843-3139

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: CXN-285845
Department: Support IDD SCOOP
Priority: Normal
Status: Closed