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.
On Mon, 2 Aug 1999, Chad Johnson wrote: >Unidata Support wrote: >> >> As you can see, we got two East IRs and one West one. The strange thing >> that I am seeing is that a notifyme from Unidata to unidata.ssec.wisc.edu >> times out while trying to make a connection. > >Tom, > >In our ldmd logs I am seeing many gethostbyaddr failures and lookup timeout >failures. The exact >errors look like. > >Aug 02 14:08:24 unidata rpc.ldmd[8929]: gethostbyaddr: failed for 130.39.129.3 >Aug 02 14:08:24 unidata rpc.ldmd[8929]: Denying connection from 130.39.129.3 > >The feeds effected appear to be... > >128.174.80.44 >128.95.89.2 >141.213.23.92 >198.115.158.1 >128.118.28.2 >130.39.129.3 > >Our Technical Computing staff is looking into the problem. Please bear with us. > >-Chad Folks, Once again, we (sirocco.lsu, i.e. 130.39.129.3) seem to be part of the problem. I'm still mystified. The logs are showing constant connection time-outs to unidata, but when I restart the feed, it makes the connection OK. I'll dig a bit deeper... -- Kind regards, Ric [ Alaric S. Haag, Computer Manager mailto:address@hidden ] [ Southern Regional Climate Center Voice: (225) 388-6438 ] [ Louisiana State University FAX: (225) 388-2912 ] [ Baton Rouge, LA 70803 http://www.srcc.lsu.edu ]