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

[LDM #XGQ-958194]: Re: [ldm-users] LDM 6.11.0 released

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 #XGQ-958194]: Re: [ldm-users] LDM 6.11.0 released
  • Date: Thu, 27 Sep 2012 14:06:15 -0600
Jeff,

At or before Sep 27 06:38:45 UTC, someone or something deleted the 
semaphore-set that's used by the upstream LDM database module to manage 
concurrent access to the database -- causing all subsequent upstream LDM 
processes to terminate prematurely in failure. By design, the database is 
deleted by the top-level LDM server upon normal termination or by the "ldmadmin 
start" command if and only if the LDM system isn't already running.

I looked at the LDM user's crontab(1) entries superficially but didn't see 
anything that would do this.

I restarted the LDM at Sep 27 19:44:52. At or before Sep 27 20:02:34 UTC 
someone or something again deleted the semaphore-set. Upstream LDM processes 
created after the deletion will again terminate in failure.

What the devil is happening on ldm.michiganwxsystem.net that's deleting 
semaphore-sets?

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: XGQ-958194
Department: Support LDM
Priority: Normal
Status: Closed