You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Greg Dickie <gr...@max-t.com> on 2006/03/21 13:39:56 UTC
Upgrade to CentOS 4.3 breaks subversion
Hi,
I've just updated a build machine to CentOS 4.3 and suddenly
subversion is busted. Has anyone else seen this in RHEL 4.3? Subversion
itself was not updated but apr was. I tried reverting it and it did not
help. I realize this is not strictly a subversion problem but if anyone
could give me a hint as to how to find the problematic RPM it would be
most appreciated.
The error I now get is:
[greg@edinburgh lvm2]$ svn up
svn: REPORT request failed on '/packages/!svn/vcc/default'
svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
(http://svn)
Any ideas?
Thanks,
Greg
--
Greg Dickie
just a guy
Maximum Throughput
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Nick Thompson <ni...@agere.com>.
NFS locks borked? I'm pretty sure FSFS requires working locks.
On Wednesday 22 March 2006 16:50, Greg Dickie wrote:
> Responding to my own post again... It seems to be the kernel.
> Reverting from 2.6.9-34.EL back to 2.6.9-22.0.2.EL seems to fix the
> problem.
>
> Just in case anyone hits this....
>
> Greg
>
> On Tue, 2006-03-21 at 08:39 -0500, Greg Dickie wrote:
> > Hi,
> >
> > I've just updated a build machine to CentOS 4.3 and suddenly
> > subversion is busted. Has anyone else seen this in RHEL 4.3?
> > Subversion itself was not updated but apr was. I tried reverting
> > it and it did not help. I realize this is not strictly a
> > subversion problem but if anyone could give me a hint as to how
> > to find the problematic RPM it would be most appreciated.
> >
> > The error I now get is:
> >
> > [greg@edinburgh lvm2]$ svn up
> > svn: REPORT request failed on '/packages/!svn/vcc/default'
> > svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
> > (http://svn)
> >
> >
> >
> > Any ideas?
> > Thanks,
> > Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Greg Dickie <gr...@max-t.com>.
Responding to my own post again... It seems to be the kernel. Reverting
from 2.6.9-34.EL back to 2.6.9-22.0.2.EL seems to fix the problem.
Just in case anyone hits this....
Greg
On Tue, 2006-03-21 at 08:39 -0500, Greg Dickie wrote:
> Hi,
>
> I've just updated a build machine to CentOS 4.3 and suddenly
> subversion is busted. Has anyone else seen this in RHEL 4.3? Subversion
> itself was not updated but apr was. I tried reverting it and it did not
> help. I realize this is not strictly a subversion problem but if anyone
> could give me a hint as to how to find the problematic RPM it would be
> most appreciated.
>
> The error I now get is:
>
> [greg@edinburgh lvm2]$ svn up
> svn: REPORT request failed on '/packages/!svn/vcc/default'
> svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
> (http://svn)
>
>
>
> Any ideas?
> Thanks,
> Greg
>
>
--
Greg Dickie
just a guy
Maximum Throughput
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Greg Dickie <gr...@max-t.com>.
Indeed we did test that and it seems the problem does occur when using
our 2.4.21-ish NFS server but not when using another CentOS4.3 NFS
server.
Thanks for the reply,
Greg
On Wed, 2006-03-22 at 22:00 -0500, Nico Kadel-Garcia wrote:
> Greg Dickie wrote:
> > Hi,
> >
> > The repository is FSFS and its been working fine for over a year. Its
> > just now that I've upgraded some workstations to 4.3 that Working
> > Copies on NFS are throwing this error.
> >
> > Thanks for the reply,
> > Greg
>
> I've recently updated a server to CentOS 4.3, and Windows and CentOS 4.3
> clients have no problem with HTTPS access to the BDB based repositories on
> the 4.3 box.
>
--
Greg Dickie
just a guy
Maximum Throughput
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Greg Dickie wrote:
> Hi,
>
> The repository is FSFS and its been working fine for over a year. Its
> just now that I've upgraded some workstations to 4.3 that Working
> Copies on NFS are throwing this error.
>
> Thanks for the reply,
> Greg
I've recently updated a server to CentOS 4.3, and Windows and CentOS 4.3
clients have no problem with HTTPS access to the BDB based repositories on
the 4.3 box.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Greg Dickie <gr...@max-t.com>.
Hi,
The repository is FSFS and its been working fine for over a year. Its
just now that I've upgraded some workstations to 4.3 that Working Copies
on NFS are throwing this error.
Thanks for the reply,
Greg
On Wed, 2006-03-22 at 17:00 +0100, Ryan Schmidt wrote:
> On Mar 22, 2006, at 15:49, Greg Dickie wrote:
>
> >> I've just updated a build machine to CentOS 4.3 and suddenly
> >> subversion is busted. Has anyone else seen this in RHEL 4.3?
> >> Subversion
> >> itself was not updated but apr was. I tried reverting it and it
> >> did not
> >> help. I realize this is not strictly a subversion problem but if
> >> anyone
> >> could give me a hint as to how to find the problematic RPM it
> >> would be
> >> most appreciated.
> >>
> >> The error I now get is:
> >>
> >> [greg@edinburgh lvm2]$ svn up
> >> svn: REPORT request failed on '/packages/!svn/vcc/default'
> >> svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
> >> (http://svn)
> >
> > Bad form replying to my own posting but since no one seems to have
> > seen
> > this, here is some more information.
> >
> > If the WC is on an NFS mount is you get the error. If its local, it
> > works fine. Building the srpm fails a bunch of tests on the 4.3
> > machine
> > as well. Didn't try building it on a local disk. Can anyone see why
> > NFS
> > would be a problem? Any way to debug this further?
>
> You did not specify whether you're using a BDB repository or an FSFS
> one. BDB repositories are known to blow up when placed on NFS
> volumes. FSFS repositories should work fine there.
>
>
--
Greg Dickie
just a guy
Maximum Throughput
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Mar 22, 2006, at 15:49, Greg Dickie wrote:
>> I've just updated a build machine to CentOS 4.3 and suddenly
>> subversion is busted. Has anyone else seen this in RHEL 4.3?
>> Subversion
>> itself was not updated but apr was. I tried reverting it and it
>> did not
>> help. I realize this is not strictly a subversion problem but if
>> anyone
>> could give me a hint as to how to find the problematic RPM it
>> would be
>> most appreciated.
>>
>> The error I now get is:
>>
>> [greg@edinburgh lvm2]$ svn up
>> svn: REPORT request failed on '/packages/!svn/vcc/default'
>> svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
>> (http://svn)
>
> Bad form replying to my own posting but since no one seems to have
> seen
> this, here is some more information.
>
> If the WC is on an NFS mount is you get the error. If its local, it
> works fine. Building the srpm fails a bunch of tests on the 4.3
> machine
> as well. Didn't try building it on a local disk. Can anyone see why
> NFS
> would be a problem? Any way to debug this further?
You did not specify whether you're using a BDB repository or an FSFS
one. BDB repositories are known to blow up when placed on NFS
volumes. FSFS repositories should work fine there.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Upgrade to CentOS 4.3 breaks subversion
Posted by Greg Dickie <gr...@max-t.com>.
Bad form replying to my own posting but since no one seems to have seen
this, here is some more information.
If the WC is on an NFS mount is you get the error. If its local, it
works fine. Building the srpm fails a bunch of tests on the 4.3 machine
as well. Didn't try building it on a local disk. Can anyone see why NFS
would be a problem? Any way to debug this further?
Thanks,
Greg
On Tue, 2006-03-21 at 08:39 -0500, Greg Dickie wrote:
> Hi,
>
> I've just updated a build machine to CentOS 4.3 and suddenly
> subversion is busted. Has anyone else seen this in RHEL 4.3? Subversion
> itself was not updated but apr was. I tried reverting it and it did not
> help. I realize this is not strictly a subversion problem but if anyone
> could give me a hint as to how to find the problematic RPM it would be
> most appreciated.
>
> The error I now get is:
>
> [greg@edinburgh lvm2]$ svn up
> svn: REPORT request failed on '/packages/!svn/vcc/default'
> svn: REPORT of '/packages/!svn/vcc/default': 400 Bad Request
> (http://svn)
>
>
>
> Any ideas?
> Thanks,
> Greg
>
>
--
Greg Dickie
just a guy
Maximum Throughput
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org