[Bug 1700472] [NEW] resolvconf cause nss_ldap connection failures while booting
Tobias Mark
1700472 at bugs.launchpad.net
Mon Jun 26 07:59:53 UTC 2017
Public bug reported:
Ubuntu 16.04.2 LTS
resolvconf: 1.78ubuntu4
If the server is configured to use a remote ldap during boot a bunch of this messages appears:
sh nss_ldap: could not connect to any LDAP server as [..] - Can't
contact LDAP server
This appears to be cause by /sbin/resolvconf:
case "$IFACE" in
*/*) report_iface_err "Slash" ; exit 1 ;;
*" "*) report_iface_err "Space" ; exit 1 ;;
.*) report_iface_err "Initial dot" ; exit 1 ;;
-*) report_iface_err "Initial hyphen" ; exit 1 ;;
~*) report_iface_err "Initial tilde" ; exit 1 ;;
esac
Proposed patch:
- ~*) report_iface_err "Initial tilde" ; exit 1 ;;
+ "~"*) report_iface_err "Initial tilde" ; exit 1 ;;
The shell will try to expand ~* to the home directory of user '*'. This
is probably not intended and cause the error because during ifup the
ldap can't be reached.
** Affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1700472
Title:
resolvconf cause nss_ldap connection failures while booting
Status in resolvconf package in Ubuntu:
New
Bug description:
Ubuntu 16.04.2 LTS
resolvconf: 1.78ubuntu4
If the server is configured to use a remote ldap during boot a bunch of this messages appears:
sh nss_ldap: could not connect to any LDAP server as [..] - Can't
contact LDAP server
This appears to be cause by /sbin/resolvconf:
case "$IFACE" in
*/*) report_iface_err "Slash" ; exit 1 ;;
*" "*) report_iface_err "Space" ; exit 1 ;;
.*) report_iface_err "Initial dot" ; exit 1 ;;
-*) report_iface_err "Initial hyphen" ; exit 1 ;;
~*) report_iface_err "Initial tilde" ; exit 1 ;;
esac
Proposed patch:
- ~*) report_iface_err "Initial tilde" ; exit 1 ;;
+ "~"*) report_iface_err "Initial tilde" ; exit 1 ;;
The shell will try to expand ~* to the home directory of user '*'.
This is probably not intended and cause the error because during ifup
the ldap can't be reached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1700472/+subscriptions
More information about the foundations-bugs
mailing list