[LDM #EIW-321327]: Updating ldm

Hi Carol,

re:
> Thanks for the quick feedback. I believe I ran those steps on Friday,
> but I've tried them again today. Here's the output from the terminal
> 
> [ccostanza@aws ~]$ sudo -i -u root
> [sudo] password for ccostanza:
> ------------- BACKUP INFORMATION ----------------
> client    name                    date    total
> aws        /home                06/17/2016 19 GB
> aws        /                    06/17/2016 15 GB
> aws        /                    07/15/2016 15 GB
> aws        /home                07/15/2016 19 GB
> -------------------------------------------------
> [root@aws ~]# cd ~ldm/ldm-6.13.2/src
> [root@aws src]# make root-actions
> chown root /home/ldm/ldm-6.13.2/bin/ldmd
> chmod 4755 /home/ldm/ldm-6.13.2/bin/ldmd
> chown root /home/ldm/ldm-6.13.2/bin/hupsyslog
> chmod 4755 /home/ldm/ldm-6.13.2/bin/hupsyslog
> if test -f /home/ldm/ldm-6.13.2/bin/noaaportIngester; then \
> chown root /home/ldm/ldm-6.13.2/bin/noaaportIngester; \
> chmod 4755 /home/ldm/ldm-6.13.2/bin/noaaportIngester; \
> fi
> if test -f /home/ldm/ldm-6.13.2/bin/dvbs_multicast; then \
> chown root /home/ldm/ldm-6.13.2/bin/dvbs_multicast; \
> chmod 4755 /home/ldm/ldm-6.13.2/bin/dvbs_multicast; \
> fi
> ./ensureRpcEntry
> ./ensureServicesEntry
> [root@aws src]# exit
> logout
> [ccostanza@aws ~]$ sudo -i -u ldm
> ------------- BACKUP INFORMATION ----------------
> client    name                    date    total
> aws        /home                06/17/2016 19 GB
> aws        /                    06/17/2016 15 GB
> aws        /                    07/15/2016 15 GB
> aws        /home                07/15/2016 19 GB
> -------------------------------------------------
> -bash-4.1$ pwd
> /home/ldm
> -bash-4.1$ ldmadmin stop
> Stopping the LDM server...
> Waiting for the LDM server to terminate...
> -bash-4.1$ rm runtime
> -bash-4.1$ ln -s ldm-6.13.2 runtime
> -bash-4.1$ ldmadmin start
> The product-queue is OK.
> Checking pqact(1) configuration-file(s)...
> /home/ldm/etc/pqact.conf: syntactically correct
> Checking LDM configuration-file (/home/ldm/etc/ldmd.conf)...
> Starting the LDM server...
> -bash-4.1$ ldmadmin config
> 
> hostname:              aws.ssec.wisc.edu
> os:                    Linux
> release:               2.6.32-573.26.1.el6.x86_64
> ldmhome:               /home/ldm
> LDM version:           6.11.7
> PATH: /home/ldm/ldm-6.11.7/bin:/usr/bin:/usr/sbin/:/bin:/sbin:/home/ldm/bin

Your output suggests that the previous installation of the LDM (v6.11.7) was
not installed according to our recommendations, OR the PATH that is being
set in the shell-specific configuration file (e.g., .cshrc for C-like shells,
etc.) has the /home/ldm/ldm-6.11.7/bin directory hardwired in.  What should
be in the PATH setting is

PATH=$PATH:$LDMHOME/bin

This assumes:

- syntax is not C Shell, so adjust to match if you are using the
  C/TCSH shell

- you have defined LDMHOME to be the HOME directory of your 'ldm'
  user

NB: it is always better to put the installed package binary subdirectory
at the end of the PATH, not at the beginning.  This is particularly
important for GEMPAK users since GEMPAK contains an executable named
'ps', and putting the GEMPAK binary directory at the beginning of
one's PATH will make finding/using the system version of 'ps' next
to impossible.

Please send the output of:

<as 'ldm'>
cd ~ldm
ls -alt

re:
> I did end up manually changing the hostname to aws.ssec.wisc.edu.

Very good.

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: EIW-321327
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.