Hi GlusterFS users,<br><br>I'm looking for the proper way to manage GlusterFS 3.3 logs.<br><br>First, I'd like to centralize all logs coming from GlusterFS. I read posts mentioning syslog support in this mailing-list archives. I tried a few volume options like "sys-log-level" or "[client|brick].syslog-level", but the gluster cli command says these options doesn't exist.<br>
<br>Reading libglusterfs/src/logging.c, I see that if GF_LINUX_HOST_OS is defined, calls to openlog/syslog will be made. Since I naively built GlusterFS myself, is there something I missed to ensure that GF_LINUX_HOST_OS is defined ?<br>
The only thing I'm sure about is I can't find any occurence of "GlusterFS" in messages received by syslogd.<br><br>I would also like to know how to define the log location of individual bricks. Currently, glusterd forks glusterfsd processes for each brick with "-l /path/to/a/default/location/brick-path.log". I tried to define a custom path using "gluster volume log filename volname /path/to/logs" but the option isn't recognized ("unrecognized word: filename"). What's strange is the manpage talks about "volume log filename" and "volume log locate" while the command line tool only knows about "volume log rotate":<br>
# gluster volume help | grep '^volume log '<br>volume log rotate <VOLNAME> [BRICK] - rotate the log file for corresponding volume/brick<br><br>Thanks for your help!<br><br>Philippe<br>