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.
> I've also been advised that these two servers: > allow EXP ^prisma\.fsl\.noaa\.gov > allow EXP ^prismb\.fsl\.noaa\.gov > > can no longer talk to fetch. Their logfile entries are: > Oct 25 23:02:11 prisma fetch1[8408]: ERROR: requester6.c:457; > ldm_clnt.c:277: Couldn't connect to LDM 6 on fetch1.arh.noaa.gov usi ng > either port 388 or portmapper; ldm_clnt.c:116: : RPC: Remote system > error - Connection timed out That's consistent with your LDM server not being owned by root and not setuid. In that situation, the LDM server wouldn't be able to obtain port 388 or register with the portmapper; consequently, downstream LDM-s would not be able to connect to it. Try the following AS THE LDM USER AND ASSUMING THAT LDM 6.3.0 IS RUNNING AND NOT LDM 6.4.6: cd cd ldm-6.4.6/src make distclean ./configure --enable-logging=local3 >configure.log 2>&1 && make >make.log 2>&1 && make install >install.log 2>&1 && su root -c 'make install_setuids' && echo LDM package installed cd ldmadmin stop ldmadmin delqueue rm runtime ln -s ldm-6.4.6 runtime ldmadmin mkqueue -f ldmadmin start Regards, Steve Emmerson Ticket Details =================== Ticket ID: SVU-966060 Department: Support LDM Priority: Normal Status: On Hold