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

Re: 20010206: Ldm quits unexpectedly (addendum)

"John C. Nordlie" wrote:
> 
> Hi, Anne.  Thanks for your reply.
> 
> I tried the pqact manually.  Here's a snipped of the output:
> 
>  > pqact -vl -
>  Feb 07 19:27:24 pqact[11977]: Starting Up
>  Feb 07 19:27:24 pqact[11977]: Successfully read pattern file
>  "/usr/local/ldm/etc/pqact.conf"
>  Feb 07 19:27:24 pqact[11977]: lastmatch: fa7803ec033d398119958cba604fa556
>  3662 20010207192725.517 IDS|DDPLUS 582  SRUS31 KWOH 071924 /pRRSPTR
>  Feb 07 19:27:24 pqact[11977]: TS_ZERO TS_ENDT {{ANY,  ".*"}}
>  Feb 07 19:27:24 pqact[11977]:        0 20010207192724.037     ANY 000
>  _BEGIN_
>  Feb 07 19:27:24 pqact[11977]:                pipe: decoders/dcnldn -m
>  25000 -b 30 -s minute05   -d data/gempak/logs/dcnldn.log  -e
>  GEMTBL=/usr/local/gempak/gempak/tables
>  data/gempak/nldn/YYYYMMDDHHNN_nldn.gem
>  Feb 07 19:27:39 pqact[11977]:     3243 20010207192725.532 IDS|DDPLUS 583
>  SRUS26 KWOH 071924 /pRRSTUA
>  Feb 07 19:27:39 pqact[11977]:      140 20010207192725.533 IDS|DDPLUS 584
>  SAUS43 KDMX 071927 /pMTRALO
>  Feb 07 19:27:39 pqact[11977]:                pipe: decoders/dcmetr -b 9
>  -m
>  72 -s sfmetar_sa.tbl -d data/gempak/logs/dcmetr.log  -e
>  GEMTBL=/usr/local/gempak/gempak/tables
>  data/gempak/surface/YYYYMMDD_sao.gem
>  Feb 07 19:27:39 pqact[11977]:     6379 20010207192725.534 IDS|DDPLUS 586
>  SRUS30 KWOH 071924 /pRRSRSA
>  Feb 07 19:27:39 pqact[11977]:      264 20010207192725.541 IDS|DDPLUS 588
>  NTUS99 KNCF 071927 /pTSTNCF
>  Feb 07 19:27:39 pqact[11977]:     7894 20010207192725.659 IDS|DDPLUS 589
>  SXUS72 KWBC 071924 /pRRSNMC
>  Feb 07 19:27:39 pqact[11977]:     1605 20010207192725.663 IDS|DDPLUS 590
>  SRUS59 KWBC 071924 /pRRSNM
>  Feb 07 19:27:39 pqact[11977]:      733 20010207192725.664 IDS|DDPLUS 591
>  SRUS54 KWBC 071924 /pRRSNY3
> <snip>
> 
> Here's what I have in the data/logs/ldmd.log file:
> 
>  > cat data/logs/ldmd.log
>  Feb 06 18:44:23 flood DCMETR[28717]: Interrupt Signal
>  Feb 06 18:44:23 flood DCNLDN[28704]: Interrupt Signal
>  Feb 06 21:58:19 flood DCACFT[28774]: Interrupt Signal
>  Feb 06 21:58:19 flood DCGRIB2[28924]: Interrupt Signal
>  Feb 06 21:58:19 flood DCAIRM[28925]: Interrupt Signal
>  Feb 06 21:58:19 flood DCUAIR[28772]: Interrupt Signal
>  Feb 06 21:58:19 flood DCMSFC[28773]: Interrupt Signal
>  Feb 06 21:58:19 flood DCLSFC[28923]: Interrupt Signal
>  Feb 06 21:58:19 flood DCMETR[28770]: Interrupt Signal
>  Feb 06 21:58:19 flood DCNLDN[28767]: Interrupt Signal
>  Feb 06 21:58:19 flood DCGRIB2[29019]: Interrupt Signal
>  Feb 06 21:58:19 flood DCGRIB2[29019]: Terminate Signal
>  Feb 07 19:27:41 flood DCLSFC[12068]: Interrupt Signal
>  Feb 07 19:27:41 flood DCMETR[12067]: Interrupt Signal
>  Feb 07 19:27:41 flood DCUAIR[12069]: Interrupt Signal
>  Feb 07 19:27:41 flood DCNLDN[11979]: Interrupt Signal
>  Feb 07 19:27:41 flood DCMSFC[12071]: Interrupt Signal
>  Feb 07 19:27:41 flood DCACFT[12070]: Interrupt Signal
> 

Hi John, 

This is getting murky for me.  So, let me list the facts as I know them:

1) Although 'ldmadmin start' won't complete, it will start rpc.ldmd and
pqact, which both continue to run.  But, rpc.ldmd and pqact run from the
command line appear fine, at least from the bit of output I've seen.

Something is keeping ldmadmin from completing this operation.  What
version of perl are you using?  

2) Something is dumping core.  I can't help you much with this since I
don't know which program is doing it.  I suggest the pain-in-the-______
approach that I described before:  test individual lines in pqact.conf
one at a time.   Yeah, it's ugly - I feel your pain.  But, even though
it's slow and tedious it may be the fastest way in the long run.  For a
bit more information about this see
http://www.unidata.ucar.edu/cgi-bin/mfs/65/3581?79#mfs.

Btw, it's possible this could solve problem #1, above.

3) Something is shutting down your decoders. Again, this could be solved
by #2, above.
 
But, the subject of your first email is "Ldm quits unexpectedly".  Is it
really the case that your ldm has stopped completely? 


> Rather than import the pqact.conf file and have the
> mailer munge it horribly, I'm putting a copy on my website
> at http://www.rwic.und.edu/~nordlie/pqact.conf so you can
> scold me about tabs and such.
> 

At first glance I see no problems.  But, looking for errors in
pqact.conf is one of my least favorable things to do.   Btw, have you
tried 'ldmadmin pqactcheck'?  That will find some problems, but not
all.  E.g., it may help you identify a problem, but a response of "no
problems" doesn't mean there aren't any.

It is very common for our users to take one of our big pqact.conf files,
edit it a bit, turn on the LDM for the first time with the result that
it's not working right.  Indeed, I am suspecting that most your problems
are due to an error in that file.  Again, although it's slow and
tedious, it may save time in the long run to start with a very small
pqact.conf file and make sure everything's working before adding another
entry.


> The os is solaris 2.5.1 (sunos 5.5.1), and it's the
> pub/binary/sunos_5.5-sparc directory on ftp.unidat.ucar.edu
> that doesn't have an ldm distro in it.  Yes, I have a compiler,
> I just didn't bother trying to build stuff after a quick
> attempt revealed I need to install a few other tools.  If that's
> the way I need to go, I can certainly do it, I'm just being lazy :).
> 

People here think that the 5.1.2 binary under built under SunOS 5.6
should work on your 5.5.1 system.  Since it's not too hard to install, I
suggest giving that a try.  At least, that may be easier than acquiring
the tools you need to build.

I would be interested in seeing your entire log file.  Can you make that
available to me like you did the pqact.conf file?

I'm sorry I can't tell you exactly what the problem is, but it's the
nature of a complex package that runs on many different platforms.  I
hope this is helpful.

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