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

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

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [LDM #FGZ-978731]: LDM installation and configuration at USNA
  • Date: Sun, 21 Aug 2016 01:10:32 -0600
Hi Alex,

I'm currently in China, where my access to the Internet is sporadic...

re:
> 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?).
> 
> 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?

The errors I see in the PDF you sent that contained LDM log file output
indicates that there is a problem using the 'ldmfile.sh' script that
should have been extracted from the compressed tarball that we sent
you to the ~ldm/etc/TDS/util directory.  This is puzzling.

Please send back the out put of the following commands:

<as 'ldm'>

cd ~ldm

pwd

ls -alt etc/TDS/util

ls -alt etc/TDS/decoders

ls -alt /data/ldm/pub

When we figure out why the 'ldmfile.sh' actions are not working, we
will be able to advise you how to take corrective action.

Again, my ability to respond quickly or interactively (I am in
a location that is 16 hours ahead of you) is very limited, so
troubleshooting the problems you are experiencing will take much
longer than usual.  For this I apologize!

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.