19991108: Re: problems with ldm Debian Linux (fwd)

===============================================================================
Robb Kambic                                Unidata Program Center
Software Engineer III                      Univ. Corp for Atmospheric Research
address@hidden             WWW: http://www.unidata.ucar.edu/
===============================================================================

---------- Forwarded message ----------
Date: Mon, 08 Nov 1999 13:09:15 -0700
From: Unidata Support <address@hidden>
To: address@hidden
Subject: 19991108: Re: problems with ldm Debian Linux


------- Forwarded Message

>To: "D. J. Raymond" <address@hidden>
>cc: address@hidden,
>cc: Jeff Masters <address@hidden>
>From: Jeff Masters <address@hidden>
>Subject: Re: problems with ldm
>Organization: .
>Keywords: 199911082001.NAA11833

Looking in my ldmd.log file, heron.nmt.edu is the only machine showing the
I/O errors for the McIdas data, so I do suspect it is something on your
end. You might try feeding from aldehyde.sprl.umich.edu to see if you get
a change, I do have the latest version of ldm running on that machine, the
ldm version on blueskies is not the latest.

The other option is to try feeding from a totally different source that
umich; however, I'm guessing you path to any other IDD machine will take
you through the Internet bottleneck we identified in our last
correspondence as the likely culprit for the lost data.

 Jeff 

On Mon, 8 Nov 1999, D. J. Raymond wrote:

> Hello,
> 
> I earlier mentioned the problems I had getting mcidas data from
> blueskies.  After trying some things I notice that restarting the
> ldm (v 5.0.6) solves the problem and mcidas data come flowing in
> again.  After a few days things deteriorate and mcidas data only
> arrive sporadically.  This began happening bigtime in October.
> 
> The transition to bad behavior appears to be accompanied by the
> following transition in log messages:
> 
> ^@Nov 06 21:21:59 blueskies[250]: run_requester: 19991106202159.009 TS_ENDT 
> {{W\
> MO,  "(^[A-OQ-X])|(^[YZ].[^AHIJRU])"}}
> ^@Nov 06 21:22:03 blueskies[250]: FEEDME(blueskies.sprl.umich.edu): RPC: 
> Progra\
> m not registered
> ^@Nov 06 21:33:58 141.213.23.92[251]: run_requester: 19991106203358.419 
> TS_ENDT\
>  {{MCIDAS,  "(^[A-OQ-X])|(^[YZ].[^AHIJRU])"}}
> ^@Nov 06 21:33:58 141.213.23.92[251]: FEEDME(141.213.23.92): RPC: Program not 
> r\
> egistered
> ^@Nov 06 21:34:06 blueskies[250]: run_requester: 19991106203406.289 TS_ENDT 
> {{W\
> MO,  "(^[A-OQ-X])|(^[YZ].[^AHIJRU])"}}
> ^@Nov 06 21:34:06 blueskies[250]: FEEDME(blueskies.sprl.umich.edu): RPC: 
> Progra\
> m not registered
> ^@Nov 06 21:45:33 141.213.23.92[251]: FEEDME(141.213.23.92): OK
> ^@Nov 06 21:45:40 blueskies[250]: FEEDME(blueskies.sprl.umich.edu): OK
> ^@Nov 06 22:03:39 141.213.23.92[251]: Timed out after 720 seconds inactivity
> ^@Nov 06 22:03:39 141.213.23.92[251]: Disconnect
> ^@Nov 06 22:04:09 141.213.23.92[251]: run_requester: 19991106213724.013 
> TS_ENDT\
>  {{MCIDAS,  "(^[A-OQ-X])|(^[YZ].[^AHIJRU])"}}
> ^@Nov 06 22:04:10 141.213.23.92[251]: FEEDME(141.213.23.92): OK
> ^@Nov 06 22:04:10 141.213.23.92[251]: Connection reset by peer
> ^@Nov 06 22:04:10 141.213.23.92[251]: Disconnect
> 
> Have you noticed this happening elsewhere?  I am using a rather early
> version of glibc -- 2.0.7 according to how Debian numbers things.
> Could this be the problem?
> 
> What is odd is that the problem started in October with no changes in
> software or hardware.
> 
> The network has been bad lately, but I am not convinced that the
> problem is solely the fault of the internet.
> 
> Dave Raymond
> 


------- End of Forwarded Message