Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > I installed these packages from sid this morning, onto > an otherwise squeeze based system: > > samba-common2:3.5.6~dfsg-4 > samba-common-bin2:3.5.6~dfsg-4 > libwbclient02:3.5.6~dfsg-4 >

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

I installed these packages from sid this morning, onto an otherwise squeeze based system: samba-common2:3.5.6~dfsg-4 samba-common-bin2:3.5.6~dfsg-4 libwbclient02:3.5.6~dfsg-4 winbind 2:3.5.6~dfsg-4 I c

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > On Mon, Jan 3, 2011 at 2:37 AM, Christian PERRIER wrote: > > > > > Eh, that's really strange, but thanks for the detailed investigation. > > > > Could you check whether you still experience the bug with the > > 3.5.6~dfsg-3 packages? I suppose this is in

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Mon, Jan 3, 2011 at 2:37 AM, Christian PERRIER wrote: > > Eh, that's really strange, but thanks for the detailed investigation. > > Could you check whether you still experience the bug with the > 3.5.6~dfsg-3 packages? I suppose this is indeed what you're doing > right now... > > I'm afraid the

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Leaving your full answer so that it's logged to the bug report, too. Quoting D G Teed (donald.t...@gmail.com): > On Sun, Jan 2, 2011 at 2:22 AM, Christian PERRIER wrote: > > > > > Coming back on this bug report again. > > > > I had more discussion with samba upstream and they pointed me to > > ht

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > On Wed, Dec 8, 2010 at 10:02 PM, Russ Allbery wrote: > > > > > > > I'll reassign it. I wanted to see if anyone disagreed with me first. :) > > > > -- > > Russ Allbery (r...@debian.org) > >

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

forcemerge 574468 606350 thanks Quoting D G Teed (donald.t...@gmail.com): > On Wed, Dec 22, 2010 at 2:05 AM, Christian PERRIER wrote: > > > > > > > Did you have any chance to test the amd64 packages I poointed you to? > > > > This fix is a good candidate for squeeze but I would like to have > > s

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 22, 2010 at 2:05 AM, Christian PERRIER wrote: > > > Did you have any chance to test the amd64 packages I poointed you to? > > This fix is a good candidate for squeeze but I would like to have > success reports before requesting a freeze exception to the release team. > I've tested the

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER wrote: > > > > > Hello, > > > > On > > http://people.debian.org/~bubulle/samba-test/, > > you'll soon find > > packages which you may want to try. I just

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER wrote: > > > > > Hello, > > > > On > > http://people.debian.org/~bubulle/samba-test/, > > you'll soon find > > packages which you may want to try. I just

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

D G Teed a écrit : On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER > wrote: Hello, On http://people.debian.org/~bubulle/samba-test/ , you'll soon find packages which you may want to try. I just appl

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Thu, Dec 9, 2010 at 5:00 PM, Christian PERRIER wrote: > > Hello, > > On > http://people.debian.org/~bubulle/samba-test/, > you'll soon find > packages which you may want to try. I just applied the patch from > Samba's Bugzilla and recompiled the

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery wrote: > > > > > Looks like a file descriptor leak in pam_winbind. I think saslauthd isn't > > at fault here. > > > > > I did a test today... I noticed the number of fds had grown overnight by > 20 to 40 pe

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery wrote: > > Looks like a file descriptor leak in pam_winbind. I think saslauthd isn't > at fault here. > > I did a test today... I noticed the number of fds had grown overnight by 20 to 40 per process. I did a restart of winbind and looked at the fd

Bug#606350: [Pkg-samba-maint] Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Quoting D G Teed (donald.t...@gmail.com): > This might be the same as the samba bug reported upstream against Debian 5: > https://bugzilla.samba.org/show_bug.cgi?id=7265<%20https://bugzilla.samba.org/show_bug.cgi?id=7265> > > That is showing a bug against samba 3.4, however it is > status NEW, fr

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 10:02 PM, Russ Allbery wrote: > > > I'll reassign it. I wanted to see if anyone disagreed with me first. :) > > -- > Russ Allbery (r...@debian.org) > > > > This might be the same as the samba bu

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

severity 606350 important reassign 606350 winbind retitle 606350 Possible file descriptor leak in pam_winbind thanks D G Teed writes: > On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery wrote: >> D G Teed writes: >>> I also count 200 connections like this: >>> unix 3 [ ] STREAM C

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 5:53 PM, Russ Allbery wrote: > D G Teed writes: > > > I also count 200 connections like this: > > > unix 3 [ ] STREAM CONNECTED 39854981 > > /var/run/samba/winbindd_privileged/pipe > > > Most users are simply using port 25 and would not be authenticat

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

D G Teed writes: > I also count 200 connections like this: > unix 3 [ ] STREAM CONNECTED 39854981 > /var/run/samba/winbindd_privileged/pipe > Most users are simply using port 25 and would not be authenticating, > so I know these numbers cannot be current connections. Look

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On Wed, Dec 8, 2010 at 4:23 PM, Dan White wrote: > On 08/12/10 15:33 -0400, D G Teed wrote: > >> Here is what one of the directories looked like: >> >> ls -l 15950/fd >> >> total 0 >> lrwx-- 1 root root 64 Dec 8 13:52 0 -> /dev/null >> lrwx-- 1 root root 64 Dec 8 13:52 1 -> /dev/null >>

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On 08/12/10 15:33 -0400, D G Teed wrote: Here is what one of the directories looked like: ls -l 15950/fd total 0 lrwx-- 1 root root 64 Dec 8 13:52 0 -> /dev/null lrwx-- 1 root root 64 Dec 8 13:52 1 -> /dev/null lrwx-- 1 root root 64 Dec 7 15:47 10 -> socket:[38109596] lrwx--

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

On 08/12/10 09:20 -0400, dteed wrote: This is working fine - users can authenticate against Active Directory when sending email over secure ports 465 and 587 on Postfix. Once every two weeks or so, saslauthd requires a restart to fix a failure to authenticate. Nothing else needs to be touched t

Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart

Package: sasl2-bin Version: 2.1.23.dfsg1-6 Severity: critical Justification: breaks unrelated software Using saslauthd in support of secure SMTP with postfix. saslauthd is configured to use pam. /etc/pam.d/smtp looks like this: account requiredpam_permit.so authsufficientpam