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.
Phil, > thanks for the speedy reply. Here's what I got: > > [ldm@twister ~]$ $HOME/bin/rpc.ldmd -vl- $HOME/etc/ldmd.conf > Oct 08 16:11:05 rpc.ldmd[15583] NOTE: Starting Up (version: 6.6.5; > built: Oct 7 2008 23:02:16) > Oct 08 16:11:05 rpc.ldmd[15583] NOTE: Using local address 0.0.0.0:388 > Oct 08 16:11:05 rpc.ldmd[15583] INFO: Resolving twister.sbs.ohio- > state.edu to 128.146.194.91 took 0.000381 seconds > get_myaddress: gethostbyaddr(127.0.0.1): Success > Oct 08 16:11:05 rpc.ldmd[15583] INFO: Exiting > Oct 08 16:11:05 rpc.ldmd[15583] NOTE: Terminating process group Hmm... Still no indication of why the top-level LDM process is terminating. Try invoking it in interactive mode again but change the "-vl-" option to "-vxl-" (i.e., put the LDM into debug mode) and send me the output. > For what it's worth, I've noticed that I am able to traceroute to > our upstream LDM's via their IP address, but NOT their name (e.g. > stokes.metr.ou.edu) > I receive the following error: > stokes.metr.ou.edu: Temporary failure in name resolution > Cannot handle "host" cmdline arg `stokes.metr.ou.edu' on position 1 > (argc 1) Looks like you have a DNS problem. That shouldn't cause the LDM to terminate, however. > Thanks for your help Steve, > > - Phil > http://www.birnies.com > > (I'm also CC'ing our Network Manager, Jim DeGrand, on this E-mail) Regards, Steve Emmerson Ticket Details =================== Ticket ID: RLJ-543699 Department: Support LDM Priority: Normal Status: On Hold