On Tue, 7 Jan 2025 04:22:43 -0600, Ryan Carsten Schmidt <subversion-2...@ryandesign.com> wrote:
>On Jan 7, 2025, at 03:48, Bo Berglund wrote: >> >> It seems like the sync was not really done for this repo for a long time even >> though the nightly sync operation actually was working for all the other >> repos >> where the mirror contains commits done up to the server crash... > >Indeed! > Today I have restored the repository using the dump files from the mirror and then for the pc repo which had not synced for a long while I did the inverse and took a dump from the main server and loaded it into the mirror. Then I also did a few manual commits using the commit emails I had from the last 20 or so commits on the server as guide so I could enter the missing information and also the commit messages which I copied from tyhe emails. In the end my main server was restored to the state when the crash happened. So I decided to try a manual version of the nightly sync call for the pc repo. I took the command from the bat file otherwise called each night. This is how the execution went (long lines are wrapped by my newsreader): H:\>"C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize --sync-username syncuser https://svn.mydomain.com/svn/pc https://agiengineering/svn/pc Failed to get lock on destination repos, currently held by 'AGIENGINEERING:4b3622e3-1724-2d47-9cdd-82690ad1fe60' repeated 10 times.... Failed to get lock on destination repos, currently held by 'AGIENGINEERING:4b3622e3-1724-2d47-9cdd-82690ad1fe60' svnsync: E000022: Couldn't get lock on destination repos after 10 attempts So I also tested on another repository: H:\>"C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize --sync-username syncuser https://svn.mydomain.com/svn/pcb https://agiengineering/svn/pcb Here there are no errors at all... In the batch file the command is created at the start and then used for all repos going down the file. Here is how it is defined (again wrapped lines): rem If a repository is not synced due to a lock problem, then use --steal-lock in a manual command rem SET SYNCCMD="C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize --steal-lock --sync-username syncuser SET SYNCCMD="C:\Program Files\VisualSVN Server\bin\svnsync.exe" synchronize --sync-username syncuser What looks like a commented out suggestion about --steal-locks may or may not apply here, what does it mean an how to use it? >> And it is a single operation on the main server that runs these sync >> operations. >> There is one TaskScheduler call to run the batch file that sets up the call string and then applies it to each repository in turn. Unfortunately there is no error handling in the batch file as yet. I don't know how to do that in a Windows environment, in Linux I have done it often and there I can make a curl call to my webserver where I have a php script that can send me an email with the supplied text. >> HOW to fix this? > >> Could I proceed like this: >> >> 1- Make a repo dump on the main server and load that into the mirror. >> That should bring the mirror to rev 4518 (same as main) > >> 2- Check out the involved 3 projects fresh from the main repo >> >> 3- Using the emailings as base commit the same files as are listed there >> Thus recreating the 10 revisions that are missing. >> >> 4- Perform a manual sync to the mirror repo to bring that to rev 4528 This step is what fails! -- Bo Berglund Developer in Sweden
