[AWIPS #IFB-805469]: Installed LDM 6.11 but EXECs no longer work?

Hi Evan,

The readnoaaport and dvbs_muticast binaries, they are not part of the 6.8.1 LDM 
RPM release by Raytheon and are not part of the Unidata awips2-ldm, so I can 
not say without doubt that they will work with this binary build.  They should, 
sure, but nothing is as it seems with AWIPS2.  

I did notice that your LDM product queue is located at 

/usr/local/ldm/data/ldm.pq 

while mine is located at

/usr/local/ldm/var/queues/ldm.pq

/usr/local/ldm/data/ is a symbolic link to /usr/local/ldm/var/data

Can you send me your ldmd.conf and pqact.conf files?

-Michael

> Thanks for the input.
> 
> So I believe I have an even more general question.
> 
> We had an LDM server (6.8) feeding our AWIPS2 EDEX servers. The ldmd.conf
> file pointed to readnoaaport and dvbs_muticast binaries. This was
> successfully getting data from our upstream servers.
> 
> We installed LDM server (6.11) using thew awips2-ldm.rpm file. It no longer
> had the two binaries but apparently just pointed to Unidata's feed.
> 
> So I moved the binaries from 6.8 bin to the 6.11 bin and set the
> permissions as you said and changed the registry.xml file to point to
> /usr/local/ldm/data/ldm.pq file and /var/log/messages says:
> 
> Jun 25 16:33:02 awips2-cp readnoaaport[24544] ERROR: ctl_gopen:
> pq->datao=4096, pq->pagesz=4096, pq->ixo=8036352, pq->ixsz=8
> Jun 25 16:33:02 awips2-cp readnoaaport[24544] ERROR: couldn't open the
> product queue /usr/local/ldm/data/ldm.pq
> 
> But the product queue is there and with proper permissions (ldm:fxalpha).
> 
> I am clearly missing something about how to configure the new 6.11 stuff to
> match my 6.8 ingest.
> 
> Any ideas?
> 
> Evan
> 
> p.s. I am taking your course on AWIPS2 and LDM this summer and that can't
> come too soon.
> 
> 
> 
> address@hidden> wrote:
> 
> > Evan,
> >
> > Verify that ~ldm/bin/dvbs_multicast is owned by "root" and setuid.
> >
> > Check the readnoaaport(1) log files, which you can find by seeing where
> > the "local3", "local4", "local5", and "local6" messages go in the
> > configuration-file for the system logging daemon.
> >
> > > All the exec calls come back with:
> > >
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27830 exited with
> > status
> > > 127: dvbs_multicast -m 224.0.1.1
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27831 exited with
> > status
> > > 127: readnoaaport -m 224.0.1.1 -n -u 3 -t mhs -r1
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27832 exited with
> > status
> > > 127: dvbs_multicast -m 224.0.1.2
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27833 exited with
> > status
> > > 127: readnoaaport -m 224.0.1.2 -n -u 4 -t mhs -r1
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27835 exited with
> > status
> > > 127: dvbs_multicast -m 224.0.1.3
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27837 exited with
> > status
> > > 127: readnoaaport -m 224.0.1.3 -n -u 5 -t mhs -r1
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27838 exited with
> > status
> > > 127: dvbs_multicast -m 224.0.1.4
> > > Jun 24 22:56:34 awips2-cp ldmd[27828] NOTE: child 27839 exited with
> > status
> > > 127: readnoaaport -m 224.0.1.4 -n -u 6 -t mhs -r1
> > >
> > > This worked before on our LDM 6.8 server but that was a few months ago. I
> > > am starting to think that something changed in our network configuration
> > to
> > > prevent us from accessing these servers.
> > >
> > > I will look into this and you should probably close the ticket.
> > >
> > > Thanks,
> > >
> > > Evan
> >
> > Regards,
> > Steve Emmerson
> >
> > Ticket Details
> > ===================
> > Ticket ID: IFB-805469
> > Department: Support AWIPS
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> 

Ticket Details
===================
Ticket ID: IFB-805469
Department: Support AWIPS
Priority: Normal
Status: Open