Re: E175002: The POST request returned invalid XML in the response: XML parse error
Mojca Miklavec writes: > I first need > to figure out how to use wireshark. Is there any chapter in SVN > documentation explaining how to troubleshoot problems with subversion > on a network level? And if not - would it be feasible to prepare one? http://subversion.apache.org/docs/community-guide/debugging.html#net-trace -- Philip
Re: E175002: The POST request returned invalid XML in the response: XML parse error
Daniel Shahaf wrote on Tue, Dec 20, 2011 at 02:43:48 +0200: > > I then added a new directory with a bunch of files and wanted to > > commit, but it complained with: > > > > > 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) > > > > > > May I ask for any hints of what could go wrong and how I could debug > > the problem? I have seen various threads after searching with google, > > but none of those that I checked provided any useful insight. (I work > > with SVN a lot, but have never experienced a problem like this one.) > > The use of POST request is new in 1.7 (client+server must be 1.7 for > this). Forgot to say: "SVNAdvertiseV2Protocol off" will work around the error.
Re: E175002: The POST request returned invalid XML in the response: XML parse error
Mojca Miklavec wrote on Tue, Dec 20, 2011 at 09:53:46 +0100:
> On Tue, Dec 20, 2011 at 01:43, Daniel Shahaf wrote:
> > Can you capture the XML response on the wire and share it here? (with
> > wireshark, or neon-debug-mask) If it contains sensitive stuff feel free
> > to share it by private mail.
>
> Maybe Philip Martin's mail already answers this question. I first need
> to figure out how to use wireshark. Is there any chapter in SVN
> documentation explaining how to troubleshoot problems with subversion
> on a network level? And if not - would it be feasible to prepare one?
>
Usage of neon-debug-mask is explained in ~/.subversion/servers
Usage of wireshark... well, in this case you don't use ssl, so it's
raelly as simple as "Fire up wireshark, tell it to monitor TCP
connections to "${server}" on port "http (80)", run the failing command,
save the TCP stream. I tend to think the wireshark docs have a generic
tutorial of this sort somewhere.
Though, yes, it might be a good idea to add something to the our docs
too.
> Mojca
Re: E175002: The POST request returned invalid XML in the response: XML parse error
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" > > > http://apache.org/dav/xmlns";> > > > could not begin a transaction > > > > 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
On Tue, Dec 20, 2011 at 01:43, Daniel Shahaf wrote: > Mojca Miklavec wrote on Mon, Dec 19, 2011 at 16:56:05 +0100: >> >> May I ask for any hints of what could go wrong and how I could debug >> the problem? I have seen various threads after searching with google, >> but none of those that I checked provided any useful insight. (I work >> with SVN a lot, but have never experienced a problem like this one.) > > The use of POST request is new in 1.7 (client+server must be 1.7 for > this). They are. > Can you capture the XML response on the wire and share it here? (with > wireshark, or neon-debug-mask) If it contains sensitive stuff feel free > to share it by private mail. Maybe Philip Martin's mail already answers this question. I first need to figure out how to use wireshark. Is there any chapter in SVN documentation explaining how to troubleshoot problems with subversion on a network level? And if not - would it be feasible to prepare one? Mojca
Re: E175002: The POST request returned invalid XML in the response: XML parse error
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. 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" http://apache.org/dav/xmlns";> could not begin a transaction That "D:(null)" is suspicious. -- Philip
Re: E175002: The POST request returned invalid XML in the response: XML parse error
Mojca Miklavec wrote on Mon, Dec 19, 2011 at 16:56:05 +0100: > Hello, > > I create a new repository on server with > svncreate /path/to/repos/suite > and added the rights (everyone is allowed to read, I'm also allowed to > edit). Server reports: > > > svn --version > svn, version 1.7.2 (r1207936) >compiled Dec 5 2011, 22:26:40 > > I checked out an empty version 0 successfully (through apache) with > > svn co http://svn.myserver.com/suite > > and client version reporting: > > > svn --version > svn, version 1.7.2 (r1207936) >compiled Dec 9 2011, 21:54:16 > > > I then added a new directory with a bunch of files and wanted to > commit, but it complained with: > > > 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) > > > May I ask for any hints of what could go wrong and how I could debug > the problem? I have seen various threads after searching with google, > but none of those that I checked provided any useful insight. (I work > with SVN a lot, but have never experienced a problem like this one.) The use of POST request is new in 1.7 (client+server must be 1.7 for this). Can you capture the XML response on the wire and share it here? (with wireshark, or neon-debug-mask) If it contains sensitive stuff feel free to share it by private mail. > > Thank you very much, > Mojca
