AW: winbind 3.3.7 memory usage

Dr. Hansjoerg Maurer hansjoerg.maurer at itsd.de
Thu Oct 8 00:41:33 MDT 2009


Hi Mr Daugherty

the problem occurs on RHEL4 and RHEL5 (or CentOS), both x86_64.
On a 32 bit testmachine, it seems no problem, 
which may also be related, that nobody is workin on it

Here the i386 Plattform
[root at rmvrhli3-ha ~]# uname -a
Linux rmvrhli3-ha.robotic.dlr.de 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:19:18 EDT 2009 i686 i686 i386 GNU/Linux
[root at rmvrhli3-ha ~]# psgrep winbind
root     25180  0.0  0.4 197472  4936 ?        Ss   Aug20   4:51 winbindd
root     25181  0.0  0.7 197248  7196 ?        S    Aug20   0:49 winbindd
root     25184  0.0  0.5  19788  5172 ?        S    Aug20   1:13 winbindd
root     25282  0.0  0.1  15612  1388 ?        S    Aug20   0:03 winbindd
root     27862  0.0  0.2  16128  2060 ?        S    08:33   0:00 winbindd
root     27863  0.0  0.1  16128  1904 ?        S    08:33   0:00 winbindd
root     27864  0.0  0.4  16360  4668 ?        S    08:33   0:00 winbindd
root     27961  1.0  0.4 197604  4136 ?        S    08:39   0:00 winbindd




Here the x86_64 Plattform
[root at rmcs31 ~]# uname -a
Linux rmcs31 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
[root at rmcs31 ~]# psgrep winbind
root     10654  0.0  0.2 303984  9204 ?        Ss   Aug26   2:56 winbindd
root     10655  0.0  0.4 356824 20120 ?        S    Aug26   1:57 winbindd
root     10669  0.0 27.3 5387512 1104628 ?     S    Aug26  29:39 winbindd
root     10670  0.0  0.0 302884   748 ?        S    Aug26   0:01 winbindd
root     10751  0.0  0.0 302896   364 ?        S    Aug26   0:00 winbindd
root     10769  0.0  0.0 304888   636 ?        S    Aug26   0:00 winbindd


Regards

Hansjörg


----- Originalnachricht -----
Von: Dave Daugherty <dave.daugherty at centrify.com>
Gesendet: Mit, 7.10.2009 19:41
An: Dr. Hansjoerg Maurer <hansjoerg.maurer at itsd.de> ; Danilo Almeida <dalmeida at likewise.com> ; Volker.Lendecke at SerNet.DE
Cc: samba-technical at lists.samba.org
Betreff: RE: winbind  3.3.7 memory usage

Dr. Maurer,

May I ask what OS platform and version you are running Samba on?  I see glibc_2.2.5 in the stack trace.

It seems a little odd that getgrnam_r would be allocating memory, since it is given a buffer to stuff things into.  

We also use this function and I would like to test ourselves.

Regards,

Dave Daugherty
Centrify Corp.

~~~~~~~~~~~~~

Sent: Tuesday, October 06, 2009 11:55 PM
To: Danilo Almeida; Volker.Lendecke at SerNet.DE
Cc: samba-technical at lists.samba.org
Subject: AW: winbind 3.3.7 memory usage

Hi Danilo,


bingo, very good point.

The unix systems are integrated into AD using Vintella Authentication Services from Quest.
Therefore they use the vas nss module in /etc/nsswitch.conf

Sorry, I did not include this information in the initial mail, but I did not realize,
that this might be relevant.

I will open a call by quest and inform the list, when they find a solution in order to document
the problem.

Thank you very much

Regards

hansjörg

 



----- Originalnachricht -----
Von: Danilo Almeida <dalmeida at likewise.com>
Gesendet: Mit, 7.10.2009 07:32
An: Dr. Hansjoerg Maurer <hansjoerg.maurer at itsd.de> ; Volker.Lendecke at SerNet.DE
Cc: samba-technical at lists.samba.org
Betreff: RE: winbind  3.3.7 memory usage

Hansjörg,

<quote from="Volker">
The only significant memory leak as reported by valgrind is
in the idmap child:

==14502== 83,415 bytes in 4,020 blocks are definitely lost in loss record 61 of 67
==14502==    at 0x4904A06: malloc (vg_replace_malloc.c:149)
==14502==    by 0x3B8E570FF1: strdup (in /lib64/tls/libc-2.3.4.so)
==14502==    by 0x14A71A61: ???
==14502==    by 0x14A7EBA4: ???
==14502==    by 0x14A85CAC: ???
==14502==    by 0x14A864F0: ???
==14502==    by 0x14A81CAD: ???
==14502==    by 0x147C51A7: ???
==14502==    by 0x147C7294: ???
==14502==    by 0x3B8E58E75E: getgrnam_r@@GLIBC_2.2.5 (in /lib64/tls/libc-2.3.4.so)
==14502==    by 0x3B8E58DDBE: getgrnam (in /lib64/tls/libc-2.3.4.so)
==14502==    by 0x391938: ??? (idmap_nss.c:189)
==14502==    by 0x387E72: idmap_backends_sid_to_unixid (idmap.c:785)
==14502==    by 0x388F0C: idmap_sid_to_gid (idmap_util.c:259)
==14502==    by 0xBFBE7: winbindd_dual_sid2gid (winbindd_idmap.c:374)
==14502==    by 0xB71B8: ??? (winbindd_dual.c:453)
==14502==    by 0xB7971: ??? (winbindd_dual.c:214)
==14502==    by 0xB7E2E: ??? (winbindd_dual.c:189)
==14502==    by 0x1445CB: run_events (events.c:233)
==14502==    by 0x85961: main (winbindd.c:850)

It seems that on your system getgrnam internally leaks
memory. There's nothing Samba can do about this.
</quote>

This might be a nsswitch module.  You might try looking at what modules you have in /etc/nsswitch.conf for groups and see if that might point you in the right direction.  If you have a non-default module, that might be the first one to investigate.

- Danilo



More information about the samba-technical mailing list