maven-repo-maintainers mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juven Xu <ju...@sonatype.com>
Subject Re: [Maven Central Repository Synchronization] FAILURE
Date Fri, 24 Sep 2010 12:09:55 GMT
it's fixed on maven central

On Fri, Sep 24, 2010 at 7:38 AM, Peter de Zwart <pdzwart@atlassian.com>wrote:

> The host for maven.atlassian.com has changed from 63.246.22.61 to
> 63.246.22.203.
>
> Begin forwarded message:
>
> > From: "maven@repo1.maven.org" <maven@repo1.maven.org>
> > Date: 24 September 2010 9:28:24 AM AEST
> > To: "repo-maintainers@maven.apache.org" <
> repo-maintainers@maven.apache.org>, Admin Team <admin-team@atlassian.com>,
> Admin Team <admin-team@atlassian.com>, Jonas Abreu <jonas@vidageek.net>,
> Simone Gianni <simoneg@apache.org>
> > Subject: [Maven Central Repository Synchronization] FAILURE
> > message-id: <
> 20111677.01285284504501.JavaMail.maven@sonatype03.managed.contegix.com>
> >
> > --- Some repositories were not synchronized ---
> > groupId: com.atlassian
> > Error:
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > The RSA host key for maven.atlassian.com has changed,
> > and the key for the according IP address 63.246.22.203
> > is unknown. This could either mean that
> > DNS SPOOFING is happening or the IP address for the host
> > and its host key have changed at the same time.
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> > Someone could be eavesdropping on you right now (man-in-the-middle
> attack)!
> > It is also possible that the RSA host key has just been changed.
> > The fingerprint for the RSA key sent by the remote host is
> > 6f:05:fb:25:79:b2:34:43:b1:87:f2:43:b5:23:d4:60.
> > Please contact your system administrator.
> > Add correct host key in /home/maven/.ssh/known_hosts to get rid of this
> message.
> > Offending key in /home/maven/.ssh/known_hosts:137
> > RSA host key for maven.atlassian.com has changed and you have requested
> strict checking.
> > Host key verification failed.
> > rsync: connection unexpectedly closed (0 bytes received so far)
> [receiver]
> > rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> > Error synchronizing metadata. Exit code: 255
> > Command line executed: /bin/sh -c 'rsync --include=*/
> --include=**/maven-metadata.xml* --exclude=*
> --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz
> "--rsh=ssh " maven@maven.atlassian.com:/home/maven/incoming//com/atlassian/
> /home/maven/repository-staging/to-ibiblio/maven2/com/atlassian/'
> >
> > groupId: com.cenqua
> > Error:
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > The RSA host key for maven.atlassian.com has changed,
> > and the key for the according IP address 63.246.22.203
> > is unknown. This could either mean that
> > DNS SPOOFING is happening or the IP address for the host
> > and its host key have changed at the same time.
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> > Someone could be eavesdropping on you right now (man-in-the-middle
> attack)!
> > It is also possible that the RSA host key has just been changed.
> > The fingerprint for the RSA key sent by the remote host is
> > 6f:05:fb:25:79:b2:34:43:b1:87:f2:43:b5:23:d4:60.
> > Please contact your system administrator.
> > Add correct host key in /home/maven/.ssh/known_hosts to get rid of this
> message.
> > Offending key in /home/maven/.ssh/known_hosts:137
> > RSA host key for maven.atlassian.com has changed and you have requested
> strict checking.
> > Host key verification failed.
> > rsync: connection unexpectedly closed (0 bytes received so far)
> [receiver]
> > rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> > Error synchronizing metadata. Exit code: 255
> > Command line executed: /bin/sh -c 'rsync --include=*/
> --include=**/maven-metadata.xml* --exclude=*
> --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz
> "--rsh=ssh " maven@maven.atlassian.com:/home/maven/incoming//com/cenqua/
> /home/maven/repository-staging/to-ibiblio/maven2/com/cenqua/'
> >
> > groupId: net.vidageek
> > Error:
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > The RSA host key for vidageek.net has changed,
> > and the key for the according IP address 173.236.132.30
> > is unknown. This could either mean that
> > DNS SPOOFING is happening or the IP address for the host
> > and its host key have changed at the same time.
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> > Someone could be eavesdropping on you right now (man-in-the-middle
> attack)!
> > It is also possible that the RSA host key has just been changed.
> > The fingerprint for the RSA key sent by the remote host is
> > 0e:c2:f6:f4:d9:86:9d:4b:c4:3d:77:e7:a4:bb:59:14.
> > Please contact your system administrator.
> > Add correct host key in /home/maven/.ssh/known_hosts to get rid of this
> message.
> > Offending key in /home/maven/.ssh/known_hosts:67
> > RSA host key for vidageek.net has changed and you have requested strict
> checking.
> > Host key verification failed.
> > rsync: connection unexpectedly closed (0 bytes received so far)
> [receiver]
> > rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> > Error synchronizing metadata. Exit code: 255
> > Command line executed: /bin/sh -c 'rsync --include=*/
> --include=**/maven-metadata.xml* --exclude=*
> --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz
> "--rsh=ssh " maven_sync@vidageek.net:/home/maven_sync/
> maven.vidageek.net//net/vidageek//home/maven/repository-staging/to-ibiblio/maven2/net/vidageek/'
> >
> > groupId: org.aspectj
> > Error:
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
> > Someone could be eavesdropping on you right now (man-in-the-middle
> attack)!
> > It is also possible that the RSA host key has just been changed.
> > The fingerprint for the RSA key sent by the remote host is
> > 86:ae:3b:0f:98:c2:3e:50:c8:0c:50:0b:f0:6f:11:27.
> > Please contact your system administrator.
> > Add correct host key in /home/maven/.ssh/known_hosts to get rid of this
> message.
> > Offending key in /home/maven/.ssh/known_hosts:86
> > RSA host key for simonegianni.it has changed and you have requested
> strict checking.
> > Host key verification failed.
> > rsync: connection unexpectedly closed (0 bytes received so far)
> [receiver]
> > rsync error: unexplained error (code 255) at io.c(635) [receiver=3.0.3]
> > Error synchronizing metadata. Exit code: 255
> > Command line executed: /bin/sh -c 'rsync --include=*/
> --include=**/maven-metadata.xml* --exclude=*
> --exclude-from=/home/maven/bin/synchronize/syncopate/exclusions.txt -Lrtivz
> "--rsh=ssh " rsync@simonegianni.it:/home/mavenrsync/repo/org/aspectj/
> /home/maven/repository-staging/to-ibiblio/maven2/org/aspectj/'
> >
> > This is an automated email, do not respond.Contact the owners at
> repo-maintainers@maven.apache.org
>
>


-- 
- juven

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message