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.
Hi Lysanias, "ldmadmin stop" does not recognize a process is running, Correct. "ldmadmin stop" looks at the PID in the file "~/ldmd.pid" for the top-level LDM process to stop. That file probably doesn't contain "24745". > and killing the processes is not working either. Sending a SIGTERM to process 24745 should work. You might have to be root. If that doesn't work, then try a SIGINT. > I would rather try to figure out what's wrong before rebooting. > Indeed. Something or someone must have started that LDM. > "ldmadmin stop" > The LDM server isn't running or its process-ID is unavailable > > netstat: > tcp 33 0 0.0.0.0:388 0.0.0.0:* > LISTEN 24745/ldmd > > "top -u ldm" > 24745 ldm 20 0 24604 1696 1172 S 0.0 0.0 0:00.05 ldmd > 24747 ldm 20 0 2031776 2004 1508 S 0.0 0.0 0:02.73 pqact Regards, Steve Emmerson LDM Developer Ticket Details =================== Ticket ID: MDC-227212 Department: Support LDM Priority: Normal Status: Open =================== 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.