http://bugzilla.suse.com/show_bug.cgi?id=1114388 http://bugzilla.suse.com/show_bug.cgi?id=1114388#c5 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com --- Comment #5 from Josef Reidinger <jreidinger@suse.com> --- (In reply to David Diaz from comment #4)

Hi Igor.

Sadly, I could not reproduce the described issue. However, I am not sure to be doing the right actions. Could you please give us the steps that you are following?

Also, could you attach the file generated by the `save_y2logs` command? It contains other files that bring us more detailed information such as the versions of packages.

With the attached log file, what I see suspicious is:

...

2018-11-06 15:56:25 <1> lnxvrx53(27015) [Ruby] modules/NtpClient.rb:157 Running ont time sync with pool.ntp.org 2018-11-06 15:56:26 <3> lnxvrx53(27015) [bash] ShellCommand.cc(shellcommand):78 2018-11-06T11:56:26Z chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG) 2018-11-06 15:56:26 <3> lnxvrx53(27015) [bash] ShellCommand.cc(shellcommand):78 2018-11-06T11:56:26Z Fatal error : Another chronyd may already be running (pid=27214), check /var/run/chrony/chronyd.pid 2018-11-06 15:56:26 <1> lnxvrx53(27015) [Ruby] modules/NtpClient.rb:168 'one-time chrony for pool.ntp.org' returned {"exit"=>1, "stderr"=>"2018-11-06T11:56:26Z chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP -SCFILTER +SIGND +ASYNCDNS +SECHASH +IPV6 -DEBUG)\n2018-11-06T11:56:26Z Fatal error : Another chronyd may already be running (pid=27214), check /var/run/chrony/chronyd.pid\n", "stdout"=>""}

Thank you so much for your report and collaboration.

well, that log line basically say that chronyd already running. So we cannot do one time sync, as daemon is already running and syncing time. This is different to ntp daemon, which allows such big steps in time. So basically we should not do one time sync if chronyd running. Only possibility is instead call chronyc with burst param, which will send multiple request to adapt time more quickly. -- You are receiving this mail because: You are on the CC list for the bug.