[Dev] Network down to component registry?

Twan Goosen twan.goosen at mpi.nl
Thu Sep 26 12:30:51 CEST 2013


On 9/26/13 10:46 , Twan Goosen wrote:
> On 9/26/13 10:28 , Twan Goosen wrote:
>> On 9/25/13 12:35 , Dieter Van Uytvanck wrote:
>>> On 24/9/13 17:20 , Dieter Van Uytvanck wrote:
>>>> And another update. We have restored the virtual machine but it is not
>>>> yet reachable from outside our network. Tomorrow morning this will
>>>> hopefully be resolved.
>>>
>>> Finally, the CLARIN IdP is working again. user.clarin.eu and
>>> infra.clarineu are also back.
>>>
>>> Now we are looking into svn+trac

Dear all,

TRAC and SVN are back up again and appear to be functioning fine. We are 
monitoring their status, but you should be able to use them in the 
meantime.

Generally you should be able to pick where you left except for the 
probably exceptional case you did commits on the morning of Monday 23 
September. Those commits have not been recovered (the last backup was 
made at 3am). If you area getting errors on commit (most likely checksum 
mismatches), please follow the instructions at the end of this e-mail.

As you can see at <http://www.clarin.eu/node/3853>, currently only the 
IdP is experiencing some issues but is up and working in principle. Tne 
worst should be over now, thanks for your patience!

Best,
Twan

===================================================================
INSTRUCTIONS FOR FIXING BROKEN WORKING COPIES AS A RESULT OF SERVER ISSUES:

1. Make a backup copy of your working copy!
2. Export the affected part of the working copy to a separate location 
(using svn export, see 
<http://svnbook.red-bean.com/en/1.7/svn.ref.svn.c.export.html>, simply 
copying will not do!)
3. Obtain a clean working copy or at least remove then update the 
affected part of your working copy
4. Update your working copy to the head revision
5. Copy the contents of your exported version of the working copy (made 
in step 2) to the corresponding part of your new working copy, 
overwriting only the conflicting files between the two
6. Carefully check the state of your working copy (svn stat), then 
commit your working copy

Again, these steps will only be required in the exceptional case that 
you have committed anything to svn.clarin.eu between Monday 23 september 
between 3am and 11am today. If you have questions about this, please 
don't hesitate to contact me directly!
===================================================================



-- 
Twan Goosen
Max Planck Institute for Psycholinguistics

twan.goosen at mpi.nl

P.O. Box 310
6500 AH Nijmegen
The Netherlands


More information about the Dev mailing list