Unable to update CVS repository due to cvslog.write.lock error
Symptoms
The following appears in the atlassian-jira.log
when updating CVS repository:
2015-06-23 10:26:49,020 ERROR [atlassian.jira.vcs.DefaultRepositoryManager] Error occurred while updating repository 'xxx': Could not obtain lock 'C:\jira\cvs\cvslog.write.lock' in 10000 msecs.
com.atlassian.jira.util.LockException: Could not obtain lock 'C:\jira\cvs\cvslog.write.lock' in 10000 msecs.
at com.atlassian.jira.vcs.cvsimpl.CvsRepositoryUtilImpl.updateCvs(CvsRepositoryUtilImpl.java:246)
at com.atlassian.jira.vcs.cvsimpl.CvsRepository.updateCvs(CvsRepository.java:204)
at com.atlassian.jira.vcs.cvsimpl.CvsRepository.updateRepository(CvsRepository.java:295)
at com.atlassian.jira.vcs.DefaultRepositoryManager.updateRepository(DefaultRepositoryManager.java:489)
at com.atlassian.jira.vcs.DefaultRepositoryManager.updateRepositories(DefaultRepositoryManager.java:445)
at com.atlassian.jira.service.services.vcs.VcsService.run(VcsService.java:54)
at com.atlassian.jira.service.JiraServiceContainer.run(JiraServiceContainer.java:59)
Cause
The lock file is created each time JIRA updates the CVS module. If JIRA is stopped while it is working with CVS it will leave the lock file behind and the lock will need to be manually removed before restarting JIRA.
Resolution
Delete the lock file manually, see the following steps:
- Stop JIRA
- Remove the corresponding lock, for example
C:\jira\cvs\cvslog.write.lock
- Restart JIRA
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.