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 recurrent error "Reason: NOT_FOUND"
Date Sat, 08 Jun 2013 11:14:25 GMT

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