Hi Tim, This happens on every curation task that I run on this machine. For example:
dspace/bin/dspace curate -t requiredmetadata -i 123456789/3770 -r - -v Adding task: requiredmetadata Task: requiredmetadata not resolved Starting curation Curating id: 123456789/3770 Ending curation. Elapsed time: 576 The same command works on the other two machines and my test machine. It was working too on this machine for couple of months and it stopped. Configurations are the same on all instances. It looks like that this problem occurs while task is getting resolved in Curator.java. I have even tried to rebuild, but I get the same issue. Is there anything else that I need to check (maybe at the OS level)? Regards, Enes On Wednesday, March 21, 2018 at 8:24:01 PM UTC+1, Tim Donohue wrote: > > Hi Enes, > > I just did a basic test of Curation Tasks on our http://demo.dspace.org > server. On that server, I ran the following on the commandline: > > [dspace]/bin/dspace curate -t checklinks -i 10673/5 -r - -v > > And, the "checklinks" curation task ran successfully on this item: > http://demo.dspace.org/xmlui/handle/10673/5 without any issues. > > So, I'm wondering if maybe it's a configuration error on your end, or if > only specific task(s) are failing. But, we'd probably need you to send > more information to the mailing list in order to help diagnose the issue. > In any case, I'd recommend double checking that your curation task > configuration, perhaps comparing it the the out-of-the-box DSpace 6.x > version: > > > https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/curate.cfg > > (And where the configuration exists shouldn't matter too much, but any > configurations in your local.cfg *will override* the settings in your > curate.cfg) > > - Tim > > On Wed, Mar 21, 2018 at 7:32 AM eneshukic via DSpace Technical Support < > [email protected] <javascript:>> wrote: > >> We have three DSpace 6 instances on CentOS 7. On one instance, curation >> tasks are not working from either CLI, XMLUI or our custom forms. The >> configuration is the same on all three instances. If we run dspace curate >> -t taskname -i 123456789/3770 -r - -v , we get Task: taskname not >> resolved. This includes curation tasks that come out of box. >> >> We have also tried to move setting from the curate.cfg to local.cfg, but >> the same issue is occurring. >> >> Did anyone experience similar issue? >> >> Regards, >> Enes >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
