Bug 499312

Summary: cannot login on gdm console nor /dev/console after suspend with winbind
Product: [Fedora] Fedora Reporter: Jason Haar <jhaar>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: azelinka, dpal, gdeschner, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 18:13:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 516998    

Description Jason Haar 2009-05-06 04:39:38 UTC
Description of problem:

I have just used the generic FC11 "wizards" to configure my Dell D430 laptop to be a member of our work Active Directory domain, and I login using domain/username. Works well in general

However, on several occasions I have found that after un-suspending (ie low power state - not hibernate) back on my home non-work network (ie winbind needs to rely on its auth cache), I cannot get a login prompt on gdm! i.e X comes back, but hitting ENTER doesn't bring up the screensaver/password screen.

If I then hit Ctrl-Alt-F2, I get the TTY prompt, enter "root", wait ~1minute for the password prompt(???) and then enter the proper password - I get access denied. After 15 minutes it's still like that - so I end up rebooting  - and then everything works.

I'm totally guessing this is due to winbind - but it seems likely. winbind shows the following in syslog - they seem totally appropriate errors to see while off corporate network.

May  6 16:10:38 tnz-jhaar-dell winbindd[1772]: [2009/05/06 16:10:38,  0] libsmb/namequery.c:getlmhostsent(918)
May  6 16:10:38 tnz-jhaar-dell winbindd[1772]:   getlmhostsent: invalid address 127.0.0.1.
May  6 16:10:38 tnz-jhaar-dell winbindd[1772]: [2009/05/06 16:10:38,  0] libsmb/namequery.c:getlmhostsent(918)
May  6 16:10:38 tnz-jhaar-dell winbindd[1772]:   getlmhostsent: invalid address 1.2.3.4.
May  6 16:10:38 tnz-jhaar-dell winbindd[1772]: [2009/05/06 16:10:38,  0] libsmb/namequery.c:getlmhostsent(918)
May  6 16:10:38 tnz-jhaar-dell winbindd[1772]:   getlmhostsent: invalid address 1.2.4.5.



Version-Release number of selected component (if applicable):

samba-winbind-3.3.2-0.33.fc11.i586


How reproducible:


Steps to Reproduce:
1. suspend at work
2. un-suspend at home
3. 
  
Actual results:

no screensaver prompt

Expected results:

password prompt, and that the password actually works.
 

Additional info:

 The fact that the correct root password didn't work on a TTY is weird. /etc/pam.d/system-auth shows PAM is only meant to tickle winbind for uid>500, so why is root being affected by this? Also, there are no failed login errors in syslog - no pam errors, no tty errors - nothing. Not good from an audit trail either?

Comment 1 Guenther Deschner 2009-05-06 14:40:50 UTC
My guess is that a initgroups() call from the operating system iterates over the winbind backend and needs to wait until winbind is able to respond. I need to investigate further though.

Comment 2 Bug Zapper 2009-06-09 15:14:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Jason Haar 2009-11-18 09:43:15 UTC
FYI I have reinstalled FC12 and still have exactly the same problem.

I have opened a ticket with the Samba group, as winbind is the root problem, but pam/whatever could respond better that hanging forever

https://bugzilla.samba.org/show_bug.cgi?id=6103

Comment 4 Fedora Admin XMLRPC Client 2010-10-08 14:43:01 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Jason Haar 2010-10-24 07:11:29 UTC
FYI, still a problem with F13 - and it triggers a regressive (?) problem in nscd too.

If winbind isn't able to talk directly to its domain controllers, then any auth attempt (eg getty, gdm, screensaver, ssh) should come out of cache. F13 uses nscd - so the "cached password" should be kept by it - but I guess (as it doesn't work) it defers to winbind? Anyway, nscd talks to winbind and for whatever reason winbind doesn't return a cached OK and instead tries to talk to the unavailable domain controllers and the whole thing times out - and is then reported up the chain as a bad password. I see very fast "bad password" failures - not long drawn out ones, so I guess that initial timeout is "corrupted" into a bad password failure...

Comment 6 Fedora End Of Life 2012-08-16 18:13:41 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping