Semaphore Locks seen in HRefresh log
Article ID: 230519
Updated On:
Products
Issue/Introduction
After upgrading Harvest, customer is unable to deploy files successfully:
The generated HRefresh logs (located in the %CA_SCM_HOME%\log folder) show the following:
Post Commands:
semaphore file already locked by another job
maximum number of retries has been reached. Aborting job.
Environment
Harvest Software Change Manager all versions
Cause
By default, Harvest tries to prevent multiple users from checking out files to the same folder by using "semaphore locks". These are files that Harvest creates in the target folders that will block subseqent hrefresh commands from checking out to the same folder until the first checkout completes. This default behavior can be overridden by using the "-nolock" option with the hrefresh command or argument file.
Resolution
We added -nolock to hrefresh.arg per this documentation:
Additional Information
More information about Semaphore Locks can be found here: Set Up hrefresh - Look for section titled "Semaphore Locks"
Feedback
