Re: NTP synchronized: no

From your email on Sep 8th: > chronyc sources > 210 Number of sources = 4 > MS Name/IP address Stratum Poll Reach LastRx Last sample > === > ^? host3.nuagelibre.org 0 8

Re: NTP synchronized: no

Hello, Following the previous email exchange, what is the next step? Is the issue clearly identified? Do I need to run more tests? Thank. === Patrick DUPRÉ | | email: pdu...@gmx.com Laborato

Re: NTP synchronized: no

On 10/09/15 00:01, Shaheen Bakhtiar wrote: On Sep 9, 2015, at 3:47 PM, John Pilkington wrote: On 09/09/15 23:43, Ed Greshko wrote: On 09/10/15 06:18, John Pilkington wrote: ... and (on my SL7 box) # tcpdump port 123 shows the outgoing probe and the response, for calculation of the transit t

Re: NTP synchronized: no

> On Sep 9, 2015, at 3:47 PM, John Pilkington wrote: > > On 09/09/15 23:43, Ed Greshko wrote: >> On 09/10/15 06:18, John Pilkington wrote: >>> ... and (on my SL7 box) # tcpdump port 123 >>> shows the outgoing probe and the response, for calculation of the transit >>> time: >>> >>> 23:01:55.706

Re: NTP synchronized: no

On 09/09/2015 03:43 PM, Ed Greshko wrote: Nice to know Yet you really should consider trimming. Otherwise you'll start to prove top-posters right. :-) :-) Indeed. One of my pet peeves is people who respond to something in the middle of a message and then quote the remainder, including

Re: NTP synchronized: no

On 09/09/15 23:43, Ed Greshko wrote: On 09/10/15 06:18, John Pilkington wrote: ... and (on my SL7 box) # tcpdump port 123 shows the outgoing probe and the response, for calculation of the transit time: 23:01:55.706587 IP HP_Box.home.ntp > vpn.webersheim.de.ntp: NTPv3, Client, length 48 23:01:5

Re: NTP synchronized: no

On 09/10/15 06:18, John Pilkington wrote: > ... and (on my SL7 box) # tcpdump port 123 > shows the outgoing probe and the response, for calculation of the transit > time: > > 23:01:55.706587 IP HP_Box.home.ntp > vpn.webersheim.de.ntp: NTPv3, Client, > length 48 > 23:01:55.741872 IP vpn.webersheim

Re: NTP synchronized: no

lt;http://smtp.inksystemsinc.com/> systemd[1]: Started NTP client/server. [root@smtp ~]# timedatectl Local time: Wed 2015-09-09 12:02:28 PDT Universal time: Wed 2015-09-09 19:02:28 UTC RTC time: Wed 2015-09-09 19:02:34 Time zone: America/Los_Angeles (PDT, -0700) NTP ena

Re: NTP synchronized: no

t > there regarding this. IT is a BAD implementation. It all but forces on to > simply buy a GPS unit or time server and house it on site. > > http://superuser.com/questions/141772/what-are-the-iptables-rules-to-permit-ntp > > <http://superuser.com/questions

Re: NTP synchronized: no

On 09/10/15 03:36, Patrick Dupre wrote: > journalctl -u chronyd -b > > - Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 21:30:01 > CE > Sep 08 11:48:18 Homere chronyd[940]: chronyd version 1.31.1 starting > Sep 08 11:48:18 Homere chronyd[940]: Frequency -15.841 +/- 0.025 ppm re

Re: NTP synchronized: no

On 9 September 2015 at 21:40, Patrick Dupre wrote: > > On 09/09/2015 10:37 AM, Patrick Dupre wrote: > I do not see any ntpd running, ntp is not installed! > > "NTP client/server" _is_ chronyd; this is just systemd's weird habit of showing a service "description" and not the actual .service name..

Re: NTP synchronized: no

> On 09/09/2015 10:37 AM, Patrick Dupre wrote: > > Still the same (always as root) > > > > journalctl -u chrony -b > > -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 > > 19:34:53 CEST. -- > > > > > > after systemctl restart chronyd > > > > systemctl list-unit-files | grep

Re: NTP synchronized: no

journalctl -u chronyd -b - Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 21:30:01 CE Sep 08 11:48:18 Homere chronyd[940]: chronyd version 1.31.1 starting Sep 08 11:48:18 Homere chronyd[940]: Frequency -15.841 +/- 0.025 ppm read from / Sep 08 12:08:01 Homere systemd[1]: Stoppin

Re: NTP synchronized: no

On 09/10/15 01:00, Rick Stevens wrote: > > journalctl -u chrony -b You want journalctl -u chronyd -b -- It seems most people that say they are "done talking about it" never really are until given the last word. -- users mailing list users@lists.fedoraproject.org To unsubscribe or c

Re: NTP synchronized: no

