https://bugzilla.novell.com/show_bug.cgi?id=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c2 --- Comment #2 from Heiner Markert 2012-09-09 16:08:03 UTC --- I tried replacing line 247 mount -at nfs,nfs4 || rc_failed 1 with sleep 2 && mount -at nfs,nfs4 & in /etc/init.d/nfs as suggested in the comment a few lines above in the same file. This makes the nfs-mount come up on boot for me. I now think this is some sort of dependency issue, as obviously the two seconds delay are enough to start the missing components. I compared the /etc/init.d/nfs scripts in 12.1 and 12.2, they are identical. In 12.1, nfs mounts come up on boot fine. There was however a similar issue with nfs mounts during boot, see bug 738448 (I don't know if it is related to this issue). -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c5 --- Comment #5 from Heiner Markert 2012-09-12 19:06:22 UTC --- I finally found the reason for that: It's a problem with the system time. If the hw clock is set to UTC, then when the system tries to mount the nfs share, the system time is still set to UTC, as the clock is adjusted later in the boot process. This causes a difference to "real time" of 2 hours for me (Germany). With such a high offset, the kerberos mount is denied by the server, which causes the problem. As a workaround I did set my hw clock to local time, which makes the problem disappear (at least as long as there is no clock offset due to daylight saving changes). A better solution would be to set the system date and time earlier in the boot process, at least before trying to mount nfs shares. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c7 --- Comment #7 from Heiner Markert 2012-09-29 17:47:14 UTC --- Hi, sorry for the delay, I did not have time to look further into this earlier. a grep HWCLOCK /etc/sysconfig/clock outputs USE_HWCLOCK="yes" Which is probably not quite what was expected. I have my system clock set to localtime, as I sometimes have to use Windows on that particular computer. Hence, I did set the corresponding option in yast that my hardware clock is set to localtime. After some experiments today, I found that everything works as expected if I config yast to set the system clock to UTC and actually set the hardware clock accordingly. If I set it to localtime in yast and adjust the hardware clock prior to booting SuSE 12.2, everything also works well. However, on shutdown or reboot, SuSE sets the hardware clock back to UTC, even if localtime is configured in yast. This causes the time offset during the next boot. Things get fixed when sntpd is started (because it readjusts the clock immediately), but this is too late in the boot process. For me, this basically seems not to be a bug in NFS, but in the scripts that store the system time back to hardware clock on reboot/shutdown. I did not yet try to add "boot.clock" to "Required-Start:" in the init script, and currently I think it will not help much. Probably, sntpd should be started prior to NFS, which would allow to correct large drifts of the hardware clock when the computer is off. However, the real cause of the problem seems to be in the shutdown scripts. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c9 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |jsuchome@suse.com, | |werner@suse.com InfoProvider|werner@suse.com | --- Comment #9 from Dr. Werner Fink 2012-10-02 06:54:11 UTC --- The question rises if /etc/sysconfig/clock and /etc/adjtime from disk are in sync with /etc/sysconfig/clock and /etc/adjtime in the initrd as otherwise the warpclock utility can not inform the kernel about the broken local time in CMOS and tell the kernel the offset to enable the kernel to set its own system clock back to real UTC. The can be check with the command lsinitrd -l /boot/initrd | grep -E '(sysconfig/clock|etc/adjtime|warpclock)' In fact if there is no old Windows[tm] system in parallel then UTC in CMOS is recommended! With Windows7[tm] and above it is possible to use UTC in CMOS. For older Windows[tm] systems it is essential to help the linux kernel to have correct UTC in its system clock as this is the reference for network time as well as for the user time. For this mkinitrd is used to copy /etc/sysconfig/clock and /etc/adjtime together with the warpclock tool from disk into the initrd, the initial ram disk to set the system clock of the kernel back to UTC before any file system is checked and touched by the kernel. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c11 --- Comment #11 from Dr. Werner Fink 2012-10-05 07:34:48 UTC --- The script /lib/mkinitrd/scripts/boot-clock.sh should be part of the initrd as well below the boot/ directory as e.g. boot/05-clock.sh in the initrd and this script does touch a controls file below /dev/shm/ ... that is you should have a file /dev/shm/warpclock after the system has booted. Also you should be aware that you have to make sure that the Daylight Saving Time switch is not done automatically, that is this has to be done by you or the by the foreign OS. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c13 --- Comment #13 from Dr. Werner Fink 2012-10-10 06:58:13 UTC --- AFAIK for the the boot scrip /etc/init.d/boot.clock has to be enabled and AFAIK this is *not* the case for openSUSE 12.2. Beside this up to the point where warpclock informs the kernel about the wrong CMOS clock the kernels initial system clock is not in UTC as the kernel always assumes that the CMOS clock is in UTC. Only the warpclock program in initrd tells the kernel that the CMOS clock is not in UTC and provides the clock offset with the settimeofday(2) system call with the correct struct timezone. Compare this with the source code of the warpclock program. You may check you CMOS clock by switching into the BIOS before booting into Linux. Then you should check if both the /etc/localtime in initrd and on disk is correct and identical with the zoneinfo file below /usr/share/zoneinfo for your timezone specified in /etc/sysconfig/clock in the variable TIMEZONE. E.g. by using . /etc/sysconfig/clock cmp /etc/localtime /usr/share/zoneinfo/$TIMEZONE zcat /boot/initrd | cpio -i --quiet --to-stdout etc/localtime | cmp /etc/localtime - Also please make sure to have all updates for openSUSE 12.2 installed. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c15 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #15 from Dr. Werner Fink 2012-10-12 06:44:23 UTC --- Try grep -rsl hwclock /etc/init.d/*.d/ /etc/systemd/ /lib/systemd/ \ /etc/udev/ /lib/udev/ /etc/profile.d/ to check this. Add the maintainer of systemd to CC list as this could be a problem with one of the systemd scriplets. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c17 Dr. Werner Fink changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mephisto@gmx.net --- Comment #17 from Dr. Werner Fink 2012-10-12 10:53:36 UTC --- I've added Frederic already :) Now let us ask Frederic if the problem could occur dues /lib/systemd/systemd and/or /lib/systemd/systemd-timedated as the strings command shows /suse/werner> strings /lib/systemd/systemd | grep hwclock hwclock_apply_localtime_delta /suse/werner> strings /lib/systemd/systemd-timedated | grep hwclock hwclock_apply_localtime_delta hwclock_get_time hwclock_set_time before this I'd like to know the content of /etc/adjtime of both initrd and disk as well the value of the variable TIMEZONE in /etc/sysconfig/clock of both initrd and disk. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c19 --- Comment #19 from Heiner Markert 2012-10-27 19:03:17 UTC --- /etc/adjtime (initrd): 436.719742 1348907835 0.000000 1348907835 LOCAL /etc/adjtime (system): 436.719742 1348907835 0.000000 1348907835 LOCAL value of TIMEZONE in /etc/sysconfig/clock (system): TIMEZONE="Europe/Berlin" File /etc/sysconfig/clock does not exist in initrd: # ls -l /tmp/initrd/etc/sysconfig total 4 -rw-r--r-- 1 root root 0 Oct 27 18:55 kernel drwxr-xr-x 6 root root 4096 Oct 27 18:55 network

