Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Failed to obtain node locks (Search initialization error)



Users report empty search landing pages and errors in the logs related to initialization of full-text search (FTS) functionality.

Error Messages


ERROR   - Failed to initialize full text search functionality for this node.

Caused by: java.lang.IllegalStateException: failed to obtain node locks, tried [index directory]  with lock id [0]; maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])?

Steps to Reproduce


Root Cause

This issue might happen on on-premise installations, where two PRPC nodes share the same file system. Multiple PRPC nodes are trying to use the same index directory, which is an illegal configuration.


  1. Make sure that the Dynamic System Setting indexing/explicitindexdir is not set,
  2. Use the JVM argument to specify index directories for search nodes, following the procedure described in SA-50626 Search Index file directory changes on restart. 
  3. Make sure that each permanent index host PRPC node uses a distinct physical directory.
    If the PRPC nodes are running on the same physical machine, the paths must be different for each of them.

Published December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us