[AWIPS #RIG-511107]: Question about LDM tarball ...

Yeah that sounds fine.  

The changes I made to the LDM are pretty minor.  The edexBridge flag (-e) for 
pqact entries was the major addition by Raytheon, and Steve Emmerson baselined 
that change fairly soon after we first reviewed their code.

My reasons for a new LDM RPM were
1) to use the latest source code (6.11.2 over 6.8.0)
2) keep $LDMHOME consistent with the LDM release that Emmerson maintains 
($LDMHOME for the Raytheon RPM is /usr/local/ldm; it should be 
/usr/local/ldm/ldm-6.11.2 )
3) provide pqact.conf entries relevant to Universities/National Centers-type 
facilities, rather than localized facilities like WFOs.

Were you able to access the beta release download page?

Michael



> Michael,
> 
> So I am setting up a both a standalone AWIPS2 development environment
> (either x86_64 or i386 or both) in which CAVE, EDEX, and LDM are all
> installed on one host.
> 
> I am also setting up a couple of EDEX servers here. One EDEX server will
> contain the LDM which expects to be closest to our SBN/NOAAPort feed. This
> is the server which I hope to provision with your latest LDM rpm. I believe
> all of our downstream EDEX servers need only the vanilla-flavored LDM
> server installed and not (necessarily) your latest LDM with all the new
> Raytheon/Unidata/NOAAPort extensions.
> 
> So, the problem we were having appeared to be network related as we would
> attempt to run LDM and it would take a while to "time-out" and say "LDM
> server not started". We did not have our host name resolution working
> correctly so instead of being fully-resolved (e.g. somehost.fsl.noaa.gov) a
> call to gettaddrinfo (or similar) would return just the host name (e.g.
> somehost).
> 
> We now have that fixed but would still like our EDEX machine (or maybe
> just an LDM machine) that is closest to the SBN/NOAAPort to have your
> latest LDM installation.
> 
> Does this approach sound correct to you?
> 
> Evan
> 
> 
> 
> 
> address@hidden> wrote:
> 
> > Hi Evan,
> >
> > I have rebuilt the LDM RPM for our release of AWIPS2, and it is installed
> > with the entire standalone server group, but of course can be installed
> > individually with yum or the rpm command.
> >
> > Before I send you a download link, maybe I can help with the problem you
> > are seeing on your end?  What exactly is happening when you're trying to
> > install the server group?  And have you tried installing the LDM RPM alone
> > (such axs "yum install awip2-ldm")?
> >
> > Michael James
> > Unidata
> >
> >
> >
> > > I am not an official customer of yours, but I have not had much luck in
> > the
> > > past using the A2 listserv, as people at Raytheon appear to be far too
> > busy
> > > getting a solution out the door.
> > >
> > > I am attempting to install the AWIPS 2 applications development
> > environment
> > > (ADE) and the only part that is failing is the yum repo group called
> > "AWIPS
> > > II LDM Server".
> > >
> > > I am thinking that if I had access to your
> > > /awips2/repo/awips2-ldm-6.11.2-2.i386.rpm I might have better luck with
> > my
> > > attempt to install the LDM.
> > >
> > > Evan Polster
> > > 303-497-6778
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: RIG-511107
> > Department: Support AWIPS
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: RIG-511107
Department: Support AWIPS
Priority: Normal
Status: Open