[LDM #VDS-923265]: LDM upgrade

Hi Eric,

Recap: after logging in, we determined that the problem was that the runtime 
links
were not created in ~ldm.  I created them as follows:

<as 'ldm'>
cd ~ldm
ln -s ldm-6.4.5 runtime
ln -s runtime/* .

After making this change, I was able to create your queue with no problems:

ldmadmin clean
ldmadmin mkqueue -f

A quick review of your ~ldm/etc/ldmd.conf file showed that you were requesting
most data from papagayo.unl.edu.  I used the LDM 'notifyme' facility to contact
papagayo.unl.edu to see if it was willing to feed data; it is not:

-bash-3.1$ notifyme -vxl- -f ANY -h papagayo.unl.edu
Jul 07 16:05:44 notifyme[23175] NOTE: Starting Up: papagayo.unl.edu: 
20060707160544.966 TS_ENDT {{ANY,  ".*"}}
Jul 07 16:05:44 notifyme[23175] NOTE: LDM-5 desired product-class: 
20060707160544.966 TS_ENDT {{ANY,  ".*"}}
Jul 07 16:05:44 notifyme[23175] INFO: Resolving papagayo.unl.edu to 
129.93.52.150 took 0.001205 seconds
Jul 07 16:05:45 notifyme[23175] ERROR: NOTIFYME(papagayo.unl.edu): 7: Access 
denied by remote server
Jul 07 16:05:47 notifyme[23175] NOTE: Interrupt
Jul 07 16:05:47 notifyme[23175] NOTE: exiting

In order to test data ingest, I pointed at the toplevel relay that we maintain, 
idd.unidata.ucar.edu:

-bash-3.1$ notifyme -vxl- -f ANY -h idd.unidata.ucar.edu
Jul 07 16:06:47 notifyme[23901] NOTE: Starting Up: idd.unidata.ucar.edu: 
20060707160647.216 TS_ENDT {{ANY,  ".*"}}
Jul 07 16:06:47 notifyme[23901] NOTE: LDM-5 desired product-class: 
20060707160647.216 TS_ENDT {{ANY,  ".*"}}
Jul 07 16:06:47 notifyme[23901] INFO: Resolving idd.unidata.ucar.edu to 
128.117.140.3 took 0.001626 seconds
Jul 07 16:06:47 DEBUG: NOTIFYME(idd.unidata.ucar.edu) returns RECLASS
Jul 07 16:06:47 notifyme[23901] NOTE: NOTIFYME(idd.unidata.ucar.edu): reclass: 
20060707160647.216 TS_ENDT 
{{EXP|NXRDSRC|NEXRAD2|NNEXRAD|NPORT|NIMAGE|GPS|FAA604|DIFAX|NMC|FSL5|FSL4|FSL3|FSL2|UNIDATA|SPARE|0x80000000,
  ".*"}}
Jul 07 16:06:47 DEBUG: NOTIFYME(idd.unidata.ucar.edu) returns OK
Jul 07 16:06:47 notifyme[23901] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK
Jul 07 16:06:48 notifyme[23901] INFO: a87956cbf6f2eab28473b59bbc33d685     6924 
20060707160647.379 NNEXRAD 21791872  SDUS53 KMQT 071603 /pN0VMQT
Jul 07 16:06:48 notifyme[23901] INFO: 756d7bef86b1a149d5a35f550675ba56     7474 
20060707160647.382 NNEXRAD 21791873  SDUS25 KABQ 071604 /pN1SFDX
Jul 07 16:06:48 notifyme[23901] INFO: ee00f0afd32e7c5f4564e64e3479a041     2422 
20060707160647.386 NNEXRAD 21791874  SDUS33 KBIS 071604 /pN3RMBX

So, your machine can receive data with no problems as long as the upstream(s) 
has(have)
allow lines for your machine.  I see you are trying to request data from two 
different
upstream hosts:

NLDN - striker2.atmos.albany.edu
other feeds - papagayo.unl.edu

You need to send an email to the LDM administrators at these sites requesting 
that they
update their allow lines for your machine:

papagayo.unl.edu:
Clint Rowe <address@hidden.

address@hidden
David Knight <address@hidden>
Support <address@hidden>

These folks will undoubtedly want the name of your new machine, so if you have 
not yet
set up name service (forward and reverse) you should do so before contacting 
them.

Please let us know if you run into any more snags.


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: VDS-923265
Department: Support LDM
Priority: Normal
Status: Closed