SVN problem

[Brad <br...@javawork.co.uk>]

Hi,

is anyone else getting problems from ths SVN server? I've been getting
intermittent PROPFIND errors. I tried looking up /repos/asf/cxf/trunk
just now and got unable to connect (curl reported moved permanantly).
Its back now but I am curious.

Brad.

Re: SVN problem

[Brad <br...@javawork.co.uk>]

Ok just wanted to check as we have a quite restrictive firewall here
that has been known to allow things through partially.

Thanks for the info.

On Wed, Apr 30, 2008 at 2:12 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> On Wednesday 30 April 2008, Brad wrote:
>  > is anyone else getting problems from ths SVN server? I've been getting
>  > intermittent PROPFIND errors. I tried looking up /repos/asf/cxf/trunk
>  > just now and got unable to connect (curl reported moved permanantly).
>  > Its back now but I am curious.
>  >
>  > Brad.
>
>  The apache SVN server crashed hard twice in the last 5 days or so with
>  the RAID array having issues.  Thus, you may have hit some of the
>  reboots.   The decision was made monday to put SVN into "read only" mode
>  while they put all new hardware in place and migrated it over to the new
>  server.  That process finished last night and now it's running
>  completely on the new hardware.   However, that's a new IP address so
>  you may also have DNS updates that need to cycle in.
>
>  The new box apparently kernel panicked this morning.  Thus, there was a
>  reboot there.   They are still investigating.
>
>
>  --
>  J. Daniel Kulp
>  Principal Engineer, IONA
>  dkulp@apache.org
>  http://www.dankulp.com/blog
>

Re: SVN problem

[Daniel Kulp <dk...@apache.org>]

On Wednesday 30 April 2008, Brad wrote:
> is anyone else getting problems from ths SVN server? I've been getting
> intermittent PROPFIND errors. I tried looking up /repos/asf/cxf/trunk
> just now and got unable to connect (curl reported moved permanantly).
> Its back now but I am curious.
>
> Brad.

The apache SVN server crashed hard twice in the last 5 days or so with 
the RAID array having issues.  Thus, you may have hit some of the 
reboots.   The decision was made monday to put SVN into "read only" mode 
while they put all new hardware in place and migrated it over to the new 
server.  That process finished last night and now it's running 
completely on the new hardware.   However, that's a new IP address so 
you may also have DNS updates that need to cycle in.

The new box apparently kernel panicked this morning.  Thus, there was a 
reboot there.   They are still investigating.


-- 
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog