rsync -Lrtivzn -e "ssh -v" [EMAIL PROTECTED]:/var/maven/release/ /home/maven/repository-staging/to-ibiblio/maven2/ OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to maven.dspace.org [18.51.1.167] port 22. debug1: Connection established. debug1: identity file /home/maven/.ssh/identity type 0 debug1: identity file /home/maven/.ssh/id_rsa type -1 debug1: identity file /home/maven/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.0 debug1: match: OpenSSH_5.0 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.9p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'maven.dspace.org' is known and matches the RSA host key. debug1: Found key in /home/maven/.ssh/known_hosts:23 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering public key: carlos debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Offering public key: amazonws-exist debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Trying private key: /home/maven/.ssh/id_rsa debug1: Offering public key: /home/maven/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 434 debug1: read PEM private key done: type DSA Connection closed by 18.51.1.167 rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: unexplained error (code 255) at io.c(453) [receiver=2.6.9]
On Sun, Jun 8, 2008 at 7:10 PM, Mark Diggory <[EMAIL PROTECTED]> wrote: > Looking into why this is failing for maven.dspace.org. Is there any detail > on the failure on client end? Perhaps an authentication failure or > something. > > thanks, > Mark > > On Jun 8, 2008, at 6:47 PM, [EMAIL PROTECTED] wrote: > >> --- Some repositories were not synchronized --- >> groupId: org.compass-project >> Error: >> rsync: failed to connect to repo.compass-project.org: Connection timed out >> (110) >> rsync error: error in socket IO (code 10) at clientserver.c(104) >> [receiver=2.6.9] >> Error synchronizing metadata. Exit code: 10 >> >> groupId: org.dspace >> Error: >> Connection closed by 18.51.1.167 >> rsync: connection unexpectedly closed (0 bytes received so far) [receiver] >> rsync error: unexplained error (code 255) at io.c(453) [receiver=2.6.9] >> Error synchronizing metadata. Exit code: 255 >> >> This is an automated email, do not respond.Contact the owners at >> [email protected] > > > > ~~~~~~~~~~~~~ > Mark R. Diggory - DSpace Developer and Systems Manager > MIT Libraries, Systems and Technology Services > Massachusetts Institute of Technology > Home Page: http://purl.org/net/mdiggory/homepage > > > > > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
