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

[LDM #UUE-301297]: ldmping one way only



Hi Donna,

re:
> What are the chances that both ldm-relay1 and earthdata have a mechanically
> faulty port 388?

I'd say zero.

re:
> Is it all software controlled and there is nothing mechanical about it?

Ports are software constructs.

In addition, we know that there is nothing wrong on ldm-relay1 since we are
able to connect to both ldm-relay0 and ldm-relay1 from machines here in Unidata
(we are able to connect to the LDMs on those machines by virtue of their
LDM configuration files having a standard ALLOW for unidata.ucar.edu machines):

<as 'ldm' on lead.unidata.ucar.edu>

~: notifyme -vl- -f ANY -h ldm-relay0.tamu.edu -o 100
20161111T153905.275983Z notifyme[11727] NOTE notifyme.c:385:main() Starting Up: 
ldm-relay0.tamu.edu: 20161111153725.275785 TS_ENDT {{ANY, ".*"}}
20161111T153905.276013Z notifyme[11727] NOTE ldm5_clnt.c:460:forn5() LDM-5 
desired product-class: 20161111153725.275785 TS_ENDT {{ANY, ".*"}}
20161111T153905.320728Z notifyme[11727] INFO error.c:236:err_log() Resolving 
ldm-relay0.tamu.edu to 165.91.55.26 took 0.044656 seconds
20161111T153905.475524Z notifyme[11727] NOTE ldm5_clnt.c:294:forn_signon() 
NOTIFYME(ldm-relay0.tamu.edu): OK
20161111T153906.475900Z notifyme[11727] INFO notifyme.c:222:notifymeprog_5()    
  77955 20161111153725.278440 NGRID 103799243  ZRNH93 KWBC 111200 
!grib2/ncep/GFS/#215/201611111200F015/RELH/975 hPa PRES
 ...

~: notifyme -vl- -f ANY -h ldm-relay1.tamu.edu -o 100
20161111T153943.704190Z notifyme[11965] NOTE notifyme.c:385:main() Starting Up: 
ldm-relay1.tamu.edu: 20161111153803.704012 TS_ENDT {{ANY, ".*"}}
20161111T153943.704219Z notifyme[11965] NOTE ldm5_clnt.c:460:forn5() LDM-5 
desired product-class: 20161111153803.704012 TS_ENDT {{ANY, ".*"}}
20161111T153943.752925Z notifyme[11965] INFO error.c:236:err_log() Resolving 
ldm-relay1.tamu.edu to 165.91.55.27 took 0.048638 seconds
20161111T153943.853466Z notifyme[11965] NOTE ldm5_clnt.c:294:forn_signon() 
NOTIFYME(ldm-relay1.tamu.edu): OK
20161111T153944.854298Z notifyme[11965] INFO notifyme.c:222:notifymeprog_5()    
  18739 20161111153803.743771 NEXRAD2 262026  
L2-BZIP2/KSFX/20161111153228/262/26/I/V06/0

These 'notifyme' invocations demonstrate that there is nothing wrong with the 
Ethernet
adapter on ldm-relay0 and ldm-relay1, and that their LDMs are running and 
receiving
realtime data.

We are also not able to contact earthdata.tamu.edu.  'ldmping's to earthdata
reported yesterday suggest that an LDM is not running on earthdata, or that it
is listening to a port other than 388:

Posted on: 20161110.2041 MST

address@hidden ~]$ ldmping -i 0 earthdata
Nov 11 03:33:56 ulog INFO:      State    Elapsed Port   Remote_Host     rpc_stat
Nov 11 03:33:56 ulog INFO: Resolving earthdata to 128.194.165.79 took 0.001451 
seconds
Nov 11 03:33:56 ulog ERROR: SVC_UNAVAIL   0.040482    0   earthdata  RPC: 
Program not registered

Yesterday, Chris M commented that the problem was likely some sort of
routing problem:

Posted on: 20161110.1452 MST

" ...
The problem we're seeing is most likely a strange routing problem of
traffic from the campus LAN to ldm-relay1.tamu.edu, specifically. The
real-server cluster nodes are able to request data from ldm-relay0.tamu.edu
just fine, but not ldm-relay1.tamu.edu. The accumulators have identical
configuration, the real-server nodes have identical configurations, and the
data paths are identical between the various hosts."

We will be very interested in knowing exactly what the problem was when it
is found and fixed!

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: UUE-301297
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.