Hi Pantelis,
This bug was resolved *after* the DSpace 6 RC1 release, as noted by Mark
Wood. Here's the bug ticket and resolution:
https://jira.duraspace.org/browse/DS-3104
https://github.com/DSpace/DSpace/pull/1364
So, if you are still running RC1, then you are likely encountering this bug.
Although the problem was manually corrected after creating the log dir and
setting the respective value in log4j.properties, I am still getting the
following error related to solr logs:
log4j:ERROR setFile(null,true) call failed.
*java.io.FileNotFoundException: /log/solr.log (No such file or
This should have been corrected in
https://github.com/DSpace/DSpace/pull/1364. log.dir no longer exists in
the DSpace configuration; it is only defined in the log4j configuration.
If a property is not defined, no substitution is done.
--
You received this message because you are subscribed
Still it seems it is unable to grasp the value of log.dir parameter and
substitute in log4j.properties.
My way around this was to hardcode the value of log.dir in log4j.properties
in which I now have an entry like:
log.dir=/home/pkaramol/Workspace/dspace6/dspace-6.0-rc1-install-dir/log
And I
On Sunday, May 22, 2016 at 6:53:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a *folder* literally named ${log.dir} is
> created in dspace_installer folder.
> It seems no parameter substitution takes place when running the ant target.
> Where are the folder names
