• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. ncelab: *F,DLNOLK: Failed to get a exclusive lock on library...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 5207
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ncelab: *F,DLNOLK: Failed to get a exclusive lock on library ...

petgusta
petgusta over 9 years ago

I keep seeing these errors:

ncelab: *N,DLWTLK: Pausing until a exclusive lock can be established on library X
ncelab: *F,DLNOLK: Failed to get a exclusive lock on library X

Where X is a library residing on our NFS server. However, we pre-compile all the libraries once and the general idea is that they should be kept constant and not changed. Is there a way to prevent this locking operation and just open the library read-only? Or is it possible to increase the timeout for the pause or just queue on lock?

Thanks!

  • Cancel
Parents
  • StephenH
    StephenH over 9 years ago
    For pre-compiled design libraries you can use the command "ncpack -readonly X" (replacing X with your library name). The exclusive locks are generally used when the tool is making dependency checks to see if would need to rebuild anything, so without knowing your exact use model and commands it's hard to know exactly why this is happening.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StephenH
    StephenH over 9 years ago
    For pre-compiled design libraries you can use the command "ncpack -readonly X" (replacing X with your library name). The exclusive locks are generally used when the tool is making dependency checks to see if would need to rebuild anything, so without knowing your exact use model and commands it's hard to know exactly why this is happening.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information