SCM Manager behind Apache and problems adding .xml files on Windows to SVN repo

[Christoph Stoppe]

Hi,

besides the strange german umlaut issue we encountered another one:

We've installed SCM Manager on SuSE Enterprise Server 11 SP2 and Apache 2.2 as reverse proxy following the instructions in the SCM Manager wiki. But when adding .xml files to a subversion repository with a Windows client (tried TortoiseSVN and Eclipse) we get this error:

Die PROPFIND-Anfrage gab in der Antwort ungültiges XML zurück: XML parse error
 at line 1: no element found
 (/scm/svn/it-betrieb/umlautetest/!svn/wrk/39cefdfc-a659-0247-8de7-8d0ae9878412/test2.xml)
Die PROPFIND-Anfrage gab in der Antwort ungültiges XML zurück: XML parse error
 at line 1: no element found

when adding the same file to this repository using the svn command line no error occurs. Adding the file on Windows with direct access to SCM Manager is working as well, so this looks like an Apache issue. But where could it be located? When working as reverse proxy Apache shouldn't look at the files at all and i really don't why this happens... anyone out there who could help with this one?

kind regards,

Christoph Stoppe

[Sebastian Sdorra]

Hi,
Could you post the reverse proxy configuration of your apache.

Sebastian

2012/6/29 Christoph Stoppe <happen...@googlemail.com>:

[Christoph Stoppe]

Hi,

this is our proxy configuration:

    <IfModule mod_rewrite.c>
       RewriteEngine On
       RewriteRule ^/$ /scm/ [redirect,last]
    </IfModule>

    <IfModule mod_proxy.c>
       ProxyPass /scm http://localhost:8080/scm
       ProxyPassReverse /scm http://localhost:8080/scm
    </IfModule>

the first block redirects all accesses to / to /scm/ the second one should be like the example in your documentation.

kind regards,

Christoph Stoppe

[Stephan Christann]

Hello Christoph,

 

yes this might be an apache error. I compared your config with one of mine running on a scientific linux 6 where we had a trailing slash problem. Perhaps try this:

 

ProxyPass /scm http://localhost:8080/scm/
ProxyPassReverse /scm http://localhost:8080/scm/

 

@Philip: Please try on our system, I configured our apache as reverse proxy as well according to my own advice.

 

 <IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule ^/$ /scm/ [redirect,last]
</IfModule>

<IfModule mod_proxy.c>

ProxyPass /scm http://localhost:8080/scm/
ProxyPassReverse /scm http://localhost:8080/scm/
</IfModule>

 

Am Freitag, 29. Juni 2012 15:14:28 UTC+2 schrieb Christoph Stoppe:

Hi,

besides the strange german umlaut issue we encountered another one:

We've installed SCM Manager on SuSE Enterprise Ser    <IfModule mod_rewrite.c>

RewriteEngine On
RewriteRule ^/$ /scm/ [redirect,last]
</IfModule>

<IfModule mod_proxy.c>
ProxyPass /scm http://localhost:8080/scm
ProxyPassReverse /scm http://localhost:8080/scm

</IfModule>ver 11 SP2 and Apache 2.2 as reverse proxy following the instructions in the SCM Manager wiki. But when adding .xml files to a subversion repository with a Windows client (tried TortoiseSVN and Eclipse) we get this error:

[Philip Pohle]

Hello Christoph,

i just tried to reproduce the error you described using TortoiseSVN 1.7.7 and scm-manager 1.16. 

All the tests i have done were successful. What versions of these applications are you using? Are there any logs made by scm-manager when the error occured?

kind regards,

Philip Pohle

[Christoph Stoppe]

Hi Stephan,

i played a little bit with slashes behind URIs and URLs and the setup will only work when adding trailing slashes to all statements or leaving them alone completly. So this:

ProxyPass /scm http://localhost:8080/scm
ProxyPassReverse /scm http://localhost:8080/scm

or this

ProxyPass /scm/ http://localhost:8080/scm/
ProxyPassReverse /scm/ http://localhost:8080/scm/

will work, but this:

ProxyPass /scm http://localhost:8080/scm/
ProxyPassReverse /scm http://localhost:8080/scm/

will not (jetty is complaining about not being able to find "/scm//"). None of the settings above solved the issue with adding XML files.

kind regards,

Christoph

[Stephan Christann]

Hello Christoph,

 

we tried some configurations on our site and your configuration is reported to be working by Philip (I configured the reverse proxy and he tested with his svn clients). We realized, that using a reverse proxy configuration hat a significant impact on the performance in our case. However, both configurations worked, maybe you can answer Philips questions?

 

For this week, this will be my last posting, because I am off till sunday.

Am Freitag, 29. Juni 2012 15:14:28 UTC+2 schrieb Christoph Stoppe:

