#741 closed defect (duplicate)
Database continually becomes corrupt
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | general | Version: | 0.7.1 |
Severity: | critical | Keywords: | subversion database corruption |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
On a fairly regular basis — seems like around once every few hours — something about trac causes the subversion database to corrupt, requiring a svnadmin recover
to fix it.
This sounds like its related to Ticket #571 (although we're not on Windows); I've tried the umask/chmod g+s stuff that bje@apnic.net
suggested on that ticket, and it's slowed down the rate of these errors, but not completely stopped them.
The error we keep getting is: ('Berkeley DB error while opening environment for filesystem /home/svn/repository/db:\nDB_RUNRECOVERY: Fatal error, run database recovery', 160029)
.
We're running Trac 0.7.1 (as a CGI) under Apache 2.0 on RedHat ES with Subversion 1.0.6.
Attachments (0)
Change History (12)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
I had the same problem. I didn't want to change the default umask for all my processes so I added the following to the trac.cgi file:
import os; os.umask(007)
before the try statement. It solved the last of my problems (like you I got improved results from using the setgid bit on the db directory and changing svn/svnserve to scripts which set the umask).
tom
Thomas Duff
duff@…
comment:3 by , 20 years ago
Interesting…
I'm not sure I totally understand how umasks work, but did you mean 002 instead of 007?
comment:4 by , 20 years ago
Priority: | normal → high |
---|
Just to follow up… the above tricks have helped slow down the frequency somewhat, but this is still happening on a far-to-regular basis.
comment:6 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:7 by , 20 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Sorry, I didn't think it would actually let me close the ticket.
comment:9 by , 20 years ago
I'm encountering the same problem, and the permissions are all set up correctly as far as I can see (including the umask for all involved processes).
Using Trac 0.7.1 (CGI on Apache1) with Subversion 1.0.6 (Apache2 module). OS is Debian Sarge.
comment:10 by , 20 years ago
Resolution: | → duplicate |
---|---|
Status: | reopened → closed |
comment:11 by , 20 years ago
Milestone: | → 0.8 |
---|
Based on some help from #trac, I've done the following:
This has (so far) seemed to work pretty well...