[dspace-tech] HTTP Status 404 - /jspui The requested resource is not available. ERROR

[Ribin Jones]

Hi,

I have a dspace 4.2 running in Ubuntu 14.04. I have many collections and 
items in the server. Recently there was a mistake from one a technical guy 
and now the the page shows 

HTTP Status 404 - /jspui
--

*type* Status report

*message* */jspui*

*description* *The requested resource is not available.*


*http://xxc.yy.in:8080/ * gets me the Tomcat page. But the xmlui and jspui 
is not working. Please let me know how to troubleshoot this. Is this some 
kind of permission issue for my dspace installation folder?


Any help is greatly appreciated.


Ribin

-- 
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.

[dspace-tech] index-discovery - exclude collection from indexing

[Gary Browne]

HI all,

In the docs:

https://wiki.duraspace.org/display/DSDOC4x/Discovery

It is stated:

-r  remove an Item, Collection or Community from index based 
on its handle


in the index-discovery parameters section.


If I use a collection handle, does this mean:


i) a collection's items will be removed from the Solr index, OR;

ii) this collection will not be (re-)indexed on this run?


Thanks for the clarification.


Regards,
Gary

-- 
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.

Re: [dspace-tech] LDAP Login issues - DSpace v5

[Tim Cullings]

Finally solved this through a combination of Wiresark and dspace logs I was
able to figure out that it wasn't binding to LDAP at all.  Fixed that by
adding \'s to my authentication-ldap.search.user.

So it is now cn=username\,ou=someou\,dc=domain\,dc=com

I then had to add a slash to the end of my ldap server name: ldap://
ldap.domain.com/

Had to add a backslash to the search context: ou=domain\,ou=com

I commented out the object context line as well.

After that it started working.

On Thu, Jul 13, 2017 at 5:00 PM, Shannon Meisenheimer  wrote:

> Weird.  That's an auth credential error, but like you said you've tested
> that user elsewhere.  I'm no LDAP wizard, I had troubleshoot our
> DSpace/LDAP setup with our team that supports active directory.
>
> Shannon
>
> Sent from my iPhone
>
> On Jul 13, 2017, at 6:18 PM, Tim Cullings  wrote:
>
> Yes, I verified that they are the same.
>
> On Wed, Jul 12, 2017 at 7:22 PM, Shannon Meisenheimer <
> meisenhei...@ucmo.edu> wrote:
>
>> Are you sure the cn and samAccountName match for that user?
>>
>> Shannon
>>
>> Sent from my iPhone
>>
>> On Jul 12, 2017, at 3:55 PM, Tim Cullings  wrote:
>>
>> I have been tasked with setting up DSpace in my environment and getting
>> it working with LDAP for user authentication.
>>
>> I've gone through every article on the site, tried every combination of
>> settings in the authentication-ldap.cfg file and can't seem to get it to
>> work.  The only error I receive is:
>>
>> ldap_authentication:type=failed_auth 
>> javax.naming.AuthenticationException\colon;
>> [LDAP\colon; error code 49 - 80090308\colon; LdapErr\colon; DSID-0C0903D9,
>> comment\colon; AcceptSecurityContext error, data 52e, v2580 ]
>>
>> Running DSPACE 5 on Windows Server 2012 R2
>>
>> Here are my settings:
>>
>> authentication-ldap.enable = true
>> authentication-ldap.autoregister = true
>> authentication-ldap.provider_url = ldap://ldap.domain.com:389
>> authentication-ldap.id_field = sAMAcoountName
>> authentication-ldap.object_context = dc=domain,dc=com
>> authentication-ldap.search_context = dc=domain,dc=com
>> authentication-ldap.email_field = mail
>> authentication-ldap.surname_field = sn
>> authentication-ldap.givenname_field = givenName
>> authentication-ldap.search_scope = 2
>> #authentication-ldap.search.anonymous = false
>> authentication-ldap.search.user = cn=user,ou=someou,dc=domain,dc=com
>> authentication-ldap.search.password = password
>>
>> I used an LDAP browsing tool from the server with the service account I
>> am attempting to use for Dspace and was able to run queries with it against
>> our AD server.  I also used ldapsearch on a UNIX box and the specified
>> credentials and that worked as well so I am fairly certain the issue is
>> with Dspace.  Domain users reside in multiple OUs that are one level down
>> from the root for example,  cn=user1,ou=Contractors,dc=domain,dc=com and
>> so on for FTEs, vendors and other types of employees.
>>
>> --
>> 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.
>>
>>
>

-- 
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.

[dspace-tech] Elsevier Acquires BePress

[David Brian Holt]

For law school institutional repositories, this is HUGE news.  

https://scholarlykitchen.sspnet.org/2017/08/02/elsevier-acquires-bepress/

This really might be an amazing opportunity for projects like Dspace.  If 
the platform was able to match what BePress has been doing with law 
reviews/journals I think you'd see lots of law schools moving from Digital 
Commons to Dspace simply out of principle.  Elsevier purchased SSRN (the 
hosting platform for social science working papers) last year so this 
recent acquisition is going to scare a lot of librarians and IR 
administrators working in legal education.  

