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.
Yoshihiro, > The only problem which still remains is with the new > computer atm78.fis.ua.pt (under fedora 5) > ----------------------------------------------------- > The log file in the atm78.fis.ua.pt seems that the problem > is related to RPC : > > more ldmd.log > Oct 25 12:33:20 atm78 rpc.ldmd[28738] NOTE: Starting Up > (version: 6.4.6; built: > Oct 21 2006 15:28:45) > Oct 25 12:33:20 atm78 rpc.ldmd[28738] NOTE: Using local > address 0.0.0.0:388 > Oct 25 12:33:21 atm78 pqact[28740] NOTE: Starting Up > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28741] NOTE: > Starting Up(6.4.6): idd.cise > -nsf.gov:388 20061025113321.010 TS_ENDT {{CONDUIT, > "prod/gfs.*pgrb2.*[05]$"}} > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28741] NOTE: LDM-6 > desired product-class: > 20061025113321.010 TS_ENDT {{CONDUIT, > "prod/gfs.*pgrb2.*[05]$"}} > ..... > ....Oct 25 12:33:21 atm78 idd.unidata.ucar.edu[28746] > NOTE: Starting Up(6.4.6): idd.unidata.ucar.edu:388 2006102 > 5113321.013 TS_ENDT {{CONDUIT, "prod/gfs.*pgrb2.*[27]$"}} > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28747] NOTE: > Starting Up(6.4.6): idd.cise-nsf.gov:388 20061025113321. > 014 TS_ENDT {{CONDUIT, "prod/gfs.*pgrb2.*[38]$"}} > Oct 25 12:33:21 atm78 idd.unidata.ucar.edu[28748] NOTE: > Starting Up(6.4.6): idd.unidata.ucar.edu:388 2006102 > 5113321.014 TS_ENDT {{CONDUIT, "prod/gfs.*pgrb2.*[38]$"}} > > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28759] NOTE: LDM-6 > desired product-class: 20061025113321.253 TS_ENDT > {{CONDUIT, "prod/gfs.*pgrb.*[49]$"}} > Oct 25 12:33:21 atm78 idd.unidata.ucar.edu[28760] NOTE: > LDM-6 desired product-class: 20061025113321.261 TS_E > NDT {{CONDUIT, "prod/gfs.*pgrb.*[49]$"}} > ... > > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28741] ERROR: > Disconnecting due to LDM failure; nullproc_6 failure to > idd.cise-nsf.gov; RPC: Unable to receive; errno = > Connection reset by peer > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28743] ERROR: > Disconnecting due to LDM failure; nullproc_6 failure to > idd.cise-nsf.gov; RPC: Unable to receive; errno = > Connection reset by peer > Oct 25 12:33:21 atm78 idd.cise-nsf.gov[28741] NOTE: LDM-6 > desired product-class: 20061025113321.405 TS_ENDT > {{CONDUIT, "prod/gfs.*pgrb2.*[05]$"}} > > > Do you have any suggestion to solve the problem ?? The LDM on idd.cise-nsf.gov logged the following message at approximately the same time: Oct 25 12:33:13 atm.cise-nsf.gov rpc.ldmd[25154] NOTE: Denying connection from "193.137.81.78" Oct 25 12:33:16 atm.cise-nsf.gov last message repeated 9 times The above means that the LDM on idd-cise-nsf.gov was unable to convert the IP address 193.137.81.78 into a hostname in order to match that hostname against an ALLOW entry in the LDM's configuration-file. The problem, therefore, is the failure to convert that IP address to a hostname. I note that my desktop workstation can't convert the IP address either: ~/ldm/package/src/protocol: nslookup 193.137.81.78 Server: 128.117.140.62 Address: 128.117.140.62#53 ** server can't find 78.81.137.193.in-addr.arpa: NXDOMAIN You must talk with your networking people and fix the problem of converting that IP address into a hostname. Regards, Steve Emmerson Ticket Details =================== Ticket ID: JCB-153899 Department: Support LDM Priority: Normal Status: Closed