I'll try to get 17.04 up somewhere and test that as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap login and ldapi
The ldapi:/// worked just fine, as did ldap:// with an IP or a name. And
I don't have an entry in /etc/hosts for the ldap server, I'm really
using DNS. Reboot works just fine, login prompt, and I can login at the
console (and via ssh) with an ldap user.
I'm sorry but I will need the files I
ldapi:/// is a unix socket connection, it shouldn't have a "name" or IP
component. It can optionally take a path component, but usually should
just be left blank.
Could you please attach your /etc/ldap.conf and /etc/ldap/ldap.conf?
Is your ldap server on localhost, or remote on another machine
I'm taking a look.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap login and ldapi set with a
name.
To manage
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
If you are dropped to an emergency shell on failure to boot, does name
resolution period work?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never
Almost certainly the issue is that login.service is not waiting for
networking before starting, when ldap is configured.
In the screenshot, I see "Failed to start Login Service" and then later
"Started to raise network interfaces".
--
You received this bug notification because you are a member
Finally, is this reproducible with 17.04? Note that 16.10 goes eol in
about 3 months so there is some non-zero cost to trying to fix it there,
if it's already fixed in 16.10.
** Changed in: libpam-ldap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
For what it's worth, the same version of libpam-ldap has been present in
Ubuntu since (at least) 15.04. So I don't think the bug is in libpam-
ldap.
When the login service fails, did you obtain the logs for it to see why
it failed?
More than likely this is a systemd change, but it's unclear yet.
