You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joerg Schaible (JIRA)" <ji...@codehaus.org> on 2009/10/31 15:31:55 UTC

[jira] Commented: (MAVENUPLOAD-1774) Sync de.berlios.jsunit

    [ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196761#action_196761 ] 

Joerg Schaible commented on MAVENUPLOAD-1774:
---------------------------------------------

The sync is broken since 19th October. There have been some outages in the last two years, but normally only for 2 or 3 days. Currently any rsync operation for the mavensync user results in:

{noformat}
[maven@sonatype03 ~]$ rsync --exclude-from=/home/maven/bin/synchronize/syncopat
e/exclusions.txt --ignore-existing -Lrtivz "--rsh=ssh" mavensync@shell.berlios.
de:/home/groups/jsunit/htdocs/maven2/repo ./berlios
Connection closed by 195.37.77.140
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
{noformat}

and even the direct shell access is broken:

{noformat}
[maven@sonatype03 ~]$ ssh mavensync@shell.berlios.de
Connection closed by 195.37.77.140
[maven@sonatype03 ~]$
{noformat}

However, from my machine I can login with my personal account without problems as well as rsyncing the repo. BerliOS is running rsync version 3.0.6 protocol version 30 and OpenSSH_4.1p1, OpenSSL 0.9.7g 11 Apr 2005.

> Sync de.berlios.jsunit
> ----------------------
>
>                 Key: MAVENUPLOAD-1774
>                 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1774
>             Project: Maven Upload Requests
>          Issue Type: Task
>            Reporter: Joerg Schaible
>            Assignee: Carlos Sanchez
>
> Please sync with de.berlios.jsunit, a JavaScript unit test library with Maven 2 plugin and Ant task. Licensed with ASL 2.0.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira