Description of problem: ======================= The logger time is by default configured to GMT. While the system will be configured based on the GEO. If IST, there's a lag of 5.5hrs which is creating confusion during error time mapping. This bug is to set the logger time in sync with the system time irrespective of the timezone. Version-Release number of selected component (if applicable): ============================================================= [root@vertigo ~]# gluster --version glusterfs 3.7dev built on Mar 12 2015 01:40:59 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@vertigo ~]# Log snippet: ============ [root@vertigo ~]# date Mon Mar 16 11:56:31 IST 2015 [root@vertigo ~]# tail -f /var/log/glusterfs/nfs.log [2015-03-16 06:19:12.844787] W [client-rpc-fops.c:2223:client3_3_create_cbk] 0-testvol-client-0: remote operation failed: Stale file handle. Path: <gfid:02c36e72-0e77-473c-b488-33a919358dbb>/1 [2015-03-16 06:19:12.844847] W [client-rpc-fops.c:2223:client3_3_create_cbk] 0-testvol-client-2: remote operation failed: Stale file handle. Path: <gfid:02c36e72-0e77-473c-b488-33a919358dbb>/1 [2015-03-16 06:19:12.845754] W [ec-common.c:162:ec_check_status] 0-testvol-disperse-0: Operation failed on some subvolumes (up=FFF, mask=FFA, remaining=0, good=FFA, bad=5)
The time in the logs are UTC, this helps enormously with geo-replication logs that come from different timezones. It also is the standard for most other enterprise storage systems. Because this topic comes up regularly, we should think about providing a configuration option that can be used to set the timezone of the logs.
Migrated to github: https://github.com/gluster/glusterfs/issues/559 Please follow the github issue for further updates on this bug.