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

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

> Tom and Jeff,

Hi Alex, 


> 
> To test the installation, I picked-up with where Tom and I left off (see
> attached pdf as a reference)  <as 'ldm> I did the following:
> 
> ldmstart
> 
> then to just re-set, I did
> 
> ldmadmin stop   (this took a mintue or two)
> ldmadmin delqueue
> ldmadmin mkqueue
> ldmadmin start
> 
> Looks like LDM started fine (I think?).


Yes, it looks like it started up correctly :)

> 
> Next, to make sure it was logging correctly, I did:
> 
> ls -alt var/logs
> cat var/logs/ldmd.log
> 
> This command dumped a lot of information to the screen (see page 2 of
> attached pdf).  However, it looks like there are a lot of "ERROR" messages
> showing up.   Is this correct?  Is something wrong at this point with the
> configuration files?


I ~think the config is ok, it seems to be that user ldm does not have "write" 
privileges (permissions)
to the data directory. Can you confirm that the user "ldm" can "write" to the 
data directory.

Other than that, things are looking good!

> 
> Thanks!
> 
> Alex
> 
> On Tue, Aug 16, 2016 at 3:18 PM, Steve Del Favero <address@hidden> wrote:
> 
> > Alex,
> >
> > We think the 13.4 version is installed and running.  Please check to see
> > that it can do what it needs to.
> >
> > R/
> >
> > Bonnie and Clyde
> >
> > On Tue, Aug 16, 2016 at 11:53 AM, Steve Del Favero <address@hidden>
> > wrote:
> >
> >> Tom,
> >>
> >> We are on the web page and still do not see LDM-6.13.4 tar ball to
> >> download.  We see all the earlier versions, but not 13.4.  Can you send us
> >> a link to git the program?
> >>
> >> Steve and Bonnie
> >>
> >> address@hidden> wrote:
> >>
> >>> Hi Bonnie, Steve and Alex,
> >>>
> >>> The new LDM release that I had anticipated being installed at the USNA,
> >>> LDM-6.13.4, was released yesterday afternoon and is available by
> >>> anonymous FTP from us.
> >>>
> >>> Here are the same instructions for installing and cutting over to the
> >>> newly built LDM that I sent yesterday but updated to reflect the new
> >>> LDM release:
> >>>
> >>> 1) first, download the LDM compressed tarball to the HOME directory of
> >>> the
> >>>    user 'ldm' on the machine on which the LDM is to be built and run
> >>>
> >>> 2) unpack the LDM distribution compressed tar file
> >>>
> >>> <as 'ldm'>
> >>> cd ~ldm
> >>> gunzip -c ldm-6.13.4.tar.gz | pax -r '-s:/:/src/:'
> >>>
> >>> 3) CD to the LDM source directory, run configure and then 'make install'
> >>>
> >>> <as 'ldm'>
> >>> cd ~ldm/ldm-6.13.4/src
> >>> ./configure > configure.log 2>&1
> >>> make install > install.log 2>&1
> >>>
> >>>    NB: both the 'configure' and 'make install' steps will require 'root'
> >>>    privilege. This does NOT mean that you should build the LDM as 'root'!
> >>>    The LDM needs to be built as a regular user, _never_ 'root'!!
> >>>
> >>>    If you want to build the LDM as user 'ldm' without having to specify
> >>>    the 'root' password during the 'configure' and 'make install' steps,
> >>>    you would run the following instead of the previous steps:
> >>>
> >>> <as 'ldm'>
> >>> cd ~ldm/ldm-6.13.4/src
> >>> ./configure --disable-root-actions > configure.log 2>&1
> >>> make install > install.log 2>&1
> >>>
> >>>    After 'make install' finishes, you will be advised that someone
> >>>    with superuser privilege will need to:
> >>>
> >>> <as 'root'>
> >>> cd ~ldm/ldm-6.13.4/src
> >>> make root-actions
> >>>
> >>> 4) after the new version of the LDM has been built, user 'ldm' can
> >>>    switch to it easily
> >>>
> >>> <as 'ldm'>
> >>> cd ~ldm
> >>> ldmadmin stop
> >>> rm runtime
> >>> ln -s ldm-6.13.4 runtime
> >>> ldmadmin start
> >>>
> >>> That's it as far as upgrading to a new LDM goes. Again, the entire
> >>> process
> >>> should take about 5-10 minutes total on a fast machine.
> >>>
> >>> 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.
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Respectfully,
> >>
> >> Steve Del Favero
> >> Computer Specialist (Sysadmin)
> >> ITSD, USNA
> >> 410-293-1418
> >>
> >>
> >
> >
> > --
> > Respectfully,
> >
> > Steve Del Favero
> > Computer Specialist (Sysadmin)
> > ITSD, USNA
> > 410-293-1418
> >
> >
> 
> 
> --
> 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
> 
> 

Jeff Weber
Unidata User Support
http://www.unidata.ucar.edu

Ticket Details
===================
Ticket ID: FGZ-978731
Department: Support IDD
Priority: Normal
Status: Open
===================
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.