You configure logging in a member's gemfire.properties or at startup with
Before you begin, make sure you understand Basic Configuration and Programming
- 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
- 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.
- Configure member logging in each member's
gemfire.properties as needed:
# Default gemfire.properties log file settings
You can also specify logging parameters when you start up members (either
locators or servers) using the gfsh
command-line utility. See start
commands for various examples. In addition, you can modify log
file properties and log-level settings while a member is already running by using
the alter runtime
- 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, we
recommend setting the log level at config 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.
- Specify the log file name in
log-file. This can be relative or absolute. If this
property is not specified, the defaults are:
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.
- 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
- 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.
- If you are using the gfsh
command-line interface, gfsh creates its own log file in the
directory where you run the gfsh or gfsh.bat script.
By default, these log files are named
where YYYY-MM-DD_HH-MM-SS corresponds to the
local date and timestamp of when you started the gfsh terminal