SVN commit does nothing

[pascal....@freescale.com]

Hi

 

I recently installed svn module (1.8.11) for apache (2.2.24). I compiled successfully everything without issue but I can’t have it working properly, I need help of advanced users.

I can create repository with svnadmin or copy repository from existing installation. I didn’t set any rights limitation for now to be able to easily test installation.

Repository checkout or update is working fine using tortoise or command line client. Repository read through web browser is also working fine.

 

BUT commit does nothing. When I try to commit existing or new file, from tortoise or command line, commit starts and is never done. It seems to be doing the commit until timeout occur (few minutes) or I cancel it. I don’t have any error message, nothing to debug. In httpd access log I see an OPTION request, that’s all. Nothing in error log.

 

My configuration is like this:

 

LoadModule dav_module lib/httpd/modules/mod_dav.so

LoadModule dav_fs_module lib/httpd/modules/mod_dav_fs.so

LoadModule dav_svn_module     libexec/mod_dav_svn.so

LoadModule authz_svn_module   libexec/mod_authz_svn.so

 

DavLockDB "/opt/amon/var/DavLock"

 

<Location /svn>

    DAV svn

    SVNParentPath /opt/amon/var/www/svn

    SVNListParentPath On

</Location>

 

Apache user and group is the same as user creating the repository.

 

After few days searching I don’t see anything else to do, what could I check now?

 

Thanks for your help!

 

Regards

Pascal

 

[Eric Johnson]

