Return-Path: Delivered-To: apmail-archiva-users-archive@www.apache.org Received: (qmail 71337 invoked from network); 7 Apr 2009 11:42:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Apr 2009 11:42:04 -0000 Received: (qmail 2237 invoked by uid 500); 7 Apr 2009 11:42:03 -0000 Delivered-To: apmail-archiva-users-archive@archiva.apache.org Received: (qmail 2126 invoked by uid 500); 7 Apr 2009 11:42:03 -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 2116 invoked by uid 99); 7 Apr 2009 11:42:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Apr 2009 11:42:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Apr 2009 11:41:55 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Lr9gK-0003Z6-Ff for users@archiva.apache.org; Tue, 07 Apr 2009 04:41:32 -0700 Message-ID: <22927284.post@talk.nabble.com> Date: Tue, 7 Apr 2009 04:41:32 -0700 (PDT) From: Marc Lustig To: users@archiva.apache.org Subject: Re: consumer to auto-remove artifact from DB In-Reply-To: <8667b1bd0904070355l3a104603p41ae5047cce3465d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: ml@marclustig.com References: <22925611.post@talk.nabble.com> <8667b1bd0904070342n70e2535cr467b146b5dd3b50c@mail.gmail.com> <22926610.post@talk.nabble.com> <8667b1bd0904070355l3a104603p41ae5047cce3465d@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org yes, of course, thanks! However, on that page, all consumers are enabled: -not-present-remove-indexed -not-present-remove-db-artifact -not-present-remove-db-project Any idea why the entries are not removed from the database? In the log, I can see entries for the ArchivaRepositoryScanningTaskExecutor, resulting in a detailed statistics overview. However I cannot see any statistics for the ArchivaDatabaseUpdateTaskExecutor. Could it be that for some reason the ArchivaDatabaseUpdateTaskExecutor is triggered, but not executed? The cron definition is "0 0 * * * ?" (default) Maria Odea Ching-5 wrote: > > Oh, it's not in the Repository Scanning page. You should be able to see it > by clicking Database from the menu. The Database page should show the > consumers attached to the db scanning, including the cleanup consumers :) > > Thanks, > Deng > > On Tue, Apr 7, 2009 at 6:52 PM, Marc Lustig wrote: > >> >> I cannot find any consumer section "Database - Artifact Cleanup >> Scanning". >> We have sections >> "Repository Scanning - Consumers of Known Content " >> ->all enabled >> >> "Repository Scanning - Consumers of Invalid Content" >> -> no consumer existing >> >> We are running Archiva 1.1.3 >> Do we have to add additional consumers? How to do that? >> >> thanks >> Marc >> >> >> >> >> Maria Odea Ching-5 wrote: >> > >> > Hi Marc, >> > >> > I think there are some consumers which already do this.. You should be >> > able >> > to see them in the Database page (Database - Artifact Cleanup Scanning >> > section). They should be enabled by default and executed during >> database >> > scanning. Were you able to check if these were enabled in your Archiva >> > instance? >> > >> > Thanks, >> > Deng >> > >> > On Tue, Apr 7, 2009 at 5:36 PM, Marc Lustig wrote: >> > >> >> >> >> We often need to remove artifacts manually. We do this by deleting the >> >> files >> >> from the managed-repo on the fs. >> >> Unfortunately, those files are not automativally removed from the >> >> database. >> >> >> >> Is there any fix for this available? >> >> >> >> If not, I propose to implement a new consumer "auto-remove artifacts >> from >> >> the database" in case files where deleted from the fs. >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/consumer-to-auto-remove-artifact-from-DB-tp22925611p22925611.html >> >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/consumer-to-auto-remove-artifact-from-DB-tp22925611p22926610.html >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/consumer-to-auto-remove-artifact-from-DB-tp22925611p22927284.html Sent from the archiva-users mailing list archive at Nabble.com.