[ 
https://issues.apache.org/jira/browse/CASSANDRA-14142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305185#comment-16305185
 ] 

ASF GitHub Bot commented on CASSANDRA-14142:
--------------------------------------------

GitHub user alexott opened a pull request:

    https://github.com/apache/cassandra/pull/183

    fix for CASSANDRA-14142

    On the first start of Cassandra JVM complains about absence of 
`${CASSANDRA_HOME}/logs/gc.log` file.
    
    This pull request fixes this issue - cassandra-env scripts now check for 
existence of the 'logs' directory and create it if it doesn't exist.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alexott/cassandra CASSANDRA-14142

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cassandra/pull/183.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #183
    
----
commit 11a3f90e705c66e2d344b34fe2d31e6327819895
Author: Alex Ott <alexott@...>
Date:   2017-12-28T08:52:55Z

    fix for CASSANDRA-14142
    
    cassandra-env scripts now check for existence of the 'logs' directory and 
create it if it
    doesn't exist.

----


> 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
>
> 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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to