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

[LDM #PVY-821721]: Problem with ldmd.conf after upgrading to 6.13.11

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 #PVY-821721]: Problem with ldmd.conf after upgrading to 6.13.11
  • Date: Tue, 21 May 2019 12:40:43 -0600
Hi Chris,

> Hi, I installed the 6.13.11, following instructions at the top of this page:
> 
> https://www.unidata.ucar.edu/software/ldm/ldm-current/basics/source-install-steps.html
> 
> Tried to start the LDM and get this message:
> 
> (blizzard) /local/ldm > ldmadmin start
> Checking the product-queue...
> Checking pqact(1) configuration-file(s)...
> /local/ldm/etc/pqact.conf: syntactically correct
> Checking LDM configuration-file (/local/ldm/etc/ldmd.conf)...
> start(): Problem with LDM configuration-file:

Was there anything after the "start():" message? Something that would indicate 
what the problem was?

> It's the same ldmd.conf file we've been using for 2 years.

Ouch!

You should probably go back to the previous version of the LDM that you were 
using by deleting the symbolic link "runtime" in the LDM user's home directory 
and re-creating it to reference the directory of the previous version.

> Help?  I've
> attached the file we use.

I don't see anything untoward in it.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: PVY-821721
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.