Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-14142

logs directory for gc.log doesn't exist on first start

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 4.0-alpha1, 4.0
    • Local/Config
    • Unix & Windows environments, when starting freshly downloaded tarball

    • Low

    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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              alexott Alex Ott
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 10m
                  10m