Archiva scanning, indexing and searching

[Wendy Smoak-3]

I am having the hardest time getting Archiva 1.2.2 to index and
display my artifacts.

To upgrade from 1.2-M1, I copied over my archiva.xml file and deleted
the .index directories in my existing, populated managed repos.  After
starting it and scanning/updating, I could get search results for
'struts' but not 'struts-core' (or 'struts AND core' as suggested on
irc.)

Then I realized that there is another directory (.indexer) in each
repo, so I stopped Archiva, deleted .index* which got both of them,
deleted the archiva database, and started it again.  After some time
and some manual "Scan Repository now" and database updates, I don't
even get any search results for 'struts' now.

What is the official way to start over, keeping repo contents, but not
any of Archiva's data?

--
Wendy

[Deng Ching-2]

Hi Wendy,

Deleting the .index and .indexer directories should be able to do the trick
when upgrading with an existing repo but with a clean database. I'll check
on my end if it's the same behavior for me.

Thanks,
Deng

On Thu, Sep 3, 2009 at 3:03 AM, Wendy Smoak <wsmoak@...> wrote:

> I am having the hardest time getting Archiva 1.2.2 to index and
> display my artifacts.
>
> To upgrade from 1.2-M1, I copied over my archiva.xml file and deleted
> the .index directories in my existing, populated managed repos.  After
> starting it and scanning/updating, I could get search results for
> 'struts' but not 'struts-core' (or 'struts AND core' as suggested on
> irc.)
>
> Then I realized that there is another directory (.indexer) in each
> repo, so I stopped Archiva, deleted .index* which got both of them,
> deleted the archiva database, and started it again.  After some time
> and some manual "Scan Repository now" and database updates, I don't
> even get any search results for 'struts' now.
>
> What is the official way to start over, keeping repo contents, but not
> any of Archiva's data?
>
> --
> Wendy
>

[Wendy Smoak-3]

On Wed, Sep 2, 2009 at 7:48 PM, Deng Ching<oching@...> wrote:
> Deleting the .index and .indexer directories should be able to do the trick
> when upgrading with an existing repo but with a clean database. I'll check
> on my end if it's the same behavior for me.

Thanks for confirming.  I've reset it again (deleting .index* dirs and
the database) and the search is not working correctly.  I get results
for 'test' or 'surefire' but not 'struts' (which I *know* is in the
internal repo, same as surefire.)

No struts artifacts are listed on the Repository Health report.
Search results (none) are the same whether I'm logged in as admin or
not.  (Guest has global repo observer, this shouldn't matter.)

Is there a way to turn up the logging so it will tell me exactly what
it's doing as it indexes and updates?

--
Wendy

[Deng Ching-2]

On Thu, Sep 3, 2009 at 11:23 PM, Wendy Smoak <wsmoak@...> wrote:

> On Wed, Sep 2, 2009 at 7:48 PM, Deng Ching<oching@...> wrote:
> > Deleting the .index and .indexer directories should be able to do the
> trick
> > when upgrading with an existing repo but with a clean database. I'll
> check
> > on my end if it's the same behavior for me.
>
> Thanks for confirming.  I've reset it again (deleting .index* dirs and
> the database) and the search is not working correctly.  I get results
> for 'test' or 'surefire' but not 'struts' (which I *know* is in the
> internal repo, same as surefire.)
>
> No struts artifacts are listed on the Repository Health report.
> Search results (none) are the same whether I'm logged in as admin or
> not.  (Guest has global repo observer, this shouldn't matter.)
>

Sorry I haven't had the chance to verify if I could reproduce this on my end
yet..


>
> Is there a way to turn up the logging so it will tell me exactly what
> it's doing as it indexes and updates?
>
>
I think you can change the log level for the consumers in log4j.xml:

 <logger name="org.apache.archiva.consumers">
    <level value="info"/>
  </logger>

Thanks,
Deng