Hi Tim, I executed: dspace/bin/dspace dsprop -p plugin.named.org.dspace.curate.CurationTask -r
My output is: [org.dspace.ctask.general.NoOpCurationTask = noop, org.dspace.ctask.general.ProfileFormats = profileformats, org.dspace.ctask.general.RequiredMetadata = requiredmetadata, org.dspace.ctask.general.ClamScan = vscan, org.dspace.ctask.general.MicrosoftTranslator = translate, org.dspace.ctask.general.MetadataValueLinkChecker = checklinks, org.dspace.ctask.general.ValidateMetadata = validatemetadata, org.dspace.ctask.general.ExtractMBRfromTFW = extractmbr, org.dspace.ctask.general.InheritCollectionPermissions = collectionpermission, org.dspace.ctask.general.DeleteReplicationItems = deletereplicationitems] It looks correct. Do you have any ideas what else could cause not resolved issue? Thanks, Enes On Thursday, March 22, 2018 at 6:27:18 PM UTC+1, Tim Donohue wrote: > > Hi Enes, > > To me, that error "Task: requiredmetadata not resolved", still sounds > suspiciously like a configuration problem. So, I'm wondering if your > primary configuration in curate.cfg is being accidentally overridden > elsewhere (e.g. in local.cfg), or perhaps if the curate.cfg files isn't > being loaded into your dspace.cfg properly (e.g. via an "include" line like > this: > https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L2005 > ) > > One thing you could try... DSpace has a commandline tool that is able to > check what configurations it "sees". Try running: > > [dspace]/bin/dspace dsprop -p plugin.named.org.dspace.curate.CurationTask > -r > > This should output the "raw" (-r) value of the > "plugin.named.org.dspace.curate.CurationTask" > configuration that DSpace is loading/seeing. In a normal, default 6.x > DSpace site, this command should return an array of values like this: > > [org.dspace.ctask.general.NoOpCurationTask = noop, > org.dspace.ctask.general.ProfileFormats = profileformats, > org.dspace.ctask.general.RequiredMetadata = > requiredmetadata, org.dspace.ctask.general.ClamScan = vscan, > org.dspace.ctask.general.MicrosoftTranslator = translate, > org.dspace.ctask.general.MetadataValueLinkChecker = checklinks] > > This array of values is defined in the curate.cfg file. If your site does > *not* return this array of values, then something is definitely wrong in > your configuration. > > - Tim > > On Thu, Mar 22, 2018 at 5:54 AM eneshukic via DSpace Technical Support < > dspac...@googlegroups.com <javascript:>> wrote: > >> 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 < >>> dspac...@googlegroups.com> 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 dspace-tech...@googlegroups.com. >>>> To post to this group, send email to dspac...@googlegroups.com. >>> >>> >>>> 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 dspace-tech...@googlegroups.com <javascript:>. >> To post to this group, send email to dspac...@googlegroups.com >> <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 dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
