[Bug 762437] New: Winbind does not work after reboot
https://bugzilla.novell.com/show_bug.cgi?id=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c0 Summary: Winbind does not work after reboot Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Samba AssignedTo: samba-maintainers@SuSE.de ReportedBy: luizluca@tre-sc.gov.br QAContact: samba-maintainers@SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 Hello, It seems like winbind is started too soon in systemd. Sometimes I get the message that "domain controler cannot be reached". Other times, I get "Time screw error" because winbind uses the clock with 1 hour less than the real one. After boot, if I restart winbind, it just works. How can I debug this problem? Reproducible: Always Steps to Reproduce: 1.Use domain authentication 2.Reboot 3.Login Actual Results: 4.One of the commented errors but I get login using offline cache login but no kerberos Expected Results: 4.Correct login and kerberos -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c1 David Disseldorp <ddiss@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddiss@suse.com --- Comment #1 from David Disseldorp <ddiss@suse.com> 2012-05-24 11:09:23 UTC --- Thanks for the report. As you've suggested, it sounds like systemd is bringing up winbind prior to the network dependency. Are you using NTP in this setup? -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c2 --- Comment #2 from Luiz Angelo Daros de Luca <luizluca@tre-sc.gov.br> 2012-05-24 17:18:13 UTC --- Yes I use ntp. I don't know why the hwclock is 2 hours before. My TZ is -03:00 (-02:00 from Oct to Feb on SummerTime). # hwclock ; date; date +%z Thu May 24 11:47:50 2012 -0.844201 seconds Thu May 24 13:47:50 BRT 2012 -0300 $ ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *LOCAL(0) .LOCL. 10 l 9 64 1 0.000 0.000 0.000 xxx.xxx.xxx.xx .INIT. 16 u 2 64 0 0.000 0.000 0.000 # cat /etc/sysconfig/clock | grep -v "^#" HWCLOCK="--localtime" SYSTOHC="" TIMEZONE="America/Sao_Paulo" DEFAULT_TIMEZONE="Brazil/East" America/Sao_Paulo and Brazil/East (BRT) are equilavents Winbind should depend on ntp? Why my hwclock is -0200? Maybe init process still uses TZ=-0200. At the time the system installation was performed, the current tz was -0200 (BRST), but still America/Sao_Paulo and Brazil/East. I don't know what to look for. -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c3 --- Comment #3 from Luiz Angelo Daros de Luca <luizluca@tre-sc.gov.br> 2012-05-24 17:36:31 UTC --- I found that if I manually set the hwclock, it works. So, according to /etc/sysconfig/clock comments: # Is set to "yes" write back the system time to the hardware # clock at reboot or shutdown. Usefull if hardware clock is # much more inaccurate than system clock. Set to "no" if # system time does it wrong due e.g. missed timer interrupts. # If set to "no" the hardware clock adjust feature is also # skipped because it is rather useless without writing back # the system time to the hardware clock. # # Note that you need to enable boot.clock for this feature to take # effect. # # defaults to 'yes' if unset # SYSTOHC="" It should set the hwclock on every reboot, which happens once a week. So is it a systemd init problem with clock? -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c4 --- Comment #4 from David Disseldorp <ddiss@suse.com> 2012-06-01 15:06:33 UTC --- (In reply to comment #3)
I found that if I manually set the hwclock, it works.
...
# Note that you need to enable boot.clock for this feature to take # effect. # # defaults to 'yes' if unset # SYSTOHC=""
It should set the hwclock on every reboot, which happens once a week. So is it a systemd init problem with clock?
Do you have boot.clock enabled? -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c5 James McDonough <jmcdonough@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jmcdonough@suse.com InfoProvider| |luizluca@tre-sc.gov.br --- Comment #5 from James McDonough <jmcdonough@suse.com> 2012-07-19 20:18:38 UTC --- setting needinfo. -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c6 Luiz Angelo Daros de Luca <luizluca@tre-sc.gov.br> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|luizluca@tre-sc.gov.br | --- Comment #6 from Luiz Angelo Daros de Luca <luizluca@tre-sc.gov.br> 2012-07-19 21:05:50 UTC --- systemd does not have boot.clock $ systemctl | grep boot boot.mount loaded active mounted /boot cycle.service loaded active exited LSB: Set default boot entry if called rc-local.service loaded active exited /etc/init.d/boot.local Compatibility $ /bin/systemctl --all | grep clock So I did a chkconfig: $ sudo chkconfig boot.clock boot.clock off $ sudo chkconfig boot.clock on Forwarding request to '/bin/systemctl --root / enable clock.service'. Is this a problem at default config? -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c7 David Disseldorp <ddiss@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |luizluca@tre-sc.gov.br --- Comment #7 from David Disseldorp <ddiss@suse.com> 2012-08-07 13:18:50 UTC --- (In reply to comment #6) ...
$ sudo chkconfig boot.clock on Forwarding request to '/bin/systemctl --root / enable clock.service'.
Is this a problem at default config?
I don't think so, as normally the hw clock should work without needing to be rewritten on shutdown. Can you confirm that winbind works with your hw clock fixed? If so I'd like to close this bug. -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c8 --- Comment #8 from James McDonough <jmcdonough@suse.com> 2012-09-06 11:43:17 UTC --- ping... nearly one month... -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c9 James McDonough <jmcdonough@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|luizluca@tre-sc.gov.br | Resolution| |NORESPONSE --- Comment #9 from James McDonough <jmcdonough@suse.com> 2012-09-10 10:42:51 UTC --- No response -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c10 Luiz Angelo Daros de Luca <luizluca@tre-sc.gov.br> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|NORESPONSE | --- Comment #10 from Luiz Angelo Daros de Luca <luizluca@tre-sc.gov.br> 2012-09-10 18:27:42 UTC --- Sorry James, I guess I missed the August email. The problem is when the hw clock is set to be at localtime. When we change to/from summertime, I got the problem described here. I guess the hw clock must be updated whether there is any significant difference at sw (from ntp) and hw time at shutdown (including the case of timezone change). For a brute-force approach, just update it everytime. Winbind works after the hwclock is set. However, it will fail again when I get again in the summertime period. -- 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=762437 https://bugzilla.novell.com/show_bug.cgi?id=762437#c11 James McDonough <jmcdonough@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |WONTFIX --- Comment #11 from James McDonough <jmcdonough@suse.com> 2014-01-07 13:19:52 UTC --- Closed as this product is out of support. If it reoccurs on 13.1, please reopen. Also please ensure the clock is properly configured. -- 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