[ https://issues.apache.org/jira/browse/CASSANDRA-14142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658146#comment-16658146 ]
Alex Ott commented on CASSANDRA-14142: -------------------------------------- It looks like that it was fixed with this commit: [https://github.com/alexott/cassandra/commit/6ba2fb9395226491872b41312d978a169f36fcdb] as part of work on CASSANDRA-9608 (Java 11 support) - the patch was very long in the review, so I haven't seen the changes. I'll mark this bug as fixed. > logs directory for gc.log doesn't exist on first start > ------------------------------------------------------ > > Key: CASSANDRA-14142 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14142 > Project: Cassandra > Issue Type: Bug > Components: Configuration > Environment: Unix & Windows environments, when starting freshly > downloaded tarball > Reporter: Alex Ott > Priority: Trivial > Labels: lhf > > This was originally reported at > https://stackoverflow.com/questions/47976248/gc-log-file-error-when-running-cassandra. > This is very minor problem related to timing of 'logs' directory creation - > when Cassandra starts first time, this directory doesn't exist, and created > when Cassandra starts to write system.log & debug.log files. But this > directory is referenced in the -Xloggc command line parameter of JVM, causing > following warning: > {{Java HotSpot(TM) 64-Bit Server VM warning: Cannot open file > bin/../logs/gc.log due to No such file or directory}} > The fix is to check existence of this directory in the cassandra-env, and > create it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org