Re: [Dspace-tech] Dspace 4.2 Issue
In [dspace]/config/modules/discovery.cfg, change search.server to http://localhost/solr/ Also change these other URLs to avoid problems with OAI and Solr statistics: https://wiki.duraspace.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-ErrorsconnectingtoSolr Then restart Tomcat. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette On Tue, Jun 16, 2015 at 2:02 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: Please find the output of the command wget http://localhost:8080/solr/; With regards, Wasefer Zaman [image: Inactive hide details for helix84 ---06/16/2015 04:52:56 PM---On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman Wasefer.Zaman@si] helix84 ---06/16/2015 04:52:56 PM---On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: From: helix84 heli...@centrum.sk To: Wasefer Zaman wasefer.za...@simplexinfra.com Cc: dspace-tech dspace-tech@lists.sourceforge.net Date: 06/16/2015 04:52 PM Subject: Re: [Dspace-tech] Dspace 4.2 Issue -- On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: Caused by: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search My initial assessent was correct, DSpace cannot reach Solr at http://localhost:8080/solr/search . Proceed as I described. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace 4.2 Issue
On Tue, Jun 16, 2015 at 2:59 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: On clicking the 'Feedback' link, we are getting the following error. Just like it says, when you enter the feedback page URL directly, this error will be thrown. This is intentional in order to provide context to you, the repository administrator. Instead, access the feedback page from any other DSpace page by clicking on the feedback link. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace 4.2 Issue
Thanks a lot. The problem has been solved. With regards, Wasefer Zaman -helix84 heli...@centrum.sk wrote: - To: Wasefer Zaman wasefer.za...@simplexinfra.com From: helix84 heli...@centrum.sk Date: 06/16/2015 05:47PM Cc: dspace-tech dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Dspace 4.2 Issue In [dspace]/config/modules/discovery.cfg, change search.server to http://localhost/solr/ Also change these other URLs to avoid problems with OAI and Solr statistics: https://wiki.duraspace.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-ErrorsconnectingtoSolr Then restart Tomcat. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette On Tue, Jun 16, 2015 at 2:02 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: Please find the output of the command wget http://localhost:8080/solr/; With regards, Wasefer Zaman helix84 ---06/16/2015 04:52:56 PM---On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: From: helix84 heli...@centrum.sk To: Wasefer Zaman wasefer.za...@simplexinfra.com Cc: dspace-tech dspace-tech@lists.sourceforge.net Date: 06/16/2015 04:52 PM Subject: Re: [Dspace-tech] Dspace 4.2 Issue On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: Caused by: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search My initial assessent was correct, DSpace cannot reach Solr at http://localhost:8080/solr/search . Proceed as I described. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace-cris invalid db.name
I've had a further dig into this and it seems that the db.name has been removed on dspace v 5.x.x but is still referenced in the cris version and so causes the problem. If I set the db.name = postgres in the build.properties file it is not propagated to the dspace.cfg file. If I set it directly in the dspace.cfg file then the exception goes away and it has a further exception: ERROR: column metadatavalue.item_id does not exist I've had a look in the database and it is correct it does not exist. The class not found exception occurs in the sword, sword2, rdf, rest and oai web applications if I remove these from the webapps directory then the errors go away. The classes in the dspace-api-CRIS-5.3.0.SNAPSHOT.jar files for these apps do not contain the CrisSearchService class but they do contain the SearchService class. I'll move back to the 4.3.0 version for the present. Alastair From: alastair.dun...@stfc.ac.uk [mailto:alastair.dun...@stfc.ac.uk] Sent: 02 June 2015 11:10 To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] Dspace-cris invalid db.name Hi, I've setup dspace-cris v 5.2.0 and this starts up and I can login ok. I've added in the default CRIS objects and can browse to these ok. This suggests that the db.name is valid. When I try and create a researcher page and save this an Internal exception is thrown which states that there is an invalid db.name: java.lang.IllegalStateException: The configuration for db.name is either invalid, or contains an unrecognised database at org.dspace.content.authority.AuthorityDAOFactory.getInstance(AuthorityDAOFactory.java:42) at org.dspace.app.webui.cris.controller.ResearcherPageDetailsController.handleDetails(ResearcherPageDetailsController.java:134) at it.cilea.osd.jdyna.web.controller.SimpleDynaController.handleRequestInternal(SimpleDynaController.java:116) I don't get this problem with v 4.3.0 Any ideas? There are a few other problems when the system starts but these do not seem to be a problem yet as I've not done any searching: Failed to startup the DSpace Service Manager: failure starting up spring service manager: Error creating bean with name 'org.dspace.servicemanager.spring.DSpaceBeanPostProcessor#0' defined in class path resource [spring/spring-dspace-applicationContext.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.dspace.servicemanager.config.DSpaceConfigurationService]: : Cannot find class [org.dspace.app.cris.discovery.CrisSearchService] nested exception is java.lang.ClassNotFoundException: org.dspace.app.cris.discovery.CrisSearchService at org.dspace.servicemanager.servlet.DSpaceKernelServletContextListener.contextInitialized(DSpaceKernelServletContextListener.java:92) This is the final problem which eventually results in a null pointer in the DspaceContextListener. Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dspace.eventService' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method [public org.dspace.services.EventService org.dspace.utils.DSpace.getEventService()] threw exception; nested exception is java.lang.IllegalStateException: DSpace kernel cannot be null Any help is appreciated. Alastair -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace log files owned by root
Andre It sounds like log rotate does its magic at night see the post Logrotate Set File Permissionshttp://www.thecave.info/logrotate-set-file-permissions/ post - it might explain your situation Monika — Monika Mevenkamp Digital Repository Infrastructure Developer Phone: 609-258-4161 333C 701 Carnegie, Princeton University, Princeton, NJ 08544 On Jun 16, 2015, at 5:56 AM, Andre Gomes ago...@itclinical.commailto:ago...@itclinical.com wrote: Hi, My dspace log files are owned by root, even although I am running tomcat as user tomcat and the files are being correctly written to them. This happens for the checker.log, cocoon.log and dspace.log. For solr log files the file solr.log is owned by tomcat but every day it is created a solr.log.-MM-DD owned by root and the next day is owned by tomcat. So when I restart tomcat I get the following error: log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /srv/dspace/log/dspace.log.2015-06-12 (Permission denied) ... I wondering what can be happening? Thanks is advance for your help. André Gomes -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace 4.2 Issue
Please find the output of the command wget http://localhost:8080/solr/; With regards, Wasefer Zaman helix84 ---06/16/2015 04:52:56 PM---On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: From: helix84 heli...@centrum.sk To: Wasefer Zaman wasefer.za...@simplexinfra.com Cc: dspace-tech dspace-tech@lists.sourceforge.net Date: 06/16/2015 04:52 PM Subject:Re: [Dspace-tech] Dspace 4.2 Issue On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: Caused by: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search My initial assessent was correct, DSpace cannot reach Solr at http://localhost:8080/solr/search. Proceed as I described. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace-cris invalid db.name
Hi, I’ve had a further dig into this and it seems that the db.name has been removed on dspace v 5.x.x but is still referenced in the cris version and so causes the problem. If I set the db.name = postgres in the build.properties file it is not propagated to the dspace.cfg file. If I set it directly in the dspace.cfg file then the exception goes away and it has a further exception: ERROR: column metadatavalue.item_id does not exist this problems has been resolved with https://github.com/Cineca/DSpace/commit/6578145e547db9f1468142e548ab1ce6c183102b Please use the dspace-5_x_x-cris branch, we will make a fix release in the next few days. The class not found exception occurs in the sword, sword2, rdf, rest and oai web applications if I remove these from the webapps directory then the errors go away. The classes in the dspace-api-CRIS-5.3.0.SNAPSHOT.jar files for these apps do not contain the CrisSearchService class but they do contain the SearchService class. Seems that there are a missing resources on classpath. You can found the CrisSearchService.class into dspace-cris-api-CRIS-5.3.0.SNAPSHOT.jar but perhaps the maven dependencies missed him. Try to add the dependency to webapps pom files and rebuild the application. e.g. dspace/modules/oai/pom.xml dependency groupIdorg.dspace/groupId artifactIddspace-cris-api/artifactId /dependency Thanks for your patience. Please keep us up-to-date with your progress, we hope to achieve a better release together. Best, Andrea Il 16/06/2015 15:20, alastair.dun...@stfc.ac.uk ha scritto: I’ve had a further dig into this and it seems that the db.name has been removed on dspace v 5.x.x but is still referenced in the cris version and so causes the problem. If I set the db.name = postgres in the build.properties file it is not propagated to the dspace.cfg file. If I set it directly in the dspace.cfg file then the exception goes away and it has a further exception: ERROR: column metadatavalue.item_id does not exist I’ve had a look in the database and it is correct it does not exist. The class not found exception occurs in the sword, sword2, rdf, rest and oai web applications if I remove these from the webapps directory then the errors go away. The classes in the dspace-api-CRIS-5.3.0.SNAPSHOT.jar files for these apps do not contain the CrisSearchService class but they do contain the SearchService class. I’ll move back to the 4.3.0 version for the present. Alastair *From:*alastair.dun...@stfc.ac.uk [mailto:alastair.dun...@stfc.ac.uk] *Sent:* 02 June 2015 11:10 *To:* dspace-tech@lists.sourceforge.net *Subject:* [Dspace-tech] Dspace-cris invalid db.name Hi, I’ve setup dspace-cris v 5.2.0 and this starts up and I can login ok. I’ve added in the default CRIS objects and can browse to these ok. This suggests that the db.name is valid. When I try and create a researcher page and save this an Internal exception is thrown which states that there is an invalid db.name: java.lang.IllegalStateException: The configuration for db.name is either invalid, or contains an unrecognised database at org.dspace.content.authority.AuthorityDAOFactory.getInstance(AuthorityDAOFactory.java:42) at org.dspace.app.webui.cris.controller.ResearcherPageDetailsController.handleDetails(ResearcherPageDetailsController.java:134) at it.cilea.osd.jdyna.web.controller.SimpleDynaController.handleRequestInternal(SimpleDynaController.java:116) I don’t get this problem with v 4.3.0 Any ideas? There are a few other problems when the system starts but these do not seem to be a problem yet as I’ve not done any searching: Failed to startup the DSpace Service Manager: failure starting up spring service manager: Error creating bean with name 'org.dspace.servicemanager.spring.DSpaceBeanPostProcessor#0' defined in class path resource [spring/spring-dspace-applicationContext.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [org.dspace.servicemanager.config.DSpaceConfigurationService]: : Cannot find class [org.dspace.app.cris.discovery.CrisSearchService] nested exception is java.lang.ClassNotFoundException: org.dspace.app.cris.discovery.CrisSearchService at org.dspace.servicemanager.servlet.DSpaceKernelServletContextListener.contextInitialized(DSpaceKernelServletContextListener.java:92) This is the final problem which eventually results in a null pointer in the DspaceContextListener. Exception sending context initialized event to listener instance of class org.springframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dspace.eventService' defined in ServletContext resource [/WEB-INF/applicationContext.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Factory method
[Dspace-tech] Upgrade to JSPUI or XMLUI or not at all ?
After all this talk about the new and improved and entirely different web UI on the strategic plan at the OR conference, I am wondering how to proceed forward. We are stuck in the past: 1.8 JSPUI with a few customizations. It would be easy to port this to JSPUI in version 5, but the bootstrap theme does not work particularly well for us - it seems rather space consuming. Has somebody a modified css / small JSPUI customizations that lead to a tighter UI layout ? Comparing what I see in the XMLUI 5 with JSPUI 1.8, I see nice features like * admin can impersonate another user * a control panel with system info - the ability to start curation tasks … * and a much more friendly interface for dealing with editing an items metadata authorization, … Aside from the different look and feel what are the functional/feature differences between the XMLUI and JSPUI ? One of the changes we made requires a custom agreement page and programming a bit of logic when to pop that page up and when to simply show a bitstream. Who I did I talk to who said they have a custom agreement type page at the OR conference ? Please holler - was that XMLUI ? Monika — Monika Mevenkamp Digital Repository Infrastructure Developer Phone: 609-258-4161 333C 701 Carnegie, Princeton University, Princeton, NJ 08544 -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] OAI behind a proxy
Hi, Our dspace box is behind a proxy, so the public name of the repository ( diposit.ub.edu) differs from the name of the box dspace is running, that is not accessible from internet. What is the best way to customize the oai module in order to build the response pages with the public repository url instead of the local name? Thanks in advance! --- Domingo Iglesias Universitat de Barcelona Area de Tecnologies -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] OAI behind a proxy
Hi, Our dspace box is behind a proxy, so the public name of the repository ( diposit.ub.edu) differs from the name of the box dspace is running, that is not accessible from internet. What is the best way to customize the oai module in order to build the response pages with the public repository url instead of the local name? Thanks in advance! --- Domingo Iglesias Universitat de Barcelona Area de Tecnologies -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Dspace 4.2 Issue
Hi, Whenever we click on the By Issue Date, Authors, Titles, Subjects menu under Browse from left side, we are getting the following error. Please help. With regards, Wasefer Zaman -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] dspace ldap
On Tue, Jun 16, 2015 at 10:22 AM, Saidy Binta bisa...@mrc.gm wrote: Please I need to know, if I have to install ldap server on my machine before I can use the dspace ldap authentication. No, you can use an existing LDAP server on another machine, if you already have one. If you don't already have one, I see no point in installing your own LDAP server just for DSpace, in that case you can just use PasswordAuthentication. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] dspace ldap
Hi, Please I need to know, if I have to install ldap server on my machine before I can use the dspace ldap authentication. Regards Binta DISCLAIMER: This message is private and confidential. If you have received this message in error please notify us and remove it from your system. Any views and opinions expressed in this message are those of the individual sender and do not necessarily represent the views and opinions of Medical Research Council Unit, The Gambia ___ This communication is confidential and may contain privileged information intended solely for the named recipient(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient, you must not copy, distribute, take any action or reliance on it. If you have received this communication in error, do not open any attachments but please notify the Help Desk by e-mailing h...@mrc.gm quoting the sender details, and then delete this message along with any attached files. E-mail messages are not secure and attachments could contain software viruses which may damage your computer system. Whilst every reasonable precaution has been taken to minimise this risk, The MRC Unit The Gambia cannot accept any liability for any damage sustained as a result of these factors. You are advised to carry out your own virus checks before opening any attachments. Unless expressly stated, opinions in this message are those of the e-mail author and not of the Medical Research Council Unit The Gambia. -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace 4.2 Issue
You should paste the text from Java full stacktrace [show] to confirm the error. My guess is that DSpace can't connect to Solr. To confirm this, run wget http://localhost:8080/solr/; (assuming you're running Solr on port 8080) - if you get anything else than a 200 OK response, there is a problem. To run Solr, make sure its Context is defined as per installation instructions and search.server in [dspace]/config/modules/discovery.cfg is a working URL endpoint (the procedure shown above). Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] dspace ldap
Okay, thanks. Regards Binta -Original Message- From: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] On Behalf Of helix84 Sent: 16 June 2015 08:43 To: Saidy Binta Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] dspace ldap On Tue, Jun 16, 2015 at 10:22 AM, Saidy Binta bisa...@mrc.gm wrote: Please I need to know, if I have to install ldap server on my machine before I can use the dspace ldap authentication. No, you can use an existing LDAP server on another machine, if you already have one. If you don't already have one, I see no point in installing your own LDAP server just for DSpace, in that case you can just use PasswordAuthentication. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette DISCLAIMER: This message is private and confidential. If you have received this message in error please notify us and remove it from your system. Any views and opinions expressed in this message are those of the individual sender and do not necessarily represent the views and opinions of Medical Research Council Unit, The Gambia ___ This communication is confidential and may contain privileged information intended solely for the named recipient(s). It may not be used or disclosed except for the purpose for which it has been sent. If you are not the intended recipient, you must not copy, distribute, take any action or reliance on it. If you have received this communication in error, do not open any attachments but please notify the Help Desk by e-mailing h...@mrc.gm quoting the sender details, and then delete this message along with any attached files. E-mail messages are not secure and attachments could contain software viruses which may damage your computer system. Whilst every reasonable precaution has been taken to minimise this risk, The MRC Unit The Gambia cannot accept any liability for any damage sustained as a result of these factors. You are advised to carry out your own virus checks before opening any attachments. Unless expressly stated, opinions in this message are those of the e-mail author and not of the Medical Research Council Unit The Gambia. -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Anonymous User Submit?
Hi, A behavior very similar is reported as DS-2556: https://jira.duraspace.org/browse/DS-2556 and DS-2527: https://jira.duraspace.org/browse/DS-2527 El 15/06/2015 7:09, Bob Arko escribió: Oh wait, setting ADD policy for Group=Anonymous does work, after all. But I think I found a bug? If you login, click on Submissions, click Start a new submission, then Select a Collection, there are no Collections displayed in the popup menu. (That's what was throwing me.) But if you navigate directly to a Collection, and click Submit a new Item, it does work. On Fri, Jun 12, 2015 at 12:05:19AM -0400, Bob Arko wrote: Greetings, I'd like to accept content from folks who self-register. How may I enable an Anonymous User to submit? I've tried setting the appropriate ADD policy for Group=Anonymous on my Community and Collection, but still get You are not authorized to submit to any collections. I'm running 5.1 JSPUI. (I've checked the Manual and FAQ.) Much thanks, Bob -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- - Javier Navascués Puyada Sección de Gestión de Servicios de Campus Servicio Informático Universidad Pública de Navarra Campus de Arrosadía 31006 Pamplona/Iruña Telf. 948 16 8464Fax. 948 16 9022 e-mail javier.navasc...@unavarra.es -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Dspace log files owned by root
Hi, My dspace log files are owned by root, even although I am running tomcat as user tomcat and the files are being correctly written to them. This happens for the checker.log, cocoon.log and dspace.log. For solr log files the file solr.log is owned by tomcat but every day it is created a solr.log.-MM-DD owned by root and the next day is owned by tomcat. So when I restart tomcat I get the following error: log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: /srv/dspace/log/dspace.log.2015-06-12 (Permission denied) ... I wondering what can be happening? Thanks is advance for your help. André Gomes -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace 4.2 Issue
Please find the Java full stacktrace output for your further analysis. Java full stacktrace [hide] org.apache.cocoon.ProcessingException: Failed to process pipeline at map:serialize type=xml - jndi:/localhost/aspects/aspects.xmap:96:31 at map:generate type=file - jndi:/localhost/aspects/aspects.xmap:95:55 at map:serialize type=xml - resource://aspects/ViewArtifacts/sitemap.xmap:340:32 at map:transform type=Navigation - resource://aspects/ViewArtifacts/sitemap.xmap:88:59 at map:generate - resource://aspects/ViewArtifacts/sitemap.xmap:76:40 at map:serialize type=xml - resource://aspects/BrowseArtifacts/sitemap.xmap:72:48 at map:transform type=ConfigurableBrowse - resource://aspects/BrowseArtifacts/sitemap.xmap:71:63 at map:transform type=Navigation - resource://aspects/BrowseArtifacts/sitemap.xmap:47:47 at map:generate - resource://aspects/BrowseArtifacts/sitemap.xmap:41:28 at map:serialize type=xml - resource://aspects/Discovery/sitemap.xmap:214:40 at map:transform type=Navigation - resource://aspects/Discovery/sitemap.xmap:78:47 at map:generate - resource://aspects/Discovery/sitemap.xmap:66:28 at map:serialize type=xml - resource://aspects/Administrative/sitemap.xmap:1037:31 at map:transform type=Navigation - resource://aspects/Administrative/sitemap.xmap:282:38 at map:transform type=SystemwideAlerts - resource://aspects/Administrative/sitemap.xmap:281:44 at map:generate - resource://aspects/Administrative/sitemap.xmap:279:19 at map:serialize type=xml - resource://aspects/EPerson/sitemap.xmap:302:31 at map:transform type=Navigation - resource://aspects/EPerson/sitemap.xmap:107:38 at map:generate - resource://aspects/EPerson/sitemap.xmap:96:19 at map:serialize - resource://aspects/Submission/sitemap.xmap:277:27 at map:generate - resource://aspects/Submission/sitemap.xmap:257:26 at map:serialize type=xml - resource://aspects/Statistics/sitemap.xmap:292:36 at map:generate - resource://aspects/Statistics/sitemap.xmap:37:19 at map:serialize - resource://aspects/Workflow/sitemap.xmap:161:27 at map:generate - resource://aspects/Workflow/sitemap.xmap:145:26 at map:serialize type=xml - jndi:/localhost/aspects/aspects.xmap:85:34 at map:transform type=PageNotFound - jndi:/localhost/aspects/aspects.xmap:84:43 at map:generate - jndi:/localhost/aspects/aspects.xmap:83:22 at map:serialize type=xhtml - jndi:/localhost/themes/Mirage/sitemap.xmap:164:34 at map:transform type=i18n - jndi:/localhost/themes/Mirage/sitemap.xmap:158:33 at map:transform - jndi:/localhost/themes/Mirage/sitemap.xmap:153:51 at map:transform type=IncludePageMeta - jndi:/localhost/themes/Mirage/sitemap.xmap:140:55 at map:transform type=IncludePageMeta - jndi:/localhost/themes/Mirage/sitemap.xmap:135:55 at map:transform type=IncludePageMeta - jndi:/localhost/themes/Mirage/sitemap.xmap:126:55 at map:generate type=file - jndi:/localhost/themes/Mirage/sitemap.xmap:120:55 at map:match - jndi:/localhost/themes/Mirage/sitemap.xmap:117:28 at map:mount - jndi:/localhost/themes/themes.xmap:33:45 at map:match type=ThemeMatcher - jndi:/localhost/themes/themes.xmap:32:35 at map:mount - jndi:/localhost/sitemap.xmap:680:94 at org.apache.cocoon.ProcessingException.throwLocated(ProcessingException.java:143) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.handleException(AbstractProcessingPipeline.java:923) at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:379) at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:750) at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71) at com.sun.proxy.$Proxy71.process(Unknown Source) at org.apache.cocoon.components.source.impl.SitemapSource.toSAX(SitemapSource.java:362) at org.apache.cocoon.components.source.util.SourceUtil.toSAX(SourceUtil.java:111) at org.apache.cocoon.components.source.util.SourceUtil.parse(SourceUtil.java:294) at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:136) at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at
Re: [Dspace-tech] Dspace 4.2 Issue
On Tue, Jun 16, 2015 at 12:24 PM, Wasefer Zaman wasefer.za...@simplexinfra.com wrote: Caused by: org.dspace.browse.BrowseException: org.dspace.discovery.SearchServiceException: Server refused connection at: http://localhost:8080/solr/search My initial assessent was correct, DSpace cannot reach Solr at http://localhost:8080/solr/search. Proceed as I described. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
