[Bug 348318] New: Very long boot time (dbus problem)
https://bugzilla.novell.com/show_bug.cgi?id=348318 Summary: Very long boot time (dbus problem) Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: diablo@roedu.net QAContact: qa@suse.de CC: diablo@roedu.net Found By: --- Created an attachment (id=187378) --> (https://bugzilla.novell.com/attachment.cgi?id=187378) dmesg output Hi, we have installed OpenSuSE 10.3 on one of our test servers. After the install, the system has been updated and a reboot was made to ensure that we will have no problems with the newly installed kernel. A whole day the system was configured to host all kind of services (smtp, imap, pop3, amavis, clamav, web [http, https], pam with ldap auth). After all the services were configured a final reboot was made to test if all the required services start at boot. Since that reboot we have a problem. The system boots in about 25 minutes. From those 25 minutes, 20 minutes we don't see anything on the screen. I have emailed the opensuse@opensuse.org mailing list, and they recomanded me to boot the system into interactive mode. I did that and I found out that the software responsable for the delay is dbus. After I choose 'y' (to start the dbus), the system just sits there for almost 20 minutes and then the boot process is continued. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User diablo@roedu.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c1
--- Comment #1 from Manuel Subredu
https://bugzilla.novell.com/show_bug.cgi?id=348318
User tom.voigt@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c2
Thomas Voigt
https://bugzilla.novell.com/show_bug.cgi?id=348318
User tom.voigt@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c3
--- Comment #3 from Thomas Voigt
https://bugzilla.novell.com/show_bug.cgi?id=348318
User tom.voigt@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c4
--- Comment #4 from Thomas Voigt
https://bugzilla.novell.com/show_bug.cgi?id=348318
User diablo@roedu.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c5
--- Comment #5 from Manuel Subredu
https://bugzilla.novell.com/show_bug.cgi?id=348318
User tom.voigt@web.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c6
--- Comment #6 from Thomas Voigt
https://bugzilla.novell.com/show_bug.cgi?id=348318
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=348318
User support@ead-systeme.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c7
Alexander Soellner
My solution:
Changed the line
# Required-Start: $local_fs
in /etc/init.d/dbus into
# Required-Start: $local_fs $network
and did a "insserv -r /etc/init.d/dbus" and a "insserv /etc/init.d/dbus".
So the starting order is now
lrwxrwxrwx 1 root root 7 Dec 14 10:38 /etc/rc.d/rc3.d/S06dbus -> ../dbus lrwxrwxrwx 1 root root 13 Dec 14 10:38 /etc/rc.d/rc3.d/S07consolekit -> ../consolekit lrwxrwxrwx 1 root root 10 Dec 14 10:38 /etc/rc.d/rc3.d/S07network -> ../network
Don't know why, but this works for me.
Hello I have the same problem. We use ldap for user authentication. After booting the client, it needs about 30 minutes to boot. /var/log/messages shows lines for reconnecting for the ldap server. Your solution above does not work for me. Because insserv -r /etc/init.d/dbus complains "loop exists for network". I can change the boot order manually, but I think when I install some updates, the boot order will be the same like before. My question is: Why does the system want connect to the ldap server, and doesn´t look to the local passwd file. At the moment the client hangs, it want likely start the consolekit daemon. Greetings George -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User jtorres@caci.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c8
--- Comment #8 from Jose Torres
https://bugzilla.novell.com/show_bug.cgi?id=348318
User jtorres@caci.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c9
Jose Torres
Hello I have the same problem. We use ldap for user authentication. After booting the client, it needs about 30 minutes to boot. /var/log/messages shows lines for reconnecting for the ldap server.
Your solution above does not work for me. Because insserv -r /etc/init.d/dbus complains "loop exists for network". I can change the boot order manually, but I think when I install some updates, the boot order will be the same like before.
My question is: Why does the system want connect to the ldap server, and doesn´t look to the local passwd file. At the moment the client hangs, it want likely start the consolekit daemon.
Greetings George
Here's what (In reply to comment #4 from Thomas Voigt)
My solution:
Changed the line
# Required-Start: $local_fs
in /etc/init.d/dbus into
# Required-Start: $local_fs $network
and did a "insserv -r /etc/init.d/dbus" and a "insserv /etc/init.d/dbus".
So the starting order is now
lrwxrwxrwx 1 root root 7 Dec 14 10:38 /etc/rc.d/rc3.d/S06dbus -> ../dbus lrwxrwxrwx 1 root root 13 Dec 14 10:38 /etc/rc.d/rc3.d/S07consolekit -> ../consolekit lrwxrwxrwx 1 root root 10 Dec 14 10:38 /etc/rc.d/rc3.d/S07network -> ../network
Don't know why, but this works for me.
It seem like more of a general Linux problem. I had the same situation with the Fedora distributions. Here's what I did was to make it work. cd /etc cp nsswitch.conf nsswitch-orig.conf Use yast to configure LDAP. This will create a new nsswitch.conf file. cp nsswitch.conf nsswitch-ldap.conf cd /etc/init.d Used the attached ldap.patch file. patch -p0 < ldap.patch Reboot. Everything works. Its a terrible hack, but it got me going. Hope this helps!!! Jose -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User support@ead-systeme.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c10
--- Comment #10 from Alexander Soellner
Hello I have the same problem. We use ldap for user authentication. After booting the client, it needs about 30 minutes to boot. /var/log/messages shows lines for reconnecting for the ldap server.
Your solution above does not work for me. Because insserv -r /etc/init.d/dbus complains "loop exists for network". I can change the boot order manually, but I think when I install some updates, the boot order will be the same like before.
My question is: Why does the system want connect to the ldap server, and doesn´t look to the local passwd file. At the moment the client hangs, it want likely start the consolekit daemon.
Greetings George
Here's what (In reply to comment #4 from Thomas Voigt)
My solution:
Changed the line
# Required-Start: $local_fs
in /etc/init.d/dbus into
# Required-Start: $local_fs $network
and did a "insserv -r /etc/init.d/dbus" and a "insserv /etc/init.d/dbus".
So the starting order is now
lrwxrwxrwx 1 root root 7 Dec 14 10:38 /etc/rc.d/rc3.d/S06dbus -> ../dbus lrwxrwxrwx 1 root root 13 Dec 14 10:38 /etc/rc.d/rc3.d/S07consolekit -> ../consolekit lrwxrwxrwx 1 root root 10 Dec 14 10:38 /etc/rc.d/rc3.d/S07network -> ../network
Don't know why, but this works for me.
It seem like more of a general Linux problem. I had the same situation with the Fedora distributions. Here's what I did was to make it work.
cd /etc
cp nsswitch.conf nsswitch-orig.conf
Use yast to configure LDAP. This will create a new nsswitch.conf file.
cp nsswitch.conf nsswitch-ldap.conf
cd /etc/init.d
Used the attached ldap.patch file. patch -p0 < ldap.patch
Reboot.
Everything works.
Its a terrible hack, but it got me going. Hope this helps!!!
Jose
Hallo Jose, did you do your hack on the ldap-server or on the client? Georg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User jtorres@caci.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c11
--- Comment #11 from Jose Torres
It seem like more of a general Linux problem. I had the same situation with the Fedora distributions. Here's what I did was to make it work.
cd /etc
cp nsswitch.conf nsswitch-orig.conf
Use yast to configure LDAP. This will create a new nsswitch.conf file.
cp nsswitch.conf nsswitch-ldap.conf
cd /etc/init.d
Used the attached ldap.patch file. patch -p0 < ldap.patch
Reboot.
Everything works.
Its a terrible hack, but it got me going. Hope this helps!!!
Jose
Hallo Jose,
did you do your hack on the ldap-server or on the client?
Georg
This hack is on the ldap server side. Jose -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User delgado@dfn-cert.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c12
Friedrich Delgado Friedrichs
https://bugzilla.novell.com/show_bug.cgi?id=348318
User delgado@dfn-cert.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c13
--- Comment #13 from Friedrich Delgado Friedrichs
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c14
Timo Hoenig
It is impossible to get rid of dbus and hal altogether, since they seem to be required by lots of packages, some of which are integral parts of the system.
Whats the reason for network requiring hal?
It's because of systems using NetworkManager. NetworkManager gets the network devices using HAL. Changing component to base system and reassigning this bug to the default assignee of it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c15
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c16
--- Comment #16 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c17
--- Comment #17 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c18
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c19
--- Comment #19 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c20
--- Comment #20 from Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=348318
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c21
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c22
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c23
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User tambet@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c24
Tambet Ingo
From what I understand, the bug here is that with ifup scripts the order of init scripts must be different from when NM is used. ie,
ifup: network, syslog, auditd, dbus NM : dbus, network, syslog, auditd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c25
Timo Hoenig
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c26
Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c27
Timo Hoenig
which is a loop in case of using NM. On the other hand the question is *why* dbus requires network to run faster and if so *which* part of the network setup is used for that and if the localnet could be used instead.
As this is only specific to LDAP setups: Can someone -- someone, who is able to reproduce this currently -- able to test whether it helps to replace the following: Required-Start: $local_fs with Required-Start: $local_fs $boot.localnet in /etc/init.d/dbus. (Werner if the above isn't what you've meant, please correct me. Thanks.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=348318
User werner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c28
--- Comment #28 from Dr. Werner Fink
https://bugzilla.novell.com/show_bug.cgi?id=348318
User chrubis@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c29
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=348318
User thoenig@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=348318#c30
Timo Hoenig
participants (1)
-
bugzilla_noreply@novell.com