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, re: > "ldmadmin stop" does not recognize a process is running, and killing > the processes is not working either. It is surprising that you are not able to kill the two running LDM processes (ldmd and pqact) presumably as the user that started them to begin with (presumably 'ldm'). Did you try: <as 'ldm'> kill -9 24745 24747 If this didn't work, did you try running the same kill command as 'root': <as 'root'> kill -9 24745 24747 re: > I would rather try to figure out what's wrong before rebooting. Yes, indeed. If you are unable to kill the running LDM processes even as 'root', rebooting is your next option. re: > "ldmadmin stop" > The LDM server isn't running or its process-ID is unavailable This is most likely because the file ~ldm/ldmd.pid does not exist or is empty. re: > 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 This fits with Steve's previous comment: there is already a process running that has port 388. Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** 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.