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.
Russ, Would you please send me the output of the command grep -i ^req ~ldm/etc/ldmd.conf And by "ldmwatch" I assume you meant "ldmadmin watch". > Good catch Steve. > > I had runtime/bin still linked to the old LDM version. Removed the > runtime link and remade it to ldm-6.13.6 and now rpcinfo -p shows port > 388. But not seeing any data in ldmwatch. > > Netstat -an shows port 388 listening > > Thanks > > Russ > > > [ldm@fos-cip ~]$ rpcinfo -p > program vers proto port service > 100000 4 tcp 111 portmapper > 100000 3 tcp 111 portmapper > 100000 2 tcp 111 portmapper > 100000 4 tcp 111 portmapper > 100000 3 tcp 111 portmapper > 100000 2 tcp 111 portmapper > 300029 6 tcp 388 ldmd > 300029 5 tcp 388 ldmd > > > > [ldm@fos-cip ~]$ ps -ef |grep ldm root > root 26526 24406 0 16:31 pts/0 00:00:00 su - ldm ldm > ldm 26563 26562 0 16:31 pts/0 00:00:00 -bash ldm > ldm 27765 1 0 17:29 ? 00:00:00 ldmd -I 0.0.0.0 -P 388 -M 256 -m 3600 > -o 3600 -q /data/ldm/queues/ldm.pq /home/ldm/etc/ldmd.conf ldm > ldm 27767 27765 0 17:29 ? 00:00:00 pqact > ldm 27860 26563 0 17:32 pts/0 00:00:00 grep --color=auto ldm Regards, Steve Emmerson Ticket Details =================== Ticket ID: CFG-797475 Department: Support LDM Priority: High Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.