Bug 5936 - winbind occassionally loses its trust - restart fixes
winbind occassionally loses its trust - restart fixes
Status: NEW
Product: Samba 3.2
Classification: Unclassified
Component: Winbind
3.2.4
Other Linux
: P3 normal
: ---
Assigned To: Michael Adam
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-12-03 23:13 UTC by Jason Haar
Modified: 2009-05-13 03:54 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Haar 2008-12-03 23:13:39 UTC
Hi there

I'm running FC10 on a laptop and have gone the whole hog and log in using pam_winbind. i.e the laptop is an Win2K3 Active Directory member, and I login using a winbind-created account instead of a true "local" one.

Anyway, a couple of times (since I installed last week) I've found myself unable to unlock the screensaver - syslog showed

Dec  4 15:47:56 tnz-jhaar-dell gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): request failed: No trusted SAM account, PAM error was System error (4), NT error was NT_STATUS_NO_TRUST_SAM_ACCOUNT

Sure enough, logging in as root (as I couldn't login as myself) and running "wbinfo -t" showed it had lost it's trust.

Restarting winbind fixes the problem.

I'd guess the "off again on again" nature of my laptop's network connection is tickling some bug you don't normally see on a server - which has a more stable, permanent network connection.

If anyone picks this bugreport up, I'm happy to turn on debugging,etc to help track it down. I'm sure I'm going to be seeing this quite routinely from now on, as I so pleased I can use a laptop like a Windows user (gasp!) that I'm not giving up on it ;-)

Jason