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

[LDM #AHC-351489]: Couldn't lock LDM lock-file (was: ldm)

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 #AHC-351489]: Couldn't lock LDM lock-file (was: ldm)
  • Date: Sun, 04 Oct 2015 10:33:42 -0600
Patrick,

[I drove your inquiry into our support-email tracking-system to benefit others.]

The lsof(1) utility can show you what other processes have the LDM lock-file, 
~ldm/.ldmadmin.lck, locked.

Could a crontab(1) job have executed ldmadmin(1)?

> ldm@crad1:~$ ldmadmin stop
> getLock(): Couldn't lock lock-file "/home/ldm/.ldmadmin.lck". Another
> ldmadmin(1) script is likely running.
> 
> fyi.. didn't see much in the archives on this error.. this is the same box
> from before.. going to try to upgrade ldm if it will let me
> 
> cheers,
> 
> --patrick
> 
> 

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: AHC-351489
Department: Support LDM
Priority: Normal
Status: Closed