saslauthd eats memory

Ken Murchison murch at andrew.cmu.edu
Wed Apr 5 10:50:36 EDT 2006


Gyorgy Knyihar wrote:
> Hello,
> 
> I installed the cyrus-sasl rpm package on my Mandriva 2006.0.
> The server is used by hundreds of users. I use pam authentication mechanism.
> My problem is that saslauthd eats up the memory of the server. After a few weeks
> run it ate 1GB of memory wich caused serious problems. After two days run top
> shows the following:
> 
> top - 15:54:02 up 36 days,  4:13,  4 users,  load average: 0.57, 0.45, 0.37
> Tasks: 167 total,   1 running, 166 sleeping,   0 stopped,   0 zombie
> Cpu(s):  0.2% us,  0.2% sy,  0.0% ni, 99.1% id,  0.4% wa,  0.0% hi,  0.0% si
> Mem:   2074604k total,  1953120k used,   121484k free,   497444k buffers
> Swap:  4241384k total,    61272k used,  4180112k free,   390548k cached
> 
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 11594 root      16   0  128m 125m 1056 S  0.0  6.2   0:31.94 saslauthd
> 11595 root      15   0  127m 124m 1056 S  0.0  6.1   0:31.61 saslauthd
> 11596 root      15   0  124m 121m 1056 S  0.0  6.0   0:30.77 saslauthd
> 11597 root      15   0  126m 123m 1056 S  0.0  6.1   0:31.40 saslauthd
> 11598 root      15   0  127m 124m 1056 S  0.0  6.2   0:31.65 saslauthd
> 
> [root at srv1 /]# ps -ef | grep sasl
> root     11594     1  0 Apr03 ?        00:00:31 saslauthd -s 10240 -a pam
> root     11595 11594  0 Apr03 ?        00:00:31 saslauthd -s 10240 -a pam
> root     11596 11594  0 Apr03 ?        00:00:30 saslauthd -s 10240 -a pam
> root     11597 11594  0 Apr03 ?        00:00:31 saslauthd -s 10240 -a pam
> root     11598 11594  0 Apr03 ?        00:00:31 saslauthd -s 10240 -a pam
> root      7236 22891  0 15:54 pts/1    00:00:00 grep sasl
> 
> I have the following packages installed:
> 
> libsasl2-plug-login-2.1.22-11mdk
> libsasl2-2.1.22-11mdk
> libsasl2-plug-digestmd5-2.1.22-11mdk
> cyrus-sasl-2.1.22-11mdk
> libsasl2-plug-plain-2.1.22-11mdk
> libsasl2-devel-2.1.22-11mdk
> 
> Could you please advise?

Its a very good bet that your PAM module(s) leak memory.

-- 
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University


More information about the Cyrus-sasl mailing list