On 2015-12-08 11:16, Stefan Sperling wrote:
please try raising HTTPD's LogLevel to "Debug" or higher. See
http://httpd.apache.org/docs/2.4/mod/core.html#loglevel Perhaps that
will shed more light on the problem.
Hi All.
I appreciate the time you guys are taking to help me. Thank you.
Here i
Thanks Philip. Great tips.
Just a remark: port to use in svn ls command is 9630 (instead of 9603)
--
Yves Martin
Chris Capon writes:
> What I don't know is how to diagnose the communications through apache
> and to the subversion server. No error messages appear in any of the
> apache2 logs nor the subversion log. So where is the error happening?
You should see the 400 in the apache logs at the very leas
On 2015-12-08 09:09, Bert Huijben wrote:
Are you using some kind of (caching) proxy server when you connect to
the server? You are focusing your search to a disk problem (probably
caused by hints on this list), while you are trying to determine what
causes a 'bad HTTP request' error. Bad reques
On Tue, Dec 08, 2015 at 04:28:21PM +0100, Bert Huijben wrote:
> This is just the Subversion operational log generated by mod_dav_svn. The
> interesting things would be in the apache access and/or error logs.
Hi Chris,
please try raising HTTPD's LogLevel to "Debug" or higher.
See http://httpd.apa
that
doesn’t tell us much why a request failed.
Bert
From: Chris Capon [mailto:ttab...@gmail.com]
Sent: dinsdag 8 december 2015 15:29
To: users@subversion.apache.org
Subject: Re: Unexpected HTTP status 400 'Bad request'.
Hi Bert.
The only log I know of is
Hello,
Really your issue is strange.
I propose you test your local checkout with HTTP protocol, with a tcpdump
network traffic collection, maybe it is possible to find clues "on the
wire".
--
Yves Martin
Bert
*From:*Yves Martin [mailto:ymartin1...@gmail.com]
*Sent:* dinsdag 8 december 2015 11:06
*To:* users@subversion.apache.org
*Subject:* Re: Unexpected HTTP status 400 'Bad request'.
Hello
Is your repository served read-write by other services like svnserve
or eventually through SSH
I Added both these lines to the section of the Apache2
configuration file. When I do an svn checkout locally, I get the same
error occurring.
On 2015-12-08 06:09, Yves Martin wrote:
Hello,
In my Apache2 configuration, I have added "LimitRequestBody 0" and
"LimitXMLRequestBody 0" to avoid
p.s. The server is around 8 years old and has been maintained and
regularly updated, pinned to the Testing release of Debian.
On 2015-12-08 05:06, Yves Martin wrote:
I guess your repository has been created long ago with a previous
version of Subversion.
> -Original Message-
> From: Chris Capon [mailto:ttab...@gmail.com]
> Sent: dinsdag 8 december 2015 14:47
> To: users@subversion.apache.org
> Subject: Re: Unexpected HTTP status 400 'Bad request'.
>
> On 2015-12-08 05:06, Yves Martin wrote:
> > Hel
On 2015-12-08 05:06, Yves Martin wrote:
Hello
Is your repository served read-write by other services like svnserve
or eventually through SSH in addition to Apache HTTPS access ?
I'm sorry. I don't understand what this asks. Permissions are
controlled by a .apache_auth and .apache_htpasswd
Hi Eric.
I did this:
svnadmin dump /root/subversion/root/repository > repository.dump
svnadmin create /root/subversion/root/tmprepo
chown -R www-data:www-data /root/subversion/root/tmprepo
svnadmin load /root/subversion/root/tmprepo < repository.dump
After this, I attempted a ch
Right. I also saw I have "LimitRequestFieldSize 6" set.
Is it possible for you to open a clear HTTP virtual host so that to inspect
Subversion client traffic and understand what may be wrong ?
--
Yves Martin
: Unexpected HTTP status 400 'Bad request'.
Hello,
In my Apache2 configuration, I have added "LimitRequestBody 0" and
"LimitXMLRequestBody 0" to avoid such troubles with a 12-year-old-really-large
repository...
Hope this helps
Regards
--
Yves Martin
Hello,
In my Apache2 configuration, I have added "LimitRequestBody 0" and
"LimitXMLRequestBody 0" to avoid such troubles with a
12-year-old-really-large repository...
Hope this helps
Regards
--
Yves Martin
)
Bert
From: Yves Martin [mailto:ymartin1...@gmail.com]
Sent: dinsdag 8 december 2015 11:06
To: users@subversion.apache.org
Subject: Re: Unexpected HTTP status 400 'Bad request'.
Hello
Is your repository served read-write by other services like svnserve or
Hello
Is your repository served read-write by other services like svnserve or
eventually through SSH in addition to Apache HTTPS access ?
If so you have to check your repository file permissions: owner, group and
modes (for instance g+w or g+s...)
I guess your repository has been created long
Is it feasible to dump and load the repository in question?
You could re-load it, and see if the repository still has problems.
On the other hand, if the load fails at a specific revision, that might
give you more of a clue about what is going wrong.
Eric.
On Mon, Dec 7, 2015 at 10:13 PM, Chris
On 2015-12-07 20:48, David Chapman wrote:
Have you verified that the repository on the server is not corrupt?
Perhaps the disk has a bad sector on the drive, and only that
repository is affected. Or maybe the hard drive itself is failing,
and the other repositories have simply been "lucky" s
On 12/7/2015 2:56 PM, Chris Capon wrote:
Hi.
We are running a Subversion server using Apache2 2.4.17-3, modDAV, and
Subversion 1.9.2-3+b1 (the latest Testing release) under Debian
GNU/Linux. We use HTTPS for security along with client certificates.
This server has been running for many years
21 matches
Mail list logo
