You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by sm...@speakeasy.net on 2004/02/08 22:49:58 UTC
Problem with subversion server running on Fedora
Hi,
I tracked down the messages in the thread of the message below:
http://www.contactor.se/~dast/svnusers/archive-2004-01/0758.shtml
Although I had the same problem, nothing in the thread helped me resolve
my error.
I'm running Fedora core 1, and installed the rpm packages through yum,
as linked through the subversion download page. I previously had 0.32.1
installed, which is available as part of the core distribution. While
that worked fine, upgrading to 0.37 has broken things.
To recap, I entirely removed my previous subversion installation, then
installed 0.37. I created a brand new repository, and tried connecting
to that over the http server. I got the following error message:
<D:error>
<C:error/>
<m:human-readable errcode="165005">
Could not open the requested SVN filesystem
</m:human-readable>
</D:error
In the error log, there's the following:
[Sun Feb 08 13:13:41 2004] [error] [client 127.0.0.1] (20014)Error
string not specified yet: Expected version '3' of repository; found
version '2'
[Sun Feb 08 13:13:41 2004] [error] [client 127.0.0.1] Could not fetch
resource information. [500, #0]
[Sun Feb 08 13:13:41 2004] [error] [client 127.0.0.1] Could not open the
requested SVN filesystem [500, #165005]
[Sun Feb 08 13:13:41 2004] [error] [client 127.0.0.1] (2)No such file or
directory: Could not open the requested SVN filesystem [500, #165005]
According to the thread, the culprit was probably a different version of
libsvn_fs.so used in building mod_dav_svn and the svnadmin programs. But
when I check with ldd...
# ldd `which svnadmin`
libsvn_repos-1.so.0 => /usr/lib/libsvn_repos-1.so.0 (0x00d3f000)
libsvn_fs-1.so.0 => /usr/lib/libsvn_fs-1.so.0 (0x00221000)
libsvn_delta-1.so.0 => /usr/lib/libsvn_delta-1.so.0 (0x008a6000)
libsvn_subr-1.so.0 => /usr/lib/libsvn_subr-1.so.0 (0x00f41000)
libaprutil-0.so.0 => /usr/lib/libaprutil-0.so.0 (0x007b4000)
libldap.so.2 => /usr/lib/libldap.so.2 (0x05f9b000)
liblber.so.2 => /usr/lib/liblber.so.2 (0x05fcf000)
libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x004cd000)
libdb-4.1.so => /usr/lib/tls/libdb-4.1.so (0x00a20000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x005f3000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x00111000)
libapr-0.so.0 => /usr/lib/libapr-0.so.0 (0x00b62000)
librt.so.1 => /lib/tls/librt.so.1 (0x009eb000)
libm.so.6 => /lib/tls/libm.so.6 (0x004a4000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x05e3b000)
libnsl.so.1 => /lib/libnsl.so.1 (0x00b3d000)
libdl.so.2 => /lib/libdl.so.2 (0x004c8000)
libc.so.6 => /lib/tls/libc.so.6 (0x00369000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00720000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00131000)
libssl.so.4 => /lib/libssl.so.4 (0x009b4000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0x00241000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00351000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00938000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x008cf000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00779000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x0077e000)
libz.so.1 => /usr/lib/libz.so.1 (0x005bd000)
# ldd mod_dav_svn.so
libsvn_repos-1.so.0 => /usr/lib/libsvn_repos-1.so.0 (0x0045a000)
libsvn_fs-1.so.0 => /usr/lib/libsvn_fs-1.so.0 (0x0089d000)
libsvn_delta-1.so.0 => /usr/lib/libsvn_delta-1.so.0 (0x00394000)
libsvn_subr-1.so.0 => /usr/lib/libsvn_subr-1.so.0 (0x0041f000)
libc.so.6 => /lib/tls/libc.so.6 (0x004f2000)
libaprutil-0.so.0 => /usr/lib/libaprutil-0.so.0 (0x00fde000)
libldap.so.2 => /usr/lib/libldap.so.2 (0x00ed7000)
liblber.so.2 => /usr/lib/liblber.so.2 (0x00116000)
libgdbm.so.2 => /usr/lib/libgdbm.so.2 (0x00be8000)
libdb-4.1.so => /lib/tls/libdb-4.1.so (0x00122000)
libexpat.so.0 => /usr/lib/libexpat.so.0 (0x001e4000)
libapr-0.so.0 => /usr/lib/libapr-0.so.0 (0x00909000)
librt.so.1 => /lib/tls/librt.so.1 (0x006a4000)
libm.so.6 => /lib/tls/libm.so.6 (0x00d31000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x0066e000)
libnsl.so.1 => /lib/libnsl.so.1 (0x004c3000)
libdl.so.2 => /lib/libdl.so.2 (0x00111000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00351000)
libresolv.so.2 => /lib/libresolv.so.2 (0x007f4000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00bab000)
libssl.so.4 => /lib/libssl.so.4 (0x00c69000)
libcrypto.so.4 => /lib/libcrypto.so.4 (0x00204000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x002f5000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x00305000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x0039c000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x00c5b000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00318000)
libz.so.1 => /usr/lib/libz.so.1 (0x0033a000)
As you can see, they use the same libsvn_fs-1.so.0, so that's not the
problem. Similarly, they are using the same libdb-4.1.so. Now, this is
my dynamic environment, and may not indicate the build environment
correctly. So I'm not even sure if ldd is giving anything useful...
The key observation here is that svnadmin and mod_dav_svn in the fedora
distributions seem to be out of sync. Has anyone gotten svn working
correctly on fedora? If so, what would be the difference between your
and my configuration?
Thanks!
Sunil
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by sm...@speakeasy.net.
I did restart apache, so that could not be the problem either :-(
Sunil
Toshio wrote:
> On Sun, 2004-02-08 at 22:44, Ben Collins-Sussman wrote:
>
>>You need to migrate your repository data by using 'svnadmin dump >
>>dumpfile' with the 0.32 svnadmin binary, and then 'svnadmin load
>>newrepos < dumpfile' with the 0.37 svnadmin binary. See the book for
>>details.
>>
>
>
> I think you missed this part:
>
> On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
>
>>>To recap, I entirely removed my previous subversion installation,
>>>then
>>>installed 0.37. I created a brand new repository, and tried
>>>connecting
>
>
> I had something similar happen to me the other day. It was because I
> forgot to restart apache. Even though the new mod_dav_svn is in the
> filesystem, the httpd thread you're accessing might still have the old
> one loaded into memory.
>
> -Toshio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by sm...@speakeasy.net.
Nevermind, found my configuration bug. (Feeling like a fool...)
S
smishra@speakeasy.net wrote:
> Hi,
>
> I'm installing from the fedora rpm's, and the corresponding download
> server set up for svn at
>
> http://summersoft.fay.ar.us/pub/subversion/latest/fedora/bin/
>
> I suspected mixed binaries, so I explicitly did a rpm -e for the
> subversion packages, and verified that mod_dav_svn and libsvn_fs had
> been removed. I then re-installed 0.37.
>
> Is there anything specific you would like me to look for? Are there any
> other ways of testing remote connections? Local connections seem to work
> fine. I tried:
>
> svnlook info /var/vc /
>
> and got back 0. I suppose this would be expected for a new repository?
>
> Sunil
>
> Ben Collins-Sussman wrote:
>
>> On Sun, 2004-02-08 at 22:32, Toshio wrote:
>>
>>
>>> On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
>>>
>>>>> To recap, I entirely removed my previous subversion installation,
>>>>> then installed 0.37. I created a brand new repository, and tried
>>>>> connecting
>>>
>>>
>>> I had something similar happen to me the other day. It was because I
>>> forgot to restart apache. Even though the new mod_dav_svn is in the
>>> filesystem, the httpd thread you're accessing might still have the old
>>> one loaded into memory.
>>
>>
>>
>> This would cause the *opposite* problem: you'd have a 0.33 mod_dav_svn
>> trying to read a 0.37 repository. It would expect schema '2' but find
>> schema '3' instead.
>>
>> The error message expected '3' but found '2'. Somehow, this indicates
>> to me that mod_dav_svn is definitely version 0.37, but that somehow you
>> used a 0.33 'svnadmin' to create your repository.
>>
>> I'm guessing you still have mixed libraries on your system from two
>> different versions, or perhaps mixed binaries lying aound.
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by sm...@speakeasy.net.
Hi,
I'm installing from the fedora rpm's, and the corresponding download
server set up for svn at
http://summersoft.fay.ar.us/pub/subversion/latest/fedora/bin/
I suspected mixed binaries, so I explicitly did a rpm -e for the
subversion packages, and verified that mod_dav_svn and libsvn_fs had
been removed. I then re-installed 0.37.
Is there anything specific you would like me to look for? Are there any
other ways of testing remote connections? Local connections seem to work
fine. I tried:
svnlook info /var/vc /
and got back 0. I suppose this would be expected for a new repository?
Sunil
Ben Collins-Sussman wrote:
> On Sun, 2004-02-08 at 22:32, Toshio wrote:
>
>
>>On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
>>
>>>>To recap, I entirely removed my previous subversion installation,
>>>>then
>>>>installed 0.37. I created a brand new repository, and tried
>>>>connecting
>>
>>I had something similar happen to me the other day. It was because I
>>forgot to restart apache. Even though the new mod_dav_svn is in the
>>filesystem, the httpd thread you're accessing might still have the old
>>one loaded into memory.
>
>
> This would cause the *opposite* problem: you'd have a 0.33 mod_dav_svn
> trying to read a 0.37 repository. It would expect schema '2' but find
> schema '3' instead.
>
> The error message expected '3' but found '2'. Somehow, this indicates
> to me that mod_dav_svn is definitely version 0.37, but that somehow you
> used a 0.33 'svnadmin' to create your repository.
>
> I'm guessing you still have mixed libraries on your system from two
> different versions, or perhaps mixed binaries lying aound.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by Ben Collins-Sussman <su...@collab.net>.
On Sun, 2004-02-08 at 22:32, Toshio wrote:
> On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
> >>To recap, I entirely removed my previous subversion installation,
> >>then
> >>installed 0.37. I created a brand new repository, and tried
> >>connecting
>
> I had something similar happen to me the other day. It was because I
> forgot to restart apache. Even though the new mod_dav_svn is in the
> filesystem, the httpd thread you're accessing might still have the old
> one loaded into memory.
This would cause the *opposite* problem: you'd have a 0.33 mod_dav_svn
trying to read a 0.37 repository. It would expect schema '2' but find
schema '3' instead.
The error message expected '3' but found '2'. Somehow, this indicates
to me that mod_dav_svn is definitely version 0.37, but that somehow you
used a 0.33 'svnadmin' to create your repository.
I'm guessing you still have mixed libraries on your system from two
different versions, or perhaps mixed binaries lying aound.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by Toshio <to...@tiki-lounge.com>.
On Sun, 2004-02-08 at 22:44, Ben Collins-Sussman wrote:
> You need to migrate your repository data by using 'svnadmin dump >
> dumpfile' with the 0.32 svnadmin binary, and then 'svnadmin load
> newrepos < dumpfile' with the 0.37 svnadmin binary. See the book for
> details.
>
I think you missed this part:
On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
>>To recap, I entirely removed my previous subversion installation,
>>then
>>installed 0.37. I created a brand new repository, and tried
>>connecting
I had something similar happen to me the other day. It was because I
forgot to restart apache. Even though the new mod_dav_svn is in the
filesystem, the httpd thread you're accessing might still have the old
one loaded into memory.
-Toshio
--
Toshio <to...@tiki-lounge.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by sm...@speakeasy.net.
Hi Ben,
If you had read my message carefully, you would have seen that I created
a *new* snv repository with 0.37 for my testing. The issue of migration
should therefore be irrelevant.
Here are the contents of my repository's format file:
3
I assume this means schema version 3? (I checked the backup of my
previous svn repository, and format there contains 2.)
Sunil
Ben Collins-Sussman wrote:
> On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
>
>>I previously had 0.32.1
>>installed, which is available as part of the core distribution. While
>>that worked fine, upgrading to 0.37 has broken things.
>
>
> The repository database schema changed, be sure to read Subversion's
> CHANGES file and release announcements.
>
>
>>[Sun Feb 08 13:13:41 2004] [error] [client 127.0.0.1] (20014)Error
>>string not specified yet: Expected version '3' of repository; found
>>version '2'
>
>
> And here's libsvn_fs.so, version 0.37, complaining about the fact that
> it's seeing a 'version 2' repository db schema, when it wants the new
> 'version 3' schema.
>
> You need to migrate your repository data by using 'svnadmin dump >
> dumpfile' with the 0.32 svnadmin binary, and then 'svnadmin load
> newrepos < dumpfile' with the 0.37 svnadmin binary. See the book for
> details.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with subversion server running on Fedora
Posted by Ben Collins-Sussman <su...@collab.net>.
On Sun, 2004-02-08 at 16:49, smishra@speakeasy.net wrote:
> I previously had 0.32.1
> installed, which is available as part of the core distribution. While
> that worked fine, upgrading to 0.37 has broken things.
The repository database schema changed, be sure to read Subversion's
CHANGES file and release announcements.
> [Sun Feb 08 13:13:41 2004] [error] [client 127.0.0.1] (20014)Error
> string not specified yet: Expected version '3' of repository; found
> version '2'
And here's libsvn_fs.so, version 0.37, complaining about the fact that
it's seeing a 'version 2' repository db schema, when it wants the new
'version 3' schema.
You need to migrate your repository data by using 'svnadmin dump >
dumpfile' with the 0.32 svnadmin binary, and then 'svnadmin load
newrepos < dumpfile' with the 0.37 svnadmin binary. See the book for
details.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org