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.
> Sorry, I tried rebooting the system to see if there was any effect and there > wasn’t. The latest error and PID are below > > 20190813T211802.850213Z idd.unidata.ucar.edu[6954] NOTE error.c:236:err_log() > Connection to upstream LDM closed: pid=27194 27194 is the PID of the *upstream/sending* LDM process; 6954 is the PID of your downstream/receiving LDM process. > #:~/var/logs$ ps -ef | grep 27194 > ldm 20702 4799 0 21:19 pts/1 00:00:00 grep --color=auto 27194 > > The fgrep doesn't bring any results from the ldmd.log file, but a simple grep > does and it only occurs once. > > #:~/var/logs$ cat ldmd.log | grep 27194 > 20190813T211802.850213Z idd.unidata.ucar.edu[6954] NOTE error.c:236:err_log() > Connection to upstream LDM closed: pid=27194 Please try again with PID 6954. Depending on your setup, you might have to search older LDM log file rather than the current one. Regards, Steve Emmerson Ticket Details =================== Ticket ID: CTE-620214 Department: Support LDM Priority: Normal 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.