So I enabled the RPMForge repository, upgraded subversion to 1.4.3, and the issue has disappeared.
Thanks, everyone, for all your help! Johann On Apr 3, 11:43 pm, [EMAIL PROTECTED] wrote: > I'm using Trac 0.10.3.1 . > I'm using Subversion 1.1.4 (wow that's old). > > I'm running this on CentOS, so most of the packages are old but > stable. > > I did a complete conversion of my repository from BDB to FSFS, did a > full restart of my server, and the issue persists. Perhaps I should > upgrade Subversion? > > Thanks, > > Johann MacDonagh > > On Apr 3, 11:09 pm, Thomas Moschny <[EMAIL PROTECTED]> wrote: > > > On Montag, 2. April 2007, Johann MacDonagh wrote: > > > > I'm running into a strange issue with Trac hooked up to my Subversion > > > repository. For every page view in Trac's integrated subversion > > > viewer, apache creates a new file handler to the > > > /svn/path/locks/db.lock file. Even when the page is done rendering, > > > the lock is not released. After a few days or running, Apache had > > > 3,500 open files. > > > What version of trac are you using? > > > Just a wild guess, but prior to r5145, trac doesn't call close() on a vc > > repository handle after using it (seehttp://trac.edgewall.org/ticket/4972), > > which may be the cause of your problem. > > > Apart from using to fsfs (which is the preferred db format for subversion > > now > > anyway), you could try to use your bdb repository together with trac's > > current head and see whether it still leaves lock files behind. > > > - Thomas > > > application_pgp-signature_part > > 1KDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
