You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ravi Roy <ra...@gmail.com> on 2012/02/11 10:10:55 UTC
Delta source ended unexpectedly [500, #200003] using Subversion
1.6.17 with Apache http server 2.2.21
Hello community,
I have compiled subversion 1.6.17 and Apache 2.2.21 from source on CentOS
5.6 and serving my repository using Apache httpd server with the following
details :
Server version: Apache/2.2.21 (Unix)
Server loaded: APR 1.4.5, APR-Util 1.3.12
Compiled using: APR 1.4.5, APR-Util 1.3.12
Getting the folloiwng normal message in apache log :
[Sat Feb 11 14:13:41 2012] [notice] Apache/2.2.21 (Unix) DAV/2
mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 SVN/1.6.17 PHP/5.1.6 configured --
resuming normal operations
Problem : When try to commit from the checkout made from master everything
works fine, but when I try to commit from the checkout from slave I get the
following message in apache's log :
[Sat Feb 11 10:04:01 2012] [error] [client xxx.xxx.xx.xxx] could not write
the file contents [500, #200003]
[Sat Feb 11 10:04:01 2012] [error] [client xxx.xxx.xx.xxx] Delta source
ended unexpectedly [500, #200003]
I am using TortoiseSVN 1.6.16 to commit to repository.
Does somebody knows if this is known bug or have somebody faced this issue
earlier?
Thanks for the help in advance!
Regards
Ravi.
Re: Delta source ended unexpectedly [500, #200003] using Subversion
1.6.17 with Apache http server 2.2.21
Posted by Ravi Roy <ra...@gmail.com>.
> So you're running a master/slave setup with a write-through proxy
> configuration, yes? You don't mention whether you're quoting logs
> from the master or from the slave server.
>
I apologize; yes I am running master/slave setup with a write-trough
proxy.
Logs belong to Master.
>
> Is the slave repository properly synced with the master?
>
Before trying to commit, both master and slave are synced.
>
> Does 'svnadmin verify' pass on both sides or is there repository
> corruption involved?
>
I used 'svnadmin verify' and all revisions are verified and no error /
inconsistency reported.
>
> Could this problem be relevant?
> http://subversion.tigris.org/issues/show_bug.cgi?id=3445
>
Could be, but I have to verify it.
Thanks!
Re: Delta source ended unexpectedly [500, #200003] using Subversion
1.6.17 with Apache http server 2.2.21
Posted by Stefan Sperling <st...@elego.de>.
On Sat, Feb 11, 2012 at 04:36:46PM +0530, Ravi Roy wrote:
> I found this under
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=193527
> in the mail archive of dated back to 2002 and this seems to be fixed as per
> the bug report.
>
> Can somebody please comment on the issue?
So you're running a master/slave setup with a write-through proxy
configuration, yes? You don't mention whether you're quoting logs
from the master or from the slave server.
Is the slave repository properly synced with the master?
Does 'svnadmin verify' pass on both sides or is there repository
corruption involved?
Could this problem be relevant?
http://subversion.tigris.org/issues/show_bug.cgi?id=3445
> On Sat, Feb 11, 2012 at 2:40 PM, Ravi Roy <ra...@gmail.com> wrote:
>
> > Hello community,
> >
> > I have compiled subversion 1.6.17 and Apache 2.2.21 from source on CentOS
> > 5.6 and serving my repository using Apache httpd server with the following
> > details :
> >
> > Server version: Apache/2.2.21 (Unix)
> > Server loaded: APR 1.4.5, APR-Util 1.3.12
> > Compiled using: APR 1.4.5, APR-Util 1.3.12
> >
> > Getting the folloiwng normal message in apache log :
> >
> > [Sat Feb 11 14:13:41 2012] [notice] Apache/2.2.21 (Unix) DAV/2
> > mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 SVN/1.6.17 PHP/5.1.6 configured --
> > resuming normal operations
> >
> > Problem : When try to commit from the checkout made from master everything
> > works fine, but when I try to commit from the checkout from slave I get the
> > following message in apache's log :
> >
> > [Sat Feb 11 10:04:01 2012] [error] [client xxx.xxx.xx.xxx] could not write
> > the file contents [500, #200003]
> > [Sat Feb 11 10:04:01 2012] [error] [client xxx.xxx.xx.xxx] Delta source
> > ended unexpectedly [500, #200003]
> >
> > I am using TortoiseSVN 1.6.16 to commit to repository.
> >
> > Does somebody knows if this is known bug or have somebody faced this issue
> > earlier?
> >
> > Thanks for the help in advance!
> >
> > Regards
> > Ravi.
> >
Re: Delta source ended unexpectedly [500, #200003] using Subversion
1.6.17 with Apache http server 2.2.21
Posted by Ravi Roy <ra...@gmail.com>.
I found this under
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=193527
in the mail archive of dated back to 2002 and this seems to be fixed as per
the bug report.
Can somebody please comment on the issue?
Thanks.
On Sat, Feb 11, 2012 at 2:40 PM, Ravi Roy <ra...@gmail.com> wrote:
> Hello community,
>
> I have compiled subversion 1.6.17 and Apache 2.2.21 from source on CentOS
> 5.6 and serving my repository using Apache httpd server with the following
> details :
>
> Server version: Apache/2.2.21 (Unix)
> Server loaded: APR 1.4.5, APR-Util 1.3.12
> Compiled using: APR 1.4.5, APR-Util 1.3.12
>
> Getting the folloiwng normal message in apache log :
>
> [Sat Feb 11 14:13:41 2012] [notice] Apache/2.2.21 (Unix) DAV/2
> mod_ssl/2.2.21 OpenSSL/0.9.8e-fips-rhel5 SVN/1.6.17 PHP/5.1.6 configured --
> resuming normal operations
>
> Problem : When try to commit from the checkout made from master everything
> works fine, but when I try to commit from the checkout from slave I get the
> following message in apache's log :
>
> [Sat Feb 11 10:04:01 2012] [error] [client xxx.xxx.xx.xxx] could not write
> the file contents [500, #200003]
> [Sat Feb 11 10:04:01 2012] [error] [client xxx.xxx.xx.xxx] Delta source
> ended unexpectedly [500, #200003]
>
> I am using TortoiseSVN 1.6.16 to commit to repository.
>
> Does somebody knows if this is known bug or have somebody faced this issue
> earlier?
>
> Thanks for the help in advance!
>
> Regards
> Ravi.
>
Re: Delta source ended unexpectedly [500, #200003] using Subversion
1.6.17 with Apache http server 2.2.21
Posted by Nico Kadel-Garcia <nk...@gmail.com>.
On Sun, Feb 12, 2012 at 1:39 AM, Ravi Roy <ra...@gmail.com> wrote:
>
>
> On Sun, Feb 12, 2012 at 4:18 AM, Nico Kadel-Garcia <nk...@gmail.com> wrote:
>>
>> On Sat, Feb 11, 2012 at 4:10 AM, Ravi Roy <ra...@gmail.com> wrote:
>> > Hello community,
>> >
>> > I have compiled subversion 1.6.17 and Apache 2.2.21 from source on
>> > CentOS
>> > 5.6 and serving my repository using Apache httpd server with the
>> > following
>> > details :
>>
>> If you need the latest Subversion features, consider hopping directly
>> to the 1.7.1 or pending 1.7.2 release for RPMforge. My .spec files are
>> at https://github.com/nkadel/subversion-1.7.2-srpm: Enjoy.
>
>
> This is a decision which is not easy to take :-) Thanks.
>>
>>
>> Why are you using CentOS 5.x to support such a large update as Apache
>> 2.2.21? Wouldn't you be better off updateing to CentOS or Scientific
>> Linux 6.x and using httpd-2.2.15 ?
>
>
> Did not know about this (large update ..etc). I updated to httpd-2.2.15 but
> problems were not resolved.
> But when I downgraded to Subversion 1.6.12 alongwith httpd-2.2.15, problems
> are resolved.
>
> May be somebody needs to analyze as to why Subversion 1.6.17 have got these
> problems...
>
> Thanks everyone for help and support.
I'm glad you're up and running. Want me to dig into my otes and find
the .spec files for building 1.6.17 SRPM for RHEL 5.x? I hadn't
bothered posting it, since 1.7.x was out and seems to be a solid,
working release. I do encourage the update to 1.7.x to be consistent
with TortoiseSVN and CygWin, for Windows access to shared working
copies. It's also why I discourage the use of svn:eol. Nothing quite
like checking it out on Linux, having your text files svn:eol managed,
then editing and checking them in on TortoiseSVN and creating.....
adventures with EOL.
Re: Delta source ended unexpectedly [500, #200003] using Subversion
1.6.17 with Apache http server 2.2.21
Posted by Ravi Roy <ra...@gmail.com>.
On Sun, Feb 12, 2012 at 4:18 AM, Nico Kadel-Garcia <nk...@gmail.com> wrote:
> On Sat, Feb 11, 2012 at 4:10 AM, Ravi Roy <ra...@gmail.com> wrote:
> > Hello community,
> >
> > I have compiled subversion 1.6.17 and Apache 2.2.21 from source on CentOS
> > 5.6 and serving my repository using Apache httpd server with the
> following
> > details :
>
> If you need the latest Subversion features, consider hopping directly
> to the 1.7.1 or pending 1.7.2 release for RPMforge. My .spec files are
> at https://github.com/nkadel/subversion-1.7.2-srpm: Enjoy.
>
This is a decision which is not easy to take :-) Thanks.
>
> Why are you using CentOS 5.x to support such a large update as Apache
> 2.2.21? Wouldn't you be better off updateing to CentOS or Scientific
> Linux 6.x and using httpd-2.2.15 ?
>
Did not know about this (large update ..etc). I updated to httpd-2.2.15 but
problems were not resolved.
But when I downgraded to Subversion 1.6.12 alongwith httpd-2.2.15,
problems are resolved.
May be somebody needs to analyze as to why Subversion 1.6.17 have got these
problems...
Thanks everyone for help and support.