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

[IDD #ZEM-237169]: Starting LDM Feed



Hi Shengting,

The fact that your 'notifyme' invocation does not connect
to idd.unidata.ucar.edu, but your 'telnet idd.unidata.ucar.edu 388'
does and then the connection is broken, is puzzling:

$ telnet idd.unidata.ucar.edu 388
Trying 128.117.140.3...
Connected to idd.unidata.ucar.edu.     <- the telnet invocation connects
Escape character is '^]'.
Connection closed by foreign host.     <- something is closing the connection

It is as if something is interrupting the port 388 connection to
idd.unidata.ucar.edu.  To my knowledge, nothing on our end should
be terminating the connection.  Also, I verified that no LDM on
the real server backends of the idd.unidata.ucar.edu cluster
received the connection attempt(s) by your 'notifyme' invocation(s).

We will need to consult our system administrator to see if he
can figure out what may be happening

Cheers,

Tom

> Here are the test results:
> 
> $ notifyme -v -h idd.unidata.ucar.edu
> 20160818T221457.638895Z notifyme[5300] NOTE notifyme.c:385:main() Starting 
> Up: idd.unidata.ucar.edu: 20160818221457.638685 TS_ENDT {{ANY, ".*"}}
> 20160818T221457.638946Z notifyme[5300] NOTE ldm5_clnt.c:460:forn5() LDM-5 
> desired product-class: 20160818221457.638685 TS_ENDT {{ANY, ".*"}}
> 20160818T221457.639196Z notifyme[5300] INFO error.c:236:err_log() Resolving 
> idd.unidata.ucar.edu to 128.117.140.3 took 0.000164 seconds
> 20160818T221547.664443Z notifyme[5300] NOTE ldm5_clnt.c:460:forn5() LDM-5 
> desired product-class: 20160818221457.638685 TS_ENDT {{ANY, ".*"}}
> 20160818T221547.664487Z notifyme[5300] INFO error.c:236:err_log() Resolving 
> idd.unidata.ucar.edu to 128.117.140.3 took 5e-06 seconds
> ^C20160818T221626.955707Z notifyme[5300] NOTE notifyme.c:66:cleanup() exiting
> 
> 
> $ telnet idd.unidata.ucar.edu 388
> Trying 128.117.140.3...
> Connected to idd.unidata.ucar.edu.
> Escape character is '^]'.
> Connection closed by foreign host.
> 
> 
> Thanks,
> Shengting
> 
> ________________________________________
> From: Unidata IDD Support [address@hidden]
> Sent: Thursday, August 18, 2016 3:13 PM
> To: Cui, Shengting
> Cc: address@hidden; Vaughan, Joseph K; Cui, Shengting
> Subject: [IDD #ZEM-237169]: Starting LDM Feed
> 
> Shengting,
> 
> Test your ability to connect with our LDM server with the command
> 
> notifyme -v -h idd.unidata.ucar.edu
> 
> If that doesn't work, then try the command
> 
> telnet idd.unidata.ucar.edu 388
> 
> Enter ^C to escape.
> 
> Let us know what you find.
> 
> > Maybe I was in too much of a hurry? The attached ldmd.log file says "... 
> > Upstream LDM didn't reply to FEEDME request; RPC: Timed out"
> 
> Regards,
> Steve Emmerson
> 
> Ticket Details
> ===================
> Ticket ID: ZEM-237169
> 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.
> 
> 
> 

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: ZEM-237169
Department: Support IDD
Priority: Normal
Status: Open
===================
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.