Hi all, I had a little Subversion repository and a little Trac system on my little WIN32 development machine for demonstration and testing purposes. Everyone in the company liked it, so they gave me a monster server machine. I installed FreeBSD, Python, Apache, Subversion, MySQL, Trac, etc. pp. yadiyadi...
Then I migrated all Subversion repositories and all flat file, zipped and/or emailed code caches throughout the company. The resulting repository is substantially larger than my test repo (roughly 10GB on disk after full check-out). When I try to browse the code in SVN from Trac, it takes some time, then a message appears: OperationalError: (1205, 'Lock wait timeout exceeded; try restarting transaction') I tried trac-admin /var/trac/projects resync, but that also times out: Resyncing repository history... Command failed: (1205, 'Lock wait timeout exceeded; try restarting transaction') In the Trac log, it says 2006-11-13 16:30:21,099 Trac[cache] DEBUG: Checking whether sync with repository is needed 2006-11-13 16:30:21,105 Trac[cache] INFO: Syncing with repository (188 to 1462) So to me it looks as if there had been 188 changes in the test SVN repo and 1462 changes in the new production repo (some of them really big). The Trac SVN cache update apparently runs into a timeout before it can work through all the new changes. Is there a way to temporarily make the timeout longer to give Trac more time ? Does anyone know of another solution ? TIA, CU z00m1n --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
