Recently, one of our work servers has been undergoing some hardware maintenance. I believe it was powered down during one of its svn mirror syncronizations.
The output from the log file showed this:
(sasvn-cm1)[csvn] cron> pwd
/opt/CollabNet_Subversion/cron
(sasvn-cm1)[csvn] cron> cat pipeline-mirror.out
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
Failed to get lock on destination repos, currently held by 'sasvn-cm1:211ba926-16bc-c94c-9718-a2e5bd4ef8e4'
svnsync: Couldn't get lock on destination repos after 10 attempts
So, looking around, it appeared that there was a lock on revision 0 but it took awhile to figure out how to remove it...
(sasvn-cm1)[csvn] cron> svn proplist -r 0 --revprop file:///repos/svn/pipeline-mirror
Unversioned properties on revision 0:
svn:sync-from-uuid
svn:sync-lock
svn:sync-last-merged-rev
svn:date
svn:sync-from-url
(sasvn-cm1)[csvn] cron> svn propdel -r 0 --revprop file:///repos/svn/pipeline-mirror
Waiting for the next cron cycle to see if it will update, but it looks promising.