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

Re: 19991108: problems with ldm Debian Linux

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: Re: 19991108: problems with ldm Debian Linux
  • Date: Mon, 8 Nov 1999 12:43:18 -0700 (MST)
On Mon, 8 Nov 1999, Unidata Support wrote:

> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >cc: Jeff Masters <address@hidden>
> >From: "D. J. Raymond" <address@hidden>
> >Subject: problems with ldm
> >Organization: .
> >Keywords: 199911081906.MAA10323
> 
> 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

Dave,

Program not register means that the blueskies ldm is not running/ not
registered with the portmapper. This is a problem at Michigan. When you
get this message go to your failover site.



> ^@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?
> 
Because the differences in Linux, UPC is  only supporting  Red Hat Linux.
I know Debian is very similar but there are differences that can cause
major problems.  Not saying that this problem is because of Debian. 


> 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.
> 
I agree.  When the problem occurs again, do a ldmping to Michigan.

Robb...


> Dave Raymond
> 
> 
> ------- End of Forwarded Message
> 

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