Hi i've got a server with lenny installed on it with samba 3.2.5. My problem is that the var partition is sometimes full. In fact, if i use df command I watch the partition full, but if I use du command the partition is not full. If i use lsof command i see plenty of log samba files into /var/log/samba wich are very big, i have - to kill the process given by lsof associated to log samba file (smbd process) - to restart samba to see the partition not full. Is there a bug with this official version of samba with lenny ? or have you got a solution for me. PS1: i've tried to put log level to 0 into the samba conf file and i've got the same problem PS2: i've got other servers with other versions of samba and debian and i've got no problem.
Quoting Didier Roques (Didier.Roques at brive.unilim.fr):> Hi > i've got a server with lenny installed on it with samba 3.2.5. > > My problem is that the var partition is sometimes full. In fact, if i use > df command I watch the partition full, but if I use du command the > partition is not full. > If i use lsof command i see plenty of log samba files into /var/log/samba > wich are very big, i have > - to kill the process given by lsof associated to log samba file (smbd > process) > - to restart samba > to see the partition not full. > > Is there a bug with this official version of samba with lenny ? or have > you got a solution for me.Well, the default settings in Debian for logging are: # This tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Cap the size of the individual log files (in KiB). max log size = 1000 # If you want Samba to only log through syslog then set the following # parameter to 'yes'. # syslog only = no # We want Samba to log a minimum amount of information to syslog. Everything # should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log # through syslog you should set the following parameter to something higher. syslog = 0 So, in short, there shuold be one log fie per client and it is limited to 1MiB size. The log level is Samba's defautl log level, hence '0', which is not verbose at all. So, with these default settings, there is a good reason to have many log files (in case you have many clients...) but not big files and I fails to see how this would fill up a reasonably sized /var partition. You should check "log level" in your smb.conf,file
On 02/18/2010 05:14 AM, Didier Roques wrote:> Hi > i've got a server with lenny installed on it with samba 3.2.5. > > My problem is that the var partition is sometimes full. In fact, if i use > df command I watch the partition full, but if I use du command the > partition is not full. > If i use lsof command i see plenty of log samba files into /var/log/samba > wich are very big, i have > - to kill the process given by lsof associated to log samba file (smbd > process) > - to restart samba > to see the partition not full. > > Is there a bug with this official version of samba with lenny ? or have > you got a solution for me.I have seen this problem with samba-3.2.3 at a large site. It would strike once every two months or so, when it happened an 80GB /var/log/samba partition would fill up in 1 or 2 minutes. We never got to the bottom of this, the problem has not reappeared since the site moved to samba-3.3.4. My advice is to update to 3.4.5 or later. - John T.