You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Steve <su...@digitalnothing.com> on 2004/07/20 14:38:00 UTC
Could not open the requested SVN filesystem
After finally getting SVN w/Apache2 support online again, I am now receiving
the error: 160029 Could not open the requested SVN filesystem.
After consulting the Apache error log, I found the following entries:
[Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] (20014)Error string
not specified yet: Berkeley DB error while opening environment for
filesystem /usr/svn/ep/db:\nInvalid argument
[Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] Could not fetch
resource information. [500, #0]
[Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] Could not open the
requested SVN filesystem [500, #160029]
[Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] (17)File exists: Could
not open the requested SVN filesystem [500, #160029]
None of the paths have changed, and the Apache configuration remains the
same as before, when access was working perfectly for three months. Any
ideas as to what's going on?
Thanks,
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Could not open the requested SVN filesystem
Posted by "Alexander L. Belikoff" <ab...@vallinor4.com>.
On Tuesday 20 July 2004 12:19, Ben Collins-Sussman wrote:
>
> I'm more concerned that your binaries are linking to multiple versions
> of bdb at the same time. Can you show us the *full* ldd output to these
> things, not just try to pick out db-4.2?
I guess this could also explain why none of my seemingly clean builds of SVN
on stock Fedora Core 1 worked. I've been asking about this several times but
with no success. SVN would build but then the load command would segfault in
APR/APU. I wonder if it is possible to have some safeguard throughout the
build process to prevent this?..
--
Alexander L. Belikoff GPG f/pr: 0D58 A804 1AB1 4CD8 8DA9
Bloomberg L.P. 424B A86E CD0D 8424 2701
abel *at* vallinor4 *dot* com (http://pgp5.ai.mit.edu for the key)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
>
> For the heck of it I tried just creating a new repo and accessing it. It
> worked fine, but as soon as I loaded in my dump file, I was no longer able
> to access it, receiving the same error as previous.
>
Since I could access the repo before loading the dump, I went and pulled out
a backup of the repo, and dumped that. Loaded it in, and it worked
perfectly. I think maybe my dump file was corrupted somehow. I don't know,
and at this point don't care, I'm just happy to have my SVN back.
Thanks for all of the help everyone.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
>
> Well, I went through the steps, doing:
>
> 1. svnadmin dump repo1 > repo1.dump
> 2. cp -R repo1 repo1bak
> 3. svnadmin create repo1 (chown & chmod as usual)
> 4. svnadmin load -q repo1 < repo1.dump
> 5. Still getting the same error
>
> Did I do anything wrong in those steps. I'm at a complete loss as
> to what to
> do here. Should I try reverting to SVN 1.0.0? Is it possible to tell which
> version of BDB my repos were created with/work with?
>
For the heck of it I tried just creating a new repo and accessing it. It
worked fine, but as soon as I loaded in my dump file, I was no longer able
to access it, receiving the same error as previous.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
> > So you're suggesting:
> >
> > 1. Dump current repo
> > 2. Remove current repo
> > 3. Create new repo with a 1.0.5 build
> > 4. Load dumped data from old repo
> > 5. Pray that it works.
> >
> > Does that sound correct, or am I missing any steps along the way?
>
> Change step 2 into:
> Move current repo away
>
> So you can always switch back.
Well, I went through the steps, doing:
1. svnadmin dump repo1 > repo1.dump
2. cp -R repo1 repo1bak
3. svnadmin create repo1 (chown & chmod as usual)
4. svnadmin load -q repo1 < repo1.dump
5. Still getting the same error
Did I do anything wrong in those steps. I'm at a complete loss as to what to
do here. Should I try reverting to SVN 1.0.0? Is it possible to tell which
version of BDB my repos were created with/work with?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Could not open the requested SVN filesystem
Posted by Marc Haisenko <ha...@webport.de>.
On Wednesday 21 July 2004 16:46, Steve wrote:
> So you're suggesting:
>
> 1. Dump current repo
> 2. Remove current repo
> 3. Create new repo with a 1.0.5 build
> 4. Load dumped data from old repo
> 5. Pray that it works.
>
> Does that sound correct, or am I missing any steps along the way?
Change step 2 into:
Move current repo away
So you can always switch back.
--
Marc Haisenko
Systemspezialist
Webport IT-Services GmbH
mailto: haisenko@webport.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Could not open the requested SVN filesystem
Posted by John Szakmeister <jo...@szakmeister.net>.
On Wednesday 21 July 2004 10:46, Steve wrote:
[snip]
> So you're suggesting:
>
> 1. Dump current repo
> 2. Remove current repo
> 3. Create new repo with a 1.0.5 build
> 4. Load dumped data from old repo
> 5. Pray that it works.
I was actually suggesting that:
1. You save off a copy of the repo
2. Build a version of linked against the old BDB library.
3. Dump the repo using the svn from step 2.
4. Create and load the new repository with the 1.0.5 build.
It sounds in your other mails that you ended up going to a backup copy and
using that. I'd be interested in taking a look at the dump (the one that
doesn't load correctly). Could I have access to that, or a copy of it?
If you've uncovered a bug, I'd like to kill it. :-)
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
> I wonder if the problem is that he wasn't using the right BDB in
> the first
> place. Back around 1.0, IIRC, there were problems when trying to build
> with BDB 4.2.52. I believe the configure script (for apr-util) wasn't
> correctly picking up the new library yet. Perhaps when Steve built it,
> it went unnoticed, and he's been using the older BDB.
>
> If this is the case Steve, rebuilding a version of SVN linked against the
> old BDB will bring it back to life. There is a way to do an in-place
> upgrade of the backend databases, but you'll need to check Sleepycat's
> home page, as I don't recall how to do that offhand. You can also do a
> dump & load, making sure that you copy your hook scripts as well.
So you're suggesting:
1. Dump current repo
2. Remove current repo
3. Create new repo with a 1.0.5 build
4. Load dumped data from old repo
5. Pray that it works.
Does that sound correct, or am I missing any steps along the way?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Could not open the requested SVN filesystem
Posted by John Szakmeister <jo...@szakmeister.net>.
On Tuesday 20 July 2004 17:25, Ben Collins-Sussman wrote:
> On Tue, 2004-07-20 at 16:13, Steve wrote:
> > > > I'm more concerned that your binaries are linking to multiple
> > > > versions of bdb at the same time. Can you show us the *full* ldd
> > > > output to these things, not just try to pick out db-4.2?
> >
> > <big snip>
> >
> > Ben, do you(or anyone else) have any thoughts regarding what I
> > posted? I checked my list of installed packagesa little while ago,
> > and noticed that it indicated both bdb4 and bdb42 were installed. I
> > removed both of them, apache2, and svn. Then I went and installed
> > apache2 with db42, and svn again, but I'm still getting the same
> > error.
>
> I'm running out of ideas here. I see nothing suspicious in your 'ldd'
> outputs.
I wonder if the problem is that he wasn't using the right BDB in the first
place. Back around 1.0, IIRC, there were problems when trying to build
with BDB 4.2.52. I believe the configure script (for apr-util) wasn't
correctly picking up the new library yet. Perhaps when Steve built it,
it went unnoticed, and he's been using the older BDB.
If this is the case Steve, rebuilding a version of SVN linked against the
old BDB will bring it back to life. There is a way to do an in-place
upgrade of the backend databases, but you'll need to check Sleepycat's
home page, as I don't recall how to do that offhand. You can also do a
dump & load, making sure that you copy your hook scripts as well.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 16:13, Steve wrote:
> > >
> > > I'm more concerned that your binaries are linking to multiple versions
> > > of bdb at the same time. Can you show us the *full* ldd output to these
> > > things, not just try to pick out db-4.2?
>
> <big snip>
>
> Ben, do you(or anyone else) have any thoughts regarding what I posted? I
> checked my list of installed packagesa little while ago, and noticed that it
> indicated both bdb4 and bdb42 were installed. I removed both of them,
> apache2, and svn. Then I went and installed apache2 with db42, and svn
> again, but I'm still getting the same error.
I'm running out of ideas here. I see nothing suspicious in your 'ldd'
outputs.
Can you show me how your libaprutil library is linked, using 'ldd'?
Also, I'd like to know what happens if you 'cp -R' your repository, then
run 'svnadmin recover' on the repos.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
> >
> > I'm more concerned that your binaries are linking to multiple versions
> > of bdb at the same time. Can you show us the *full* ldd output to these
> > things, not just try to pick out db-4.2?
<big snip>
Ben, do you(or anyone else) have any thoughts regarding what I posted? I
checked my list of installed packagesa little while ago, and noticed that it
indicated both bdb4 and bdb42 were installed. I removed both of them,
apache2, and svn. Then I went and installed apache2 with db42, and svn
again, but I'm still getting the same error.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
> > ldd /usr/local/lib/libdb-4.2.so.2 returned no list. Does that indicate a
> > problem?
>
> I'm more concerned that your binaries are linking to multiple versions
> of bdb at the same time. Can you show us the *full* ldd output to these
> things, not just try to pick out db-4.2?
svnadmin:
libsvn_repos-1.so.0 => /usr/local/lib/libsvn_repos-1.so.0
(0x28077000)
libsvn_fs-1.so.0 => /usr/local/lib/libsvn_fs-1.so.0 (0x2808a000)
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
(0x280aa000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x280b1000)
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9
(0x280d1000)
libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x280e5000)
libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x281bb000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x281db000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x282ca000)
libm.so.2 => /lib/libm.so.2 (0x282e7000)
libcrypt.so.2 => /lib/libcrypt.so.2 (0x28300000)
libc.so.5 => /lib/libc.so.5 (0x28319000)
svnserve:
libsvn_repos-1.so.0 => /usr/local/lib/libsvn_repos-1.so.0
(0x28079000)
libsvn_fs-1.so.0 => /usr/local/lib/libsvn_fs-1.so.0 (0x2808c000)
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
(0x280ac000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x280b3000)
libsvn_ra_svn-1.so.0 => /usr/local/lib/libsvn_ra_svn-1.so.0
(0x280d3000)
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9
(0x280e1000)
libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x280f5000)
libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x281cb000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x281eb000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x282da000)
libm.so.2 => /lib/libm.so.2 (0x282f7000)
libcrypt.so.2 => /lib/libcrypt.so.2 (0x28310000)
libc.so.5 => /lib/libc.so.5 (0x28329000)
svn:
libsvn_client-1.so.0 => /usr/local/lib/libsvn_client-1.so.0
(0x28087000)
libsvn_wc-1.so.0 => /usr/local/lib/libsvn_wc-1.so.0 (0x280a5000)
libsvn_ra-1.so.0 => /usr/local/lib/libsvn_ra-1.so.0 (0x280c8000)
libsvn_diff-1.so.0 => /usr/local/lib/libsvn_diff-1.so.0 (0x280cb000)
libsvn_ra_local-1.so.0 => /usr/local/lib/libsvn_ra_local-1.so.0
(0x280d2000)
libsvn_repos-1.so.0 => /usr/local/lib/libsvn_repos-1.so.0
(0x280d6000)
libsvn_fs-1.so.0 => /usr/local/lib/libsvn_fs-1.so.0 (0x280e9000)
libsvn_ra_dav-1.so.0 => /usr/local/lib/libsvn_ra_dav-1.so.0
(0x28109000)
libsvn_ra_svn-1.so.0 => /usr/local/lib/libsvn_ra_svn-1.so.0
(0x2811b000)
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
(0x28129000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x28130000)
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9
(0x28150000)
libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x28164000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2823a000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x28329000)
libm.so.2 => /lib/libm.so.2 (0x28346000)
libneon.so.24 => /usr/local/lib/libneon.so.24 (0x2835f000)
libssl.so.3 => /usr/local/lib/libssl.so.3 (0x2837b000)
libz.so.2 => /lib/libz.so.2 (0x283ac000)
libgssapi.so.7 => /usr/lib/libgssapi.so.7 (0x283ba000)
libkrb5.so.7 => /usr/lib/libkrb5.so.7 (0x283c8000)
libasn1.so.7 => /usr/lib/libasn1.so.7 (0x28405000)
libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0x2842b000)
libroken.so.7 => /usr/lib/libroken.so.7 (0x28531000)
libcrypt.so.2 => /lib/libcrypt.so.2 (0x28540000)
libcom_err.so.2 => /usr/lib/libcom_err.so.2 (0x28559000)
libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x2855b000)
libc.so.5 => /lib/libc.so.5 (0x2857b000)
libssl.so.3 => /usr/lib/libssl.so.3 (0x28656000)
libcrypto.so.3 => /lib/libcrypto.so.3 (0x28688000)
mod_dav_svn.so:
libsvn_repos-1.so.0 => /usr/local/lib/libsvn_repos-1.so.0
(0x28168000)
libsvn_fs-1.so.0 => /usr/local/lib/libsvn_fs-1.so.0 (0x2817b000)
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0
(0x2819b000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x281a2000)
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9
(0x281c2000)
libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x281d6000)
libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x282ac000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x282cc000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x283bb000)
libm.so.2 => /lib/libm.so.2 (0x283d8000)
libcrypt.so.2 => /lib/libcrypt.so.2 (0x283f1000)
mod_authz_svn.so:
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x28155000)
libaprutil-0.so.9 => /usr/local/lib/apache2/libaprutil-0.so.9
(0x28175000)
libdb-4.2.so.2 => /usr/local/lib/db42/libdb-4.2.so.2 (0x28189000)
libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x2825f000)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2827f000)
libapr-0.so.9 => /usr/local/lib/apache2/libapr-0.so.9 (0x2836e000)
libm.so.2 => /lib/libm.so.2 (0x2838b000)
libcrypt.so.2 => /lib/libcrypt.so.2 (0x283a4000)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 11:15, Steve wrote:
> >
> > Yes, how about your apr-util library? What version of BDB is it linked
> > against? Use 'ldd' to find out, but also ask its own config program:
> >
> > apu-config --db-version
>
> ldd /usr/local/lib/libdb-4.2.so.2 returned no list. Does that indicate a
> problem?
I'm more concerned that your binaries are linking to multiple versions
of bdb at the same time. Can you show us the *full* ldd output to these
things, not just try to pick out db-4.2?
>
> ./apu-config --db-version
> 4
>
> So I'm guessing a reinstall of Apache2 with BDB 4.2 is in order, or not
> necessarily?
>
No, this is fine. apu-config prints only the major version number of
bdb.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
>
> Yes, how about your apr-util library? What version of BDB is it linked
> against? Use 'ldd' to find out, but also ask its own config program:
>
> apu-config --db-version
ldd /usr/local/lib/libdb-4.2.so.2 returned no list. Does that indicate a
problem?
./apu-config --db-version
4
So I'm guessing a reinstall of Apache2 with BDB 4.2 is in order, or not
necessarily?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 10:47, Steve wrote:
> svnadmin, svnserve, svn, mod_dav_svn.so, mod_authz_svn.so all show the line:
>
> libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x280e5000)
>
> So I would assume that this indicates BDB 4.2, correct? Is there anything
> else I should be looking for/at?
Yes, how about your apr-util library? What version of BDB is it linked
against? Use 'ldd' to find out, but also ask its own config program:
apu-config --db-version
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
> Try running 'ldd' on your various 1.0.5 svn binaries: svn, svnadmin,
> svnserve, and so on. Verify that it's really db4.2, and not something
> older. That 'invalid argument' error you're seeing from BDB in the
> apache errorlog is very likely an older version of BDB trying to open a
> database produced by a newer version.
svnadmin, svnserve, svn, mod_dav_svn.so, mod_authz_svn.so all show the line:
libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x280e5000)
So I would assume that this indicates BDB 4.2, correct? Is there anything
else I should be looking for/at?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 10:14, Steve wrote:
> > > None of the paths have changed, and the Apache configuration remains the
> > > same as before, when access was working perfectly for three months. Any
> > > ideas as to what's going on?
> >
> > Has *anything* changed? Did you upgrade subversion? Or BDB? What OS
> > is this? What version of subversion? What version of BDB?
> >
>
> Sorry for not including that information. Yes, some things have changed. SVN
> was upgraded from 1.0.0 to 1.0.5. BDB is still 4.2 I believe(that is what I
> installed Apache2 with). FreeBSD 5.2.1 is the OS. I was under the impression
> that nothing should have to change with the repo until a later version(1.2
> maybe?) or did I misread that?
Try running 'ldd' on your various 1.0.5 svn binaries: svn, svnadmin,
svnserve, and so on. Verify that it's really db4.2, and not something
older. That 'invalid argument' error you're seeing from BDB in the
apache errorlog is very likely an older version of BDB trying to open a
database produced by a newer version.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Could not open the requested SVN filesystem
Posted by Steve <su...@digitalnothing.com>.
> > None of the paths have changed, and the Apache configuration remains the
> > same as before, when access was working perfectly for three months. Any
> > ideas as to what's going on?
>
> Has *anything* changed? Did you upgrade subversion? Or BDB? What OS
> is this? What version of subversion? What version of BDB?
>
Sorry for not including that information. Yes, some things have changed. SVN
was upgraded from 1.0.0 to 1.0.5. BDB is still 4.2 I believe(that is what I
installed Apache2 with). FreeBSD 5.2.1 is the OS. I was under the impression
that nothing should have to change with the repo until a later version(1.2
maybe?) or did I misread that?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Could not open the requested SVN filesystem
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 09:38, Steve wrote:
> After finally getting SVN w/Apache2 support online again, I am now receiving
> the error: 160029 Could not open the requested SVN filesystem.
>
> After consulting the Apache error log, I found the following entries:
>
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] (20014)Error string
> not specified yet: Berkeley DB error while opening environment for
> filesystem /usr/svn/ep/db:\nInvalid argument
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] Could not fetch
> resource information. [500, #0]
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] Could not open the
> requested SVN filesystem [500, #160029]
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] (17)File exists: Could
> not open the requested SVN filesystem [500, #160029]
>
> None of the paths have changed, and the Apache configuration remains the
> same as before, when access was working perfectly for three months. Any
> ideas as to what's going on?
Has *anything* changed? Did you upgrade subversion? Or BDB? What OS
is this? What version of subversion? What version of BDB?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Could not open the requested SVN filesystem
Posted by Ben Collins-Sussman <su...@collab.net>.
On Tue, 2004-07-20 at 09:38, Steve wrote:
> After finally getting SVN w/Apache2 support online again, I am now receiving
> the error: 160029 Could not open the requested SVN filesystem.
>
> After consulting the Apache error log, I found the following entries:
>
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] (20014)Error string
> not specified yet: Berkeley DB error while opening environment for
> filesystem /usr/svn/ep/db:\nInvalid argument
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] Could not fetch
> resource information. [500, #0]
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] Could not open the
> requested SVN filesystem [500, #160029]
> [Tue Jul 20 07:39:54 2004] [error] [client 10.0.0.14] (17)File exists: Could
> not open the requested SVN filesystem [500, #160029]
>
> None of the paths have changed, and the Apache configuration remains the
> same as before, when access was working perfectly for three months. Any
> ideas as to what's going on?
Has *anything* changed? Did you upgrade subversion? Or BDB? What OS
is this? What version of subversion? What version of BDB?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org