Artifacts not being indexed

2008-02-15 Thread Brown, Carlton
Hi,

I've got a problem where an artifact downloaded to the filesystem cannot
be browsed.  There's some problem with either the database scanning or
repository indexing.   The maven metadata files are not being generated.
The pom file appears to be good.

How can I troubleshoot this problem and determine whether it's the
database failing to pick it up, or archiva failing to index it, or
something else?  Would there be errors written to a log somewhere?  I've
checked archiva.log which shows nothing except the requests for the
scanning and indexing tasks.

This is a frequent problem I've been having, it would be good if there
were some good diagnostics for indexing problems.

-Carlton

-

This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the 
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on 
the contents of this message is prohibited. In such
case please notify us and destroy and delete all 
copies of this transmission.  Thank you.



RE: Artifacts not being indexed

2008-02-15 Thread Brown, Carlton
 -Original Message-
 From: Wendy Smoak [mailto:[EMAIL PROTECTED]
 Sent: Friday, February 15, 2008 1:17 PM
 To: archiva-users@maven.apache.org
 Subject: Re: Artifacts not being indexed
 
 On Fri, Feb 15, 2008 at 11:06 AM, Brown, Carlton
 [EMAIL PROTECTED] wrote:
 
   I've got a problem where an artifact downloaded to the filesystem
 cannot
   be browsed.  There's some problem with either the database scanning
or
   repository indexing.   The maven metadata files are not being
 generated.
   The pom file appears to be good.
 
 By downloaded, do you mean you are using Archiva as a proxy?  Or do
 you have an external process that is writing to the filesystem?

External process writing to the filesystem.

 The first thing I'd track down is why there is no metadata file.
 
 There is a checkbox in the Archiva config that will make it create
 missing metadata files.  Try checking that box and then clicking
 'scan' and then 'update database'.  Does it now show up in browse?

It does not.  That checkbox appears to be enabled by default, and I have
been doing 'scan' and 'update database', so no luck there.  Strangely,
when this happens, the artifacts show up in a search, but you can't
browse to them.  I mean they don't show up under the /archiva/browse
URL, you can use the /repository URL and see them there just fine.
 
 (I've seen it create missing metadata files.  I'm less sure about its
 ability to repair broken ones.)

It does create missing metadata files, but the process seems to be very
hit-or-miss, and shows almost nothing in the way of useful feedback or
diagnostics.  

Is there some other, more decisive manual way to force it to re-scan the
entire filesystem and recreate the metadata files?

-

This message contains PRIVILEGED and CONFIDENTIAL
information that is intended only for use by the 
named recipient. If you are not the named recipient,
any disclosure, dissemination, or action based on 
the contents of this message is prohibited. In such
case please notify us and destroy and delete all 
copies of this transmission.  Thank you.



Re: Artifacts not being indexed

2008-02-15 Thread Wendy Smoak
On Fri, Feb 15, 2008 at 11:31 AM, Brown, Carlton
[EMAIL PROTECTED] wrote:

  Is there some other, more decisive manual way to force it to re-scan the
  entire filesystem and recreate the metadata files?

Sure.  Stop Archiva, and delete both the Lucene index files and the
Archiva database.

Look for a .index directory at the top of your repository.  Delete the
whole directory, not just the contents.  Likewise, delete the whole
directory for the Derby database, which is usually in
data/archiva/database.

Re-start, and then scan and update (in that order.)

When you say they can't be browsed, are you seeing an error message?

I've had problems when I'm missing a parent pom in the repository.  It
will say it can't find the object model or some such thing.

What version of Archiva are you using?  Is it standalone (Plexus
Appserver) or are you using the war file in Tomcat/Jetty/etc.?

-- 
Wendy