Samba 3.2.3 has a memory leak that vanishes by upgrading to 3.2.5

[ivelo]

Binary package hint: samba

Running Intrepid Ibex Kubuntu 8.10. Window system fluxbox. Samba version 3.2.3, Vmware 6.5.1. 4gb memory. Intel core2 quad. All the latest software is installed. From the moment upgraded to 8.10 had memory problems. Out-of-Memory killers would work every night. Found Samba 3.2.3 constantly jumping in memory usage. Un-installed Samba. Downloaded Samba 3.2.5 from Samba site. Compiled and installed. Problem is gone.

[Jamie Strandboge (jdstrand)]

Thank you for using Ubuntu and taking the time to report a bug. Can you try the updated version that was fixed in http://www.ubuntu.com/usn/USN-680-1?

[ivelo (mark-temple)]

Jamie,

Here is the dpkg.log entry when I installed/upgraded to that version. It
 did not fix the problem (and I must say I have spent a lot of time
finding this memory leak and then the solution). It was with much
sadness of heart that I left the "Ubuntu way" for a "tar-ball-of-old":

29291 2008-11-27 10:43:51 configure samba-common 2:3.2.3-1ubuntu3.3
2:3.2.3-1ubuntu3.3
29292 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
29293 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
29294 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
29295 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
29296 2008-11-27 10:43:51 status half-configured samba-common
2:3.2.3-1ubuntu3.3
29297 2008-11-27 10:43:52 status installed samba-common 2:3.2.3-1ubuntu3.3
29298 2008-11-27 10:43:52 configure samba 2:3.2.3-1ubuntu3.3
2:3.2.3-1ubuntu3.3
29299 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
29300 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
29301 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
29302 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
29303 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
29304 2008-11-27 10:43:52 status half-configured samba 2:3.2.3-1ubuntu3.3
29305 2008-11-27 10:43:54 status installed samba 2:3.2.3-1ubuntu3.3

Jamie Strandboge wrote:
> Thank you for using Ubuntu and taking the time to report a bug. Can you
> try the updated version that was fixed in
> http://www.ubuntu.com/usn/USN-680-1?
>
> ** Changed in: samba (Ubuntu)
> Assignee: (unassigned) => Jamie Strandboge (jdstrand)
> Status: New => Incomplete
>

--
|______________________________________________________
| Mark Temple
|
| Notice: This email is for use by the named recipient.
| Sender strictly prohibits any other use.
|

[ivelo (mark-temple)]

I'm running Samba 2:3.2.3-1ubuntu3.3 on a server:

Linux frodo 2.6.27-7-server #1 SMP Thu Oct 30 05:04:11 UTC 2008 i686
GNU/Linux

and I do not have this problem.

Mark Temple wrote:
> Jamie,
>
> Here is the dpkg.log entry when I installed/upgraded to that version. It
> did not fix the problem (and I must say I have spent a lot of time
> finding this memory leak and then the solution). It was with much
> sadness of heart that I left the "Ubuntu way" for a "tar-ball-of-old":
>
> 29291 2008-11-27 10:43:51 configure samba-common 2:3.2.3-1ubuntu3.3
> 2:3.2.3-1ubuntu3.3
> 29292 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
> 29293 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
> 29294 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
> 29295 2008-11-27 10:43:51 status unpacked samba-common 2:3.2.3-1ubuntu3.3
> 29296 2008-11-27 10:43:51 status half-configured samba-common
> 2:3.2.3-1ubuntu3.3
> 29297 2008-11-27 10:43:52 status installed samba-common 2:3.2.3-1ubuntu3.3
> 29298 2008-11-27 10:43:52 configure samba 2:3.2.3-1ubuntu3.3
> 2:3.2.3-1ubuntu3.3
> 29299 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
> 29300 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
> 29301 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
> 29302 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
> 29303 2008-11-27 10:43:52 status unpacked samba 2:3.2.3-1ubuntu3.3
> 29304 2008-11-27 10:43:52 status half-configured samba 2:3.2.3-1ubuntu3.3
> 29305 2008-11-27 10:43:54 status installed samba 2:3.2.3-1ubuntu3.3
>
>
> Jamie Strandboge wrote:
>> Thank you for using Ubuntu and taking the time to report a bug. Can you
>> try the updated version that was fixed in
>> http://www.ubuntu.com/usn/USN-680-1?
>>
>> ** Changed in: samba (Ubuntu)
>> Assignee: (unassigned) => Jamie Strandboge (jdstrand)
>> Status: New => Incomplete
>>
>

--
|______________________________________________________
| Mark Temple
|
| Notice: This email is for use by the named recipient.
| Sender strictly prohibits any other use.
|

[Jamie Strandboge (jdstrand)]

Mark,

Based on your last comment, it seems that this should be marked 'Fix Released'. Can you confirm?

[ivelo (mark-temple)]

Jamie,

There is not problem on the Ubuntu 8.10 server with Samba
3.2.3-1Ubuntu... and network mounted shares. However, that system is not
using shares accessed by Vmware 6.5.1 and Windows XP. In my opinion
there is still a problem with Samba 3.2.3-1Ubuntu... in the workstation
context where Vmware shares are concerned. I believe that when
Vmware/Windows XP mounts shares from Samba 3.2.3-1Ubuntu a memory leak
occurs. This memory leak does not occur with the same context and Samba
3.2.5 installed. I do not have the resources to give greater details to
this problem, but for me, in the latter context, I cannot use Samba
3.2.3-1Ubuntu... without having a memory leak problem.

Jamie Strandboge wrote:
> Mark,
>
> Based on your last comment, it seems that this should be marked 'Fix
> Released'. Can you confirm?
>

--
|______________________________________________________
| Mark Temple
|
| Notice: This email is for use by the named recipient.
| Sender strictly prohibits any other use.
|

[ivelo (mark-temple)]

Jamie,

Here is an update:

I noticed that there is a new Samba package in the repository. I
installed it per this dpkg.log entry:

2008-12-06 08:59:20 status installed samba 2:3.2.3-1ubuntu3.3

By 13:02 my system was locked up from OOM. Here is the syslog entry:

Dec 6 12:38:35 velo kernel: [769372.951847] postgres invoked
oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0

I'm back on Samba 3.2.5

root@velo:/var/log# smbd -V
Version 3.2.5

I ran all last week with no OOM errors on Samba 3.2.5 (how refreshing).

It still has a problem.

Jamie Strandboge wrote:
> Mark,
>
> Based on your last comment, it seems that this should be marked 'Fix
> Released'. Can you confirm?
>

--
|______________________________________________________
| Mark Temple
|
| Notice: This email is for use by the named recipient.
| Sender strictly prohibits any other use.
|

[Jamie Strandboge (jdstrand)]

Marking as new so the bug doesn't auto-close. Unassigning myself since this doesn't seem to be related to a security update.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. May you please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Steve Langasek (vorlon)]

marking as fixed for jaunty.