[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[LDM #CGE-685224]: Texas Tech connection to idd
- Subject: [LDM #CGE-685224]: Texas Tech connection to idd
- Date: Fri, 15 Dec 2017 13:39:37 -0700
Bruce,
The wireshark dump has this:
1 2017-12-15 10:39:16.563050 128.117.140.3 129.118.157.89
TCP 78 388→32884 [SYN, ACK] Seq=0 Ack=1 Win=14480 Len=0 MSS=1460
SACK_PERM=1 TSval=2685230929 TSecr=4959212 WS=256
2 2017-12-15 10:39:16.611079 128.117.140.3 129.118.157.89
TCP 70 388→32884 [ACK] Seq=1 Ack=125 Win=14592 Len=0
TSval=2685230978 TSecr=4959260
3 2017-12-15 10:39:17.436585 128.117.140.3 129.118.157.89
TCP 94 388→32884 [PSH, ACK] Seq=1 Ack=125 Win=14592 Len=24
TSval=2685231803 TSecr=4959260
4 2017-12-15 10:39:17.436620 128.117.140.3 129.118.157.89
TCP 70 388→32884 [RST, ACK] Seq=25 Ack=125 Win=14592 Len=0
TSval=2685231803 TSecr=4959260
5 2017-12-15 10:39:18.207817 128.117.140.3 129.118.157.89
TCP 58 388→32884 [RST] Seq=25 Win=0 Len=0
A reset (RST) packet from 128.117.140.3 would definitely cause the connection
to close.
I tried a reverse DNS lookup on 129.118.157.89 and got nothing. That's the
problem. Our LDM server is trying to convert the IP address associated with the
incoming connection into a fully-qualified hostname to match against the ALLOW
entries the LDM configuration-file. The conversion can't be done because your
system doesn't have a DNS entry.
Tell your network administrator to add a DNS entry for your LDM host's IP
address. Once that's done, things should work.
> Perhaps this will help? Attached are two wireshark reports... one of which
> is in plain text if necessary Also included is a portion of the log file
> when the connection went down. ldmping still reports no access to
> idd.unidata.ucar.edu.
>
> 20171213T071035.923494Z idd.unidata.ucar.edu[25663] NOTE
> svc_tcp.c:358:readtcp() EOF on socket 5
> 20171213T071035.923507Z idd.unidata.ucar.edu[25663] NOTE
> one_svc_run.c:95:one_svc_run() one_svc_run(): RPC layer closed connection
> 20171213T071035.923512Z idd.unidata.ucar.edu[25663] NOTE
> ldm_config_file.c:841:requester_exec() Log messages flushed
> 20171213T071035.923520Z idd.unidata.ucar.edu[25663] NOTE
> error.c:236:err_log() Connection to upstream LDM closed: pid=28607
> 20171213T071036.273487Z idd.unidata.ucar.edu[25664] NOTE
> svc_tcp.c:358:readtcp() EOF on socket 6
> 20171213T071036.273502Z idd.unidata.ucar.edu[25664] NOTE
> one_svc_run.c:95:one_svc_run() one_svc_run(): RPC layer closed connection
> 20171213T071036.273507Z idd.unidata.ucar.edu[25664] NOTE
> ldm_config_file.c:841:requester_exec() Log messages flushed
> 20171213T071036.273515Z idd.unidata.ucar.edu[25664] NOTE
> error.c:236:err_log() Connection to upstream LDM closed: pid=28603
> 20171213T071036.635618Z idd.unidata.ucar.edu[25662] NOTE
> svc_tcp.c:358:readtcp() EOF on socket 5
> 20171213T071036.635636Z idd.unidata.ucar.edu[25662] NOTE
> one_svc_run.c:95:one_svc_run() one_svc_run(): RPC layer closed connection
> 20171213T071036.635645Z idd.unidata.ucar.edu[25662] NOTE
> ldm_config_file.c:841:requester_exec() Log messages flushed
> 20171213T071036.635654Z idd.unidata.ucar.edu[25662] NOTE
> error.c:236:err_log() Connection to upstream LDM closed: pid=28602
Regards,
Steve Emmerson
Ticket Details
===================
Ticket ID: CGE-685224
Department: Support LDM
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.