ttp://superuser.com/questions/762579/why-does-ntp-require-bi-directional-firewall-access-to-udp-port-123 <http://superuser.com/questions/762579/why-does-ntp-require-bi-directional-firewall-access-to-udp-port-123> [root@smtp ~]# systemctl status chronyd.service ● chronyd.service - NTP client/

Re: NTP synchronized: no

On 09/09/2015 10:37 AM, Patrick Dupre wrote: Still the same (always as root) journalctl -u chrony -b -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 19:34:53 CEST. -- after systemctl restart chronyd systemctl list-unit-files | grep chrony chrony-wait.service

Re: NTP synchronized: no

Still the same (always as root) journalctl -u chrony -b -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 19:34:53 CEST. -- after systemctl restart chronyd systemctl list-unit-files | grep chrony chrony-wait.service disabled chronyd.service

Re: NTP synchronized: no

On 09/09/2015 10:04 AM, Patrick Dupre wrote: On 09/09/2015 08:17 AM, Patrick Dupre wrote: Hello, According to the domain administrator, the port is open. Could it be an issue with the firewall? iptables -L |grep udp ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ct

Re: NTP synchronized: no

> On 09/09/2015 08:17 AM, Patrick Dupre wrote: > > Hello, > > > > According to the domain administrator, the port is open. > > Could it be an issue with the firewall? > > > > iptables -L |grep udp > > ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns > > ctstate NEW > > AC

Re: NTP synchronized: no

On 09/09/2015 08:17 AM, Patrick Dupre wrote: Hello, According to the domain administrator, the port is open. Could it be an issue with the firewall? iptables -L |grep udp ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ctstate NEW ACCEPT udp -- anywhere

Re: NTP synchronized: no

189A, avenue Maurice Schumann | | 59140 Dunkerque, France > > === > > > > > >> Sent: Tuesday, September 08, 2015 at 8:27 PM > >> From: "Rick Stevens" > >>

Re: NTP synchronized: no

ot;Rick Stevens" To: "Community support for Fedora users" Subject: Re: NTP synchronized: no On 09/08/2015 10:52 AM, Patrick Dupre wrote: Hello, I am not sure to understand. The previous conclusion was that the firewall did not

Re: NTP synchronized: no

Community support for Fedora users" > Subject: Re: NTP synchronized: no > > On 09/08/2015 10:52 AM, Patrick Dupre wrote: > > Hello, > > > > I am not sure to understand. > > The previous conclusion was that the firewall did not let me go through. > > Now,

Re: NTP synchronized: no

block UDP port 123 on their firewalls so your best bet is to ask the admins which NTP servers are available to you. On my corporate firewall, I block NTP for most of my users, but I have NTP services running on my DNS cache servers. That's what the people behind my firewall get access to

Re: NTP synchronized: no

On 09/08/2015 10:42 AM, John Pilkington wrote: On 08/09/15 18:02, Rick Stevens wrote: On 09/08/2015 03:27 AM, John Pilkington wrote: On 08/09/15 10:52, Ed Greshko wrote: On 09/08/15 17:29, Patrick Dupre wrote: I cannot synchronize the date: My undestanding is that it should be set by: timedat

Re: NTP synchronized: no

ue, France === > Sent: Tuesday, September 08, 2015 at 7:42 PM > From: "John Pilkington" > To: users@lists.fedoraproject.org > Subject: Re: NTP synchronized: no > > On 08/09/15 18:02, Rick Stevens wrote: > > On 09/08/2015 03:27 AM, John Pilkington wrote: > >> O

Re: NTP synchronized: no

On 08/09/15 18:02, Rick Stevens wrote: On 09/08/2015 03:27 AM, John Pilkington wrote: On 08/09/15 10:52, Ed Greshko wrote: On 09/08/15 17:29, Patrick Dupre wrote: I cannot synchronize the date: My undestanding is that it should be set by: timedatectl set-ntp yes Here, the results of some comm

Re: NTP synchronized: no

On 09/08/2015 03:27 AM, John Pilkington wrote: On 08/09/15 10:52, Ed Greshko wrote: On 09/08/15 17:29, Patrick Dupre wrote: I cannot synchronize the date: My undestanding is that it should be set by: timedatectl set-ntp yes Here, the results of some commands: netstat -a |grep ntp udp0

Re: NTP synchronized: no

On 09/08/15 19:11, Patrick Dupre wrote: > Should I ask to have the port ntp open ? > Is it 123? Yes, UDP port 123 -- It seems most people that say they are "done talking about it" never really are until given the last word. -- users mailing list users@lists.fedoraproject.org To unsubscribe or

Re: NTP synchronized: no

M > From: "Ed Greshko" > To: "Community support for Fedora users" > Subject: Re: NTP synchronized: no > > On 09/08/15 18:42, Patrick Dupre wrote: > > traceroute to 123.204.45.116 (123.204.45.116), 30 hops max, 60 byte packets > > 1 cisco-dk.univ-lit