Just an FYI,

David

-- 
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.

Re: [dspace-tech] Batch import from CSV slower and slower

[helix84]

Although you're right that this should be fixed, the extent to which
we can fix this will be limited.

Each batch import is basically a DB-level transaction. As it gets
bigger, there will be some slowdown which is understandable (up to
some extent). By isolating the whole import, we can roll it back as a
whole if it fails.

We could split it down into manageable parts (e.g. 1000 rows) which
would run in separate transactions, but we would lose the benefits of
the isolation.

That's why it's probably better to split your import into smaller
parts yourself. You can use the command-line "split" command on your
csv file (don't forget to copy the header, too).

Of course, we should investigate whether the slowdown comes fully from
the transaction size or may have other reason, too. Feel free to file
a Jira issue.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


On Wed, Aug 2, 2017 at 12:27 PM, João Silva  wrote:
> Hi,
>
> I am trying to batch ingest around ~19k records from a CSV into a DSpace
> 6.x, clean instance. It stayed online the whole night and is currently at
> record ~7300.
>
> It seems like the system just gets slower and slower. I then tried
> increasing the heap size in bin/dspace to -Xms256m -Xmx1024m, no luck.
>
> Any tips on how to improve this?
>
> Thanks,
> João Rocha.
>
> --
> 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.

-- 
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.

[dspace-tech] Batch import from CSV slower and slower

[João Silva]

Hi,

I am trying to batch ingest around ~19k records from a CSV into a DSpace 
6.x, clean instance. It stayed online the whole night and is currently at 
record ~7300. 

It seems like the system just gets slower and slower. I then tried 
increasing the heap size in bin/dspace to -Xms256m -Xmx1024m, no luck.

Any tips on how to improve this?

Thanks,
João Rocha.

-- 
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.

Re: [dspace-tech] Re: Understanding index-discovery -o

[helix84]

No reason to make it a no-op in DSpace (if you need it, you have it
available without needing to fire a curl query to Solr), but running
the scheduled task daily is not necessary. That said, it doesn't cost
much, either. The excessive usage Solr devs referred to was running it
after every batch update or even after every added document.

We might also change the help output of index-discovery -h to
something more descriptive like "if excessive, reduce the number of
segments in Solr search core".

Current output:

stats-util -h
 -o,--optimizeRun maintenance on the SOLR index

index-discovery -h
 -o optimize search core


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


On Wed, Aug 2, 2017 at 9:24 AM, Alan Orth  wrote:
> Hi,
>
> What is the current best practices recommendation for `index-discovery -o`
> in DSpace 4, 5, and 6? In this thread helix84 pointed out a quite old issue
> on the Solr bug tracker that discussed the usefulness of the "optimize"
> (forceMerge) operation in Solr. I've had this disabled on our DSpace
> instances for almost a year now but notice it is still recommended on the
> various scheduled tasks pages on the wiki[0].
>
> What are people's thoughts on this? Should we remove it from the official
> list of scheduled tasks (and make the `index-discovery -o` subcommand a
> noop)?
>
> [0] https://wiki.duraspace.org/display/DSDOC6x/Scheduled+Tasks+via+Cron
>
> Regards,
>
> On Thu, Mar 17, 2016 at 8:38 PM Terry Brady 
> wrote:
>>
>> See the prior note from helix84 that references the log files of interest.
>> Take a look at those files to diagnose the problem.
>>
>>> The 503 error you see is from the Solr client side (DSpace). To see the
>>> actual error you need to look into Solr log (catalina.out or solr.log
>>> depending on DSpace version).
>>
>>
>> If the errors are unclear, please post the error messages to this thread.
>>
>> Terry
>>
>> On Thu, Mar 17, 2016 at 4:44 AM, Lulamile Mangali
>>  wrote:
>>>
>>> Hi Terry,
>>>
>>> Can you assist us here, we have installed a new 5.3 DSpace instance and
>>> now are getting an error that says "503 Service Temporarily Unavailable" -
>>> could you please give us an indicator as to what might be the problem...?
>>>
>>> Thanking you in advance..
>>>
>>>
>>>
>>> On Wednesday, January 13, 2016 at 10:52:09 AM UTC+2, helix84 wrote:

 Hi Terry,

 1. The 503 error you see is from the Solr client side (DSpace). To see
 the actual error you need to look into Solr log (catalina.out or solr.log
 depending on DSpace version).

 2. Running the forceMerge operation (-o) on a regular basis is not
 really necessary. It can help in special circumstances, but it's not such a
 big deal in normal operation, especially in read-heavy use case such as
 DSpace. You can more about that here: [1]

 [1] https://issues.apache.org/jira/browse/SOLR-3141


 Regards,
 ~~helix84

 Compulsory reading: DSpace Mailing List Etiquette
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

>>
>>
>>
>> --
>> Terry Brady
>> Applications Programmer Analyst
>> Georgetown University Library Information Technology
>> https://www.library.georgetown.edu/lit/code
>> 425-298-5498 (Seattle, WA)
>>
>> --
>> 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.
>
> --
> Alan Orth
> alan.o...@gmail.com
> https://picturingjordan.com
> https://englishbulgaria.net
> https://mjanja.ch
>
> --
> 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.

-- 
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.

Re: [dspace-tech] Re: Understanding index-discovery -o

[Alan Orth]

Hi,

What is the current best practices recommendation for `index-discovery -o`
in DSpace 4, 5, and 6? In this thread helix84 pointed out a quite old issue
on the Solr bug tracker that discussed the usefulness of the "optimize"
(forceMerge) operation in Solr. I've had this disabled on our DSpace
instances for almost a year now but notice it is still recommended on the
various scheduled tasks pages on the wiki[0].

What are people's thoughts on this? Should we remove it from the official
list of scheduled tasks (and make the `index-discovery -o` subcommand a
noop)?

[0] https://wiki.duraspace.org/display/DSDOC6x/Scheduled+Tasks+via+Cron

Regards,

On Thu, Mar 17, 2016 at 8:38 PM Terry Brady 
wrote:

> See the prior note from helix84 that references the log files of
> interest.  Take a look at those files to diagnose the problem.
>
> The 503 error you see is from the Solr client side (DSpace). To see the
>> actual error you need to look into Solr log (catalina.out or solr.log
>> depending on DSpace version).
>
>
> If the errors are unclear, please post the error messages to this thread.
>
> Terry
>
> On Thu, Mar 17, 2016 at 4:44 AM, Lulamile Mangali <
> lulamile.mang...@gmail.com> wrote:
>
>> Hi Terry,
>>
>> Can you assist us here, we have installed a new 5.3 DSpace instance and
>> now are getting an error that says "503 Service Temporarily Unavailable" -
>> could you please give us an indicator as to what might be the problem...?
>>
>> Thanking you in advance..
>>
>>
>> On Wednesday, January 13, 2016 at 10:52:09 AM UTC+2, helix84 wrote:
>>>
>>> Hi Terry,
>>>
>>> 1. The 503 error you see is from the Solr client side (DSpace). To see
>>> the actual error you need to look into Solr log (catalina.out or solr.log
>>> depending on DSpace version).
>>>
>>> 2. Running the forceMerge operation (-o) on a regular basis is not
>>> really necessary. It can help in special circumstances, but it's not such a
>>> big deal in normal operation, especially in read-heavy use case such as
>>> DSpace. You can more about that here: [1]
>>>
>>> [1] https://issues.apache.org/jira/browse/SOLR-3141
>>>
>>>
>>> Regards,
>>> ~~helix84
>>>
>>> Compulsory reading: DSpace Mailing List Etiquette
>>> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>>
>>>
>
>
> --
> Terry Brady
> Applications Programmer Analyst
> Georgetown University Library Information Technology
> https://www.library.georgetown.edu/lit/code
> 425-298-5498 (Seattle, WA)
>
> --
> 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.
>
-- 
Alan Orth
alan.o...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch

-- 
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.

[dspace-tech] Batch Import (ZIP) exception on edited file on Win8

[Evelthon Prodromou]

 

Hi all,


I am seeing some odd behavior in batch import (ZIP). We are migrating  
collections from one DS instance to another (both 5.5/Mirage2). We 
decompress,  remove unnecessary files, re-compress (zip) and finally, 
upload.


The thing is, if the above procedure is done in linux, all goes well. If it 
is done in windows (8, 64bit) an exception is thrown. I've tried zipping 
with native windows zip function, winzip, winrar, 7-zip. I am adding the 
full stack at the end of this message.


To be clear, metadata and filenames include both latin and non-latin 
characters, in utf8. I'm thinking this might be a character encoding issue 
on the window OS. 


Anyone else faced the same issue?


Thanks,


Evelthon




Java stacktrace follows:


*Java stacktrace: *java.lang.IllegalArgumentException: MALFORMED

at java.util.zip.ZipCoder.toString(ZipCoder.java:58)

at java.util.zip.ZipFile.getZipEntry(ZipFile.java:531)

at java.util.zip.ZipFile.access$900(ZipFile.java:56)

at java.util.zip.ZipFile$1.nextElement(ZipFile.java:513)

at java.util.zip.ZipFile$1.nextElement(ZipFile.java:483)

at 
org.dspace.app.itemimport.ItemImport.unzip(ItemImport.java:2026)

at 
org.dspace.app.itemimport.ItemImport.unzip(ItemImport.java:1987)

at 
org.dspace.app.xmlui.aspect.administrative.FlowBatchImportUtils.processUploadZIP(FlowBatchImportUtils.java:173)

at sun.reflect.GeneratedMethodAccessor189.invoke(Unknown Source)

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)

at 
org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)

at 
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)

at 
org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)

at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)

at 
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)

at 
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)

at 
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)

at org.mozilla.javascript.Context.call(Context.java:538)

at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)

at 
org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803)

at 
org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698)

at 
org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94)

at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)

at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)

at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)

at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)

at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)

at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)

at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)

at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)

at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)

at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)

at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)

at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)

at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)

at 
org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)

at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)

at 
org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:87)

at