[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #UWG-237907]: access to idd



Hi Greg,

> Our ldm server is currently unable to connect to idd.unidata.ucar.edu .     
> The connection was working successfully until a restart of the ldm server 
> about an hour ago.  We've checked the typical problems and aren't finding an 
> explanation.  Below are the logs and responses from an ldmping and our ldm 
> server.  Any insight into trouble shooting would be appreciated.  Our ldm 
> server host is ldm.dri.edu.  Is there a possibility of confirmation if the 
> connections requests are being seen by idd.unidata.ucar.edu?
> 
> ldmping
> 
> # ldmping idd.unidata.ucar.edu
> 20190510T213142.400290Z ldmping[24299] INFO ldmping.c:51:print_label()      
> State    Elapsed Port   Remote_Host           rpc_stat
> 20190510T213142.400798Z ldmping[24299] INFO error.c:236:err_log() Resolving 
> idd.unidata.ucar.edu to 128.117.140.3 took 0.00037 seconds
> 20190510T213143.233528Z ldmping[24299] ERROR ldmping.c:75:print_hstat()  
> ADDRESSED   0.833139    0   idd.unidata.ucar.edu  RPC: Unable to receive; 
> errno = Connection reset by peer
> 20190510T213218.245748Z ldmping[24299] ERROR ldmping.c:75:print_hstat()      
> NAMED  10.012074    0   idd.unidata.ucar.edu  can't contact portmapper: RPC: 
> Timed out
> 20190510T213243.246696Z ldmping[24299] INFO error.c:236:err_log() Resolving 
> idd.unidata.ucar.edu to 128.117.140.3 took 3.3e-05 seconds
> 20190510T213244.087546Z ldmping[24299] ERROR ldmping.c:75:print_hstat()  
> ADDRESSED   0.840909    0   idd.unidata.ucar.edu  RPC: Unable to receive; 
> errno = Connection reset by peer
> 20190510T213319.093696Z ldmping[24299] ERROR ldmping.c:75:print_hstat()      
> NAMED  10.006020    0   idd.unidata.ucar.edu  can't contact portmapper: RPC: 
> Timed out
> 
> ldmadmin tail
> 
> 20190510T213529.439850Z idd.unidata.ucar.edu[24246] NOTE 
> requester6.c:588:req6_new() LDM-6 desired product-class: 
> 20190510203529.439790 TS_ENDT {{CONDUIT, ".*"},{NONE, 
> "SIG=97f3e3036e2ca58cab30fc47115b4a78"}}
> 20190510T213529.440217Z idd.unidata.ucar.edu[24244] NOTE 
> requester6.c:588:req6_new() LDM-6 desired product-class: 
> 20190510203529.440175 TS_ENDT {{CONDUIT, "gfs.*0p25*"},{NONE, 
> "SIG=c7d16b48b480c6a334ce0cf0d9f1181e"}}
> 20190510T213529.607686Z idd.unidata.ucar.edu[24245] NOTE 
> requester6.c:588:req6_new() LDM-6 desired product-class: 
> 20190510203529.607654 TS_ENDT {{CONDUIT, "nam.*"},{NONE, 
> "SIG=97f3e3036e2ca58cab30fc47115b4a78"}}
> 20190510T213530.302718Z idd.unidata.ucar.edu[24246] NOTE 
> error.c:236:err_log() Upstream LDM didn't reply to FEEDME request; RPC: 
> Unable to receive; errno = Connection reset by peer
> 20190510T213530.430721Z idd.unidata.ucar.edu[24244] NOTE 
> error.c:236:err_log() Upstream LDM didn't reply to FEEDME request; RPC: 
> Unable to receive; errno = Connection reset by peer
> 20190510T213530.542036Z idd.unidata.ucar.edu[24245] NOTE 
> error.c:236:err_log() Upstream LDM didn't reply to FEEDME request; RPC: 
> Unable to receive; errno = Connection reset by peer

Thanks for reporting this.

Because your host is in the ".edu" domain, it should have been allowed to 
connect to our LDM. Apparently, however, there was no reverse-DNS lookup for 
your hostname at the time in question:

$ ssh uni15-r grep ^20190510T2135 logs/ldmd.log.1 | egrep 
'134\.197\.190\.156|dri\.edu'
20190510T213531.580886Z                 ldmd[20890]             
ldmd.c:runChildLdm() ERROR Denying connection from "134.197.190.156" because 
not allowed
20190510T213531.709825Z                 ldmd[20891]             
ldmd.c:runChildLdm() ERROR Denying connection from "134.197.190.156" because 
not allowed
20190510T213531.821460Z                 ldmd[20892]             
ldmd.c:runChildLdm() ERROR Denying connection from "134.197.190.156" because 
not allowed
$ 

I notice that your host is now connected, however, so I assume the situation 
has been resolved.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: UWG-237907
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.



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.