[ https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571344#comment-17571344 ]
Claude Warren commented on CASSANDRA-17773: ------------------------------------------- I think the problem is here: [https://github.com/apache/cassandra/blob/trunk/bin/cassandra.in.sh#:~:text=%23%20The%20directory,fi] On Debian the contents of the conf directory are not in CASSANDRA_HOME/conf (/usr/share/cassandra/conf) but are in /etc/cassandra So the cassandra-env.sh is not being read. In addition all the configuration files are not included in the class path. In addition cassandra-in.sh assumes that there are a number of directories under CASSANDRA_HOME (e.g. /data) that do not exist in the debian packaging. Unless Cassandra runs as root I don't see how any of this works. > Incorrect cassandra.logdir on Debian systems > -------------------------------------------- > > Key: CASSANDRA-17773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17773 > Project: Cassandra > Issue Type: Bug > Components: Packaging > Reporter: Eric Evans > Priority: Normal > Labels: lhf > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1-rc > > > The Debian packaging patches bin/cassandra to use /var/log/cassandra for > logs, it does so conditionally however, only if CASSANDRA_LOG_DIR is unset. > This occurs _after_ cassandra-env.sh is sourced though, which also sets > CASSANDRA_LOG_DIR if unset (to $CASSANDRA_HOME/logs). The result is that > -Dcassandra.lodir is set to /usr/share/cassandra/logs on Debian systems. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org