https://bugzilla.novell.com/show_bug.cgi?id=395402 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com AssignedTo|yast2-maintainers@suse.de |jkupec@novell.com -- 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=395402 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c2 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thoenig@novell.com Status|NEW |NEEDINFO Info Provider| |dkukawka@novell.com --- Comment #2 from Ján Kupec 2008-05-29 10:09:34 MDT --- No, but maybe the hal/dbus guys can help us. Danny, Timo, what can be the cause of this hal error? "Connection was disconnected before a reply was received (org.freedesktop.DBus.Error.Disconnected)" The following succeeds: conn = dbus_bus_get(DBUS_BUS_SYSTEM, &err.error); hctx = libhal_ctx_new(); libhal_ctx_set_dbus_connection(hctx, conn); but then libhal_ctx_init(hctx) fails in the very same method. The code is at http://svn.opensuse.org/svn/zypp/trunk/libzypp/zypp/target/hal/HalContext.cc, look for "HalContext_Impl::HalContext_Impl()". -- 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=395402 Stanislav Visnovsky changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |visnov@novell.com Priority|P5 - None |P2 - High -- 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=395402 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c10 --- Comment #10 from Ján Kupec 2008-10-23 08:56:22 MDT --- Created an attachment (id=247533) --> (https://bugzilla.novell.com/attachment.cgi?id=247533) yast logs from new occurance -- 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=395402 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c12 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |thoenig@novell.com --- Comment #12 from Ján Kupec 2008-10-23 09:11:42 MDT --- Timo, we have a VBox snapshot of this situation. Could you take a look at it, if you think it could help? -- 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=395402 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c14 Timo Hoenig changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|thoenig@novell.com |jkupec@novell.com --- Comment #14 from Timo Hoenig 2008-10-28 06:38:00 MDT --- Jan? -- 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=395402 User thoenig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c16 --- Comment #16 from Timo Hoenig 2008-10-29 08:36:15 MDT --- (In reply to comment #15 from Ján Kupec)

But c#11 suggests that there is a chance that this is reproducible - it seems that installing a package that triggers restart of dbus makes the problem to appear on installation of another package.

What package is that? We shall not restart D-Bus. At least as there isn't a strict reason for doing so. -- 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=395402 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c18 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@novell.com --- Comment #18 from Ján Kupec 2008-10-29 08:50:02 MDT --- OK, looking closer, it wasn't a package, it was the yast2-ldap-client module itself: 2008-10-23 15:59:28 <1> dhcp41(4469) [YCP] Progress.ycp:380 Progress::New(Writing LDAP Configuration..., 4, ["Stop services", "Update configurat ion files", "Start services", "Update configuration in LDAP directory"]) 2008-10-23 15:59:28 <1> dhcp41(4469) [YCP] Progress.ycp:469 No progress icons defined 2008-10-23 15:59:28 <1> dhcp41(4469) [YCP] Service.ycp:461 Stopping service ypbind 2008-10-23 15:59:28 <1> dhcp41(4469) [YCP] Service.ycp:280 Running service initscript ypbind stop 2008-10-23 15:59:29 <1> dhcp41(4469) [YCP] Ldap.ycp:1888 file /etc/openldap/ldap.conf was modified 2008-10-23 15:59:30 <3> dhcp41(4469) [agent-ldap] LdapAgent.cc(debug_exception):485 ldap error while starting TLS (-11): Connect error 2008-10-23 15:59:30 <3> dhcp41(4469) [agent-ldap] LdapAgent.cc(debug_exception):487 additional info: error:14077410:SSL routines:SSL23_GET_SERVE R_HELLO:sslv3 alert handshake failure 2008-10-23 15:59:31 <1> dhcp41(6981) [ag_passwd] new plus lines in passwd: +:::::: 2008-10-23 15:59:31 <1> dhcp41(6981) [ag_passwd] new plus lines in shadow: + 2008-10-23 15:59:32 <1> dhcp41(4469) [YCP] Service.ycp:433 Restarting service dbus 2008-10-23 15:59:32 <1> dhcp41(4469) [YCP] Service.ycp:280 Running service initscript dbus restart -- 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=395402 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c20 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rhafer@novell.com Status|REOPENED |NEEDINFO Info Provider| |lmuelle@novell.com --- Comment #20 from Jiří­ Suchomel 2008-10-30 04:02:31 MDT --- The dbus restart in YaST Samba and LDAP clients was introduced as a "fix" for bug 174589 (see e.g. comment 26, 43, 47... and others). Lars: is the restart of dbus still required solution? -- 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=395402 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c22 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |behlert@novell.com, jsrain@novell.com, | |coolo@novell.com AssignedTo|jkupec@novell.com |jsuchome@novell.com Status|NEEDINFO |ASSIGNED Info Provider|lmuelle@novell.com | --- Comment #22 from Jiří­ Suchomel 2008-10-30 06:34:52 MDT --- We already show a message "This change only affects newly created processes and not already running services. Restart your services manually or reboot the machine to enable it for all services." in yast2-(samba|ldap)-client modules, but only when they are run on installed system. The situation when they are running during installation (in the configuration part, called 2nd stage) is different. Such popup may be shown, but may be confusing, because the YaST configuration continues after samba/ldap and there is no place for user to do manual restart. I'll try to summarize the options of what could be done. Remember that the precondition is that we are in 2nd stage of installation, configuring Samba (or LDAP). The restart of dbus is required so it can get the current information from NSS (see bug 174589). We have these options: 1. Tell user to restart after Samba/LDAP is configured. As written above, probably too confusing. 2. restart dbus and fix the application that are not able to survive it (zypp). Problem: probably too costly and we do not know all the problematic applications. 3. restart dbus at the end of 2nd stage, after everything is configured and YaST exits (and zypp is also closed). This looks nice, but currently we do not have an API to postpone some action (e.g. restart of certain service) from the middle of 2nd stage to the end. (But theoretically it should not be such a big deal, proper testing of such a thing is required) 4. reboot the machine once the Samba/LDAP configuration is done: similar situation to rebooting after installation of kernel in 2nd stage. We do have an API for it, but we need to test it properly, of course. 5. reboot the machine at the end of 2nd stage a) unconditionally, so we really know everything is in perfect state before first login. Many users would oppose as it is very much windows-like and in most cases probably needless. b) only when Samba/LDAP was configured before: similar to 3, it is postponing some action to the end of installation (also technical solution would probably be similar). 6. implement 'reload' command for dbus init script, which would not cause the problems to applications like zypp, but reload the correct information that could have been changed (like the nsswitch info from bug 174589). I have no idea if this is possible and how difficult would it be. -- 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=395402 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c24 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com --- Comment #24 from Ján Kupec 2008-10-30 07:30:14 MDT --- (In reply to comment #19 from Timo Hoenig)

