we have upgraded dspace 5.1 after having inherited system more capable dspace administrator.
one of issues have noticed of citations appear not generated. there nothing find in either of dspace / tomcat / solr logs point fault (that find).
running curation task manually (as cron every 2 minutes) runs expected duration , doesn't abort failure.
sudo -u tomcat /usr/local/dspace/bin/dspace curate -q continually -r - -v from administrative interface, following fails if specify don't specify handle.
- curation tasks > citation tasks > general purpose tasks > generate citation metadata > perform
if specify handle of object doesn't have citation, works.
here says on failure:
task: generate citation metadata task completed successfully. status: fail, result: curation task did not provide more information outcome.
and on success:
task: generate citation metadata task completed successfully. status: success, result: added citation ...
when generate citation successfully, following logs (filtered) in dspace log:
2015-04-28 16:47:26,122 info org.dspace.content.item @ ...:session_id=...:ip_addr=...:update_item:item_id=5966 2015-04-28 16:47:26,367 info org.dspace.curate.curator @ curation task: citation performed on: .../5634 status: 0. result: 'added citation ... if run task no handle, following:
2015-04-28 16:52:19,972 info org.dspace.curate.curator @ curation task: citation performed on: status: 1 hmmm, wonder if have specify handle prefix/0 on end
task: generate citation metadata task completed successfully.
status: skip, result: item has citation, skipping; item_id=2479
should running curation tasks (from cron) differently now?
perhaps curation tasks not getting queued correctly when new object submitted; can inspect curation task queue (even in database)?
cheers, cameron
update
/usr/local/dspace/ctqueues/continually# ls -l total 448 -rw-r--r-- 1 tomcat tomcat 0 apr 17 09:40 lock0 -rw-r--r-- 1 tomcat tomcat 420832 apr 17 09:37 queue0 -rw-r--r-- 1 tomcat tomcat 15691 apr 28 10:44 queue1 -rw-r--r-- 1 tomcat tomcat 12986 apr 14 13:39 queue6 i wanted try , preserve contents of queue drain, removed lock0 file , ran sudo -u tomcat /usr/local/dspace/bin/dspace curate -q continually -r - -v try , drain work queues, seem 2 new lock files, lock0 , lock1.
i expecting dspace command finish , queue files should removed, think understanding must false. deleted files , went restart tomcat. see server busy , seems doing curation task activities, i'll consider promising sign. thanks.
first of all, citation generator not standard dspace task.
secondly, yes need run systemwide curation tasks in admin ui using [your-prefix]/0; dspace should throw error message if isn't given, not sure whether does.
none of changes in dspace 5.1 have impact on how you'd run curation tasks via cron.
the curation task queue file based , lives in [dspace]/ctqueues/[name-of-queue]/[queue-file]. command above, looks task queue you're interested in "continually" queue. may hiccup in processing curation tasks left behind old queuen files , may disrupt processing of queue / adding new tasks queue. may wish delete old queuen files.
update
your understanding of how queue files should behave correct; may seeing 2 lock files if there 2 commands working off curation queue (eg second gets started while first 1 still running, may happen if work off same queue , reason there pileup of queue files). believe i've seen lock files left behind when curate command crashed, may wish add queue directories list of things check after crash. also, make sure ctqueues directory tree has correct permissions (not issue in case looks like).
