Page 1 of 1
Sourceforge CVS
Posted: Fri Mar 31, 2006 5:32 pm
by mgroeninger
To head off anyone's concerns, I thought I would post this here.
Sourceforge developer CVS has been down for about nine hours (by my reckoning) and won't be up for a while longer. It seems that anonymous CVS is still working.
From
http://sourceforge.net/docman/display_d ... 1143722250( 2006-03-31 07:00:01 - Project CVS Service ) On 2006-03-30 the developer CVS server had a hardware issue that required us to take the service offline. We are actively working on this problem and hope to have it back up soon. There is not a current estimate for the duration of this outage, but when we get one, it will be posted on the site status page (this page). We currently expect this outage to last 48 hours, at minimum.
This means updates to (external) plugins will not be added to Spartacus until Sourceforge fixes their problems.
Re: Sourceforge CVS
Posted: Fri Mar 31, 2006 8:10 pm
by garvinhicking
Thanks for posting! I noticed that somewhen mid-day yesterday, so 24 offline hours are already past
)
Let's hope it soon gets fixed, I already have a lot of fixes pending.
Regards,
Garvin
An Update...
Posted: Mon Apr 03, 2006 4:14 pm
by mgroeninger
From the same page above:
( 2006-04-03 05:55:21 - Project CVS Service ) On 2006-03-30 the developer CVS server had a substantial system failure. Due to the implementation of the CVS service, there is a single point of failure with multiple points of recovery (there is more than one data source we could potentially recover from if there is any data loss as a result of the failure). This outage currently affects developer CVS access directly, but we have disabled tarball updates and data syncs from the developer CVS server to the anonymous pserver/ViewCVS hosts as an additional level of precaution. Our main focus since the outage was detected has been to safegaurd all data on the developer CVS server as well as possible. We are currently attempting to backup the data on the host, which is taking longer than we initially anticipated it would, but is a necessary step to fully safegaurd the host's data. Next, we are going to perform some data validation to ensure the data set appears valid. Pending successful completion of those steps, we'll reenable developer CVS access. A few days after, we'll reenable CVS tarballs and syncs to anonymous CVS. In the mean time, we're currently advancing plans for a CVS architecture change based upon the knowledge we gained during Subversion deployment to eliminate the single point of failure that developer CVS currently has, add horizontal scalability and overall service resiliance. However, we still do not have an estimate on when developer CVS services will be restored, but we have been, and currently are actively working to restore access to CVS. We appreciate your patience with us while we work to properly resolve this major outage.
So, they are running some test, then they will re-enable developer access, then "a few days later" they will re-enable the connection to anonymous CVS. So we may still see sync problems for the next week...