Description of problem: ntpdate service fails to start Version-Release number of selected component (if applicable): ntpdate-4.2.8p11-1.mga6 How reproducible: # systemctl start ntpdate Job for ntpdate.service failed because the control process exited with error code. See "systemctl status ntpdate.service" and "journalctl -xe" for details.
What's the output of 'systemctl status ntpdate.service -l -n50'?
There are 2 problems in this package. 1. Invalid path to 'ntpdate-wrapper' Edit '/lib/systemd/system/ntpdate.service' Change: ExecStart=/usr/sbin/ntpdate-wrapper to: ExecStart=/usr/libexec/ntpdate-wrapper 2. Invalid option '-U ntp' in ntpdate command Edit '/usr/libexec/ntpdate-wrapper' Change: /usr/sbin/ntpdate -U ntp -s -b $OPTIONS $tickers &> /dev/null To /usr/sbin/ntpdate -s -b $OPTIONS $tickers &> /dev/null
(In reply to Jani Välimaa from comment #1) > What's the output of 'systemctl status ntpdate.service -l -n50'? Here is the result when using the original ntpclient package: * ntpdate.service - Set time via NTP Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since mar. 2018-05-01 14:12:59 CEST; 1s ago Process: 31776 ExecStart=/usr/sbin/ntpdate-wrapper (code=exited, status=203/EXEC) Main PID: 31776 (code=exited, status=203/EXEC) mai 01 14:12:59 envy systemd[1]: Starting Set time via NTP... mai 01 14:12:59 envy systemd[1]: ntpdate.service: Main process exited, code=exited, status=203/EXEC mai 01 14:12:59 envy systemd[1]: Failed to start Set time via NTP. mai 01 14:12:59 envy systemd[1]: ntpdate.service: Unit entered failed state. mai 01 14:12:59 envy systemd[1]: ntpdate.service: Failed with result 'exit-code'.
CC: (none) => lists.jjorge, luigiwalser, marja11Assignee: bugsquad => pkg-bugs
It was my fault, with last ntp update I forgot to sync some SOURCE files.
Assignee: pkg-bugs => qa-bugsStatus: NEW => ASSIGNED
Suggested advisory : Last ntp security update broke ntpdate service start. This update fixes the startup scripts. Updated packages in {core}/updates_testing: ======================== ntp-4.2.8p11-1.1.mga6 ntpdate-4.2.8p11-1.1.mga6 sntp-4.2.8p11-1.1.mga6 ntp-doc-4.2.8p11-1.1.mga6 ntp-perl-4.2.8p11-1.1.mga6
*** Bug 23001 has been marked as a duplicate of this bug. ***
CC: (none) => petlaw726
Mageia 6, x86_64 Installed the updates and tried to start ntpdate.service. It failed even though the startup scripts had been modified. Shall poke around a bit but it does not look good.
CC: (none) => tarazed25
(In reply to José Jorge from comment #5) > Suggested advisory : > > Last ntp security update broke ntpdate service start. This update fixes the > startup scripts. > > > Updated packages in {core}/updates_testing: > ======================== > ntp-4.2.8p11-1.1.mga6 > ntpdate-4.2.8p11-1.1.mga6 > sntp-4.2.8p11-1.1.mga6 > ntp-doc-4.2.8p11-1.1.mga6 > ntp-perl-4.2.8p11-1.1.mga6 for me the same as Len Lawrence: ntpdate-4.2.8p11-1.1.mga6 doesn't work sorry
The problem was a clash with ntpd. 'journalctl -xe' yields "port already in use". # systemctl stop ntpd # systemctl start ntpdate # systemctl status ntpdate ● ntpdate.service - Set time via NTP Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; disabled; vendor pre Active: active (exited) since Tue 2018-05-08 13:44:16 BST; 12s ago Process: 2439 ExecStart=/usr/libexec/ntpdate-wrapper (code=exited, status=0/SU Main PID: 2439 (code=exited, status=0/SUCCESS) May 08 13:44:10 difda systemd[1]: Starting Set time via NTP... May 08 13:44:16 difda systemd[1]: Started Set time via NTP. So it works.
(In reply to Len Lawrence from comment #9) > The problem was a clash with ntpd. 'journalctl -xe' yields "port already in > use". > > # systemctl stop ntpd > # systemctl start ntpdate > # systemctl status ntpdate > ● ntpdate.service - Set time via NTP > Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; disabled; vendor > pre > Active: active (exited) since Tue 2018-05-08 13:44:16 BST; 12s ago > Process: 2439 ExecStart=/usr/libexec/ntpdate-wrapper (code=exited, > status=0/SU > Main PID: 2439 (code=exited, status=0/SUCCESS) > > May 08 13:44:10 difda systemd[1]: Starting Set time via NTP... > May 08 13:44:16 difda systemd[1]: Started Set time via NTP. > > So it works. perhaps (I've not yet tested), but ntpd no longer works!
Hello, by default, you cannot use 'ntpdate' command when 'ntpd' is running. This is not a Mageia bug, this is how ntpd works. Usually, ntpdate is run once at boot time, before ntpd is started. If you want to run ntpdate after system is started: Solution 1: # systemctl stop ntpd # systemctl start ntpdate # systemctl start ntpdate Solution 2: Add '-u' (lowercase) option to 'ntpdate' command. E.g; in '/usr/libexec/ntpdate-wrapper', line 28: /usr/sbin/ntpdate -u -s -b $OPTIONS $tickers &> /dev/null
(In reply to Len Lawrence from comment #9) > The problem was a clash with ntpd. 'journalctl -xe' yields "port already in > use". > > # systemctl stop ntpd > # systemctl start ntpdate > # systemctl status ntpdate > ● ntpdate.service - Set time via NTP > Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; disabled; vendor > pre > Active: active (exited) since Tue 2018-05-08 13:44:16 BST; 12s ago > Process: 2439 ExecStart=/usr/libexec/ntpdate-wrapper (code=exited, > status=0/SU > Main PID: 2439 (code=exited, status=0/SUCCESS) > > May 08 13:44:10 difda systemd[1]: Starting Set time via NTP... > May 08 13:44:16 difda systemd[1]: Started Set time via NTP. > > So it works. sorry, it doesn't work for me: [root@mag6 alain4]# systemctl stop ntpd.service [root@mag6 alain4]# systemctl start ntpdate.service Job for ntpdate.service failed because the control process exited with error code. See "systemctl status ntpdate.service" and "journalctl -xe" for details.
(In reply to François Andriot from comment #11) > Hello, by default, you cannot use 'ntpdate' command when 'ntpd' is running. > This is not a Mageia bug, this is how ntpd works. > > Usually, ntpdate is run once at boot time, before ntpd is started. > > If you want to run ntpdate after system is started: > > Solution 1: > # systemctl stop ntpd > # systemctl start ntpdate > # systemctl start ntpdate > > Solution 2: > Add '-u' (lowercase) option to 'ntpdate' command. > E.g; in '/usr/libexec/ntpdate-wrapper', line 28: > /usr/sbin/ntpdate -u -s -b $OPTIONS $tickers &> /dev/null neither your solution 1 nor solution 2 work (for sol. 1 see comment 12)
(In reply to François Andriot from comment #11) > Hello, by default, you cannot use 'ntpdate' command when 'ntpd' is running. > This is not a Mageia bug, this is how ntpd works. > > Usually, ntpdate is run once at boot time, before ntpd is started. > > If you want to run ntpdate after system is started: > > Solution 1: > # systemctl stop ntpd > # systemctl start ntpdate > # systemctl start ntpdate > > Solution 2: > Add '-u' (lowercase) option to 'ntpdate' command. > E.g; in '/usr/libexec/ntpdate-wrapper', line 28: > /usr/sbin/ntpdate -u -s -b $OPTIONS $tickers &> /dev/null furthermore the line 28 of '/usr/libexec/ntpdate-wrapper' is: /usr/sbin/ntpdate -U ntp -s -b $OPTIONS $tickers &> /dev/null which is different of what you wrote: I replaced '-U ntp' by '-u' following your indication, and it didn't work
(In reply to peter lawford from comment #14) > > furthermore the line 28 of '/usr/libexec/ntpdate-wrapper' is: > /usr/sbin/ntpdate -U ntp -s -b $OPTIONS $tickers &> /dev/null > > which is different of what you wrote: I replaced '-U ntp' by '-u' following > your indication, and it didn't work Did you install the updated ntp packages from the 'updates_testing', as said in comment#5 ? It looks like you didn't .... With current mga6 packages, Edit '/lib/systemd/system/ntpdate.service', change following line to: ExecStart=/usr/libexec/ntpdate-wrapper Edit '/usr/libexec/ntpdate-wrapper', change following line to: /usr/sbin/ntpdate -u -s -b $OPTIONS $tickers &> /dev/null Then run following commands systemctl daemon-reload systemctl start ntpdate It just works on my 4 computers running Mageia 6 ... I don't see why it wouldn't work on yours.
(In reply to François Andriot from comment #15) > (In reply to peter lawford from comment #14) > > > > furthermore the line 28 of '/usr/libexec/ntpdate-wrapper' is: > > /usr/sbin/ntpdate -U ntp -s -b $OPTIONS $tickers &> /dev/null > > > > which is different of what you wrote: I replaced '-U ntp' by '-u' following > > your indication, and it didn't work > > Did you install the updated ntp packages from the 'updates_testing', as said > in comment#5 ? It looks like you didn't .... > > With current mga6 packages, > > Edit '/lib/systemd/system/ntpdate.service', change following line to: > ExecStart=/usr/libexec/ntpdate-wrapper > > Edit '/usr/libexec/ntpdate-wrapper', change following line to: > /usr/sbin/ntpdate -u -s -b $OPTIONS $tickers &> /dev/null > > Then run following commands > systemctl daemon-reload > systemctl start ntpdate > > It just works on my 4 computers running Mageia 6 ... I don't see why it > wouldn't work on yours. OK! ntpdate (current mga6 package) works now and ntpd too! how have you found that? I am just an honest linux user, no more thank you very much for the indication
Both ntpd and ntpdate work at the same time for me as well now. Thanks for your input Peter and François. This update is OK. [OT] Hope to see you around Peter.
Whiteboard: (none) => MGA6-64-OK
FYI, there is a discussion about deprecating NTPdate. https://support.ntp.org/bin/view/Dev/DeprecatingNtpdate > ntpd and sntp now implements the functions of ntpdate. As soon as a few > remaining issues with sntp are resolved the ntpdate program will be retired The link gives command replacement for ntpdate.
CC: (none) => guichard.adrien
(In reply to Adrien Guichard from comment #18) > FYI, there is a discussion about deprecating NTPdate. > https://support.ntp.org/bin/view/Dev/DeprecatingNtpdate > > > ntpd and sntp now implements the functions of ntpdate. As soon as a few > > remaining issues with sntp are resolved the ntpdate program will be retired > > The link gives command replacement for ntpdate. I went to the link you gave above, and, as advised in this discussion, I typed under root the commande: ntpd -gq the result is catastrophic, since ntpd.service which worked well before refuses now to work, even through mcc > system > date/time: before typing ntpd -gq: [root@magaux alain4]# systemctl status ntpd.service ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: enabled) Active: active (running) since mer. 2018-05-09 11:50:08 CEST; 3s ago Process: 27921 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 27924 (ntpd) CGroup: /system.slice/ntpd.service └─27924 /usr/sbin/ntpd -u ntp:ntp -g mai 09 11:50:08 magaux systemd[1]: Starting Network Time Service... mai 09 11:50:08 magaux ntpd[27921]: ntpd 4.2.8p11@1.3728-o Mon Apr 2 08:42:42 UTC 2018 (1): Starting mai 09 11:50:08 magaux ntpd[27921]: Command line: /usr/sbin/ntpd -u ntp:ntp -g mai 09 11:50:08 magaux systemd[1]: Started Network Time Service. mai 09 11:50:08 magaux ntpd[27924]: proto: precision = 0.052 usec (-24) mai 09 11:50:08 magaux ntpd[27924]: Listen and drop on 0 v4wildcard 0.0.0.0:123 mai 09 11:50:08 magaux ntpd[27924]: Listen normally on 1 lo 127.0.0.1:123 mai 09 11:50:08 magaux ntpd[27924]: Listen normally on 2 eth2 192.168.1.14:123 mai 09 11:50:08 magaux ntpd[27924]: Listening on routing socket on fd #19 for interface updates after typing ntpd -gq: [root@magaux alain4]# systemctl status ntpd.service ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since mer. 2018-05-09 12:56:45 CEST; 3s ago Process: 6523 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 6526 (code=exited, status=1/FAILURE) mai 09 12:56:45 magaux systemd[1]: Starting Network Time Service... mai 09 12:56:45 magaux ntpd[6523]: ntpd 4.2.8p11@1.3728-o Tue May 1 12:56:04 UTC 2018 (1): Starting mai 09 12:56:45 magaux ntpd[6523]: Command line: /usr/sbin/ntpd -u ntp:ntp -g mai 09 12:56:45 magaux systemd[1]: Started Network Time Service. mai 09 12:56:45 magaux ntpd[6526]: proto: precision = 0.072 usec (-24) mai 09 12:56:45 magaux systemd[1]: ntpd.service: Main process exited, code=exited, status=1/FAILURE mai 09 12:56:45 magaux systemd[1]: ntpd.service: Unit entered failed state. mai 09 12:56:45 magaux systemd[1]: ntpd.service: Failed with result 'exit-code'. but ntpdate.service is now active what to do now for ntpd.service ?
I cannot reproduce on Mageia 6 and Mageia 7, but ntpdate is not started on my machines: [root@localhost auo]# systemctl stop ntpd.service [root@localhost auo]# ntpd -gq 9 May 15:52:16 ntpd[22838]: ntpd 4.2.8p11@1.3728-o Sun Apr 1 08:45:20 UTC 2018 (1): Starting 9 May 15:52:16 ntpd[22838]: Command line: ntpd -gq 9 May 15:52:16 ntpd[22838]: proto: precision = 0.030 usec (-25) 9 May 15:52:16 ntpd[22838]: Listen and drop on 0 v6wildcard [::]:123 9 May 15:52:16 ntpd[22838]: Listen and drop on 1 v4wildcard 0.0.0.0:123 9 May 15:52:16 ntpd[22838]: Listen normally on 2 lo 127.0.0.1:123 9 May 15:52:16 ntpd[22838]: Listen normally on 3 enp24s0 10.109.55.53:123 9 May 15:52:16 ntpd[22838]: Listen normally on 4 lo [::1]:123 9 May 15:52:16 ntpd[22838]: Listen normally on 5 enp24s0 [fe80::329c:23ff:feb0:810a%2]:123 9 May 15:52:16 ntpd[22838]: Listening on routing socket on fd #22 for interface updates 9 May 15:52:17 ntpd[22838]: Soliciting pool server 62.4.3.34 ^C 9 May 15:52:26 ntpd[22838]: ntpd exiting on signal 2 (Interrupt) [root@localhost auo]# systemctl start ntpd.service [root@localhost auo]# systemctl status ntpd.service ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2018-05-09 15:52:33 CEST; 10s ago Process: 23705 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 23707 (ntpd) CGroup: /system.slice/ntpd.service └─23707 /usr/sbin/ntpd -u ntp:ntp -g mai 09 15:52:33 localhost systemd[1]: Started Network Time Service. mai 09 15:52:33 localhost ntpd[23707]: proto: precision = 0.040 usec (-24) mai 09 15:52:33 localhost ntpd[23707]: Listen and drop on 0 v6wildcard [::]:123 mai 09 15:52:33 localhost ntpd[23707]: Listen and drop on 1 v4wildcard 0.0.0.0:123 mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 2 lo 127.0.0.1:123 mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 3 enp24s0 10.109.55.53:123 mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 4 lo [::1]:123 mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 5 enp24s0 [fe80::329c:23ff:feb0:810a%2]:123 mai 09 15:52:33 localhost ntpd[23707]: Listening on routing socket on fd #22 for interface updates mai 09 15:52:34 localhost ntpd[23707]: Soliciting pool server 62.4.3.34 [root@localhost auo]# Did you kill all ntpd process before trying to start ntpd? What happen if you stop ntpdate.service before starting ntpd?
(In reply to Adrien Guichard from comment #20) > I cannot reproduce on Mageia 6 and Mageia 7, but ntpdate is not started on > my machines: > > [root@localhost auo]# systemctl stop ntpd.service > [root@localhost auo]# ntpd -gq > 9 May 15:52:16 ntpd[22838]: ntpd 4.2.8p11@1.3728-o Sun Apr 1 08:45:20 UTC > 2018 (1): Starting > 9 May 15:52:16 ntpd[22838]: Command line: ntpd -gq > 9 May 15:52:16 ntpd[22838]: proto: precision = 0.030 usec (-25) > 9 May 15:52:16 ntpd[22838]: Listen and drop on 0 v6wildcard [::]:123 > 9 May 15:52:16 ntpd[22838]: Listen and drop on 1 v4wildcard 0.0.0.0:123 > 9 May 15:52:16 ntpd[22838]: Listen normally on 2 lo 127.0.0.1:123 > 9 May 15:52:16 ntpd[22838]: Listen normally on 3 enp24s0 10.109.55.53:123 > 9 May 15:52:16 ntpd[22838]: Listen normally on 4 lo [::1]:123 > 9 May 15:52:16 ntpd[22838]: Listen normally on 5 enp24s0 > [fe80::329c:23ff:feb0:810a%2]:123 > 9 May 15:52:16 ntpd[22838]: Listening on routing socket on fd #22 for > interface updates > 9 May 15:52:17 ntpd[22838]: Soliciting pool server 62.4.3.34 > ^C 9 May 15:52:26 ntpd[22838]: ntpd exiting on signal 2 (Interrupt) > [root@localhost auo]# systemctl start ntpd.service > [root@localhost auo]# systemctl status ntpd.service > ● ntpd.service - Network Time Service > Loaded: loaded (/usr/lib/systemd/system/ntpd.service; disabled; vendor > preset: disabled) > Active: active (running) since Wed 2018-05-09 15:52:33 CEST; 10s ago > Process: 23705 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, > status=0/SUCCESS) > Main PID: 23707 (ntpd) > CGroup: /system.slice/ntpd.service > └─23707 /usr/sbin/ntpd -u ntp:ntp -g > > mai 09 15:52:33 localhost systemd[1]: Started Network Time Service. > mai 09 15:52:33 localhost ntpd[23707]: proto: precision = 0.040 usec (-24) > mai 09 15:52:33 localhost ntpd[23707]: Listen and drop on 0 v6wildcard > [::]:123 > mai 09 15:52:33 localhost ntpd[23707]: Listen and drop on 1 v4wildcard > 0.0.0.0:123 > mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 2 lo 127.0.0.1:123 > mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 3 enp24s0 > 10.109.55.53:123 > mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 4 lo [::1]:123 > mai 09 15:52:33 localhost ntpd[23707]: Listen normally on 5 enp24s0 > [fe80::329c:23ff:feb0:810a%2]:123 > mai 09 15:52:33 localhost ntpd[23707]: Listening on routing socket on fd #22 > for interface updates > mai 09 15:52:34 localhost ntpd[23707]: Soliciting pool server 62.4.3.34 > [root@localhost auo]# > > > Did you kill all ntpd process before trying to start ntpd? > > What happen if you stop ntpdate.service before starting ntpd? I attempted to reproduce what you did; here is the result: [root@magaux alain4]# systemctl stop ntpd.service [root@magaux alain4]# ntpd -gq 9 May 16:12:32 ntpd[28203]: ntpd 4.2.8p11@1.3728-o Tue May 1 12:56:04 UTC 2018 (1): Starting 9 May 16:12:32 ntpd[28203]: Command line: ntpd -gq 9 May 16:12:32 ntpd[28203]: proto: precision = 0.052 usec (-24) 9 May 16:12:32 ntpd[28203]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING [root@magaux alain4]# systemctl start ntpd.service [root@magaux alain4]# systemctl status ntpd.service ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since mer. 2018-05-09 16:13:52 CEST; 9s ago Process: 2085 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2088 (code=exited, status=1/FAILURE) mai 09 16:13:51 magaux systemd[1]: Starting Network Time Service... mai 09 16:13:51 magaux systemd[1]: Started Network Time Service. mai 09 16:13:52 magaux systemd[1]: ntpd.service: Main process exited, code=exited, status=1/FAILURE mai 09 16:13:52 magaux systemd[1]: ntpd.service: Unit entered failed state. mai 09 16:13:52 magaux systemd[1]: ntpd.service: Failed with result 'exit-code'. as you can see, ntpd.service couldn't be reactivated but by killing the unique process of ntpd -g I have found, now ntpd.service can be activated, and ntpdate.service reminds active: [root@magaux alain4]# systemctl status ntpd.service ● ntpd.service - Network Time Service Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; vendor preset: enabled) Active: active (running) since mer. 2018-05-09 16:24:39 CEST; 6min ago Process: 2218 ExecStart=/usr/sbin/ntpd -u ntp:ntp $OPTIONS (code=exited, status=0/SUCCESS) Main PID: 2221 (ntpd) CGroup: /system.slice/ntpd.service └─2221 /usr/sbin/ntpd -u ntp:ntp -g mai 09 16:24:39 magaux systemd[1]: Starting Network Time Service... mai 09 16:24:39 magaux ntpd[2218]: ntpd 4.2.8p11@1.3728-o Tue May 1 12:56:04 UTC 2018 (1): Starting mai 09 16:24:39 magaux ntpd[2218]: Command line: /usr/sbin/ntpd -u ntp:ntp -g mai 09 16:24:39 magaux systemd[1]: Started Network Time Service. mai 09 16:24:39 magaux ntpd[2221]: proto: precision = 0.056 usec (-24) mai 09 16:24:39 magaux ntpd[2221]: Listen and drop on 0 v4wildcard 0.0.0.0:123 mai 09 16:24:39 magaux ntpd[2221]: Listen normally on 1 lo 127.0.0.1:123 mai 09 16:24:39 magaux ntpd[2221]: Listen normally on 2 eth2 192.168.1.14:123 mai 09 16:24:39 magaux ntpd[2221]: Listening on routing socket on fd #19 for interface updates [root@magaux alain4]# systemctl status ntpdate.service ● ntpdate.service - Set time via NTP Loaded: loaded (/usr/lib/systemd/system/ntpdate.service; disabled; vendor preset: enabled) Active: active (exited) since mer. 2018-05-09 16:19:45 CEST; 11min ago Process: 5399 ExecStart=/usr/libexec/ntpdate-wrapper (code=exited, status=0/SUCCESS) Main PID: 5399 (code=exited, status=0/SUCCESS) CGroup: /system.slice/ntpdate.service mai 09 16:19:39 magaux systemd[1]: Starting Set time via NTP... mai 09 16:19:45 magaux systemd[1]: Started Set time via NTP. it seems it was only a process problem actually everything is OK
Advisory from title, comment 5 and bug RPMs page.
Keywords: (none) => advisory, validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2018-0080.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED