[CASSANDRA-14142] logs directory for gc.log doesn't exist on first start

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Local/Config
• Labels: lhf

Environment

Unix & Windows environments, when starting freshly downloaded tarball

• Severity: Low
• Assignee: Unassigned
• Reporter: Alex Ott
• Created: 28/Dec/17 08:51
• Updated: 16/Mar/22 11:24
• Resolved: 21/Oct/18 09:12

Description

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.

Issue Links

• is part of: CASSANDRA-9608 Support Java 11
• links to: GitHub Pull Request #183