Re: NTP synchronized: no

On 09/08/15 18:42, Patrick Dupre wrote: > traceroute to 123.204.45.116 (123.204.45.116), 30 hops max, 60 byte packets > 1 cisco-dk.univ-littoral.fr (193.49.194.1) 2.168 ms 2.332 ms 2.598 ms > 2 192.168.168.203 (192.168.168.203) 0.441 ms 0.458 ms 0.506 ms > 3 * * * > 4 * * * > 5 * *

Re: NTP synchronized: no

traceroute to 123.204.45.116 (123.204.45.116), 30 hops max, 60 byte packets 1 cisco-dk.univ-littoral.fr (193.49.194.1) 2.168 ms 2.332 ms 2.598 ms 2 192.168.168.203 (192.168.168.203) 0.441 ms 0.458 ms 0.506 ms 3 * * * 4 * * * 5 * * * 6 * * * 7 * * * 27 * * * 28 * * * 29 * * *

Re: NTP synchronized: no

On 09/08/15 18:26, Patrick Dupre wrote: > This is at the Unversity. Maybe it is a firewall issue. > Is there a test that I can do to double check? What do you get with this. traceroute -p 123 -U 123.204.45.116 -- It seems most people that say they are "done talking about it" never really ar

Re: NTP synchronized: no

system at home or a workplace? Could be a firewall issue if it is in a workplace. timedatectl Local time: Tue 2015-09-08 09:12:19 CEST Universal time: Tue 2015-09-08 07:12:19 UTC RTC time: Tue 2015-09-08 07:12:19 Time zone: Europe/Paris (CEST, +0200) NTP enabled

Re: NTP synchronized: no

e 11 7 172m -0.256 0.254 +1239us 475us > atelieralica.idv.tw 7 5 103m +2.341 1.821 +9709us 1310us > > So, it seems your system is having problems to communicate with the remote > servers. > > Is this system at home or a workplace? Could b

Re: NTP synchronized: no

103m +2.341 1.821 +9709us 1310us So, it seems your system is having problems to communicate with the remote servers. Is this system at home or a workplace? Could be a firewall issue if it is in a workplace. > > > > timedatectl > Local time: Tue 2015-09-08 09:12

Re: NTP synchronized: no

0 +0.000 2000.000 +0ns 4000ms timedatectl Local time: Tue 2015-09-08 09:12:19 CEST Universal time: Tue 2015-09-08 07:12:19 UTC RTC time: Tue 2015-09-08 07:12:19 Time zone: Europe/Paris (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in local TZ

Re: NTP synchronized: no

On 09/08/15 01:48, Patrick Dupre wrote: > Now, I have: > > Local time: Mon 2015-09-07 17:46:49 CEST > Universal time: Mon 2015-09-07 15:46:49 UTC > RTC time: Mon 2015-09-07 17:46:49 >Time zone: Europe/Paris (CEST, +0200) > NTP enabled: yes > NTP synchronized: yes > RTC

Re: NTP synchronized: no

Sun 2015-10-25 02:59:59 CEST Sun 2015-10-25 02:00:00 CET But the time to 2 hours off. It should be 19:46:49 Why? Subject: NTP synchronized: no Hello, In fedora 22, how do I synchronize the ntp: timedatectl Local time: Mon 2015-09-07 17:04:58 CEST Universal

Re: NTP synchronized: no

3:00:00 CEST > > Next DST change: DST ends (the clock jumps one hour backwards) at > >Sun 2015-10-25 02:59:59 CEST > >Sun 2015-10-25 02:00:00 CET > > > > > > > > But the time to 2 hours off. > > It should be 19:46:49 > &g

Re: NTP synchronized: no

2015-10-25 02:00:00 CET But the time to 2 hours off. It should be 19:46:49 Why? Subject: NTP synchronized: no Hello, In fedora 22, how do I synchronize the ntp: timedatectl Local time: Mon 2015-09-07 17:04:58 CEST Universal time: Mon 2015-09-07 15:04:58 UTC RTC time: Mon

Re: NTP synchronized: no

. It should be 19:46:49 Why? > Subject: NTP synchronized: no > > Hello, > > In fedora 22, how do I synchronize the ntp: > timedatectl > Local time: Mon 2015-09-07 17:04:58 CEST > Universal time: Mon 2015-09-07 15:04:58 UTC > RTC time: Mon 2015-09-07

NTP synchronized: no

Hello, In fedora 22, how do I synchronize the ntp: timedatectl Local time: Mon 2015-09-07 17:04:58 CEST Universal time: Mon 2015-09-07 15:04:58 UTC RTC time: Mon 2015-09-07 17:04:58 Time zone: Europe/Paris (CEST, +0200) NTP enabled: yes NTP synchronized: no RTC in