On Wed, 08 Jan 2025 15:02:51 +0100, Bo Berglund <bo.bergl...@gmail.com> wrote:
>Where can I find a howto that is used with Apache SVN to do the sync config >properly? So I asked ChatGPT and got a reply which I checked against the svnbook and the state of my existing working repositories. This way I could create a new empty pc repository on the mirror and have the hooks set up like on the other repos to allow only user svnsync etc. Then after initializing this as a sync target (done from the main server's command line) I started a sync operation and it seemed to work OK albeit a bit slow, but that is probably because big binaries are part of some revisions. 4521 revisions in all should be mirrored. To do the sync I used a command that was present in the batch file used nightly to sync all 10 repositories. I showed that earlier in this thread. RESULT when doing the first sync: --------------------------------- 1) After about 550 revs it stalled without any message on screen! I waited about an hour and nothing happened, so I entered Ctrl-C into the window hoping to stop the operation, but instead it continued happily with the next rev! Very strange and no info on why it stopped.... 2) Later on when it reached rev 1865 it exited with the following error message: svnsync: E1752002: REPORT request on '/svn/pc/!svn/rev/1866' failed This was both an error message and a full stop. 3) At this time I repeated the original sync command and it restarted by transmitting the 1865 data then moved on to rev 1866 4) From then on it took a while but it finally reached rev 4521 and exited successfully. Now my two repositories seem to be exactly the same, which is the whole purpose. WHAT TO DO NOW? ---------------- I realized by seeng this that my problems with the pc repo might be because some time ago back in 2023 there was something that made it stop like my first stop during sync and NOT FINISH, just hang there. That explains the error message I have reported earlier in this thread about the lock on the repo that stopped future sync operations to complete. So is there some way to force svnsync to EXIT with an error when there is a stop in communications or similar? Maybe a timeout value... If not then I believe that svnsync cannot be used in an automated fashion to keep a mirror updated. Note that whatever can be done must be done on the Windows Server 2016 that hosts the main repositories. So methods used on Linux do not apply here. In order to handle an svnsync hang I need a way to STOP svnsync rather than it does a halt. It needs to clear the lock when it exits... Or a way to have a timeout that exits the svnsync application such that a log can be created and possibly also a forced restart. But the restart is not important because the sync will run the followiing day anyway and then the comm problem (if that is the cause) likely is not present anymore. Any ideas? -- Bo Berglund Developer in Sweden
