allura-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eugène Adell <Eugene.Ad...@d2-si.eu>
Subject RE:recurrent error "Reason: NOT_FOUND"
Date Mon, 10 Jun 2013 15:10:47 GMT

Hello


# pgrep -fl start.jar
654 java -Dsolr.solr.home=/root/envs/allura/src/apache-solr-1.4.1/example/solr -jar start.jar

# grep solr.server ./envs/allura/src/allura/Allura/development.ini
solr.server = http://localhost:8983/solr/core0

I suppose this command must be run in my local git repo.. :
# git rev-parse HEAD
51e056f56b6de70662a00199cb563ee6d2bf7d53

Solr Implementation Version: 1.4.1 955763M - mark - 2010-06-17 18:06:42





De : Tim Van Steenburgh [tvansteenburgh@gmail.com]
Envoyé : lundi 10 juin 2013 14:32
À : allura-users@incubator.apache.org
Objet : Re: recurrent error "Reason: NOT_FOUND"


The first thing to do is make sure Solr is running: 


$ pgrep -fl start.jar


If it's not, and you're using the Vagrant box:


$ cd ~ && ./start_allura


Otherwise, follow the instructions in the repo README for starting Solr.




If starting Solr doesn't resolve the problem, please post the output of the following commands
and we can help you further:


$ cat Allura/development.ini | grep solr.server
$ git rev-parse HEAD
Also let us know which version of Solr you're running (can be found at http://localhost:8983/solr/admin).


-- 
Tim Van Steenburgh




On Saturday, June 8, 2013 at 7:14 AM, Eugène Adell wrote:


Hi all


the taskd.log is filled up with such errors "[pysolr] [Reason: NOT_FOUND]" which occur many
times :


01:07:50,176 INFO [allura.command] Initialize command with config 'development.ini'
01:07:51,002 INFO [allura.command] Loaded tools
01:07:51,002 INFO [allura.command] Starting taskd, pid 660
01:07:51,230 INFO [ew.resource] Loading ep ew_resources = allura.config.resources:register_ew_resources
01:07:51,239 INFO [ew.resource] Loading ep ew_resources = forgeactivity.config.resources:register_ew_resources
01:07:51,250 INFO [ew.resource] Loading ep ew_resources = forgetracker.config.resources:register_ew_resources
14:45:41,395 INFO [allura.model.monq_model] starting <MonQTask 51b30b52506eed02a019949b
(busy) P:10 allura.tasks.index_tasks.add_artifacts shaman pid 660 project:/u/testuser/ app:wiki
user:testuser>
14:45:42,681 INFO [pysolr] Finished 'http://localhost:8983/solr/core0/update/?commit=false'
(POST) with body '<add commi' in 0.599 seconds.
14:45:42,708 ERROR [pysolr] [Reason: NOT_FOUND]
14:45:42,709 INFO [allura.model.monq_model] Error on job <MonQTask 51b30b52506eed02a019949b
(busy) P:10 allura.tasks.index_tasks.add_artifacts shaman pid 660 project:/u/testuser/ app:wiki
user:testuser>, re-raising it




Is this bad ? Is there any way to cure such behavior ?


Thanks & best regards 
E.A.

Mime
View raw message