I have F12_x86_64 installed from alpha ISO and kept up to date with a yum update. (running on a intel core2-duo) I am always getting a hang on boot at the stage of.. Starting system message bus. It waits at this point for just over 10 minutes, then continues through normally to runlevel 5. Errors in /var/log/messages say nss_ldap: failed to bind to LDAP server ......can't contact LDAP server It repeats this many times while starting the dbus-daemon and eventually times out. It repeats the error through automountd and rpc.statd and then finally NetworkManager runs again and starts the network Where should I report this as a bug? and against what... Network manager for not getting its act together earlier or general init.d boot script order..?? In an F10 install we had to remove NetworkManager to get a working system. Currently I'm testing F11 and F12alpha and F11 works fine. (on the same hardware machines) Any help or pointers on what to report greatly received.

On Thu, 2009-10-15 at 15:00 +1300, Peter Glassenbury (CSSE) wrote: > I have F12_x86_64 installed from alpha ISO and kept up to date > with a yum update. (running on a intel core2-duo) > > I am always getting a hang on boot at the stage of.. > Starting system message bus. > > It waits at this point for just over 10 minutes, then > continues through normally to runlevel 5. > > Errors in /var/log/messages say > > nss_ldap: failed to bind to LDAP server ......can't contact LDAP server > > It repeats this many times while starting the dbus-daemon and eventually times out. > It repeats the error through automountd and rpc.statd > and then finally NetworkManager runs again and starts the network > > > Where should I report this as a bug? and against what... > Network manager for not getting its act together earlier or > general init.d boot script order..?? > > In an F10 install we had to remove NetworkManager to get a > working system. > Currently I'm testing F11 and F12alpha and F11 works fine. > (on the same hardware machines) > > Any help or pointers on what to report greatly received. ---- add the following to /etc/ldap.conf nss_initgroups_ignoreusers root, ldap, dbus, named timelimit 30 bind_timelimit 30 bind_policy soft you might want to add other daemon 'users' from /etc/passwd the the 'ignoreusers' line too.

Craig White wrote: So the workaround works -- is it a bug to be reported? Pete

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, Oct 15, 2009 at 5:05 AM, Scott Robbins wrote: > On Thu, Oct 15, 2009 at 06:28:54PM +1300, Peter Glassenbury (CSSE) wrote: >> Craig White wrote: >> >> So the workaround works -- is it a bug to be reported? >> Pete > As I mentioned, it was reported 5 years ago. :) > So, it's a known issue. > You could try to reopen it--I *think* it was reported against RH, but > the problem exists in Fedora and CentOS clients. > > As mentioned, I couldn't find the bug with a quick search, but it > definitely is there. > -- > Scott Robbins Not sure its the same, but here is a (recent) BZ: https://bugzilla.redhat.com/show_bug.cgi?id=502072 Some work arounds and discussion there. This the same?

On 10/15/2009 05:35 PM, Scott Robbins wrote: > On Thu, Oct 15, 2009 at 06:28:54PM +1300, Peter Glassenbury (CSSE) wrote: >> Craig White wrote: >> >> So the workaround works -- is it a bug to be reported? >> Pete > As I mentioned, it was reported 5 years ago. :) > > So, it's a known issue. > > You could try to reopen it--I *think* it was reported against RH, but > the problem exists in Fedora and CentOS clients. > Hrrm, I have to throw Ubuntu or something on a VM and see if it is a > problem for them too. > > As mentioned, I couldn't find the bug with a quick search, but it > definitely is there. If you can't find it, please file a new bug report and pass the bug report number to this list. Some bugs do get lost at times but we need to fix the problem. Rahul

Not sure its the same, but here is a (recent) BZ: https://bugzilla.redhat.com/show_bug.cgi?id=502072