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

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