[Christoph Stoppe]

Hi Philip,

i did not find a log entry anywhere when the error occurred. I would be happy, if you could give some advice on how to increase the loglevel of scm-manager.

We use SCM-Manager version 1.16 on SuSE Enterprise Server 11 SP2 with Apache 2.2.12 and subversion 1.7.5. On the client side i tried TortoiseSVN versions 1.7.3, 1.7.5 and 1.7.7 (the current one).

kind regards,

Christoph

[Christoph Stoppe]

Hi,

i've cut out a sequence of entries from the apache log file, which where created when i tried to commit the addition of a xml file to the repository:

10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "OPTIONS /scm/svn/it-betrieb/umlautetest HTTP/1.1" 401 -
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "OPTIONS /scm/svn/it-betrieb/umlautetest HTTP/1.1" 200 162
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "PROPFIND /scm/svn/it-betrieb/umlautetest HTTP/1.1" 207 351
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "MKACTIVITY /scm/svn/it-betrieb/umlautetest/!svn/act/ef66684e-a999-2a4e-9683-387cd09fe356 HTTP/1.1" 201 296
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "PROPFIND /scm/svn/it-betrieb/umlautetest HTTP/1.1" 207 250
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "CHECKOUT /scm/svn/it-betrieb/umlautetest/!svn/vcc/default HTTP/1.1" 201 324
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "PROPPATCH /scm/svn/it-betrieb/umlautetest/!svn/wbl/ef66684e-a999-2a4e-9683-387cd09fe356/13 HTTP/1.1" 207 278
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "CHECKOUT /scm/svn/it-betrieb/umlautetest/!svn/ver/13 HTTP/1.1" 201 323
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "PROPFIND /scm/svn/it-betrieb/umlautetest/!svn/wrk/ef66684e-a999-2a4e-9683-387cd09fe356/test3.xml HTTP/1.1" 404 -
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "PROPFIND /scm/svn/it-betrieb/umlautetest/test3.xml HTTP/1.1" 404 -
10.1.3.12 - - [19/Jul/2012:07:23:01 +0200] "DELETE /scm/svn/it-betrieb/umlautetest/!svn/act/ef66684e-a999-2a4e-9683-387cd09fe356 HTTP/1.1" 204 -

looks like the problem is in the two "PROPFIND" operations logged in the lines with return code 404 - but why is this happening?

I tried this with the current version of SCM Manager using TortoiseSVN (current version) on Windows and commandline client (Version 1.6.18 and 1.7.5) on Linux.

Any ideas on this?

kind regards,

Christoph Stoppe

[Stephan Christann]

Hello Christoph,

maybe you can raise the log level of scm-manager itself. To do so, configure it as follows:

How do I enable trace logging?

Edit scm-server/conf/logging.xml change the line from:

<logger name="sonia.scm" level="INFO" />

to:

<logger name="sonia.scm" level="TRACE" />

If you are using the war version with an application server such as tomcat, you have to edit the logback.xml in WEB-INF/classes.

(This is taken from the FAQs - https://bitbucket.org/sdorra/scm-manager/wiki/faq)

SCM-Manager has its own log file, in our case it is located under: /usr/share/tomcat6/.scm/logs

[Christoph Stoppe]

Hi Stephan,

ok, did it and it generated loads of information about authentacting me and checking if i'm allowed to access the repository. The last messages when the error appears are:

10:43:54.945 [qtp927829105-18] TRACE sonia.scm.web.filter.BasicAuthenticationFilter - user stoppe successfully authenticated
10:43:54.945 [qtp927829105-18] TRACE sonia.scm.web.filter.PermissionFilter - write access to repository it-betrieb/umlautetest for user stoppe granted
10:43:54.945 [qtp927829105-18] TRACE sonia.scm.repository.RepositoryRequestListenerUtil - no repository request listener defined

there are no other suspicious messages in the logfile. I'll have a look at increasing the verbosity of the Apache logfiles. Since the error only happens, when the Apache is used as reverse proxy, this might be the more promising approach in solving this issue.

kind regards,

Christoph

[Christoph Stoppe]

Hi,

today i tried playing with the "http-library" setting of our client, which changed the error message from the original one to a Error 500 when setting this to "http-library = neon" (so "http-library = serf" seems to be the default). This makes me think this is some kind of incompatability issue between SCM Manager and the client and may be related to the other issue someone observed and posted in the article with subject "doesn't support subversion client with ra_sef?".

kind regards,

Christoph Stoppe

[Christoph Stoppe]

Hi,

just for the records: We solved this issue (adding xml files to SVN repositories failed) by switching from the standalone version to a Tomcat 7 deployed web app archive version.

kind regards,

Christoph

Am Freitag, 29. Juni 2012 15:14:28 UTC+2 schrieb Christoph Stoppe: