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 David, re: > For the last few hours, our LDM server (rcz006.ust.hk) has > failed to get any data from idd.cise-nsf.gov server. In the > /var/log/messages file, I keep seeing these messages: > > ... > Feb 02 07:35:16 rcz006 idd[2577] ERROR: Terminating due to LDM failure; > Connection to upstream LDM closed > Feb 02 07:35:16 rcz006 idd[2577] NOTE: LDM-6 desired product-class: > 20070202063516.612 TS_ENDT {{IDS|DDPLUS, ".*"}} > Feb 02 07:35:21 rcz006 idd[2577] NOTE: Upstream LDM-6 on idd.cise-nsf.gov is > willing to be a primary feeder > Feb 02 07:36:28 rcz006 idd[2577] ERROR: Terminating due to LDM failure; > Connection to upstream LDM closed > Feb 02 07:36:29 rcz006 idd[2577] NOTE: LDM-6 desired product-class: > 20070202063629.570 TS_ENDT {{IDS|DDPLUS, ".*"}} > Feb 02 07:36:30 rcz006 idd[2577] NOTE: Upstream LDM-6 on idd.cise-nsf.gov is > willing to be a primary feeder > Feb 02 07:38:03 rcz006 idd[2577] ERROR: Terminating due to LDM failure; > Connection to upstream LDM closed > Feb 02 07:38:05 rcz006 idd[2577] NOTE: LDM-6 desired product-class: > 20070202063805.988 TS_ENDT {{IDS|DDPLUS, ".*"}} > Feb 02 07:38:10 rcz006 idd[2577] NOTE: Upstream LDM-6 on idd.cise-nsf.gov is > willing to be a primary feeder > .. > > Can someone help? I am not sure why rcz006 is not able to receive data from idd.cise-nsf.gov at the moment. I see numerous errors in the ~ldm/logs/ldmd.log file on idd.cise-nsf.gov of the sort: Feb 02 07:45:25 atm.cise-nsf.gov rcz006.ust.hk(feed)[21357] NOTE: feed or notify failure; HEREIS: RPC: Unable to send; errno = Broken pipe I have just initiated an LDM restart on idd.cise-nsf.gov to see if this might clear the problem you are seeing (although I doubt if it will help). After the restart: I still see the same kind of 'Unable to send' messages in the ldmd.log file on idd.cise-nsf.gov In order to get you going again AND test to see if the problem is at/near idd.cise-nsf.gov or your machine, please do the following: - replicate every ~ldm/etc/ldmd.conf request line you have for idd.cise-nsf.gov replacing idd.cise-nsf.gov with idd.unidata.ucar.edu. After the change, you will have duplicate request line(s): one to idd.cise-nsf.gov and the other(s) to idd.unidata.ucar.edu - after making the additions to your ldmd.conf file, you need to restart your LDM: ldmadmin stop ldmadmin start If data starts flowing to your machine, then the problem is at/near idd.cise-nsf.gov. If it does not, the problem is somewhere closer to your machine. > Thanks No worries. Please let us know if adding the redundant feed requests clears your problem. 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: OGC-117993 Department: Support LDM Priority: Normal Status: Closed