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

20020314: ldm / problem at Utah State

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20020314: ldm / problem at Utah State
  • Date: Sat, 16 Mar 2002 15:36:11 -0700
>From: "Dan A. Dansereau" <address@hidden>
>Organization: USU
>Keywords: 200203141849.g2EInqa04914 LDM

Dan,

I would have gotten to your emails (3 of them) sooner, but I was involved
in two days worth of meetings here at the UPC.

>I'm back - again!

Just when I thought it was safe to go in the water ;-)

>I have a few questions/comments
>
>**1**
>I'm getting a large number of error of the following type
>conection reset by peer/disconnects/retransmission.
>so I sent the sysadmin/master the following
>.................................................
>On Mon, 11 Mar 2002, Dan A. Dansereau wrote:
>
>DAD> Paul
>DAD> Hi - sorry to bother you - but I'm trying complete
>DAD> the ldm hookup for the database - and I have one (?) 
>DAD> small problem - I get the following ( this is in the LDM log),
>DAD> 
>DAD> Mar 11 17:59:28 tornado pqexpire[256768]: > Recycled 171262.185 kb/hr ( 
>DAD> 19803.664 prods per hour)
>DAD> Mar 11 17:59:49 tornado 129.123.57.192[256791]: run_requester: 
>DAD> 20020311170349.349 TS_ENDT {{UNIDATA, ".*"}}
>DAD> Mar 11 17:59:49 tornado 129.123.57.192[256791]: FEEDME(129.123.57.192): 
>OK
>DAD> Mar 11 18:00:24 tornado 129.123.57.192[256791]: Connection reset by peer
>DAD> Mar 11 18:00:24 tornado 129.123.57.192[256791]: Disconnect
>DAD> Mar 11 18:00:54 tornado 129.123.57.192[256791]: run_requester: 

So, this appears that tornado is attempting to feed from allegan.nr.usu.edu
and the connection is going up or down.

>....................................................................
>His response was
>....................................................................
>Looks like there is a problem with the format of your RPC request.
>You might want to forward the err messages to the developers and see if
>there is a problem with your app or if you have it misconfigured.
>My Syslog msgs:
>----------------------
>Mar 11 17:59:49 allegan tornado[13207]: 
>Connection from tornado.ser.usu.edu
>Mar 11 17:59:49 allegan tornado(feed)[13207]:
>Starting Up:20020311170349.349 TS_ENDT {{UNIDATA, ".*"}}
>Mar 11 17:59:49 allegan tornado(feed)[13207]:
>topo: tornado.ser.usu.edu UNIDATA
>Mar 11 18:00:24 allegan tornado(feed)[13207]: 
>HRLK70 KWBC 111200 /mAVN:
>RPC: Server can't decode arguments (11)
>Mar 11 18:00:24 allegan tornado(feed)[13207]: 
>pq_sequence failed: I/O error (errno = 5)
>Mar 11 18:00:24 allegan tornado(feed)[13207]: Exiting
>
>Problem is on your end
>...........................................................................

I don't think there is a problem with the LDM as other DEC OSF/1 sites
are using it.

>I have 5-8Mbits/sec wireless link - and DEC ALPHA's with OSF 5.1
>He has a Ultra Spark -???
>
>The link has operated at over 5Mbits/sec on NCEP large file xfers,
>LMD seems to max out at 1.5Mbytes/sec but averages below 800Kbytes/sec
>so I don't think that it is the link.

I suppose the NCEP xfers were FTPs.  The LDM uses remote procedure calls,
so it is exercising a different code set from FTP.

>Any clues?????

Not right off.  I will see if anyone else here has any ideas.

What happens when you try some simple notifymes to allegan:

<from tornado as 'ldm'>

notifyme -vxl- -f ANY -h allegan.nr.usu.edu -o 600

Tom Yoksas