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

[IDD #ABS-260282]: Cluster Fisica Disconnecting due to LDM fail ure

Hi Reymer,

I apologize for the very slow response on your questions below.  I was on
travel for all of last week, and I had limited access to the Internet...

re:
> I hope that you be ok, I've a trouble this is the log output:
> 
> 
> Oct 28 19:52:06 cluster 128.117.140.3[8180] ERROR: Disconnecting due to LDM 
> fail
> ure; nullproc_6 failure to 128.117.140.3; RPC: Unable to receive; errno = 
> Connec
> tion reset by peer
> Oct 28 19:52:06 cluster 128.117.140.3[8181] ERROR: Disconnecting due to LDM 
> fail
> ure; nullproc_6 failure to 128.117.140.3; RPC: Unable to receive; errno = 
> Connec
> tion reset by peer
> Oct 28 19:52:14 cluster 128.117.140.3[8183] NOTE: LDM-6 desired 
> product-class: 2
> 0101028185214.831 TS_ENDT {{ANY,  ".*"},{NONE,  
> "SIG=8af2840a378ae63106b2818534e
> daff6"}}
> Oct 28 19:52:15 cluster 128.117.140.3[8183] ERROR: Disconnecting due to LDM 
> fail
> ure; nullproc_6 failure to 128.117.140.3; RPC: Unable to receive; errno = 
> Connec
> tion reset by peer
> Oct 28 19:52:26 cluster 128.117.140.3[8182] NOTE: LDM-6 desired 
> product-class: 2
> 0101028185226.140 TS_ENDT {{UNIWISC,  ".*"},{NONE,  
> "SIG=db386e3ba11cca5adefc7cc
> 50c6182e2"}}
> Oct 28 19:52:26 cluster 128.117.140.3[8182] ERROR: Disconnecting due to LDM 
> fail
> ure; nullproc_6 failure to 128.117.140.3; RPC: Unable to receive; errno = 
> Connec
> tion reset by peer


We see the same kind of disconnect messages on our side.  I am not sure what
is causing this, but I suspect some problem in your network connection.  i
will need to talk to our system administrators to make sure that this is,
in fact, the problem.

re:
> the IP address of the ldm server on the cluster is declared on our DNS
> server like cluster.fisica.ucr.ac.cr
> 
> ravs@gauss:~$ dig @8.8.8.8 cluster.fisica.ucr.ac.cr
> 
> ; <<>> DiG 9.7.1-P2 <<>> @8.8.8.8 cluster.fisica.ucr.ac.cr
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55358
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
> 
> ;; QUESTION SECTION:
> ;cluster.fisica.ucr.ac.cr.    IN      A
> 
> ;; ANSWER SECTION:
> cluster.fisica.ucr.ac.cr. 86400       IN      A       200.9.33.37
> 
> ;; Query time: 338 msec
> ;; SERVER: 8.8.8.8#53(8.8.8.8)
> ;; WHEN: Thu Oct 28 13:53:17 2010
> ;; MSG SIZE  rcvd: 58
> 
> ravs@gauss:~$

Reverse DNS is still not available:

% nslookup cluster.fisica.ucr.ac.cr
Server:  laraine.unidata.ucar.edu
Address:  128.117.140.62

Non-authoritative answer:
Name:    cluster.fisica.ucr.ac.cr
Address:  200.9.33.37

% nslookup 200.9.33.37
Server:  laraine.unidata.ucar.edu
Address:  128.117.140.62

*** laraine.unidata.ucar.edu can't find 200.9.33.37: Non-existent host/domain

The reverse DNS (IP to name) is what is needed most for the LDM.

re:
> we don't have ldm data..

We currently do not see a feed request from your machine.  Are you
still trying to request data?

re:
> So another question how a can download data for the WRF using the LDM.

The question is which data do you want to download.  Typically sites
like to get the global half degree GFS data available in the CONDUIT
datastream.  One problem with this is the data volume is very high.
If your Internet2 pipe is large enough, this is the feed you are
likely to want.  First we need to figure out why your feed requests
to idd.unidata.ucar.edu failed (and are no longer active).

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: ABS-260282
Department: Support IDD
Priority: Normal
Status: Closed