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.
Pete
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.
How is this system configured? What does it need to contact the LDAP server for?
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
Craig White wrote:
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.
I just have the default ldap settings except for the ldap server config.. The timelimits default to 120 the bind_policy has been changed to soft as you said. This is the default ignore users line.... nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm,polkituser
In /etc/nsswitch we set automount,aliases,services,netgroup, protocols,group,shadow,passwd to "files ldap" and hosts to "files dns" and the rest to "files"
The above change to bind_policy and shortening the timelimits has no hang.. Gives the following ERROR (in red on startup) but then continues on and appears to come up OK and in reasonable time. Starting NFS daemon: rpc.nfsd: unable to resolve ANYADDR: nfs to inet address: Name or service not known
So the workaround works -- is it a bug to be reported? Pete
On Thu, 2009-10-15 at 18:28 +1300, Peter Glassenbury (CSSE) wrote:
The above change to bind_policy and shortening the timelimits has no hang.. Gives the following ERROR (in red on startup) but then continues on and appears to come up OK and in reasonable time. Starting NFS daemon: rpc.nfsd: unable to resolve ANYADDR: nfs to inet address: Name or service not known
So the workaround works -- is it a bug to be reported? Pete
---- possibly is a bug worth reporting but I think it's easily fixed.
If you open system-config-network, select your primary NIC and choose 'Edit' you can uncheck the box called 'Controlled by NetworkManager' and check the box 'Activate device when computer starts'
At that point, you run the commands...
chkconfig NetworkManager off chkconfig network on
and you should be good at next bootup.
If you prefer not using GUI tools, the file we are editing is likely
/etc/sysconfig/network-scripts/ifcfg-eth0
and the values we are changing...
ONBOOT=yes NM_CONTROLLED=no
Craig
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.
-----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. 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.
-- 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?
tom - -- Tom London
Tom London wrote:
-----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?
Yes, This is the same bug. I was coming from a different symptom (the hang in dbus) and the bug reports the ldap error I had in /var/log/messages. It still appears to be alive so I added a comment saying also in F12rawhide (Is there another way to say that it is in multiple versions)
Pete
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
Rahul Sundaram wrote:
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
Scott Robbins said
Not sure its the same, but here is a (recent) BZ: https://bugzilla.redhat.com/show_bug.cgi?id=502072
As scott said in the above two lines, this bug appears to be active for F11 and is the same as the one I had. The workaround is the same and worked.
I have added a comment that the same bug is F12rawhide but don't know what I am supposed to do to make it searchable as an F12rawhide bug.. (do I copy and paste the same bug but change the version to 12 ?? )
Pete
On Thu, Oct 15, 2009 at 03:00:13PM +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
This may be a 5 year old bug, which I can't find right now, reported against RedHat.
What happens, if it is set to authenticate against LDAP, is that if it can't find a server. it will hang. There are probably a few lines in /etc/nsswitch.conf reading files ldap
Though it's supposed to check local files first, it doesn't.
Oddly enough, it seems to just want reassurance that an LDAP server exists--for example, if you have it set to look to an LDAP server, but there are no accounts that can authenticate against said server, it won't hang.
This can often be fixed (again, making the assumption that is the same issue), by editing /etc/ldap.conf (NOT /etc/openldap/ldap.conf) and changing the commented line bind_policy hard to an uncommented
bind_policy soft
If you have no ldap entries in nsswitch.conf, of course, it's some other issue.