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 Russ, re > I’ve noticed a couple significant gaps in data flow to our LDM lately, mostly > recently today (and ongoing). Looking in the logs, it seems that there’s an > issue connecting to idd.unidata.ucar.edu: > > 20200714T195847.722975Z idd.unidata.ucar.edu[9065] error.c:err_log:236 > WARN Couldn't connect to LDM on idd.unidata.ucar.edu using either > port 388 or portmapper; : RPC: Remote system error - Connection timed out > 20200714T195847.722975Z idd.unidata.ucar.edu[9064] error.c:err_log:236 > WARN Couldn't connect to LDM on idd.unidata.ucar.edu using either > port 388 or portmapper; : RPC: Remote system error - Connection timed out > 20200714T195847.722975Z idd.unidata.ucar.edu[9063] error.c:err_log:236 > WARN Couldn't connect to LDM on idd.unidata.ucar.edu using either > port 388 or portmapper; : RPC: Remote system error - Connection timed out > 20200714T195847.722988Z idd.unidata.ucar.edu[9062] error.c:err_log:236 > WARN Couldn't connect to LDM on idd.unidata.ucar.edu using either > port 388 or portmapper; : RPC: Remote system error - Connection timed out > 20200714T195847.722994Z idd.unidata.ucar.edu[9067] error.c:err_log:236 > WARN Couldn't connect to LDM on idd.unidata.ucar.edu using either > port 388 or portmapper; : RPC: Remote system error - Connection timed out > 20200714T195847.723044Z idd.unidata.ucar.edu[9065] > LdmConfFile.c:requester_exec:925 NOTE Sleeping 60 seconds before > retrying... > 20200714T195847.723093Z idd.unidata.ucar.edu[9064] > LdmConfFile.c:requester_exec:925 NOTE Sleeping 60 seconds before > retrying... > 20200714T195847.723141Z idd.unidata.ucar.edu[9063] > LdmConfFile.c:requester_exec:925 NOTE Sleeping 60 seconds before > retrying... > 20200714T195847.723188Z idd.unidata.ucar.edu[9062] > LdmConfFile.c:requester_exec:925 NOTE Sleeping 60 seconds before > retrying... > 20200714T195847.723236Z idd.unidata.ucar.edu[9067] > LdmConfFile.c:requester_exec:925 NOTE Sleeping 60 seconds before > retrying... > 20200714T195847.726927Z idd.unidata.ucar.edu[9066] error.c:err_log:236 > WARN Couldn't connect to LDM on idd.unidata.ucar.edu using either > port 388 or portmapper; : RPC: Remote system error - Connection timed out > > Are there issues with the server on your end, or is there something I need to > look at on our end? An outage at the NWSC that was originally plannd to last for a half hour stretched to 90 minutes, then an additional 3.5 hours plus extending the outage to at least 3 pm MDT today. Emails to the address@hidden and address@hidden have informed sites about the outage and have recommended replicating LDM configuration file REQUEST(s) to redundantly feed from our backup IDD relay cluster iddb.unidata.ucar.edu until our primary top level IDD relay cluster,idd.unidata.ucar.edu, can once again access the Internet. If you are not subscribed to the ldm-users or conduit email lists, we recommend subscribing so you will be notified about outages like the one today. We apologize for the interruption of data deliver services! 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: MVK-912520 Department: Support IDD 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.