[
https://issues.apache.org/jira/browse/MRM-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Stockhammer updated MRM-1983:
------------------------------------
Fix Version/s: 3.1.0
> RHEL7 - RPM Tomcat installs with symlinks from /usr/share/tomcat. Archiva
> cannot follow
> ---------------------------------------------------------------------------------------
>
> Key: MRM-1983
> URL: https://issues.apache.org/jira/browse/MRM-1983
> Project: Archiva
> Issue Type: Bug
> Components: Audit Logging
> Affects Versions: 2.2.3
> Environment: Red Hat Enterprise Linux 7
> Reporter: Matakaheru
> Priority: Minor
> Fix For: 3.1.0
>
>
> When installing Tomcat 7 through RHEL repositories, it sets up Tomcat in a
> "Red Hat" fashion. This means config files go in /etc, log files go in
> /var/log, webapps go in /var/lib, and so on. $CATALINA_HOME is then set as
> /usr/share/tomcat which holds symlinks all over the system. The Archiva
> installation instructions indicate setting -Dappserver.home=$CATALINA_HOME
> -Dappserver.base=$CATALINA_HOME.
> When configured in this way, the system is either unable to recognize that a
> logs directory exists, or is unable to follow the link as it errors:
> 2018-08-01 09:17:23,496 localhost-startStop-1 ERROR Cannot access
> RandomAccessFile java.io.IOException: Could not create directory
> /$CATALINA_HOME/logs java.io.IOException: Could not create directory
> /$CATALINA_HOME/logs
> However, if configured to set those two home directives to
> =/actual/path/to/archiva then the system is able to find the directory and
> write a data and logs directory to that location.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
