Set Up Logging

Before you begin, make sure you understand Basic Configuration and Programming.
  1. Run a time synchronization service such as NTP on all GemFire host machines. This is the only way to produce logs that are useful for troubleshooting. Synchronized time stamps ensure that log messages from different hosts can be merged to accurately reproduce a chronological history of a distributed run.
  2. Use a sniffer to monitor your logs and, if you begin seeing new or unexpected warnings, errors, or severe messages, contact VMware technical support. The logs output by your system have their own characteristics, indicative of your system configuration and of the particular behavior of your applications, so you must become familiar with your applications' logs to use them effectively.
  3. Configure logging in the as needed:
    # Default log file settings

    1. Set log-level. Options are severe (the highest level), error, warning, info, config, and fine. The lower levels include higher level settings, so a setting of warning would log warning, error, and severe messages. For general troubleshooting, set the level at info or higher.
      Note: The fine setting can fill up disk too quickly and impact system performance. Use fine only if asked to do so by VMware technical support.
    2. Specify the log file name in log-file. This can be relative or absolute. Defaults are:
      • Standard output for applications
      • cacheserver.log for the cacheserver
      • locator.log for the standalone locator and the member’s log file for the colocated locator.
      For the easiest logs examination and troubleshooting, send your logs to files instead of standard out.
      Note: Make sure each member logs to its own files. This makes the logs easier to decipher.
    3. Set the maximum size of a single log file in log-file-size-limit. If not set, the single, main log file is used. If set, the metadata file, the main log, and rolled child logs are used.
    4. Set the maximum size of all log files in log-disk-space-limit. If non-zero, this limits the combined size of all inactive log files, deleting oldest files first to stay under the limit. A zero setting indicates no limit.