Bug#385288: libapache2-svn sometimes create db logs owned by root
On Luni 02 Ianuarie 2012, Jonathan Nieder wrote: Hi Vitalie, Hello Jonathan, Peter Samuelson wrote: [Vitalie Lazu] Only nightly backup, but it can not break repositories That's the culprit, then. With the bdb backend, _no_ operation is truly read-only - even 'svnlook youngest' writes to log files, and can create new log files. This is an implementation choice in the Berkeley DB library, so it cannot be fixed in Subversion. Thanks for reporting this --- the bug report serves as useful documentation for anyone considering whether the bdb backend is appropriate for their particular setup. I'd like to go a step further: do you remember what documentation you looked at when coming up with your setup and later when investigating its misbehavior? Any ideas for hints that could save future readers from the same trouble? It was long time ago ;-) We switched to fsfs repository type. As I remember it was a standart apache configuration to serve many repositories from parent directory with user authorization. -- Best regards, Vitalie WWW: http://vitalie.webng.md -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#385288: libapache2-svn sometimes create db logs owned by root
Hi Vitalie, Peter Samuelson wrote: [Vitalie Lazu] Only nightly backup, but it can not break repositories That's the culprit, then. With the bdb backend, _no_ operation is truly read-only - even 'svnlook youngest' writes to log files, and can create new log files. This is an implementation choice in the Berkeley DB library, so it cannot be fixed in Subversion. Thanks for reporting this --- the bug report serves as useful documentation for anyone considering whether the bdb backend is appropriate for their particular setup. I'd like to go a step further: do you remember what documentation you looked at when coming up with your setup and later when investigating its misbehavior? Any ideas for hints that could save future readers from the same trouble? Thanks much, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#385288: libapache2-svn sometimes create db logs owned by root
Package: libapache2-svn Version: 1.1.4-2 Severity: important We host a lot of repositories at www.assembla.com, sometimes we have problems because in db/ directory of svn repository appears log files owned by root, apache run as www-data user and it can not serve that repository anymore. We had manualy to chown files and run svnadmin recover to that repository. It happens at least twice per week with 30 active svn repositories. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.27-2-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages libapache2-svn depends on: ii apache2 2.0.54-5sarge1 next generation, scalable, extenda ii apache2-mpm-prefork [ 2.0.54-5sarge1 traditional model for Apache2 ii db4.2-util4.2.52-18 Berkeley v4.2 Database Utilities ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an ii libsvn0 1.1.4-2shared libraries used by Subversio -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385288: libapache2-svn sometimes create db logs owned by root
[Vitalie Lazu] We host a lot of repositories at www.assembla.com, sometimes we have problems because in db/ directory of svn repository appears log files owned by root, apache run as www-data user and it can not serve that repository anymore. If apache does not have permission to create files as root, I wonder who is doing it. Files owned by root don't just appear out of nowhere; some process running as root has to create them. Do you have some administrative cron job, or something, which touches the repositories? Thanks, Peter signature.asc Description: Digital signature
Bug#385288: libapache2-svn sometimes create db logs owned by root
Only nightly backup, but it can not break repositories and it happens sometimes and on random repositories.below is my backup script:backup_svn() { local REVFILE=$1/backup_rev.txt local OLDREV=`cat $REVFILE 2/dev/null || echo -n 0`
local NEWREV=`svnlook youngest $1` echo Repository: $1 if [ $OLDREV != $NEWREV ] then local OUTPUT_FILE=$TMP_SVN_DIR/$1-$OLDREV-$NEWREV.dump OLDREV=$(($OLDREV+1))
echo $OLDREV:$NEWREV svnadmin dump -q -r $OLDREV:$NEWREV --incremental $1 $OUTPUT_FILE echo -n $NEWREV $REVFILE fi}
On 8/30/06, Peter Samuelson [EMAIL PROTECTED] wrote:
[Vitalie Lazu] We host a lot of repositories at www.assembla.com, sometimes we have problems because in db/ directory of svn repository appears log files owned by root, apache run as www-data user and it can not serve that
repository anymore.If apache does not have permission to create files as root, I wonderwho is doing it.Files owned by root don't just appear out of nowhere;some process running as root has to create them.Do you have some
administrative cron job, or something, which touches the repositories?Thanks,Peter-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.5 (GNU/Linux)iD8DBQFE9eGAXk7sIRPQRh0RAqC2AKCEfgUNiHMG2J76b7JeDNk3M/SOcgCbBRM1
D5ngnWwhSEJIdWYeJ8MvHh8==63jm-END PGP SIGNATURE--- Best regards,Vitalie
Bug#385288: libapache2-svn sometimes create db logs owned by root
tags 385288 upstream wontfix
thanks
[Vitalie Lazu]
Only nightly backup, but it can not break repositories
That's the culprit, then. With the bdb backend, _no_ operation is
truly read-only - even 'svnlook youngest' writes to log files, and can
create new log files. This is an implementation choice in the Berkeley
DB library, so it cannot be fixed in Subversion.
(This is not true of the fsfs backend, by the way, so if you convert
repositories to fsfs, this particular problem will disappear.)
I suggest running svnlook and svnadmin as the 'www-data' user:
svnrun() {
su www-data -c $*
}
local NEWREV=$(svnrun svnlook youngest $1)
...
svnrun svnadmin dump -q -r $OLDREV:$NEWREV --incremental $1
Or perhaps it is more convenient to run your entire backup script as
the www-data user.
Peter
signature.asc
Description: Digital signature
