[Samba] WINBIND failing in 2.2.3

[Noel Kelly (VPN)]

Thanks for the reply Sean.  Yes, I have recompiled those files as well:

-rwxr-xr-x    1 root     root        16224 Feb  6 21:01
/lib/libnss_winbind.so
lrwxrwxrwx    1 root     root           17 Nov 21 15:05
/lib/libnss_winbind.so.2 -> libnss_winbind.so
-rwxr-xr-x    1 root     root       592819 Feb  6 22:52 /lib/libnss_wins.so
-rwxr-xr-x    1 root     root        15486 Feb  6 21:00
/lib/security/pam_winbind.so

    Noel

----- Original Message -----
From: "Sean Trammell" <strammell at siumed.edu>
To: "Noel Kelly (VPN)" <nkelly at tarsus.co.uk>
Sent: Monday, February 11, 2002 12:02 AM
Subject: Re: [Samba] WINBIND failing in 2.2.3


> I had a similar problem, but in my case I had just
> forgotten to replace the 2.2.2 pam module and the 2.2.2
> nsswitch module in /lib and /lib/security with the new
> 2.2.3 versions.  those files were not replaced during
> the install process for me, did you replace them
> manually?  After I recompiled samba and put those two
> files back into place 2.2.3 with winbind started to work
> again instead of dying once a day.
>
> Quoting "Noel Kelly (VPN)" <nkelly at tarsus.co.uk>:
>
> > Hi,
> >
> > I wrote before about a winbind problem I was
> > having with 2.2.3pre and this
> > problem has carried over onto 2.2.3.
> >
> > I am using the same winbindd_idmap.tdb carried
> > over from the original 2.2.2
> > installation.  The log spits out the messages
> > below as users/machines
> > authenticate and about two or three times a day
> > the winbind daemon dies.  It
> > continues to remain in memory and ostensibly
> > functioning but when I do a
> > 'getent passwd' there is no more entries for our
> > main domain (UK).
> > Interestingly the entries for a small trusted
> > domain we have for migration
> > reasons continue to be listed.  Once winbind is
> > killed (-HUP does nothing)
> > and restarted it works fine again.
>