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

[LDM #ROJ-852250]: Cron job can't reset LDM registry?



Hi Chris,

re: is it OK for us to rebuild your LDM v6.13.3 installation?

> Yes, go ahead.  I noticed that this installation appeared to
> be different than what I was used to, but I'm not sure why.

OK, thanks.  I rebuilt and installed LDM v6.13.6 from source (I
downloaded the compressed tar file from our anonymous FTP site)
after doing the following:

<as 'ldm'>
-- FTP ldm-6.13.6.tar.gz from ftp.unidata.ucar.edu

ldmadmin stop
cd ldm-6.13.6
mkdir src
mv * src

cd

mv bin ldm-6.13.6
mv include ldm-6.13.6
mv share ldm-6.13.6
mv ldm-6.13.6 ldm-6.13.6-

gunzip -c ldm-6.13.6.tar.gz | pax -r '-s:/:/src/:'

cd ldm-6.13.6/src
./configure && make install

cd

ls -alt
 ...
lrwxrwxrwx.  1 ldm  users       13 Apr 11 15:04 share -> runtime/share
lrwxrwxrwx.  1 ldm  users       11 Apr 11 15:04 lib -> runtime/lib
lrwxrwxrwx.  1 ldm  users       15 Apr 11 15:04 include -> runtime/include
lrwxrwxrwx.  1 ldm  users       11 Apr 11 15:04 bin -> runtime/bin
lrwxrwxrwx.  1 ldm  users       11 Apr 11 15:04 src -> runtime/src
drwxr-xr-x.  7 ldm  users     4096 Apr 11 15:04 ldm-6.13.6
drwxr-xr-x.  6 ldm  users     4096 Apr 11 15:01 ldm-6.13.6-
-rw-rw-r--.  1 ldm  users  6251152 Apr 11 12:45 ldm-6.13.6.tar.gz
-rw-rw-r--.  1 ldm  users   126198 Apr 11 02:49 dcidft.log
-rw-------.  1 ldm  users      814 Apr  7 10:47 .bash_history
lrwxrwxrwx.  1 ldm  users       10 Apr  2 13:20 runtime -> ldm-6.13.6

The reason for the rebuild was that the previous build of v6.13.6 was
apparently done by unpacking the LDM tarball but not running the
output of 'gunzip' through 'pax'.  This resulted in the source code
being unpacked in ~ldm/ldm-6.13.6 not ~ldm/ldm-6.13.6/src.  It also
resulted in the LDM executables being put ~ldm/bin not
~ldm/runtime/bin.

The other things I did were:

- edited your crontab file and modified all invocations to run
  the actions directly

  Example:

0 1 * * * bin/ldmadmin scour >/dev/null

- added a couple of crontab entries:

0 0 * * * bin/newlog logs/ldm-mcidas.log 7

#
# LDM metrics gathering
#
* * * * * bin/ldmadmin addmetrics > /dev/null
0 0 1 * * bin/ldmadmin newmetrics > /dev/null

- modified the bin/ldmadmin newlog entry to save 7 ldmd.log files:

0 0 * * * bin/ldmadmin newlog -n 7

- changed the crontab file to force the actions to run at UTC times:

#
# Run cron entries at UTC time
#
CRON_TZ="UTC"

- suppress error messages being mailed to 'ldm':

MAILTO=""

- modified your ~ldm/.cshrc file to put the LDM directories last
  in the 'path' setting:

set path=($path $HOME/decoders $HOME/util $HOME/bin)

- I made the same change to .login:

(blizzard) /local/ldm > cat .login
set path=($path $HOME/decoders $HOME/util $HOME/bin)
setenv MANPATH $HOME/share/man:/usr/share/man:/usr/local/man

  My objective was for the three LDM directories to be at the end of
  'ldm's PATH, and they now are:

(blizzard) /local/ldm > echo $path
. /bin /usr/bin /usr/local /usr/local/bin /usr/bin/X11 /usr/ucb /usr/opt/bin 
/local/ldm /local/ldm/decoders /local/ldm/util /local/ldm/bin 
/home/gempak/GEMPAK7/os/linux64/bin /home/gempak/GEMPAK7/bin 
/local/ldm/decoders /local/ldm/util /local/ldm/bin

Let's see if the above changes have resulted in things working correctly
now.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: ROJ-852250
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.



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.