** Attachment added: "common-session"
http://launchpadlibrarian.net/13412212/common-session
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a du
** Attachment added: "common-password"
http://launchpadlibrarian.net/13412208/common-password
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a
** Attachment added: "common-auth"
http://launchpadlibrarian.net/13412198/common-auth
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicat
** Attachment added: "nsswitch.conf"
http://launchpadlibrarian.net/13412162/nsswitch.conf
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a dupl
I have the same problem on a Hardy server installation. I have updated it from
Gutsy, but i count it as a Hardy install because i only used Gutsy server cd to
install the base system then i have updated it to hardy straight away. In my
case it was not enough to put "bind_policy soft" in ldap.con
** Attachment added: "common-account"
http://launchpadlibrarian.net/13412173/common-account
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a du
** Attachment added: "ldap-auth-config"
http://launchpadlibrarian.net/13412230/ldap-auth-config
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of
** Attachment added: "packages.txt"
http://launchpadlibrarian.net/13412251/packages.txt
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplic
Good criteria. But please also consider the PAM rules for logins. Some allow
a graceful fall thru to pam_unix.so as a backup. This should be a default no
matter what other auth system is used. There are many other pam auth
systems, eg: fingerprint, usb key etc... LDAP is only one of many. So when
c
Okay, snapshot of conclusions at this point...
(1) Any systems Feisty (and earlier) upgraded to Hardy (and later) would
require a manual migration of /etc/libnss-ldap.conf and /etc/pam-
ldap.conf if either or both of those files exist.
(2) None of the 5+ Ubuntu developers who have looked at this
ldap-auth-client combined /etc/libnss-ldap.conf and /etc/pam-ldap.conf.
If either or both of these files exist on upgrade, then the user is
prompted with a message to manually migrate the files. From debian
/ldap-auth-config.templates:
Template: ldap-auth-config/move-to-debconf
Type: boolean
Defa
On Tue, Apr 8, 2008 at 2:45 PM, Dustin Kirkland <[EMAIL PROTECTED]>
wrote:
>
> Please clarify... Would you be prompted with a login? Were you able to
> enter a username? And what about a password? Is that, then, the point
> at which your system 'hung'? If so, I am able to reproduce this
> beh
On Tue, 2008-04-08 at 12:07 +, Kevin Slater wrote:
> I had the problem in two different desktop machines running Fiesty,
> with LDAP client authentication working, when I upgraded them to
> Gutsy.
@Kevin,
Thanks for confirming our suspicions, that this problem arises in
systems upgraded from
Dustin,
I had the problem in two different desktop machines running Fiesty, with
LDAP client authentication working, when I upgraded them to Gutsy. The fix
was to change bind policy to soft and to manually configure the proper files
using various sources on the web as a guide. The machines would h
Err.. Ok. For a while only. Am at home now.
Tommorow OK?
Will get logs etc...
On Mon, Apr 7, 2008 at 11:57 PM, Dustin Kirkland <[EMAIL PROTECTED]>
wrote:
> @Hilton-
>
> Would it be possible for you to switch it back to hostname and reproduce
> the problem and report any meaningful error messages
Jamie hasn't had time to look at this and has transferred it to me.
** Changed in: libnss-ldap (Ubuntu)
Assignee: Jamie Strandboge (jamie-strandboge) => Dustin Kirkland (kirkland)
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug
@Hilton-
Would it be possible for you to switch it back to hostname and reproduce
the problem and report any meaningful error messages in /var/log/syslog
for the failed boot? (Note, you might have to look in one of the log
rotations in /var/log/syslog.*)
:-Dustin
--
ldap config causes Ubuntu
@Brian-
A few more questions, then...
So you can reproduce this problem reliably on a Hardy Beta fresh
install? And by reproduce, the machine hangs on boot (and not just on
login)?
Your process for reproducing this problem involves a fresh install of Hardy
Beta, and then customizing the config
Sorry I can't provide more detailed config info, but as I explained before,
the machine has been wiped and reinstalled and reconfigured many times since
the original problem. But mine was a clean Hardy install, and all our
configs lived in ldap.conf (no pam_ldap.conf or anything like that), and we
Ok. It's a production system that started with Debian stable, then Ubuntu
Hoary, then Ubuntu Dapper. Hopefully Ubuntu Hardy soon.
No re-installs, could not afford downtime. All the time very problematic
upgrading.
On Mon, Apr 7, 2008 at 10:57 PM, Dustin Kirkland <[EMAIL PROTECTED]>
wrote:
> On Mo
On Mon, 2008-04-07 at 20:10 +, Hilton Gibson wrote:
> With "pam_ldap.conf" my ref is a uri and works, but when I make it a
> straight host name ref, then it hangs.
Ahh... Okay, so this tells us something very interesting.
pam_ldap.conf hasn't existed since Feisty. There, it was part of the
l
Same happened to me. I think the problem lies in the reference to ldap
server.
With "pam_ldap.conf" my ref is a uri and works, but when I make it a
straight host name ref, then it hangs.
Dunno if this helps.
On Mon, Apr 7, 2008 at 6:49 PM, Dustin Kirkland <[EMAIL PROTECTED]>
wrote:
> @Brian-
>
>
@Brian-
I'm still trying, albeit unsuccessfully, to reproduce this problem. It
seems that the complexity of the configuration is a bit deeper than in
my test cases.
If possible, would you (or anyone else) who is seeing this problem in
Hardy Beta please ping me in IRC? My handle is 'kirkland' an
Dustin,
Sorry, this was Hardy Beta... I'm not sure as to the particular release, since
I'm doing test preseed installs over a network from a local mirror that is
updated daily. I do recall that the version of libnss-ldap was 259 at the time,
though 258 is the latest I see in the repos now.
--
@Brian:
Please confirm, is this Hardy? If so, which alpha/beta release?
:-Dustin
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
I only got the problem when I was using "groups: ldap files" in
nsswitch.conf, and without the "bind_policy soft" in ldap.conf. Changing
to groups: files ldap and bind_policy soft resolved the problem for me,
though I'm not sure of the udev version as the machine has been
reinstalled several times
Hi all,
I've been trying for several days to reproduce this problem in Hardy,
without any luck.
Can anyone confirm that this problem is endemic in Hardy?
If so, can you please provide very detailed instructions to reproduce?
Also, please note your udev version.
Thanks,
:-Dustin
--
ldap config
I'm pretty sure that this is not a problem of nss-ldap but nss-files or
the nss subsystem at all!
nss-ldap should never get asked about any account informations (root,
daemon,...) found by nss-files already.
And yes, it is really a pita that no one took care for this major bug
already.
--
ldap
I do also think, that a fix should made available for an LTS release.
libnss-ldap is critical for an enterprise environment.
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/155947
You received this bug notification because you are a member of Ubuntu
Server Team,
I Agree with Darren.
This bug has been biting people sinds Dapper. And it's not only
laptops. If you have an Ubuntu server in a network where the LDAP is
down or unreachable for some reason, it no longer boots.
--
ldap config causes Ubuntu to hang at a reboot
https://bugs.launchpad.net/bugs/1
Given that Hardy defaults to roaming network mode and that any use of
libnss-ldap will result in a non-bootable machine, shouldn't the
importance of this bug be made critical?
Sorry, I'm not trying to rant - I just want to make sure appropriate
resources are made available to fix this for an LTS r
An added twist to this bug...
I've been running LDAP servers on Feisty and Breezy and Hoary for a long time,
without this problem.
The latest couple I've set up have shown me this problem. This problem is very
significant in this case because the LDAP servers themselves are unable to
boot. Bec
32 matches
Mail list logo
