Support Article
write.lock file stops work indexer from indexing
SA-31373
Summary
Intermittent issues with Search Index in PRPC 6.3 SP1.
Error Messages
Lock obtain timed out: NativeFSLock@/.../PegaRULESIndex/WorkIndex/write.lock
Steps to Reproduce
Not Applicable
Root Cause
A defect or configuration issue in the operating environment.
An unknown event happened that left the write.lock file on the file system preventing further updates to the index file.
Resolution
Perform the following local-change:
Delete the write.lock file and re-index the work objects.
Published December 19, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.