Bug 1009726

Summary: Samba vfs plug-in log file in /var/log/samba/<logfile> getting overwritten after it reaches to maximum size
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Lalatendu Mohanty <lmohanty>
Component: sambaAssignee: Poornima G <pgurusid>
Status: CLOSED NOTABUG QA Contact: Lalatendu Mohanty <lmohanty>
Severity: high Docs Contact:
Priority: unspecified    
Version: 2.1CC: sdharane, spalai, vagarwal
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 2.1.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-16 08:40:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lalatendu Mohanty 2013-09-19 02:03:27 UTC 
Description of problem:

Samba vfs plug-in log file in /var/log/samba/glusterfs-<volname>.log getting overwritten after it reaches to certain size (may be 100MB) where it should have been archived.

Version-Release number of selected component (if applicable):

rpm -qa | grep 'glusterfs\|samba'
samba-doc-3.6.9-160.3.el6rhs.x86_64
glusterfs-fuse-3.4.0.33rhs-1.el6rhs.x86_64
samba-winbind-3.6.9-160.3.el6rhs.x86_64
samba-glusterfs-3.6.9-160.3.el6rhs.x86_64
samba-swat-3.6.9-160.3.el6rhs.x86_64
samba-winbind-krb5-locator-3.6.9-160.3.el6rhs.x86_64
samba-domainjoin-gui-3.6.9-160.3.el6rhs.x86_64
glusterfs-libs-3.4.0.33rhs-1.el6rhs.x86_64
glusterfs-geo-replication-3.4.0.33rhs-1.el6rhs.x86_64
glusterfs-server-3.4.0.33rhs-1.el6rhs.x86_64
glusterfs-api-3.4.0.33rhs-1.el6rhs.x86_64
samba-common-3.6.9-160.3.el6rhs.x86_64
samba-3.6.9-160.3.el6rhs.x86_64
samba-client-3.6.9-160.3.el6rhs.x86_64
samba-winbind-devel-3.6.9-160.3.el6rhs.x86_64
glusterfs-3.4.0.33rhs-1.el6rhs.x86_64
samba4-libs-4.0.0-55.el6.rc4.x86_64
glusterfs-rdma-3.4.0.33rhs-1.el6rhs.x86_64
samba-winbind-clients-3.6.9-160.3.el6rhs.x86_64


How reproducible:

Always

Steps to Reproduce:
1. 
2.
3.

Actual results:

As mentioned the log file is getting overwritten and the older logs are lost. The size of the log file becomes 0KB and again grows as the logging happens.

Expected results:

We should be renaming the old log file to .old or something if it reaches to limit of maximum size

Additional info:
Comment 3 Poornima G 2013-10-15 05:27:38 UTC 
The logrotate policy ("max log size") specified in smb.conf applies to the log files: log.<client addr>, log.smbd 

/var/log/samba/glusterfs-<volname>.log is not affected by the "max log size" entry in smb.conf and gluster also doesn't have any logrotate policy for /var/log/samba/glusterfs-<volname>.log.

But apart from "max log size" configuration, samba by default has a weekly logrotate policy, where all the files  in /var/log/samba/* are rotated(moved) to /var/log/samba/old/*.

In this case, it could be that /var/log/samba/glusterfs-<volname>.log was moved to /var/log/samba/old/* as a part of samba weekly logrotate, and hence a 0 sized /var/log/samba/glusterfs-<volname>.log was created.
Comment 4 Lalatendu Mohanty 2013-10-16 08:40:12 UTC 
Agree with Poornima's findings, hence closing the bug as not a defect.