Having this said: I'm not responsible for applications failing at the restart of the D-Bus system bus. However, I'm happy to help if fix up applications in order to survive it. I just don't have the time to analyze this scenario, but if someone is willing to work on this, I'm happy to help.

I would like to fix this particular libzypp scenario. If you could help, it would be great if we find some time to work on that. Let's arrange that by mail. -- 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=395402 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c26 --- Comment #26 from Jiří­ Suchomel 2008-10-30 09:41:30 MDT --- I forgot to mention: in all cases, the restart of dbus on _configured system_ would be removed. -- 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=395402 User kukuk@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c30 --- Comment #30 from Thorsten Kukuk 2008-11-04 06:12:06 MST --- (In reply to comment #21 from Lars Mueller)

After the experiences of the last years please suggest a reboot after a domain join (YaST Windows Domain Membership). This is a straight and simple approach and not only required by dbus as Timo explained in comment #19. This is also required by the authentication stack (pam, nscd).

nscd: rcnscd try-restart will solve this problem. pam: that's wrong. pam always reads the config at pam_start() and throws them away with pam_end(), means for every single authentication. If not, it's an application bug. So this are no valid reasons for a reboot. -- 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=395402 User kukuk@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c33 --- Comment #33 from Thorsten Kukuk 2008-11-04 06:44:16 MST --- nscd -i does not reread modified /etc/nsswitch.conf. So a nscd try-restart would be better if we modify /etc/nsswitch.conf. -- 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.

I forgot to mention: in all cases, the restart of dbus on _configured system_ would be removed. I guess that will leave the system in a broken state when running -ldap-client or -samba-client on an already installed system. I don't quite understand what

https://bugzilla.novell.com/show_bug.cgi?id=395402 User rhafer@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c35 --- Comment #35 from Ralf Haferkamp 2008-11-04 08:00:33 MST --- (In reply to comment #26 from Jiří­ Suchomel) the big deal about a reboot is. We have problems with finding which services to restart from the (samba|ldap)-client modules with almost every release. See e.g. bug#174589 for details. Forcing a reboot if /etc/nsswitch.conf was altered during or after installation would fix this once an for all.

From https://bugzilla.novell.com/show_bug.cgi?id=174589#c88 : "If you modify /etc/nsswitch.conf, the best is to reboot. Else you have to restart __ALL__ applications which are running at the time of modification."

