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

[LDM #NTH-493887]: ldmping one way only



Donna,

Are the firewalls on ldm-relay1 and ldm3 configured to allow incoming TCP
connections from ldm3 to port 388? You can test this by executing the command
"telnet ldm-relay1 388" on ldm3.

Also, you might get some ideas from
<https://github.com/Unidata/LDM/wiki/Troubleshooting#receiving>.

We don't know how these systems are supposed to be working together. Would you
please explain or call us at 303-497-8642.

> I'm stuck with a problem. With one relay down we have only the other relay
> working (until tomorrow).
> 
> I find that ldm-relay1 will successfully ldmping the cluster nodes (ldm1,
> ldm2, and ldm3). But ldmping from ldm1, ldm2 and ldm3 does not succeed.
> 
> address@hidden ~]$ ldmping -i 0 ldm-relay1
> > Nov 09 18:53:09 ulog INFO:      State    Elapsed Port   Remote_Host
> >     rpc_stat
> > Nov 09 18:53:09 ulog INFO: Resolving ldm-relay1 to 165.91.55.27 took
> > 0.001211 seconds
> > Nov 09 18:53:19 ulog ERROR: SVC_UNAVAIL  10.001596    0   ldm-relay1
> > h_clnt_create(ldm-relay1): Timed out while creating connection
> > address@hidden ~]$
> 
> ?With all three acting this way, there is a lot of data not getting out to
> users.?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: NTH-493887
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.



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.