Bug 22167

Summary:	Attempting to configure an ntp server gives error
Product:	Mageia	Reporter:	andré blais <andr999>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	Normal	CC:	guillomovitch, lists.jjorge, luigiwalser, marja11
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	ntp-4.2.6p5-33.mga6.src.rpm	CVE:
Status comment:

Description andré blais 2017-12-10 22:34:25 CET

Description of problem:

See summary.
Error message = 
"Impossible de synchroniser avec 'ca.pool.ntp.org'."
(Impossible to synchronise with ...)

'north-america.pool.ntp.org' was also tried, with same result.

Function accessed via MCC/System/Configure date & time.

My ntp.conf file contains already
server 0.ca.pool.ntp.org
server 1.ca.pool.ntp.org
server 2.ca.pool.ntp.org

Note that http://www.pool.ntp.org/zone/ca
suggests an additional line of
server 3.ca.pool.ntp.org

Don't think that that would make any difference.

Entering '0.ca.pool.ntp.org' in navigator shows that site does respond.

Comment 1 andré blais 2017-12-10 22:37:56 CET

Use desktop mate fully up to date.
Another user reports same problem on KDE Plasma.

Comment 2 Marja Van Waes 2017-12-11 16:09:54 CET

Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC'ing some recent committers.

CC: (none) => guillomovitch, lists.jjorge, luigiwalser, marja11
Assignee: bugsquad => pkg-bugs

Comment 3 Guillaume Rousse 2017-12-11 19:22:46 CET

You have to use a suitable ntp server, such as documented here:
http://www.pool.ntp.org/en/use.html

I'm closing this ticket as invalid, as I don't see any evidence of a software/package malfunction here.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 Guillaume Rousse 2017-12-11 19:30:03 CET

BTW, I couldn't reproduce the issue, even using the same server set, meaning your issue may not be related to your ntp setup.

Comment 5 andré blais 2017-12-11 21:48:49 CET

It must have been a transient problem in the pool.ntp.org network
 (at least for ca and north-america),
since it now works without making any changes in my configuration.