Red Hat Summit12.4. Configuring the Log Level
Every log message has a log level associated with it. The levels, in descending order, are CRITICAL, ERROR, WARNING, INFO, DEBUG, and TRACE. Red Hat Gluster Storage can be configured to generate log messages only for certain log levels. Only those messages that have log levels above or equal to the configured log level are logged.
For example, if the log level is set to
INFO, only CRITICAL, ERROR, WARNING, and INFO messages are logged.
The components can be configured to log at one of the following levels:
- CRITICAL
- ERROR
- WARNING
- INFO
- DEBUG
- TRACE
Important
Setting the log level to TRACE or DEBUG generates a very large number of log messages and can lead to disks running out of space very quickly.
To configure the log level on bricks
# gluster volume set VOLNAME diagnostics.brick-log-level <value>
Example 12.7. Set the log level to warning on a brick
# gluster volume set testvol diagnostics.brick-log-level WARNING
To configure the syslog level on bricks
# gluster volume set VOLNAME diagnostics.brick-sys-log-level <value>
Example 12.8. Set the syslog level to warning on a brick
# gluster volume set testvol diagnostics.brick-sys-log-level WARNING
To configure the log level on clients
# gluster volume set VOLNAME diagnostics.client-log-level <value>
Example 12.9. Set the log level to error on a client
# gluster volume set testvol diagnostics.client-log-level ERROR
To configure the syslog level on clients
# gluster volume set VOLNAME diagnostics.client-sys-log-level <value>
Example 12.10. Set the syslog level to error on a client
# gluster volume set testvol diagnostics.client-sys-log-level ERROR
To configure the log level for
glusterd persistently
Edit the
/etc/sysconfig/glusterd file, and set the value of the LOG_LEVEL parameter to the log level that you want glusterd to use.
## Set custom log file and log level (below are defaults) #LOG_FILE='/var/log/glusterfs/glusterd.log' LOG_LEVEL='VALUE'
This change does not take effect until glusterd is started or restarted with the
service or systemctl command.
Example 12.11. Set the log level to WARNING on glusterd
In the
/etc/sysconfig/glusterd file, locate the LOG_LEVEL parameter and set its value to WARNING.
## Set custom log file and log level (below are defaults) #LOG_FILE='/var/log/glusterfs/glusterd.log' LOG_LEVEL='WARNING'
Then start or restart the glusterd service. On Red Hat Enterprise Linux 7, run:
# systemctl restart glusterd.service
On Red Hat Enterprise Linux 6, run:
# service glusterd restart
To run a gluster command once with a specified log level
# gluster --log-level=ERROR VOLNAME COMMAND
Example 12.12. Run volume status with a log level of ERROR
# gluster --log-level=ERROR volume status
