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

Christian PERRIER bubulle at debian.org
Mon Jan 3 06:37:22 UTC 2011


Leaving your full answer so that it's logged to the bug report, too.

Quoting D G Teed (donald.teed at gmail.com):
> On Sun, Jan 2, 2011 at 2:22 AM, Christian PERRIER <bubulle at debian.org>wrote:
> 
> >
> > Coming back on this bug report again.
> >
> > I had more discussion with samba upstream and they pointed me to
> > https://bugzilla.samba.org/show_bug.cgi?id=7684 which is a duplicate
> > of #7265.
> >
> > From #7684, the bug is fixed in samba 3.5.6, which reached testing as
> > of Oct 21st  2010.
> >
> > And, indeed, the patch I applied is useless and redundant.
> >
> > So, Donald, your original report doesn't mention which version of
> > winbind was running on your system when you reported #606350 but I
> > somehow suspect it might have been a version lower than 3.5.6. Still,
> > your system is reported to be using testing so it should have been
> > 3.5.6
> >
> > Are you in position to test again with the genuine 3.5.6 version from
> > testing and not the packages I pointed you to? Alternatively, if you
> > confirm that, at the moment you reported this bug, the version fo
> > samba was lower than 3.5.6, then I will close it as fixed in 3.5.6
> >
> >
> The version I had installed from testing was current as of the time of the
> bug report.
> 
> According to the dpkg logs, I had winbind 3.5.6~dfsg-1 installed Oct 26th
> onward,
> until I installed the test packages manually from the
> http://people.debian.org/~bubulle/samba-test/
> location on Dec 22.
> 
> I do remember looking at the /lib/security/ directory prior to installing
> the ~bubulle
> test packages.  I noticed only pam_winbind.so file in /lib/security
> was older than Oct 21.  All other pam library files were dated Oct 21st.
> 
> I can use the index on our backup service as a sort of time machine to
> verify my
> memory of this.
> 
> I can set the time on the backup indexes, to view the file size and
> timestamp.
> In an "ls -l" report as of Dec 1, 2010, I see:
> 
> -rw-r--r-- root            60168 Oct 10 06:54 pam_winbind.so
> 
> All other files in the directory have a time stamp of Oct 21, 14:39
> winbind package was updated to 3.5.6~dfsg-1 according to dpkg logs on Oct
> 26th.
> 
> Right now, if I install winbind and friends from the squeeze repository, I
> get
> a pam_winbind.so dated Dec 7th.  This is from winbind 3.5.6~dfsg-3.
> 
> Perhaps there was a build problem with dfsg-1 and /lib/security/
> pam_winbind.so/
> which is not seen in dfsg-3?
> 
> --Donald

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...


-- 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20110103/2e9b0881/attachment.pgp>


More information about the Pkg-samba-maint mailing list