www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darryl L. Miles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8448) Apache Release JAR repo appears to not have all current artifacts in it
Date Fri, 17 Oct 2014 05:03:33 GMT

    [ https://issues.apache.org/jira/browse/INFRA-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174724#comment-14174724
] 

Darryl L. Miles commented on INFRA-8448:
----------------------------------------

First what is the cause of the data being so stale ?  Nexus does not update and no errors
in the log?  Some file system permission issue ?  Some publishing issue between source nexus
server and the content the public sees ?

Does the URL (and data at it) the public hits come directly off the Nexus instance (i.e. no
CDN or reverse-HTTP-proxy ahead of the data) ?  
Is the data the public sees exactly the same data available in the Nexus instance (needs shell
access) ?

Yes there is a rebuild index function, this should fix the problem, this is in the scheduled
task area of the Nexus admin panel.
Once it has completed take a look at the actual files and confirm they have changed and been
updated.
Now wait for a user (with write privilege) to publish some new data and then go back and check
the index got updated and a new incremental number exists.

It is my understanding that Nexus should continuously and automatically update the index and
there is no way to turn it off.  But really contact your Nexus support contract over the matter.

> Apache Release JAR repo appears to not have all current artifacts in it
> -----------------------------------------------------------------------
>
>                 Key: INFRA-8448
>                 URL: https://issues.apache.org/jira/browse/INFRA-8448
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Nexus
>            Reporter: Darryl L. Miles
>         Attachments: screenshot-1.png
>
>
> For example the project commons-logging:commons-logging:1.2 is not listed but it was
published in 05-Jul-2014.
> The index timestamp incremental version is 46
> The index timestamp is 20140509170106.295 +0000
> Note the timestamp looks really old!
> This data is available from sonatype-work/nexus/indexer/apache-release-ctx/nexus-maven-repository-index-updater.properties
from a satalite Nexus repo points to your Nexus repo.
> This index only has commons-logging:commons-logging:1.1.3 listed as the most recent version
available.
> Please ensure your nexus repo is running a new index every day, the system has not errors
in logs when doing it and nexus process has write permissions to store the index data.
> You might need to enable a scheduled task to update local indexes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message