Do you have appropriate permissions on the directories?

You should be able to delete the .indexer directory completely and then run the 
scan again with "process all" (there is no need to touch the repository files).

- Brett

On 27/02/2010, at 2:24 AM, phillips1021 wrote:

> 
> Reference our problem - Here is the log error when we try to use the Process
> All Artifacts feature on the repositories admin web page:
> 
> 2010-02-26 09:05:07,723 [btpool0-9] INFO 
> org.apache.maven.archiva.web.action.admin.SchedulerAction  - [ActionMessage]
> Your request to have repository [internal] be indexed has been queued.
> 2010-02-26 09:05:07,744 [pool-2-thread-1] INFO 
> org.apache.maven.archiva.scheduled.executors.ArchivaRepositoryScanningTaskExecutor
>  
> - Executing task from queue with job name: RepositoryTask
> [repositoryId=internal, resourceFile=null, scanAll=true,
> updateRelatedArtifacts=false]
> 2010-02-26 09:05:07,818 [pool-2-thread-1] WARN 
> org.apache.maven.archiva.repository.scanner.functors.TriggerBeginScanClosure 
> - Consumer [index-content] cannot begin:
> /root/apps/apache-archiva-1.3/data/repositories/internal/.indexer/_7n.cfs
> (No such file or directory)
> org.apache.maven.archiva.consumers.ConsumerException:
> /root/apps/apache-archiva-1.3/data/repositories/internal/.indexer/_7n.cfs
> (No such file or directory)
> 
> 
> 
> phillips1021 wrote:
>> 
>> Please help us get Archiva working correctly after we copied it from one
>> server to a new server.  
>> 
>> We are using Archiva 1.3
>> 
>> We had to move our Archiva installation from one server to another.
>> 
>> We copied the complete apache-archiva-1.3 directory and sub directories to
>> the new server.
>> 
>> Archiva runs on the new server, but after the first hourly scan completes
>> nothing shows up in the browse and no artifacts can be found using the
>> search.
>> 
>> The internal repository is present in the same place in the new server as
>> it was in the old.  All the artifacts from the old server are there.
>> 
>> On the repositories web page in admin we tried checking the Process All
>> Artifacts and clicking on the Scan Repository Now button (we first did a
>> touch of all the repository files) but it says it only found 37 new files
>> but there are hundreds in our internal repository.
>> 
>> Please help us get Archiva working correctly on the new server.  We don't
>> want to have to start over with Archiva on the new server as we have added
>> numerous artifacts of our own.
>> 
> 
> -- 
> View this message in context: 
> http://old.nabble.com/Transfer-Archiva-From-One-Server-To-Another-tp27719462p27719563.html
> Sent from the archiva-users mailing list archive at Nabble.com.
> 

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/




Reply via email to