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

[LDM #FGZ-978731]: LDM installation and configuration at USNA

Hi Alex,

I don't understand why ldmadmin is not being found in the ~ldm/bin directory...

Unfortunately, I am not in a location where I can easily work on this issue 
today
(I'm with a friend at the hospital).  Can we work on your problem tomorrow (via 
a call like before)?

Cheers,

To 
> There have been a few emails with some thoughts on how to resolve our issue
> here at USNA. I've been a little confused on the order of operations.  We
> follow these following directions:
> 
> <as 'ldm'>
> >
> > cd ~ldm
> > ldmadmin stop              <- should already be stopped, but this can't
> > hurt
> >
> > -- edit the .bashrc or .bash_profile file and set LDMHOME as follows:
> >
> > LDMHOME=/usr/local/ldm
> > export LDMHOME
> >
> > - make the LDMHOME setting active in the login:
> >
> > export LDMHOME=/usr/local/ldm
> >
> > - rebuild LDM-6.13.4
> >
> > cd ldm-6.13.4/src
> > make distclean
> > ./configure --disable-root-actions > configure.log 2>&1
> > make install > install.log 2>&1
> >
> > <as 'root'>
> > cd /usr/local/ldm/ldm-6.13.4/src
> > make root-actions
> > exit
> >
> > <as 'ldm'>
> > cd ~ldm
> >
> > rm runtime
> > ln -s ldm-6.13.4 runtime
> >
> > ldmadmin start
> >
> > This test should not take long; I estimate that it would take between
> > 5 and 10 minutes.
> >
> 
> And here is our result:
> 
> [ldm@edmapsserver src]$ ./configure --disable-root-actions > configure.log
> 2>&1
> [ldm@edmapsserver src]$ make install > install.log 2>&1
> [ldm@edmapsserver src]$ cd ~ldm
> [ldm@edmapsserver ~]$ rm runtime
> [ldm@edmapsserver ~]$ ln -s ldm-16.13.4 runtime
> [ldm@edmapsserver ~]$ ldmadmin start
> bash: /usr/local/ldm/bin/ldmadmin: No such file or directory
> 
> I've been told you cannot VPN into the network... but I've also been told
> we now can use google hangouts (our email services is all through google).
> So we should be able to screen share that way.  What do you suggest as the
> next step?
> 
> Thanks again!
> 
> Alex
> 
> 
> address@hidden> wrote:
> 
> > Hi Bonnie,
> >
> > re:
> > > done - output as follows:
> > >
> > > chown root /usr/local/ldm/ldm-6.12.14/bin/ldmd
> > > chmod 4755 /usr/local/ldm/ldm-6.12.14/bin/ldmd
> > > chown root /usr/local/ldm/ldm-6.12.14/bin/hupsyslog
> > > chmod 4755 /usr/local/ldm/ldm-6.12.14/bin/hupsyslog
> > > if test -f /usr/local/ldm/ldm-6.12.14/bin/noaaportIngester; then \
> > > chown root /usr/local/ldm/ldm-6.12.14/bin/noaaportIngester; \
> > > chmod 4755 /usr/local/ldm/ldm-6.12.14/bin/noaaportIngester; \
> > > fi
> > > if test -f /usr/local/ldm/ldm-6.12.14/bin/dvbs_multicast; then \
> > > chown root /usr/local/ldm/ldm-6.12.14/bin/dvbs_multicast; \
> > > chmod 4755 /usr/local/ldm/ldm-6.12.14/bin/dvbs_multicast; \
> > > fi
> > > ./ensureSyslogEntry local0 /etc/rsyslog.conf
> > > /usr/local/ldm/var/logs/ldmd.log
> > > ./ensureRpcEntry
> > > ./ensureServicesEntry
> >
> > Thanks for your quick help!
> >
> > The reason Alex and I asked you to do the above was so that we can
> > revert the LDM back to a pre-ldm--6.13.x version to see if the strangeness
> > we are seeing with the LDM-6.13.[34] installations is related to the
> > version or not.  It turns out that LDM-6.12.14 was installed on the
> > machine, but it was built/installed incorrectly, so we had to redo
> > the build for the test.  As you now know, one step in the LDM
> > installation process requires 'root' access, and Alex does not have
> > the necessary credentials to do this one step.
> >
> > What have we found so far?  Unfortunately, nothing definitive.  I
> > am hoping that reverting the LDM back to ldm-6.12.14 might shed
> > some light on what is going on.
> >
> > One thing that just occurred to me that might (or might not) have
> > something to do with the strange behavior we are seeing with the
> > LDM-6.13.[34] builds is their being built in an environment where
> > LDMHOME is not defined.  In order to test to see if this makes
> > any difference, I would love to see the following tried:
> >
> > <as 'ldm'>
> >
> > cd ~ldm
> > ldmadmin stop              <- should already be stopped, but this can't
> > hurt
> >
> > -- edit the .bashrc or .bash_profile file and set LDMHOME as follows:
> >
> > LDMHOME=/usr/local/ldm
> > export LDMHOME
> >
> > - make the LDMHOME setting active in the login:
> >
> > export LDMHOME=/usr/local/ldm
> >
> > - rebuild LDM-6.13.4
> >
> > cd ldm-6.13.4/src
> > make distclean
> > ./configure --disable-root-actions > configure.log 2>&1
> > make install > install.log 2>&1
> >
> > <as 'root'>
> > cd /usr/local/ldm/ldm-6.13.4/src
> > make root-actions
> > exit
> >
> > <as 'ldm'>
> > cd ~ldm
> >
> > rm runtime
> > ln -s ldm-6.13.4 runtime
> >
> > ldmadmin start
> >
> > This test should not take long; I estimate that it would take between
> > 5 and 10 minutes.
> >
> > 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: FGZ-978731
> > Department: Support IDD
> > 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.
> >
> >
> >
> 
> 
> --
> Alexander R. Davies
> Instructor of Practical Applications for Oceanography
> Environmental Data Manager
> Meteorologist and Oceanographer
> Oceanography Department, U.S. Naval Academy
> 
> *Email*: address@hidden
> *Phone*: 410.293.6565
> *Office*: CH210
> *Website*: www.usna.edu/weather
> 
> *Address*:
> Oceanography Department
> Attn: Alexander R. Davies
> 572C Holloway Road, Room 200
> Annapolis, MD 21402
> 
> 

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: FGZ-978731
Department: Support IDD
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.