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

[LDM #EIW-321327]: Updating ldm



Hi Carol,

Thanks for the fast reply!

re:
> -bash-4.1$ ls -alt
> total 10496
> -rw-------.  1 ldm  users       4107 Jul 18 16:15 .bash_history
> -rw-r--r--.  1 ldm  sysgroup       6 Jul 18 16:13 ldmd.pid
> drwxrwxr-x. 12 ldm  sysgroup    4096 Jul 18 16:13 ./
> -rw-r--r--.  1 ldm  users          0 Jul 18 16:13 .ldmadmin.lck
> drwxr-xr-x.  2 ldm  users       4096 Jul 18 16:13 etc/
> -rw-------.  1 ldm  sysgroup    4920 Jul 18 16:13 .viminfo
> lrwxrwxrwx.  1 ldm  sysgroup      10 Jul 18 16:10 runtime -> ldm-6.13.2/
> drwxr-xr-x.  7 ldm  sysgroup    4096 Jul 15 20:15 ldm-6.13.2/
> -rw-r--r--.  1 ldm  sysgroup 6166311 Jul 15 17:48 ldm-6.13.2.tar.gz
> drwxr-xr-x. 22 root root        4096 Jun 17 16:01 ../
> drwxr-xr-x.  2 ldm  users       4096 Jun 16 16:54 util/
> drwx------.  2 ldm  users       4096 Aug  5  2015 .ssh/
> -rw-r--r--.  1 ldm  users         82 Jun 26  2015 .bash_profile
> drwxr-xr-x.  5 ldm  users       4096 Jun 26  2015 var/
> drwxr-xr-x.  3 ldm  users       4096 Jun 26  2015 include/
> drwxr-xr-x.  2 ldm  users       4096 Jun 26  2015 bin/
> drwxr-xr-x.  4 ldm  users       4096 Jun 26  2015 share/
> drwxr-xr-x.  2 ldm  users       4096 Jun 26  2015 lib/
> drwxr-xr-x. 45 ldm  users       4096 Jun 26  2015 src/
> -rw-r--r--.  1 ldm  users    4502783 Jun 26  2015 ldm-6.11.7.tar.gz

Very good, the runtime link is correct.  This means that the problem
is how PATH is being set in your shell-specific definition file which
should be either .bashrc, .bash_profile or .profile IF the shell for
'ldm' is BASH as it appears to be from your 'ls' listing.  Correct the
setting of PATH, log off and then back on, and then restart your
LDM.

Again, the correct setting of PATH will be something like:

PATH=$PATH:/home/ldm/bin

** assuming that you remove /home/ldm/ldm-6.11.7/bin from PATH first **

> Carol Costanza
> Antarctic Meteorological Research Center
> University of Wisconsin-Madison Space Science and Engineering Center
> 1225 W Dayton St, Rm 947, Madison, WI 53706
> Email: address@hidden
> Web: http://amrc.ssec.wisc.edu
> 
> On 07/18/2016 04:24 PM, Unidata LDM Support wrote:
> > 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
> >>
> >> address@hidden ~]$ 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
> >> -------------------------------------------------
> >> address@hidden ~]# cd ~ldm/ldm-6.13.2/src
> >> address@hidden 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
> >> address@hidden src]# exit
> >> logout
> >> address@hidden ~]$ 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.
> >
> >
> 
> 

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.



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.