[Bug 1764853] Re: winbind returns PAM_AUTHINFO_UNAVAIL on first login after reboot

[msaxl]

Yes, I think a version between 16.04 and 18.04 added this (Don't
remember what version).

If someone installs libnss-resolve it will modify nsswitch
automatically.

I think we can close this ticket since it does not apply to a default configuration.
Also I think /etc/hosts is not empty by default but still contains localhost and hostname.
Just keep in mind that myhostname would also allow removing localhost and hostname from /etc/hosts. I expect ubuntu to do that at some point in the future.
In that case installing libnss-resolve could make problems that are not easy to track.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1764853

Title:
  winbind returns PAM_AUTHINFO_UNAVAIL on first login after reboot

Status in samba package in Ubuntu:
  Incomplete

Bug description:
  The following issue exists only on Ubuntu 18.04

  I've upgraded ubuntu from 17.10 and noticed that winbind does not work well.
  90% of the time I reboot my system I'm getting PAM_AUTHINFO_UNAVAIL when trying to log in with a domain account.
  clicking login again on the login screen most of the time succeeds (so the password is correct)

  I've checked if it works if I wait 10 minutes before logging in, no success, so it is not a timing issue.
  Also I've checked if winbind is working (log in with ssh using a local account)
  getent passwd xy and wbinfo -K user%pwd both work always.

  Now my workaround is putting
  winbind request timeout = 3
  in smb.conf, since the PAM_AUTHINFO_UNAVAIL is returned about 60sec after trying to login. This workaround solves nothing, it only makes logging in faster. (But now it fails mostly two times, but waiting 6 seconds is better than 60)

  To me it seems like deadlock, but I was unable to track it since it
  happens only on the first login. Then I would have to reboot
  (restarting winbind does not trigger it twice, also removing all
  caches in /run/samba does not trigger it twice)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1764853/+subscriptions