Bug #5671
Updated by Matthieu CERDA over 9 years ago
this causes issues on xen VMs...
those issues cause the technique to never be stable (if the interval is 240 min, it will go to error every 240 min)
there are many workarounds,
easiest thing would be to define a interval of 0 to not set the clock
more helpful things would be i.e. to disable that bit for xen pv + linux.
-No distro has ever simply fixed the issue within hwclock since it doesn't affect dev laptops :)-
@
2014-10-21T22:44:27+0200 info: /default/check_clock_configuration/commands/'/sbin/hwclock'[0]: Executing 'no timeout' ... '/sbin/hwclock --systohc'
2014-10-21T22:44:27+0200 error: /default/check_clock_configuration/commands/'/sbin/hwclock'[0]: Finished command related to promiser '/sbin/hwclock' -- an error occurred, returned 1
2014-10-21T22:44:27+0200 notice: /default/check_clock_configuration/commands/'/sbin/hwclock'[0]: Q: "...in/hwclock --sy": Cannot access the Hardware Clock via any known method.
Q: "...in/hwclock --sy": Use the --debug option to see the details of our search for an access method.
2014-10-21T22:44:27+0200 info: /default/check_clock_configuration/commands/'/sbin/hwclock'[0]: Last 2 quoted lines were generated by promiser '/sbin/hwclock --systohc'
2014-10-21T22:44:27+0200 info: /default/check_clock_configuration/commands/'/sbin/hwclock'[0]: Completed execution of '/sbin/hwclock --systohc'
R: @@ntpConfiguration@@result_success@@d3664232-fa67-48e3-8e92-0cbb147dfded@@e0f66890-bc7e-4618-ab62-a6f2d232d8c5@@6@@Time synchronization (NTP)@@None@@2014-10-21 20:44:21+00:00##f5b5ef75-b03f-4acc-a47b-ffbb4cea355b@#ntp daemon installed, configured and running
R: @@ntpConfiguration@@log_info@@d3664232-fa67-48e3-8e92-0cbb147dfded@@e0f66890-bc7e-4618-ab62-a6f2d232d8c5@@6@@Time synchronization (NTP)@@None@@2014-10-21 20:44:21+00:00##f5b5ef75-b03f-4acc-a47b-ffbb4cea355b@#ntp package already installed
R: @@ntpConfiguration@@result_error@@d3664232-fa67-48e3-8e92-0cbb147dfded@@e0f66890-bc7e-4618-ab62-a6f2d232d8c5@@6@@Hardware clock (RTC)@@None@@2014-10-21 20:44:21+00:00##f5b5ef75-b03f-4acc-a47b-ffbb4cea355b@#The hardware clock could not be synchronized with the NTP time
R: @@ntpConfiguration@@result_success@@d3664232-fa67-48e3-8e92-0cbb147dfded@@e0f66890-bc7e-4618-ab62-a6f2d232d8c5@@6@@Time zone@@None@@2014-10-21 20:44:21+00:00##f5b5ef75-b03f-4acc-a47b-ffbb4cea355b@#Time zone was already correctly configured
R: @@ntpConfiguration@@log_info@@d3664232-fa67-48e3-8e92-0cbb147dfded@@e0f66890-bc7e-4618-ab62-a6f2d232d8c5@@6@@Time zone@@None@@2014-10-21 20:44:21+00:00##f5b5ef75-b03f-4acc-a47b-ffbb4cea355b@#Time zone was already set (localtime file didn't need changing)
R: @@ntpConfiguration@@log_info@@d3664232-fa67-48e3-8e92-0cbb147dfded@@e0f66890-bc7e-4618-ab62-a6f2d232d8c5@@6@@Time zone@@None@@2014-10-21 20:44:21+00:00##f5b5ef75-b03f-4acc-a47b-ffbb4cea355b@#SuSE-style time zone parameters already correct (/etc/sysconfig/clock)
@