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

[LDM #TMA-441215]: Beta test 6.9?


[I'm back from the AGU.]

> Two things:
> 2010-12-15T00:11:00.450421-06:00 weather3 pqact[3785] ERROR: Couldn't
> exec(make_index): No such file or directory
> 2010-12-15T00:11:00.450456-06:00 weather3 pqact[3785] NOTE: Exiting
> 2010-12-15T00:11:00.451300-06:00 weather3 pqact[1078] NOTE: child 3785
> exited with status 1
> 2010-12-15T00:11:03.500681-06:00 weather3 pqact[3842] ERROR: Couldn't
> exec(make_index): No such file or directory
> 2010-12-15T00:11:03.500698-06:00 weather3 pqact[3842] NOTE: Exiting
> 2010-12-15T00:11:03.501457-06:00 weather3 pqact[1078] NOTE: child 3842
> exited with status 1
> 2010-12-15T00:11:03.959259-06:00 weather3 pqact[3843] ERROR: Couldn't
> exec(make_index): No such file or directory
> This used to work up until this beta version. I have a script in
> /usr/local/bin/make_index and it used to find it. This is my path by
> typeing the "env" command:
> PATH=/usr/local/bin:/bin:/usr/bin:/usr/sbin:/sbin:/usr/games:/etc:/usr/etc:/usr/local/etc:/usr/lib/mh:/usr/bin/mh:/home/scripts:/home/ldm:/home/ldm/bin:/share/bin:/home/mcidas/bin:/home/ldm/wxpscripts:/sbin:/usr/sbin:/usr/local/sbin:.

How pqact(1) executes programs hasn't changed with LDM 6.9, nor has the 
ldmadmin(1) script's manipulation of the PATH environment variable.

I'd like to know the value of the PATH environment variable as seen by ldmd(1) 
child processes. Create the script "log-env" in ~/bin with the following 

    env >env.log

Make sure it's executable. Then add the following entry to the LDM 
configuration-file (etc/ldmd.conf):

    EXEC bin/log-env

Then restart the LDM and send me the file "env.log".

> And I'm seeing this for the first time:
> Date: Wed, 15 Dec 2010 00:01:01 -0600 (CST)
> From: Cron Daemon <address@hidden>
> To: address@hidden
> Subject: Cron <address@hidden> /bin/bash -l -c '/home/ldm/bin/ldmadmin check
> >/dev/null'
> [ The following text is in the "UTF-8" character set. ]
> [ Your display is set for the "ISO-8859-1" character set.  ]
> [ Some characters may be displayed incorrectly. ]
> vetQueueSize(): The maximum acceptable latency (registry parameter
> "/server/max-latency": 600 seconds) is greater than the observed minimum
> virtual residence time of data-products in the queue (295 seconds).
> This will hinder detection of duplicate data-products.
> I'm not understanding this. This seems to tell me it can handle 600
> seconds, but the queue only has 295 seconds worth of data.

Your analysis is correct: Your LDM discards data-products with a latency 
greater than 600 seconds yet your product-queue is only large enough to contain 
the last 295 seconds worth of data.

> *******************************************************************************
> Gilbert Sebenste                                                     ********
> (My opinions only!)                                                  ******
> Staff Meteorologist, Northern Illinois University                      ****
> E-mail: address@hidden                                  ***
> web: http://weather.admin.niu.edu                                      **
> *******************************************************************************

Steve Emmerson

Ticket Details
Ticket ID: TMA-441215
Department: Support LDM
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.