Return-Path: Delivered-To: apmail-archiva-users-archive@www.apache.org Received: (qmail 11279 invoked from network); 25 Jun 2009 04:54:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jun 2009 04:54:23 -0000 Received: (qmail 12359 invoked by uid 500); 25 Jun 2009 04:54:33 -0000 Delivered-To: apmail-archiva-users-archive@archiva.apache.org Received: (qmail 12283 invoked by uid 500); 25 Jun 2009 04:54:33 -0000 Mailing-List: contact users-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@archiva.apache.org Delivered-To: mailing list users@archiva.apache.org Received: (qmail 12272 invoked by uid 99); 25 Jun 2009 04:54:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2009 04:54:33 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.246.22.40] (HELO mail.atlassian.com) (63.246.22.40) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jun 2009 04:54:23 +0000 Received: from heck.sydney.atlassian.com (ATL146140-1.gw.connect.com.au [203.63.130.33]) by mail.atlassian.com (Postfix) with ESMTP id 52C1E163046F for ; Wed, 24 Jun 2009 23:54:01 -0500 (CDT) Message-ID: <4A4302E6.20208@atlassian.com> Date: Thu, 25 Jun 2009 14:53:58 +1000 From: James William Dumay User-Agent: Postbox 1.0b12 (Macintosh/2009051120) MIME-Version: 1.0 To: users@archiva.apache.org Subject: Re: Archiva 1.2.1 - repos won't get index References: <23854158.post@talk.nabble.com> <23854203.post@talk.nabble.com> <8667b1bd0906031750x1fe29e58i278fbdadebf2a5f@mail.gmail.com> <23866718.post@talk.nabble.com> In-Reply-To: <23866718.post@talk.nabble.com> Content-Type: multipart/alternative; boundary="------------070402030603070307060505" X-Virus-Checked: Checked by ClamAV on apache.org --------------070402030603070307060505 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I have the same problem with our installation. We followed the upgrade notes and the search index never gets populated. James Marc Lustig wrote: > Indeed, > find [REPOSITORY_DIRECTORY_NAME] | xargs touch > is tremendously faster than > find [REPOSITORY_DIRECTORY_NAME] -exec touch {} \; > > > > > Deng Ching-2 wrote: > >> Hi Marc, >> >> Did you touch the contents of the repository? The last modified date of >> the >> artifacts need to be more recent than the last run of the repository scan. >> You can execute *find [REPOSITORY_DIRECTORY_NAME] | xargs touch *at the >> base >> dir where your repo is located. >> >> Thanks, >> Deng >> >> On Wed, Jun 3, 2009 at 11:54 PM, Marc Lustig wrote: >> >> >>> I forgot to add an excerpt from the log: >>> >>> 2009-06-03 17:42:11,554 [pool-2-thread-1] INFO >>> >>> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor >>> - Finished repository task: >>> .\ Scan of internal \.__________________________________________ >>> Repository Dir : /opt/managed_repos/internal >>> Repository Name : .... >>> Repository Layout : default >>> Known Consumers : (7 configured) >>> auto-rename >>> metadata-updater >>> repository-purge >>> auto-remove >>> update-db-artifact >>> create-missing-checksums >>> index-content >>> Invalid Consumers : >>> Duration : 1 Minute 13 Seconds 689 Milliseconds >>> When Gathered : 6/3/09 5:42 PM >>> Total File Count : 107263 >>> Avg Time Per File : >>> ______________________________________________________________ >>> 2009-06-03 17:42:55,317 [pool-1-thread-1] INFO >>> >>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor >>> - Executing task from queue with job name: database-job:user-requested >>> 2009-06-03 17:42:55,319 [pool-1-thread-1] INFO >>> >>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor >>> - Task: Updating unprocessed artifacts >>> 2009-06-03 17:42:55,318 [http-8080-6] INFO >>> org.apache.maven.archiva.web.action.admin.SchedulerAction - >>> [ActionMessage] >>> Your request to update the database has been queued. >>> 2009-06-03 17:42:55,591 [pool-1-thread-1] INFO >>> >>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor >>> - Task: Updating processed artifacts >>> 2009-06-03 17:44:20,355 [pool-1-thread-1] INFO >>> >>> org.apache.maven.archiva.scheduled.executors.ArchivaDatabaseUpdateTaskExecutor >>> - Finished database task in 85035ms. >>> >>> >>> >>> Marc Lustig wrote: >>> >>>> We upgraded our test-server to release 1.2.1, removed .index and >>>> >>> .indexer >>> >>>> from all the repos, ran the Scan for the repos and then the Update >>>> Database. >>>> >>>> As a result, before the upgrade we had 500 MB inside in all of the >>>> >>> .index >>> >>>> directories. >>>> After the upgrade and the repo-scan, the total size is less than 1 MB. >>>> Apparently the repo indexing-process does not work anymore. The >>>> Search-function does not give any results. >>>> >>>> Any idea how to make the repos to get indexed again? >>>> >>>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Archiva-1.2.1---repos-won%27t-get-index-tp23854158p23854203.html >>> Sent from the archiva-users mailing list archive at Nabble.com. >>> >>> >>> >> > > --------------070402030603070307060505--