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

Re: 20010129: ldm trouble

Hi Jennie,

I'm looking into this at the moment.  'ldmadmin watch' seems to be
working at the moment and data seems to be coming in.  I see that
something in mcidas is not finding batch.k - not sure why.  I also see
the old path in batch.k.  I will change that.  And, I see all the error
messages in the log - yuck!  That wasn't happening last week.  Will try
to fix ASAP.

Anne


Unidata Support wrote:
> 
> ------- Forwarded Message
> 
> >To: address@hidden
> >cc: address@hidden
> >From: Local Data Manager <address@hidden>
> >Subject: ldm trouble
> >Organization: UCAR/Unidata
> >Keywords: 200101291912.f0TJCgX19824
> 
> Anne,
> 
> Well, as I was trying to look at what the ldm was doing, it
> seemed to fail altogether, I did and ldmadmin watch, and nothing
> came up, but just about that time, I got a message that the ldm
> had failed over.  When I looked at the logs, I find the response
> to a FEEDME on navier (my default upstream host) was RPC: Program
> not registered, and then everything seemed to stop all together.
> 
> I am uncertain about  restarting things at the moment.  A few
> thoughts come to mind, did changing the user making requests
> have any impact on our upstream host (they only know that
> requests
> come from a certain IP address, correct, so its doesn't
> "register"
> if we are user ldma or user ldm?
> 
> As I noted, we have been getting some data updated, so some
> things
> were getting through.  I did note that there is an old PATH
> in the /usr/local/ldm/util file batch.k.  This is the script
> that launches mcidas commands, and it needs the path of the
> ldm-mcidas.  It is still pointing to /home/ldma/bin/ldm-mcidas
> and it should now be /usr/local/ldm/ldm-mcidas/bin (I think.
> I only have one terminal open at the moment, so I cannot look).
> This is probably minor, unless the new ldm required a new version
> of ldm-mcidas and we were telling it to use the old, that would
> potentially mess up some of our scripts that make new products.
> 
> Here is the tail of the ldmd.log file:
> 
> Jan 29 18:38:56 windfall.evsc.Virginia.EDU pqact[6694]: child
> 19618 exited with
> status 127
> Jan 29 18:38:57 windfall.evsc.Virginia.EDU pqact[6694]: child
> 19620 exited with
> status 127
> Jan 29 18:38:57 windfall.evsc.Virginia.EDU pqact[6694]: child
> 19622 exited with
> status 127
> Jan 29 18:38:57 windfall.evsc.Virginia.EDU pqact[6694]: child
> 19624 exited with
> status 127
> Jan 29 18:39:21 windfall.evsc.Virginia.EDU navier[6697]:
> Connection reset by pee
> r
> Jan 29 18:39:21 windfall.evsc.Virginia.EDU navier[6697]:
> Disconnect
> Jan 29 18:39:51 windfall.evsc.Virginia.EDU navier[6697]:
> run_requester: 20010129
> 183831.903 TS_ENDT {{HDS|DDPLUS,  ".*"},{MCIDAS,  "^pnga2area
> Q[01]"}}
> Jan 29 18:39:51 windfall.evsc.Virginia.EDU navier[6697]:
> FEEDME(navier.meteo.psu
> .edu): RPC: Program not registered
> Jan 29 18:50:00 windfall.evsc.Virginia.EDU ldmping[25551]:
> SVC_UNAVAIL   0.25273
> 9    0   navier.meteo.psu.edu  RPC: Program not registered
> Jan 29 18:50:02 windfall.evsc.Virginia.EDU rpc.ldmd[6692]:
> Exiting
> Jan 29 18:50:02 windfall.evsc.Virginia.EDU rpc.ldmd[6692]:
> Terminating process g
> roup
> Jan 29 18:50:02 windfall.evsc.Virginia.EDU pqact[6694]: Exiting
> Jan 29 18:50:02 windfall.evsc.Virginia.EDU pqbinstats[6696]:
> Exiting
> Jan 29 18:50:32 windfall.evsc.Virginia.EDU navier[6697]: Exiting
> 
> Unsure of what to do ....
> 
> Jennie
> 
> --
> 
> ------- End of Forwarded Message

-- 
***************************************************
Anne Wilson                     UCAR Unidata Program            
address@hidden                 P.O. Box 3000
                                  Boulder, CO  80307
----------------------------------------------------
Unidata WWW server       http://www.unidata.ucar.edu/
****************************************************