[Bug 630845] New: Windows domain membership lost after every reboot
http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c0 Summary: Windows domain membership lost after every reboot Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers@SuSE.de ReportedBy: toddrme13@gmail.com QAContact: samba-maintainers@SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 I used YaST Windows Domain Membership module (Samba Client) to join an AD domain. When I logout, I have a list of domains I can login to in KDM. However, every time I reboot the computer the contents of the list are gone, with only "<local>" and "Null" available. If I login as root and run the windows domain membership YaST module, then just click okay then logout again, the list is back (I don't have to pick an OU again). This sort of thing happened occasionally under openSUSE 11.2 but it happens every time under openSUSE 11.3. Reproducible: Always Steps to Reproduce: 1. Open YaSt 2. Open the Windows Domain Membership module. 3. Join a windows domain. 4. Logout 5. Verify that there is a list of domains available in your login manager which at least contains the domain you joined. 6. Reboot 7. Wait for the login screen to appear. Actual Results: The list of domains contains "<local>" and "Null", nothing else. Expected Results: The list contains "<local>" and other domains present on the network, including the one you just joined. I only tested this under KDM, not GDM or any other login manager. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c1 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |toddrme2178@gmail.com --- Comment #1 from Lars Müller <lmuelle@novell.com> 2010-08-12 19:28:26 UTC --- Very, very likely this is a side effect of the parallel boot process. The display manager in use (kdm or gdm for example) already start while the network and/ or winbindd aren't up and ready to provide the required information. /etc/sysconfig/network/config:WAIT_FOR_INTERFACES="30" is the default. If you upgraded the value doesn't get changed (which is a feature and not a bug). At least on one of my older systems it was set to 20 while the comment in the sysconfig file got updated to ## Type: integer ## Default: 30 # # Some interfaces need some time to come up or come asynchronously via hotplug. # WAIT_FOR_INTERFACES is a global wait for all mandatory interfaces in # seconds. If empty no wait occurs. # WAIT_FOR_INTERFACES="30" Hm, while reading the /etc/sysconfig/network/config comment to the MANDATORY_DEVICES setting I'm more and more sure you have to add your device here. If that helps we have to consider to enhance the YaST Microsoft Domain Membership aka samba-client module in this direction. Please check and report back. I'm letting this defect in the samba-maintainers queue as I'll be on vacation for the next two weeks starting tomorrow. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c2 Todd R <toddrme2178@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|toddrme2178@gmail.com | --- Comment #2 from Todd R <toddrme2178@gmail.com> 2010-08-13 14:42:40 UTC --- This is a clean install, and WAIT_FOR_INTERFACES="30" I set MANDATORY_DEVICES to eth0 but, although that is the correct device, I am not sure it is the correct name to use there. If it is, it didn't work. Another thing, I don't actually have to re-join the domain, if I just login as root then logout again I get the list of domains. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c3 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |toddrme2178@gmail.com --- Comment #3 from Lars Müller <lmuelle@novell.com> 2010-08-13 15:35:48 UTC --- To ensure it's the correct network device name call this command from inside a terminal session (xterm or konsole for example): /sbin/ip r s | tail -n 1 This results in an output like: default via 192.168.0.1 dev eth0 For the example case the MANDATORY_DEVICES would be "eth0"
if I just login as root then logout again
I guess you're talking about the display manager level. Or more verbose: the login to Gnome or KDE. Correct? If that's the case it's not surprising as the system had enough time to bring the network and the winbind daemon up. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c4 Todd R <toddrme2178@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|toddrme2178@gmail.com | --- Comment #4 from Todd R <toddrme2178@gmail.com> 2010-08-13 16:17:23 UTC --- (In reply to comment #3)
To ensure it's the correct network device name call this command from inside a terminal session (xterm or konsole for example)...
It says eth0, which means I put the correct value in. That means the suggestions in the first comment did not work.
if I just login as root then logout again
I guess you're talking about the display manager level. Or more verbose: the login to Gnome or KDE. Correct?
If that's the case it's not surprising as the system had enough time to bring the network and the winbind daemon up.
Yes, I am using KDM. I don't know how to login to a windows domain via the text consoles. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=630845 http://bugzilla.novell.com/show_bug.cgi?id=630845#c5 James McDonough <jmcdonough@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |toddrme2178@gmail.com --- Comment #5 from James McDonough <jmcdonough@novell.com> 2010-08-13 19:42:49 UTC --- instead of logging in as root at the kdm prompt, please hit ctrl+alt+f1 and login as root. Then try the commands to see if the eth0 interface is up. -- Configure bugmail: http://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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c6 Todd R <toddrme2178@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|toddrme2178@gmail.com | --- Comment #6 from Todd R <toddrme2178@gmail.com> 2010-08-18 19:07:28 UTC --- It tried press ctrl+alt+f1 and found that the system hadn't finished loading yet. I got kdm, but the system was still loading in the background. If I wait until the system finishes loading, then I get the list of domains. Why would kdm be appearing before the system has finished loading the software needed for kdm to run properly? -- 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c James McDonough <jmcdonough@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low CC| |samba-maintainers@SuSE.de AssignedTo|samba-maintainers@SuSE.de |lmuelle@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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c7 Lars Müller <lmuelle@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |toddrme2178@gmail.com --- Comment #7 from Lars Müller <lmuelle@novell.com> 2011-01-13 22:46:00 CET --- That's the result of init scripts are executed in parallel. Try to set RUN_PARALLEL="no" in /etc/sysconfig/boot and report back if that works. If that's the case we have to identify which service is blocking the network setup. Please check /var/log/boot.msg there you see timestamps at the begin of each line. Between two of such there must the a bigger gap close to the time you have to wait. If the last suggestion doesn't help please attach the file /var/log/boot.msg Sorry for being this generic with the suggestions. -- 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c8 Brian Gade <brian.gade@cdw.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brian.gade@cdw.com --- Comment #8 from Brian Gade <brian.gade@cdw.com> 2011-03-07 00:40:16 UTC --- Has there been any further progress on this? I have the same issue, but logging in as root does not fix my problem. I joined the domain via konsole (see http://www.soluflex.co.uk/index.php?option=com_content&view=article&id=74&catid=62:suse&Itemid=18 for the steps I followed). I tried using the boot.local script to rejoin the domain, but I get a message when the script runs saying that it was unable to find a DC for the domain. However, if I login and use the same commands as my boot.local script, it joins fine. Then I can logout and login with my domain account. -- 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c9 --- Comment #9 from Brian Gade <brian.gade@cdw.com> 2011-03-07 01:15:50 UTC --- I was able to get mine to work. After following the steps in my previous link, I did the following: YaST > Network Services > Hostnames, set a static entry for my domain controller YaST > Network Services > Kerberos Client, selected Use Kerberos YaST > Network Services > Windows Domain Membership, Check "Also Use SMB Information for LinuxAuthentication" and "Offline Authentication." After those steps, I was able to login to the domain immediately after reboot. My domain selection list also populated itself with the rest of the domains that my PDC is aware of. -- 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c10 --- Comment #10 from Todd R <toddrme2178@gmail.com> 2011-03-07 02:04:02 UTC --- Sorry, I've been doing some extremely long (~several weeks) runs on that computer and haven't been able to restart to test 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c11 --- Comment #11 from Brian Gade <brian.gade@cdw.com> 2011-03-07 02:06:14 UTC --- Well, it was working until about five minutes ago. Now it shows the domains in the list but fails at logon. Not sure why yet, but I'm working on 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c12 --- Comment #12 from Brian Gade <brian.gade@cdw.com> 2011-03-07 02:16:15 UTC --- So now I've gotten it to the same point as Todd R, where my domain list will populate with local and null on reboot. Then if I wait a minute or two, it populates with the rest of the domain options. However, I have to login as root and then logout again before I can login with a domain account. -- 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c13 --- Comment #13 from Brian Gade <brian.gade@cdw.com> 2011-03-07 02:24:09 UTC --- So I've confirmed 100% that the issue is definately within KDM and not the kernel. If I get to the KDM login and have a local + null domain list, I can still login with a domain account via a console login. Then I startx and everything is normal. Why this happens is beyond my level of linux expertise, but at least we know this much... -- 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=630845 https://bugzilla.novell.com/show_bug.cgi?id=630845#c14 Lars Müller <lmuelle@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED CC| |kde-maintainers@suse.de InfoProvider|toddrme2178@gmail.com | Resolution| |NORESPONSE --- Comment #14 from Lars Müller <lmuelle@suse.com> 2012-03-27 14:32:19 CEST --- Can you please test this with a more recent openSUSE version like 12.1 or openSUSE Factory and please reopen this issue if it still applies. Sorry for the late reply, we had other more pressing issues. If this still applies we have to shift this issue to the KDE guys. The display managers have to check repopulate the list of available domains if they're configured to display a domain list. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com