After you have created repositories, do you see them listed when you browse to the ____/svn location in your browser. Do the error logs for Apache show anything? Have you checked into all the logging options for Subversion + Apache (sorry, don't have the link handy from my phone)?

Also, try checkout and commit directly on the machine (as the same user running Apache), using file:/// URLs, and see if that reports anything that gives you a clue as to whether it is working. Or does it just work?

Eric

[pascal....@freescale.com]

Hi Eric

Thanks for your answer.

 

The repository are well created under the location ___/svn and I can access them through http, that’s fine.

Error log from apache does not show anything.

I added svn logging in httpd.conf (following this http://svnbook.red-bean.com/en/1.7/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.logging), I see read operations being done (update, or show log from tortoise) but not the commit.

I tried to checkout and commit directly on the machine (as the same user running apache) using file:/// and commit works!

That’s a first step but I don’t see what is wrong then…

 

Thanks

Pascal

[Eric Johnson]

My next guess - make sure you don't have a firewall or other agent blocking some of your HTTP traffic. Could be you're accidentally blocking some of the requests being sent to Apache.

I mention that, because that would be consistent with the client waiting for the response, and the server not thinking there's anything to be done.

Eric.

[pascal....@freescale.com]

Hi

 

That’s something I was thinking about also but I am within a company that ‘probably’ don’t have firewall for internal traffic. I still need to confirm it.

 

I tried few other things directly from the server.

As I said in a previous message, I did a svn commit on the repository using URL file:///location/to/svn/myrepository/, that’s working fine.

I tried a svn commit on the repository using URL http://localhost:1080/svn/myrepository/, also working fine.

I tried a svn commit on the repository using URL http://hostname/svn/myrepository/ or http://hostname:1080/svn/myrepository/ which is not working (I am still able to make checkout/update from repository using any address)

I tried a svn commit on the repository using URL http://ipaddress/svn/myrepository/ or http://ipaddress:1080/svn/myrepository/ which is not working (I am still able to make checkout/update from repository using any address)

 

I forgot to mention that this server is listening port 1080 using global http.conf directive:

Listen 1080

But I don’t expect this to make a change.

 

I continue searching the solution, any idea of thing to check would be appreciated.

[pascal....@freescale.com]

Hi again

In fact my previous conclusion are wrong.

What exactly works is svn commit from a client that is version 1.6. Using a svn client 1.7 or 1.8, commit does not proceed until stopped by the timeout.

svn version on server is 1.8.11.

What is different between version 1.6 and 1.7 or 1.8 during a commit that could make it fail?

[Les Mikesell]

On Wed, Mar 11, 2015 at 11:51 AM, pascal....@freescale.com
<pascal....@freescale.com> wrote:
> Hi again
>
> In fact my previous conclusion are wrong.
>
> What exactly works is svn commit from a client that is version 1.6. Using a
> svn client 1.7 or 1.8, commit does not proceed until stopped by the timeout.
>
> svn version on server is 1.8.11.
>
> What is different between version 1.6 and 1.7 or 1.8 during a commit that
> could make it fail?

There have been some client issues involving the serf or neon
libraries mentioned before but usually things get better with newer
clients, not the other way around. Taking a step back, why are you
compiling your own server? Isn't there a packaged version available
for your platform? It might help to start with a known-working
server build.

--
Les Mikesell
lesmi...@gmail.com

[pascal....@freescale.com]

I'm in a company that use redhat as base distribution. I asked for a web server to migrate some tools from an old server. I asked for recent versions of some tools like php, perl or mysql.
For this reason (mostly compile a newer version of php) and to be able to put all the binaries and configuration on a storage with backup they gave me a custom web stack compiled with httpd 2.2. Now I have to add svn, that's why I compiled it from source.
I found that discussion where POST request where not handled by svn. Except I have to error, it seems I face the same kind of problem: http://grokbase.com/t/subversion/users/123tdmwx9x/subversion-1-7-server-client-issue-not-able-to-commit-e160013-path-not-found. I don't have mod_wsgi but could it be same issue with other module?
Here is the list of modules I'm loading:

LoadModule authn_file_module lib/httpd/modules/mod_authn_file.so
LoadModule authn_dbm_module lib/httpd/modules/mod_authn_dbm.so
LoadModule authn_anon_module lib/httpd/modules/mod_authn_anon.so
LoadModule authn_dbd_module lib/httpd/modules/mod_authn_dbd.so
LoadModule authn_default_module lib/httpd/modules/mod_authn_default.so
LoadModule authn_alias_module lib/httpd/modules/mod_authn_alias.so
LoadModule authz_host_module lib/httpd/modules/mod_authz_host.so
LoadModule authz_groupfile_module lib/httpd/modules/mod_authz_groupfile.so
LoadModule authz_user_module lib/httpd/modules/mod_authz_user.so
LoadModule authz_dbm_module lib/httpd/modules/mod_authz_dbm.so
LoadModule authz_owner_module lib/httpd/modules/mod_authz_owner.so
LoadModule authnz_ldap_module lib/httpd/modules/mod_authnz_ldap.so
LoadModule authz_default_module lib/httpd/modules/mod_authz_default.so
LoadModule auth_basic_module lib/httpd/modules/mod_auth_basic.so
LoadModule auth_digest_module lib/httpd/modules/mod_auth_digest.so
LoadModule file_cache_module lib/httpd/modules/mod_file_cache.so
LoadModule cache_module lib/httpd/modules/mod_cache.so
LoadModule disk_cache_module lib/httpd/modules/mod_disk_cache.so
LoadModule mem_cache_module lib/httpd/modules/mod_mem_cache.so
LoadModule dbd_module lib/httpd/modules/mod_dbd.so
LoadModule dumpio_module lib/httpd/modules/mod_dumpio.so
LoadModule reqtimeout_module lib/httpd/modules/mod_reqtimeout.so
LoadModule ext_filter_module lib/httpd/modules/mod_ext_filter.so
LoadModule include_module lib/httpd/modules/mod_include.so
LoadModule filter_module lib/httpd/modules/mod_filter.so
LoadModule substitute_module lib/httpd/modules/mod_substitute.so
LoadModule deflate_module lib/httpd/modules/mod_deflate.so
LoadModule ldap_module lib/httpd/modules/mod_ldap.so
LoadModule log_config_module lib/httpd/modules/mod_log_config.so
LoadModule log_forensic_module lib/httpd/modules/mod_log_forensic.so
LoadModule logio_module lib/httpd/modules/mod_logio.so
LoadModule env_module lib/httpd/modules/mod_env.so
LoadModule mime_magic_module lib/httpd/modules/mod_mime_magic.so
LoadModule cern_meta_module lib/httpd/modules/mod_cern_meta.so
LoadModule expires_module lib/httpd/modules/mod_expires.so
LoadModule headers_module lib/httpd/modules/mod_headers.so
LoadModule ident_module lib/httpd/modules/mod_ident.so
LoadModule usertrack_module lib/httpd/modules/mod_usertrack.so
LoadModule unique_id_module lib/httpd/modules/mod_unique_id.so
LoadModule setenvif_module lib/httpd/modules/mod_setenvif.so
LoadModule version_module lib/httpd/modules/mod_version.so
LoadModule proxy_module lib/httpd/modules/mod_proxy.so
LoadModule proxy_connect_module lib/httpd/modules/mod_proxy_connect.so
LoadModule proxy_ftp_module lib/httpd/modules/mod_proxy_ftp.so
LoadModule proxy_http_module lib/httpd/modules/mod_proxy_http.so
LoadModule proxy_scgi_module lib/httpd/modules/mod_proxy_scgi.so
LoadModule proxy_ajp_module lib/httpd/modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module lib/httpd/modules/mod_proxy_balancer.so
LoadModule mime_module lib/httpd/modules/mod_mime.so
LoadModule dav_module lib/httpd/modules/mod_dav.so
LoadModule status_module lib/httpd/modules/mod_status.so
LoadModule autoindex_module lib/httpd/modules/mod_autoindex.so
LoadModule asis_module lib/httpd/modules/mod_asis.so
LoadModule info_module lib/httpd/modules/mod_info.so
LoadModule suexec_module lib/httpd/modules/mod_suexec.so
LoadModule cgi_module lib/httpd/modules/mod_cgi.so
LoadModule dav_fs_module lib/httpd/modules/mod_dav_fs.so
LoadModule vhost_alias_module lib/httpd/modules/mod_vhost_alias.so
LoadModule negotiation_module lib/httpd/modules/mod_negotiation.so
LoadModule dir_module lib/httpd/modules/mod_dir.so
LoadModule imagemap_module lib/httpd/modules/mod_imagemap.so
LoadModule actions_module lib/httpd/modules/mod_actions.so
LoadModule speling_module lib/httpd/modules/mod_speling.so
LoadModule userdir_module lib/httpd/modules/mod_userdir.so
LoadModule alias_module lib/httpd/modules/mod_alias.so
LoadModule rewrite_module lib/httpd/modules/mod_rewrite.so
LoadModule php5_module lib/httpd/modules/libphp5.so

LoadModule dav_svn_module libexec/mod_dav_svn.so
LoadModule authz_svn_module libexec/mod_authz_svn.so

LoadModule perl_module /opt/amon/pkgs/lib/httpd/modules/mod_perl.so

How can I trace requests and see where are they handle in httpd?
Should I try to build an older version of svn?

Thanks for your help

Pascal

-----Original Message-----
From: Les Mikesell [mailto:lesmi...@gmail.com]
Sent: Wednesday, March 11, 2015 6:17 PM
To: Sandrez Pascal-B09824
Cc: Eric Johnson; us...@subversion.apache.org
Subject: Re: SVN commit does nothing

[Les Mikesell]

On Wed, Mar 11, 2015 at 12:32 PM, pascal....@freescale.com
<pascal....@freescale.com> wrote:
> I'm in a company that use redhat as base distribution. I asked for a web server to migrate some tools from an old server. I asked for recent versions of some tools like php, perl or mysql.
> For this reason (mostly compile a newer version of php) and to be able to put all the binaries and configuration on a storage with backup they gave me a custom web stack compiled with httpd 2.2. Now I have to add svn, that's why I compiled it from source.

> I found that discussion where POST request where not handled by svn. Except I have to error, it seems I face the same kind of problem:

[...]

> How can I trace requests and see where are they handle in httpd?

Does the httpd error_log show a problem? It could be something simple
like needing to increase apache's setting for LimitRequestBody. Or
not.

> Should I try to build an older version of svn?

Personally, I've gotten tired of fighting that kind of battle and
would either switch to running svnserve so you don't have to deal
with apache at all, or find a way to run a stock apache rpm and either
the stock older subversion or a packaged newer one like wandisco's.
Is there any chance of getting RHEL7 as your base system? That
shouldn't be horribly outdated at this point. You didn't say what
version you have, but mixing httpd 2.2 with new custom stuff seems
like asking for trouble.

--
Les Mikesell
lesmi...@gmail.com

[Johan Corveleyn]

Op 11-mrt.-2015 18:32 schreef "pascal....@freescale.com" <pascal....@freescale.com>:

>
> I'm in a company that use redhat as base distribution. I asked for a web server to migrate some tools from an old server. I asked for recent versions of some tools like php, perl or mysql.
> For this reason (mostly compile a newer version of php) and to be able to put all the binaries and configuration on a storage with backup they gave me a custom web stack compiled with httpd 2.2. Now I have to add svn, that's why I compiled it from source.
> I found that discussion where POST request where not handled by svn. Except I have to error, it seems I face the same kind of problem: http://grokbase.com/t/subversion/users/123tdmwx9x/subversion-1-7-server-client-issue-not-able-to-commit-e160013-path-not-found.

That doesn't sound like the same issue to me. That thread mentions a specific error message (E160013 path not found) while you said commit just does nothing (hangs until timeout or something). Or did you forget to add the tiny detail that you got an error ;-) ?

Apart from that, the thread does suggest something to try: did you test if the issue goes away if you set "SVNAdvertiseV2Protocol off"?

--
Johan

[pascal....@freescale.com]

I don't have any error or warning in httpd error_log.

We are currently using RHEL5.5, it's hard to understand why we are so late in upgrading software versions but I can't choose, I have to live with it. But now I understand that I should better try to use a global package including all I need instead of trying to assemble piece of software.

Do you know which version of svn should I use with httpd2.2?

Pascal

-----Original Message-----
From: Les Mikesell [mailto:lesmi...@gmail.com]
Sent: Wednesday, March 11, 2015 7:01 PM
To: Sandrez Pascal-B09824
Cc: Eric Johnson; us...@subversion.apache.org
Subject: Re: SVN commit does nothing

[pascal....@freescale.com]

Hi

 

I tried to set “SVNAdvertiseV2Protocol off” and it worked!

It’s something like subversion > 1.6 and httpd 2.2 can’t work properly together.

Finally I compiled subversion 1.6 which is enough for the purpose of this installation and that is OK

 

Thanks a lot for your help!

 

Pascal

 

 

From: Johan Corveleyn [mailto:jco...@gmail.com]

Sent: Wednesday, March 11, 2015 7:37 PM
To: Sandrez Pascal-B09824

[Philip Martin]

Subversion 1.8 works with httpd 2.2. Something (a module, a proxy, a
load balancer) is interfering with POST requests. The best solution is
to identify what is interfering with POST and fix it, but if you cannot
do that you are advised to run 1.8 with "SVNAdvertiseV2Protocol off"
rather than 1.6. 1.6 has lower performance, more bugs, and is no longer
supported.

"pascal....@freescale.com" <pascal....@freescale.com> writes:

> Hi
>
> I tried to set “SVNAdvertiseV2Protocol off” and it worked!
> It’s something like subversion > 1.6 and httpd 2.2 can’t work properly together.
> Finally I compiled subversion 1.6 which is enough for the purpose of
> this installation and that is OK
>
> Thanks a lot for your help!
>
> Pascal
>
>
> From: Johan Corveleyn [mailto:jco...@gmail.com]
> Sent: Wednesday, March 11, 2015 7:37 PM
> To: Sandrez Pascal-B09824
> Cc: Eric Johnson; Les Mikesell; us...@subversion.apache.org
> Subject: RE: SVN commit does nothing
>
>
> Op 11-mrt.-2015 18:32 schreef

> "pascal....@freescale.com<mailto:pascal....@freescale.com>"
> <pascal....@freescale.com<mailto:pascal....@freescale.com>>:

>>
>> I'm in a company that use redhat as base distribution. I asked for a
>> web server to migrate some tools from an old server. I asked for
>> recent versions of some tools like php, perl or mysql.
>> For this reason (mostly compile a newer version of php) and to be
>> able to put all the binaries and configuration on a storage with
>> backup they gave me a custom web stack compiled with httpd 2.2. Now
>> I have to add svn, that's why I compiled it from source.
>> I found that discussion where POST request where not handled by
>> svn. Except I have to error, it seems I face the same kind of
>> problem:
>> http://grokbase.com/t/subversion/users/123tdmwx9x/subversion-1-7-server-client-issue-not-able-to-commit-e160013-path-not-found.
>
> That doesn't sound like the same issue to me. That thread mentions a
> specific error message (E160013 path not found) while you said commit
> just does nothing (hangs until timeout or something). Or did you
> forget to add the tiny detail that you got an error ;-) ?
>
> Apart from that, the thread does suggest something to try: did you
> test if the issue goes away if you set "SVNAdvertiseV2Protocol off"?
>
> --
> Johan

--
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*

[pascal....@freescale.com]

I also think that "something" is interfering with this request but I don't know how to identify this issues as I don't master these technologies and don't see any error.
But thanks, I take note that it would be better to install version 1.8 anyway.
Pascal

-----Original Message-----
From: Philip Martin [mailto:philip...@wandisco.com]
Sent: Thursday, March 12, 2015 4:40 PM
To: Sandrez Pascal-B09824

Cc: Johan Corveleyn; Eric Johnson; Les Mikesell; us...@subversion.apache.org
Subject: Re: SVN commit does nothing

[Les Mikesell]

On Thu, Mar 12, 2015 at 11:59 AM, pascal....@freescale.com
<pascal....@freescale.com> wrote:
> I also think that "something" is interfering with this request but I don't know how to identify this issues as I don't master these technologies and don't see any error.
> But thanks, I take note that it would be better to install version 1.8 anyway.
> Pascal
>

If you had a stock RHEL5.x apache, I'd recommend starting here:
http://opensource.wandisco.com/rhel/5/svn-1.8/RPMS/. You might be
able to get the src.rpms to rebuild against what you have, but I think
the apr* part has to match your apache build.

--
Les Mikesell
lesmi...@gmail.com