Hello,
When I say hang, I mean that the command does not finish, I don't retrieve the hand.
I can't access the repository from this machine (I have installed several versions of SVN client).
Yes, if I say something like "svn mkdir http://foo.bar/baz" I do
not get an error message, The command does not finish.
I know that 1.1.4 is pretty old. But I can access to it from other machine, so I think it is not a server problem.
How can I run a trace on the process?
Regards
Hervé
-----Message d'origine-----
De : Ryan Schmidt [mailto:subversion-2007a@ryandesign.com]
Envoyé : samedi 17 février 2007 06:01
À : Hervé Heudebert
Cc : users@subversion.tigris.org
Objet : Re: Svn hangs up
On Feb 15, 2007, at 08:48, Hervé Heudebert wrote:
> I have a problem using SVN client on Linux Redhat 7.2.
>
> When I execute a command which read information from the server
> (ex. Svn list, svn cat, svn co,.), there is no problem.
>
> When I execute a command which write data to the server (svn
> commit, svn import, svn mkdir .). Ex. svn mkdir http://
> svn.nexotelematics.com/test/test The command hangs up.
Do you mean "hang" as in "to freeze or lock up", or do you mean "hang
up" as in "to disconnect", like a telephone? Is an error message
printed?
> The client is accessing the server by apache module.
>
>
>
> A client in another machine works well.
So another client can access this repository just fine, but this
1.4.3 client on this Redhat machine cannot?
> Concerning apache logs : During svn list, logs are written. During
> svn mkdir no log are written.
>
> If a put a bad http address in svn mkdir command, I don't have
> error message, the command hangs up too.
So if you say something like "svn mkdir http://foo.bar/baz" you do
not get an error message? It hangs then also, with an invalid URL
that does not point to your server? Then it must be a problem with
the client only, and not the server; nevertheless:
> In Server side :
>
> *Apache version is 2.0.54-5sarge1
>
> *Apache module for SVN is libapache2svn version 1.1.4-2
1.1.4 is pretty old, and I would recommend upgrading to 1.4.3 on
principle, so that you don't run into any bugs that have been fixed
since then.
> * We are using FSFS repository.
>
>
>
> *The apache directive is
>
>
>
> <Location /test>
>
> DAV svn
>
> SVNPath /opt/subversion/repositories/test
>
> </Location>
>
> There are no active hooks
>
>
>
> In client side :
>
> * OS : Redhat 7.2
>
> *uname -a output : Linux AMBER 2.4.9-31 #1 Tue Feb 26 07:11:02 EST
> 2002 i686 unknown
>
> * svn, version 1.4.3 (r23084)
>
> compiled Feb 14 2007, 14:23:43
>
>
>
> Copyright (C) 2000-2006 CollabNet.
>
> Subversion is open source software, see http://subversion.tigris.org/
>
> This product includes software developed by CollabNet (http://
> www.Collab.Net/).
>
>
>
> The following repository access (RA) modules are available:
>
>
>
> * ra_dav : Module for accessing a repository via WebDAV (DeltaV)
> protocol.
>
> - handles 'http' scheme
>
> - handles 'https' scheme
>
> * ra_svn : Module for accessing a repository using the svn network
> protocol.
>
> - handles 'svn' scheme
>
> * ra_local : Module for accessing a repository on local disk.
>
> - handles 'file' scheme
>
>
>
>
>
>
>
> The others clients have been installed in redhat enterprise and
> Windows Xp OS. They wrok well.
>
>
>
> Does anybody have a idea for a way to resolve my problem ?
Reinstall the Subversion client on the machine where it doesn't work?
Or run a trace on the process and see where it's hanging; maybe that
will provide some insight into what's wrong.
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 19 09:34:15 2007