Red Hat Bugzilla – Bug 764776
provide option to set syslog loglevel through CLI
Last modified: 2015-12-01 11:45:32 EST
currently all the CRITICAL logs goes to syslog, but there is no option for admin to change that to send everything from 'WARNING' to send to syslog. Need that option in CLI.
Junaid, lets talk on implementation details when ever you pick up this bug.
PATCH: http://patches.gluster.com/patch/7667 in master (libglusterfs/logging: Added functions to set sys-log-level.)
PATCH: http://patches.gluster.com/patch/7628 in master (mgmt/glusterd: Make glusterd aware of sys-log-level options.)
PATCH: http://patches.gluster.com/patch/7629 in master (debug/io-stats: Added sys-log-level option.)
Its works now. Set the sys log level for the bricks to WARNING.
gluster volume set <volname> brick-log-level WARNING. Ran posix compliance test on the mount point (which tries to create files with filename exceeding the maximum limit). File /var/log/messages had the error logs of glusterfsd.
Sep 16 06:39:56 Centos1 GlusterFS: [2011-09-16 06:39:56.127213] E [posix.c:129:posix_lookup] 0-mirror-posix: lstat on /_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345 failed: File name too long