RE: [dspace-tech] Citation Page Generator
Someone 2 directories were set to read-only in DSpace. I removed the read-only setting and it appears things are working properly again. -- Jake Cameron, BCS(UNB) Systems Support Specialist III Information Systems and Technical Services University of Lethbridge Library Phone:(403)329-2756 This e-mail, including any and all attachments, is only for the use of the intended recipient(s) and may contain information that is confidential or privileged. If you are not the intended recipient, you are advised that any dissemination, copying or other use of this e-mail is prohibited. Please notify the sender of the error in communication by return e-mail and destroy all copies of this e-mail. Thank you. -Original Message- From: dspace-tech@googlegroups.com On Behalf Of Cameron, Jacob Sent: Wednesday, November 25, 2020 10:20 AM To: Mark H. Wood ; DSpace Technical Support Subject: RE: [dspace-tech] Citation Page Generator Hi Mark, There doesn't appear to be any issues with the permissions. Everything is owned by the local dspace account. However, I'm not able to run any dspace commands now. Apparently the tomcat upgrade I did has broken things. When I try to run dspace solr-stats or dspace oai import it says it can't access the log files, permission is denied, but the log files are all owned by the local dspace account as well. None of the errors are showing up in my log files either, as the solr log files are not being generated. None of my DSpace commands seem to be working since Tomcat was updated. Same for dspace filter-media. They all get angry with the log files. Any thoughts? Using DSpace installation in: C:\dspace log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: C:\dspace\log\dspace.log.2020-11-25 (Access is denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) at org.dspace.app.util.DailyFileAppender.activateOptions(DailyFileAppender.java:95) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) at org.apache.log4j.LogManager.(LogManager.java:127) at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:81) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:295) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:315) at org.dspace.servicemanager.DSpaceKernelInit.(DSpaceKernelInit.java:24) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:46) log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: C:\dspace\log\checker.log.2020-11-25 (Access is denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) at org.dspace.app.util.DailyFileAppender.activateOptions(DailyFileAppender.java:95) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) at
RE: [dspace-tech] Citation Page Generator
Hi Mark, There doesn't appear to be any issues with the permissions. Everything is owned by the local dspace account. However, I'm not able to run any dspace commands now. Apparently the tomcat upgrade I did has broken things. When I try to run dspace solr-stats or dspace oai import it says it can't access the log files, permission is denied, but the log files are all owned by the local dspace account as well. None of the errors are showing up in my log files either, as the solr log files are not being generated. None of my DSpace commands seem to be working since Tomcat was updated. Same for dspace filter-media. They all get angry with the log files. Any thoughts? Using DSpace installation in: C:\dspace log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: C:\dspace\log\dspace.log.2020-11-25 (Access is denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) at org.dspace.app.util.DailyFileAppender.activateOptions(DailyFileAppender.java:95) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) at org.apache.log4j.LogManager.(LogManager.java:127) at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:81) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:295) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:315) at org.dspace.servicemanager.DSpaceKernelInit.(DSpaceKernelInit.java:24) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:46) log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: C:\dspace\log\checker.log.2020-11-25 (Access is denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165) at org.dspace.app.util.DailyFileAppender.activateOptions(DailyFileAppender.java:95) at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172) at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104) at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842) at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768) at org.apache.log4j.PropertyConfigurator.parseCatsAndRenderers(PropertyConfigurator.java:672) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:516) at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580) at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526) at org.apache.log4j.LogManager.(LogManager.java:127) at org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:81) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:295) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:315) at org.dspace.servicemanager.DSpaceKernelInit.(DSpaceKernelInit.java:24) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:46) log4j:ERROR setFile(null,true) call failed. java.io.FileNotFoundException: C:\dspace\log\cocoon.log.2020-11-25 (Access is denied) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at java.io.FileOutputStream.(Unknown Source) at org.apache.log4j.FileAppender.setFile(FileAppender.java:294) at
[dspace-tech] Re: ORCID Researcher Information
Good day
After alot of digging, the solution was to go into admin mode in
dspace-cris, edit the researchers public profile, go edit Profile, select
editing on the Profile box, edit ORCID box and change custom rendering to:
http://orcid.org/{0};>{0}
Regards
Eldridge
On Wednesday, 25 November 2020 at 10:52:51 UTC+2 Eldridge van der
Westhuizen wrote:
> Good day all
>
> Running DSpace-Cris 6.3 on Ubuntu using JSPUI.
>
> We did the Sandbox testing of ORCID integration with DSPACE-CRIS. All
> went well.
>
> We then moved all settings to Production and this also worked well. All
> the sandbox options are commented out in the local.cfg and
> authentication-oauth.cfg files.
>
> However, when you go to researcher profile, the prefix to the ORCID id is
> still pointing to sandbox. Any idea where this setting is?
>
> If you edit the researcher’s page, you only input the ORCID number and not
> the prefix. It somehow gets this from config somewhere.
>
> Please find some images attached to depict the problem.
>
> Thanks for your help.
>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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 view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/aa0e31b6-4ac7-45e8-8827-95e4ee8be8a8n%40googlegroups.com.
Re: [dspace-tech] Citation Page Generator
On Tue, Nov 24, 2020 at 10:20:40PM +, Cameron, Jacob wrote: > We've had the citation page generator turned on for a couple of years. I > upgraded Tomcat and Java last week, but even before that, some documents > seemed to be corrupted when the citation page was added to the document. If > I was logged in the document appeared, opened fine, etc.. However if I was > not logged in and I clicked the View/Open button, it opened to a blank page > and said there was a problem with the document. If I downloaded it, it saved > a 0mb file, obviously corrupted. However, I turned off the citation page > feature and everything works 100% for all the documents. Any thoughts or > suggestions on what I could be doing wrong here? Well, it sounds like a permissions problem of some sort, and one that should not happen. I would look in the DSpace logs around the times of these failures to see if there are any clues. -- Mark H. Wood Lead Technology Analyst University Library Indiana University - Purdue University Indianapolis 755 W. Michigan Street Indianapolis, IN 46202 317-274-0749 www.ulib.iupui.edu -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/20201125134924.GA3588%40IUPUI.Edu. signature.asc Description: PGP signature
[dspace-tech] ORCID Researcher Information
Good day all Running DSpace-Cris 6.3 on Ubuntu using JSPUI. We did the Sandbox testing of ORCID integration with DSPACE-CRIS. All went well. We then moved all settings to Production and this also worked well. All the sandbox options are commented out in the local.cfg and authentication-oauth.cfg files. However, when you go to researcher profile, the prefix to the ORCID id is still pointing to sandbox. Any idea where this setting is? If you edit the researcher’s page, you only input the ORCID number and not the prefix. It somehow gets this from config somewhere. Please find some images attached to depict the problem. Thanks for your help. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- 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 view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/3b12321a-12a7-486c-b99e-118ade760174n%40googlegroups.com.