-- 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=395402 User lmuelle@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c37 --- Comment #37 from Lars Müller 2008-11-04 08:07:24 MST --- Comment 23 +1 by me. Please, please, please reboot in this use case. Else we'll see this type of bug reports with SUSE Linux Enterprise 11 again and again. Rebooting is such a simple approach compared to all the pain we cause by trying to fix the issues in a different way. It's ok to me to limit the reboot case to the Samba, LDAP and LUM case. But please no longer try to fix this very long standing issue in a different way. One rcnscd try-restart alone will not fix this issue. Even if this is suggested again and again. It is not true. And this is not only Samba, LDAP or LUM. It's also DBUS see comment #19. Please keep the solution to address this pain straight and simple and don't try to be smart here. Reboot instead. -- 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=395402 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c39 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@novell.com Status|NEEDINFO |ASSIGNED Info Provider|locilka@novell.com | --- Comment #39 from Lukas Ocilka 2008-11-05 03:03:05 MST --- No, we currently do not have any functionality that would allow to setup and show a generic message at the end of the installation. And of course, we can't guarantee what happens if we add a step to the workflow (just because of this) and Add-Ons change it. The only way would be to "invent" a new API allowing to set such message and show it just before finishing the installation (but it's not so easy as YaST has to remember that while restarting itself for instance). -- 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=395402 User kukuk@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c41 --- Comment #41 from Thorsten Kukuk 2008-11-05 06:34:15 MST --- At the time, where you can choose which service you wish to use for authentication (means local, nis, ldap, samba, ...), the following daemons are running: syslog-ng klogd dbus hal acpid console-kit-daemon YaST2 syslog-ng, klogd, acpid should not have any problems with modifying /etc/nsswitch.conf. Means there are dbus,hal, console-kit-daemon left. Sorry, but I see it as bad joke if we should reboot a system only because of we are not able to restart three services! So no, a reboot at this point is inacceptable. If we cannot restart dbus/hal because of YaST2, we have to do it at the end. -- 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=395402 User kukuk@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c43 --- Comment #43 from Thorsten Kukuk 2008-11-05 06:58:32 MST --- (In reply to comment #42 from Lars Müller)

As it's possible to change the authentication method from inside of an installed system as well, we'll see more services running in this case than those listed in comment #41.

Correct, and in that case we tell the user to reboot. But we cannot force a reboot, since we don't know what else is running and if it is possible at that time.

Also a modification of the authentication system happens very rarely. Usually this is configured _one_ time. Therefore suggesting or causing a reboot isn't an issue to the user.

It is, if it is for various reasons not possible at that time. -- 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=395402 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c45 --- Comment #45 from Lukas Ocilka 2008-11-05 07:31:39 MST --- (In reply to comment #41 from Thorsten Kukuk)

So no, a reboot at this point is inacceptable. If we cannot restart dbus/hal because of YaST2, we have to do it at the end.

That would need some additional support added to installation / installation scripts. Installation itself (Some Installation module) could write the list of services which should be restarted to the /etc/install.inf and the installation scripts (that actually call YaST and handle its return) would restart the services listed there (these scripts actually check that file for another information already). -- 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=395402 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c47 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #249668|0 |1 is obsolete| | --- Comment #47 from Jiří­ Suchomel 2008-11-06 04:51:01 MST --- Created an attachment (id=250273) --> (https://bugzilla.novell.com/attachment.cgi?id=250273) patch for restarting list of services at the end of 2nd stage This could read list of services to restart from the file (written by YaST before) -- 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=395402 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c49 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |chrubis@novell.com --- Comment #49 from Jiří­ Suchomel 2008-11-11 13:35:39 MST --- Cyril, are you able to reproduce the wrong behavior with latest medias? -- 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=395402 User jsuchome@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c51 Jiří­ Suchomel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mclark@novell.com, ggireeshkumar@novell.com --- Comment #51 from Jiří­ Suchomel 2008-11-13 02:01:13 MST --- (In reply to comment #23 from Ralf Haferkamp)

We should not restrict that to the Samba/LDAP case btw, I think LUM requires the same. (We had that discussion in the past already)

I forgot about this one: yast2-linux-user-mgmt should be updated the same way... -- 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=395402 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c53 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|chrubis@novell.com |jsuchome@novell.com --- Comment #53 from Cyril Hrubis 2008-11-13 04:10:26 MST --- I can try installation from media today, (I haven't time to test it since reporting this bug). Which media should I use? OpenSuSE 11.1 beta 5? -- 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=395402 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=395402#c55 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|chrubis@novell.com | --- Comment #55 from Cyril Hrubis 2008-11-13 08:20:29 MST --- Okay I've just finished the installation and I can confirm it's fixed. -- 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.