Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-17 Thread liv...@gmail.com 
Hello Paul,

I will double check ant output. Maybe I'll see some clues. 
Thank you very much!
 
Liviu

Pe miercuri, 16 septembrie 2020, la 09:16:15 UTC+3, Paul Münch a scris:

> Hello Liviu,
>
> as I read in the code, the 'log.report.dir' is not used in 
> 'org.apache.log4j', but the key 'log.dir' in 
> 'dspace/config/log4j.properties'. Its default value is '${dspace.dir}/log'. 
>
> Maybe something went wrong during Ant process, so your configuration was 
> not set up correctly.
>
> Kind regards,
>
> Paul Münch
>
> Am 15.09.20 um 22:58 schrieb liv...@gmail.com:
>
> Thank you, 
>
> Yes, that line exists in /home/dspace/dspace/config/dspace.cfg
>
> Best regards,
> Liviu
>
> Pe luni, 14 septembrie 2020, la 23:53:15 UTC+3, bla...@umich.edu a scris:
>
>> In dspace.log you should set where the log files live: 
>>
>> # directory where logs are stored
>>
>> log.report.dir = ${dspace.dir}/log
>>
>> On Mon, Sep 14, 2020 at 2:20 PM liv...@gmail.com  
>> wrote:
>>
>>> 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 liv...@gmail.com:

 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) 
 .
  
  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.(FileOutputStream.java:213)
 at java.io.FileOutputStream.(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.(LogManager.java:127)
 at org.apache.log4j.Logger.getLogger(Logger.java:117)
 at 
 org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
 at 
 org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
 at 
 org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech...@googlegroups.com.
 To view this discussion on the web visit

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-16 Thread Paul Münch 
Hello Liviu,

as I read in the code, the 'log.report.dir' is not used in
'org.apache.log4j', but the key 'log.dir' in
'dspace/config/log4j.properties'. Its default value is '${dspace.dir}/log'.

Maybe something went wrong during Ant process, so your configuration was
not set up correctly.

Kind regards,

Paul Münch

Am 15.09.20 um 22:58 schrieb liv...@gmail.com:
> Thank you,
>
> Yes, that line exists in /home/dspace/dspace/config/dspace.cfg
>
> Best regards,
> Liviu
>
> Pe luni, 14 septembrie 2020, la 23:53:15 UTC+3, bla...@umich.edu a scris:
>
> In dspace.log you should set where the log files live:
>
> # directory where logs are stored
>
> log.report.dir =${dspace.dir}/log
>
>
> On Mon, Sep 14, 2020 at 2:20 PM liv...@gmail.com
>  wrote:
>
> 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 liv...@gmail.com:
>> 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)
>> 
>> .
>>  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.(FileOutputStream.java:213)
>>         at
>> java.io.FileOutputStream.(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.(LogManager.java:127)
>>         at org.apache.log4j.Logger.getLogger(Logger.java:117)
>>         at
>> 
>> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
>>         at
>> 
>> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>>         at
>> 
>> org.dspace.app.launcher.ScriptLauncher.(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?
>>

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-15 Thread liv...@gmail.com 
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 liv...@gmail.com:
>
> 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 liv...@gmail.com:
>>
>> 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) 
>> .
>>  
>>  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.(FileOutputStream.java:213)
>> at java.io.FileOutputStream.(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.(LogManager.java:127)
>> at org.apache.log4j.Logger.getLogger(Logger.java:117)
>> at 
>> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
>> at 
>> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>> at 
>> org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
>>  
>> 
>> .
>>
>>
>> -- 
> 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

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-15 Thread liv...@gmail.com 
Thank you,

Yes, that line exists in /home/dspace/dspace/config/dspace.cfg

Best regards,
Liviu

Pe luni, 14 septembrie 2020, la 23:53:15 UTC+3, bla...@umich.edu a scris:

> In dspace.log you should set where the log files live:
>
> # directory where logs are stored
>
> log.report.dir = ${dspace.dir}/log
>
> On Mon, Sep 14, 2020 at 2:20 PM liv...@gmail.com  wrote:
>
>> 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 liv...@gmail.com:
>>>
>>> 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) 
>>> .
>>>  
>>>  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.(FileOutputStream.java:213)
>>> at java.io.FileOutputStream.(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.(LogManager.java:127)
>>> at org.apache.log4j.Logger.getLogger(Logger.java:117)
>>> at 
>>> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
>>> at 
>>> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>>> at 
>>> org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>>
>>> -- 
>> 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...@googlegroups.com.
>>
> To view this discussion on the web visit 
>>

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-15 Thread Paul Münch 
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 liv...@gmail.com:
> 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 liv...@gmail.com:
>> 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)
>> 
>> .
>>  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.(FileOutputStream.java:213)
>>         at java.io.FileOutputStream.(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.(LogManager.java:127)
>>         at org.apache.log4j.Logger.getLogger(Logger.java:117)
>>         at
>> 
>> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
>>         at
>> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>>         at
>> org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit
>> 
>> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
>> 
>> .
>
> -- 
> 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

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-14 Thread Jose Blanco 
In dspace.log you should set where the log files live:

# directory where logs are stored

log.report.dir = ${dspace.dir}/log

On Mon, Sep 14, 2020 at 2:20 PM liv...@gmail.com  wrote:

> 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 liv...@gmail.com:
>>
>> 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)
>> .
>>  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.(FileOutputStream.java:213)
>> at java.io.FileOutputStream.(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.(LogManager.java:127)
>> at org.apache.log4j.Logger.getLogger(Logger.java:117)
>> at
>> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
>> at
>> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>> at
>> org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
>> 
>> .
>>
>>
>> --
> 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/f3dacd86-7c50-419d-8816-b9595594d90fn%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct:

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-14 Thread liv...@gmail.com 
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 liv...@gmail.com:
>
> 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) 
> .
>  
>  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.(FileOutputStream.java:213)
> at java.io.FileOutputStream.(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.(LogManager.java:127)
> at org.apache.log4j.Logger.getLogger(Logger.java:117)
> at 
> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
> at 
> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
> at 
> org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
>  
> 
> .
>
>
>

-- 
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/f3dacd86-7c50-419d-8816-b9595594d90fn%40googlegroups.com.

Re: [dspace-tech] java.io.FileNotFoundException: /dspace.log.2020-09-13 (Permission denied)

2020-09-14 Thread Paul Münch 
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 liv...@gmail.com:
> 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)
> .
>  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.(FileOutputStream.java:213)
>         at java.io.FileOutputStream.(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.(LogManager.java:127)
>         at org.apache.log4j.Logger.getLogger(Logger.java:117)
>         at
> org.dspace.core.ConfigurationManager.(ConfigurationManager.java:50)
>         at
> org.dspace.app.launcher.ScriptLauncher.getConfig(ScriptLauncher.java:256)
>         at
> org.dspace.app.launcher.ScriptLauncher.(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 dspace-tech+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/14733cd7-098b-4221-8007-64347b43706fn%40googlegroups.com
> .

-- 
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/60b8543d-9c06-8ff1-5e13-78a98a9296e3%40staff.uni-marburg.de.