From my understanding this would mean that the system does not know about the correct timezone during early boot, as initrd does not contain the required information. This seems to explain the behavior.

Given that /etc/sysconfig/clock does not exist in initrd, do you still need the dmesg debug output of systemd? -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c21 --- Comment #21 from Heiner Markert 2012-11-03 15:43:30 UTC --- The files etc/localtime and etc/adjtime are available in my initrd and identical to those on /etc (at least identical time stamp and file size). usr/share/zoneinfo/UTC is available in the initrd and identical to the version in /usr, according to time stamp and file size bin/warpclok is available in initrd. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c23 --- Comment #23 from Heiner Markert 2012-11-03 17:01:37 UTC --- Created an attachment (id=511854) --> (http://bugzilla.novell.com/attachment.cgi?id=511854) dmesg output after booting with systemd.log_level=debug, hw clock initially right This is the output of dmesg after booting with systemd.log_level=debug, systemd.log_target=kmsg and the system clock being set to localtime manually before booting. Note that in this case, the first boot is successful (/home partition gets mounted successfully via kerberized nfs4). While booting the hwclock is however set to UTC, so that subsequent boots fail. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c25 Heiner Markert changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mephisto@gmx.net | --- Comment #25 from Heiner Markert 2012-12-24 19:08:22 UTC --- Has any progress on this bug been archived? -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #511854|application/octet-stream |text/plain mime type| | -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c27 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|fcrozat@suse.com |mephisto@gmx.net --- Comment #27 from Frederic Crozat 2013-01-31 17:37:28 UTC --- there is something problematic in your systemd log: if systemd was correctly detecting your system configured as localtime, we should see on the log something like : "[ 6.894360] systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time." or an error message. And yet, we don't see it in both logs, so systemd doesn't apply localtime delta to your system, which could explain your issue (and since you use ntp, clock is becoming "fixed" somehow while system is running. Please attach /etc/adjtime to this bug report -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c29 --- Comment #29 from Dr. Werner Fink 2013-02-01 08:08:25 UTC --- Created an attachment (id=522946) --> (http://bugzilla.novell.com/attachment.cgi?id=522946) clocktest --- a bash script to check clock setup A bash script I've wrote to check clock configuration -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c31 --- Comment #31 from Dr. Werner Fink 2013-02-01 09:32:00 UTC --- (In reply to comment #30) Please could you retest as I'd like to see an strace of the warpclock call that is please add strace to the initrd and reboot to do so. The mkinitrd package should have the changelog entry Wed Jul 4 2012 werner@suse.de - Fix boot clock scriptlet by testing /etc/adjtime before /etc/sysconfig/clock to make sure that warpclock is executed if CMOS clock is in local time otherwise it will not work correct -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c33 --- Comment #33 from Dr. Werner Fink 2013-02-01 16:25:24 UTC --- Thanks ... found a bug. the only problem that the mkinitrd for 12.2 is locked due an other maintenance act (#672) -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c35 --- Comment #35 from Dr. Werner Fink 2013-02-01 16:40:57 UTC --- Thanks a lot ... in Base:System you find a fixed version of mkinitrd. This one should do the job. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c37 --- Comment #37 from Bernhard Wiedemann 2013-02-01 19:00:09 CET --- This is an autogenerated message for OBS integration: This bug (779145) was mentioned in https://build.opensuse.org/request/show/150758 Factory / mkinitrd -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c39 --- Comment #39 from Frederic Crozat 2013-02-05 08:50:23 UTC --- just wondering, could this bug be a duplicate of bnc#791106 ? Heiner, could you try updating ntp from update and see if clock is becoming wrong after two boots ? -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c42 --- Comment #42 from Bernhard Wiedemann 2013-02-14 15:00:10 CET --- This is an autogenerated message for OBS integration: This bug (779145) was mentioned in https://build.opensuse.org/request/show/155423 Maintenance / -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c43 --- Comment #43 from Benjamin Brunner 2013-02-21 13:34:01 CET --- The mkinitrd update for openSUSE 12.2 is released. Feel free to close the bug if everything is done. -- 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=779145 https://bugzilla.novell.com/show_bug.cgi?id=779145#c45 --- Comment #45 from Heiner Markert 2013-02-21 20:53:43 UTC --- The update "openSUSE-RU-2013:0317-1" fixes the problem for me, thank you! -- 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.