Comment 0 for bug 1722090
Revision history for this message
| Andres Rodriguez (andreserl) wrote [2.3, HWTv2] Logs do not provide an idea of why a test failed | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
NTP test failed, and viewing the log it gives me NO idea whatsoever on what failed.
remote refid st t when poll reach delay offset jitter
=======
*216.218.254.202 .CDMA. 1 u 163 256 377 78.136 -0.100 2.249
+204.2.134.163 199.233.236.226 3 u 181 256 377 88.554 3.771 1.956
+69.164.198.192 199.102.46.77 2 u 67 256 377 41.023 -2.132 0.954
-195.21.137.209 195.66.241.3 2 u 681 256 304 38.065 -3.373 1.174
7 Oct 19:55:18 ntpd[4842]: ntpd 4.2.8p4@1.3265-o Thu Sep 7 20:43:09 UTC 2017 (1): Starting
7 Oct 19:55:18 ntpd[4842]: Command line: ntpd -gq
7 Oct 19:55:18 ntpd[4842]: proto: precision = 0.049 usec (-24)
7 Oct 19:55:18 ntpd[4842]: Listen and drop on 0 v6wildcard [::]:123
7 Oct 19:55:18 ntpd[4842]: Listen and drop on 1 v4wildcard 0.0.0.0:123
7 Oct 19:55:18 ntpd[4842]: Listen normally on 2 lo 127.0.0.1:123
7 Oct 19:55:18 ntpd[4842]: Listen normally on 3 enp0s25 10.90.90.71:123
7 Oct 19:55:18 ntpd[4842]: Listen normally on 4 lo [::1]:123
7 Oct 19:55:18 ntpd[4842]: Listen normally on 5 enp0s25 [fe80::
7 Oct 19:55:18 ntpd[4842]: Listening on routing socket on fd #22 for interface updates
7 Oct 19:55:19 ntpd[4842]: Soliciting pool server 38.126.113.10
7 Oct 19:55:20 ntpd[4842]: Soliciting pool server 69.89.207.99
7 Oct 19:55:21 ntpd[4842]: Soliciting pool server 162.248.241.94
7 Oct 19:55:22 ntpd[4842]: Soliciting pool server 129.6.15.30
7 Oct 19:55:28 ntpd[4842]: ntpd exiting on signal 15 (Terminated)
7 Oct 19:55:28 ntpd[4842]: 38.126.113.10 local addr 10.90.90.71 -> <null>
7 Oct 19:55:28 ntpd[4842]: 69.89.207.99 local addr 10.90.90.71 -> <null>
7 Oct 19:55:28 ntpd[4842]: 162.248.241.94 local addr 10.90.90.71 -> <null>
7 Oct 19:55:28 ntpd[4842]: 129.6.15.30 local addr 10.90.90.71 -> <null>