[ 
http://jira.codehaus.org/browse/MRM-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234046#action_234046
 ] 

Brett Porter commented on MRM-1418:
-----------------------------------

for the two sets of data you presented above, they correspond to different 
times and a significantly different duration. So either they are a different 
repository, or something deleted all the files in the intervening 6 hours. Does 
that period of time correspond to the scanning crons in either the database or 
repository tabs?

Changing the location may have had an effect - does it display correctly in the 
web interface as well as the log above?

You may get to the point where you need to refresh - make sure you have no 
~/.m2/archiva.xml, check that the application archiva.xml contains the config 
desired, delete the database, and restart forcing it to scan everything again.

As for your configuration question - the documentation is referring to the 
Repository Scanning page, where you are looking at the Database scanning page 
(which only has one consumer). You should make sure update-db-artifact is 
enabled in both.

> Archiva Repostories Index is dissapearing with no reason
> --------------------------------------------------------
>
>                 Key: MRM-1418
>                 URL: http://jira.codehaus.org/browse/MRM-1418
>             Project: Archiva
>          Issue Type: Bug
>          Components: repository scanning
>    Affects Versions: 1.3.1
>         Environment: Archiva 1.3.1
> Linux RedHat
> Apache maven 2.0.9
> Continuum 1.3.6
>            Reporter: Mario Parra
>
> After I migrated from Archiva 1.2.2 to Archiva 1.3.1 the repositories that 
> already existed on my previous installation of Archiva are dissapearing from 
> the Archiva browser index.
> Everyday I need to do a re-scan of the repositories to have the repositories 
> and artifacts listed again.
> I have looked at the logs at the same time the repositories are been erased 
> from the index but there is no output there.
> I have also tried to identify if there is a cronjob or something that causes 
> this behavior but haven't find anything and also the time when this happens 
> is random.
> Please Help.
> Thanks

-- 
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

        

Reply via email to