This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Michael, > We're still experiencing the ldmping problem. We've recently tried a number > of things to fix it so I'd like to bring you up to date and then ask your > advice as to how to proceed. > > About 2:00 this afternoon we completely rebuilt ldm-12.crh.noaa.gov from the > Red Hat site. Everything with the rebuild went well. We're on the latest > software. We also loaded ldm 6.7.0. We followed the directions on the "load > ldm" website. The "configure" and "make" steps all went well. LDM is > running on ldm-12 and we're receiving data. > > Ldmping localhost fails. Ldmping 127.0.0.1 fails. We get the same result > when we ldmping ldm-12 from another server. > > [ldm@ldm-12 ldm]$ ldmping localhost > Apr 16 20:02:47 INFO: State Elapsed Port Remote_Host > rpc_stat > Apr 16 20:02:47 INFO: Resolving localhost to 127.0.0.1 took 0.000331 seconds > Apr 16 20:02:47 ERROR: SVC_UNAVAIL 0.000863 0 localhost RPC: > Program not registered > Apr 16 20:03:12 ERROR: SVC_UNAVAIL 0.000078 0 localhost RPC: > Program not registered > > [ldm@ldm-12 ldm]$ ldmping 127.0.0.1 > Apr 16 20:03:31 INFO: State Elapsed Port Remote_Host > rpc_stat > Apr 16 20:03:31 ERROR: SVC_UNAVAIL 0.000338 0 127.0.0.1 RPC: > Program not registered > Apr 16 20:03:56 ERROR: SVC_UNAVAIL 0.000117 0 127.0.0.1 RPC: > Program not registered > > [ldm@ldm-12 ldm]$ > > > We believe this happened sometime last Saturday. Last Wednesday we loaded > the latest patches for Red Hat. Both ldm-11 and ldm-12 ran fine until > Saturday. Then we started getting disconnects and connection denials. We > believe nothing has changed on the network. Last Monday I changed the port > from 388 to 1388 on both ldm-11 and another ldm server and I was able to > ldmping localhost and ldmping ldm-11 from the other server. I changed the > port back to 388 and the problem returned. Any suggestions you might have > would be greatly appreciated. Did you execute the command "install setuids" as part of the installation process and did it succeed? Who is the owner of the LDM program (bin/rpc.ldmd) and is the set-uid bit enabled for that file? If the owner of the LDM program is "root" and the set-uid bit is enabled, will the O/S honor those settings or is the program on a disk for which the O/S ignores those settings? > Thanks, > Michael Johnson > NWS-CRH, Kansas City Regards, Steve Emmerson Ticket Details =================== Ticket ID: LXP-916564 Department: Support LDM Priority: Normal Status: Closed