You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Philip Martin <ph...@wandisco.com> on 2011/12/20 02:34:12 UTC
Re: E175002: The POST request returned invalid XML in the response: XML parse error
Mojca Miklavec <mo...@gmail.com> writes:
>> svn ci -m "some comment"
> svn: E175002: Commit failed (details follow):
> svn: E175002: The POST request returned invalid XML in the response:
> XML parse error at line 3: not well-formed (invalid token)
> (/suite/!svn/me)
One thing that can cause this error is when the OS permissions prevent
Apache writing to the repository.
The underlying error on the server is:
"Can't open file '.../db/txn-current-lock': Permission denied"
but it looks like we have a problem with the error reporting. I don't
see anything logged in the apache log, and wireshark shows the response
HTTP/1.1 500 Internal Server Error
Date: Tue, 20 Dec 2011 01:22:45 GMT
Server: Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 SVN/1.8.0-dev
Content-Length: 207
Connection: close
Content-Type: text/xml; charset="utf-8"
<?xml version="1.0" encoding="utf-8"?>
<D:error xmlns:D="DAV:" xmlns:m="http://apache.org/dav/xmlns">
<D:(null)/>
<m:human-readable errcode="13">
could not begin a transaction
</m:human-readable>
</D:error>
That "D:(null)" is suspicious.
--
Philip
Re: E175002: The POST request returned invalid XML in the response:
XML parse error
Posted by Mojca Miklavec <mo...@gmail.com>.
On Tue, Dec 20, 2011 at 02:34, Philip Martin wrote:
> Mojca Miklavec writes:
>
>>> svn ci -m "some comment"
>> svn: E175002: Commit failed (details follow):
>> svn: E175002: The POST request returned invalid XML in the response:
>> XML parse error at line 3: not well-formed (invalid token)
>> (/suite/!svn/me)
>
> One thing that can cause this error is when the OS permissions prevent
> Apache writing to the repository.
Thank you very much for the hint. This is a quite likely cause. I
don't have the computer at hand, but I indeed created the repository
with "sudo svncreate" and if apache needs to write to it, I can easily
believe that the rights are not sufficient to do so.
Still, it would help a lot if the error message was more descriptive
than it was (I would then figure out what to do myself).
> The underlying error on the server is:
>
> "Can't open file '.../db/txn-current-lock': Permission denied"
>
> but it looks like we have a problem with the error reporting. I don't
> see anything logged in the apache log, and wireshark shows the response
>
> HTTP/1.1 500 Internal Server Error
> Date: Tue, 20 Dec 2011 01:22:45 GMT
> Server: Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 SVN/1.8.0-dev
> Content-Length: 207
> Connection: close
> Content-Type: text/xml; charset="utf-8"
>
> <?xml version="1.0" encoding="utf-8"?>
> <D:error xmlns:D="DAV:" xmlns:m="http://apache.org/dav/xmlns">
> <D:(null)/>
> <m:human-readable errcode="13">
> could not begin a transaction
> </m:human-readable>
> </D:error>
>
> That "D:(null)" is suspicious.
Thank you for the precise analysis.
Mojca
Re: E175002: The POST request returned invalid XML in the response:
XML parse error
Posted by Mojca Miklavec <mo...@gmail.com>.
On Tue, Dec 20, 2011 at 02:34, Philip Martin wrote:
> Mojca Miklavec writes:
>
>>> svn ci -m "some comment"
>> svn: E175002: Commit failed (details follow):
>> svn: E175002: The POST request returned invalid XML in the response:
>> XML parse error at line 3: not well-formed (invalid token)
>> (/suite/!svn/me)
>
> One thing that can cause this error is when the OS permissions prevent
> Apache writing to the repository.
Thank you very much for the hint. This is a quite likely cause. I
don't have the computer at hand, but I indeed created the repository
with "sudo svncreate" and if apache needs to write to it, I can easily
believe that the rights are not sufficient to do so.
Still, it would help a lot if the error message was more descriptive
than it was (I would then figure out what to do myself).
> The underlying error on the server is:
>
> "Can't open file '.../db/txn-current-lock': Permission denied"
>
> but it looks like we have a problem with the error reporting. I don't
> see anything logged in the apache log, and wireshark shows the response
>
> HTTP/1.1 500 Internal Server Error
> Date: Tue, 20 Dec 2011 01:22:45 GMT
> Server: Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 SVN/1.8.0-dev
> Content-Length: 207
> Connection: close
> Content-Type: text/xml; charset="utf-8"
>
> <?xml version="1.0" encoding="utf-8"?>
> <D:error xmlns:D="DAV:" xmlns:m="http://apache.org/dav/xmlns">
> <D:(null)/>
> <m:human-readable errcode="13">
> could not begin a transaction
> </m:human-readable>
> </D:error>
>
> That "D:(null)" is suspicious.
Thank you for the precise analysis.
Mojca