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, LDM did compile but since then I have not been able to resolve the error > below. What does it mean; never seen this one before: > > 20201028T134244.282916Z ldmd[28681] ldmd.c:main:988 > NOTE Starting Up (version: 6.13.12; built: Oct 22 2020 16:24:29) > 20201028T134244.283136Z ldmd[28681] > ldmd.c:create_ldm_tcp_svc:48 > 4 ERROR Address already in use > 20201028T134244.283162Z ldmd[28681] > ldmd.c:create_ldm_tcp_svc:48 > 4 ERROR Couldn't obtain local address 0.0.0.0:388 for server > 20201028T134244.283196Z ldmd[28681] ldmd.c:cleanup:197 > NOTE Exiting > 20201028T134244.283257Z ldmd[28681] ldmd.c:cleanup:256 > NOTE Terminating process group > The above messages mean that the LDM server couldn't obtain it's well-known port number, 388. This is most-likely because another process (e.g., another LDM server) has that port number. You can discover what process has that port number via the netstat(1) utility: $ sudo netstat --listening --tcp --inet --program --numeric | grep 388 tcp 0 0 0.0.0.0:388 0.0.0.0:* LISTEN 382059/ldmd $ The above shows the LDM running in process 382059 and listening on port 388. You now need to ask yourself *why* another LDM is running. 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.