Hello Paul,
I checked the paths.
In /home/dspace/dspace/config/local.cfg exists this line:
dspace.dir=/home/dspace/dspace
and in /home/dspace/dspace/config/log4j.properties:
log4j.appender.A1.File=${log.dir}/dspace.log
log4j.appender.A2.File=${log.dir}/checker.log
log4j.appender.A3.File=${log.dir}/cocoon.log
It seems to be ok to me...
Thank you,
Liviu
Pe marți, 15 septembrie 2020, la 11:11:01 UTC+3, Paul Münch a scris:
> Hello Liviu,
>
> yes, it seems so. Maybe there are wrong or missing paths in the
> configuration files. Please check the configuration keys 'dspace.dir' in
> dspace/config/local.cfg and 'log.dir' in dspace/config/log4j.properties.
>
> Kind regards,
>
> Paul Münch
>
> Am 14.09.20 um 20:19 schrieb [email protected]:
>
> Hello,
>
> Thank you for your response. Dspace user is "dspace" and has write
> permissions on /usr/local/tomcat/log and /home/dspace/dspace/log.
> What intrigues me is that the path of the log (/dspace.log.2020-09-13)
> seems to start from the root system, or am I wrong?
>
> Thank you.
> Liviu
>
> Pe luni, 14 septembrie 2020, la 11:29:45 UTC+3, Paul Münch a scris:
>
>> Hello,
>>
>> please take a look at the error message. The 'dspace.log'-file can't be
>> written because of false permissions. Please check if the system user which
>> run DSpace (e.g. 'tomcat' or 'dspace') has permissions to write into the
>> configured directory.
>>
>> I hope this helps and kind regards,
>>
>> Paul Münch
>>
>> Am 13.09.20 um 22:27 schrieb [email protected]:
>>
>> Hi,
>>
>> We are trying to migrate from DSpace 6.0 to DSpace-CRIS 6RC2 and we have
>> followed the instructions to Upgrade an existent DSpace (not CRIS)
>> <https://wiki.lyrasis.org/display/DSPACECRIS/Installation#Installation-UpgradeanexistentDSpace(notCRIS)installation>.
>>
>> After successfully building and deploying the application, if I run:
>>
>> ~ $ dspace/bin/dspace database info
>>
>> the error is:
>>
>> log4j:ERROR setFile(null,true) call failed.
>> java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)
>> at java.io.FileOutputStream.open0(Native Method)
>> at java.io.FileOutputStream.open(FileOutputStream.java:270)
>> at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
>> at java.io.FileOutputStream.<init>(FileOutputStream.java:133)
>> 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:94)
>> 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.<clinit>(LogManager.java:127)
>> at org.apache.log4j.Logger.getLogger(Logger.java:117)
>> at
>> org.dspace.core.ConfigurationManager.<clinit>(ConfigurationManager.java:50)
>> at
>> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>> at
>> org.dspace.app.launcher.ScriptLauncher.<clinit>(ScriptLauncher.java:35)
>>
>> I think the culprit is a wrong configuration, although I copied the
>> necessary files to the new source directory. Please, does anyone have an
>> idea where the mistake is?
>>
>> Thank you very much,
>> Liviu
>>
>> --
>> 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 [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>>
>> --
> 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 [email protected].
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/f3dacd86-7c50-419d-8816-b9595594d90fn%40googlegroups.com
>
> <https://groups.google.com/d/msgid/dspace-tech/f3dacd86-7c50-419d-8816-b9595594d90fn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/ba9bc444-78b3-4cb2-a7c5-af77b4ec3eb1n%40googlegroups.com.
