Your message dated Sun, 01 Jul 2012 21:07:20 -0500
with message-id <[email protected]>
and subject line being rocked back and forth a hundred minutes per call
has caused the Debian Bug report #226747,
regarding chrony: being rocked back and forth a hundred minutes per call
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
226747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226747
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 1.20-1
Severity: normal
Recent version of chrony seem to blast my computer tons of seconds per
call, then back, the next call!:
$ zgrep -h +0[^0]$ `ls -r /var/log/chrony/tracking.log*`
2003-11-10 22:56:59 210.59.157.40 3 73.758 2.849 -4.358e+01
2003-11-10 22:57:48 210.59.157.40 3 73.758 2.849 4.503e+01
2003-11-12 03:20:45 210.59.157.41 3 73.952 6.227 -1.165e+01
2003-11-12 03:22:21 210.59.157.41 3 73.952 6.227 1.419e+01
2003-11-13 04:23:02 210.59.157.40 3 75.161 20.312 2.867e+01
2003-11-13 04:29:32 210.59.157.41 3 75.161 20.312 -2.077e+01
2003-11-23 02:29:19 210.59.157.41 3 73.835 1.347 -3.212e+01
2003-11-25 22:36:59 210.59.157.40 3 74.368 8.334 -2.551e+01
2003-11-25 22:37:26 210.59.157.40 3 74.368 8.334 2.234e+01
2003-12-18 03:19:48 210.59.157.41 3 82.309 25.916 -1.261e+01
2003-12-19 22:54:56 210.59.157.40 3 82.309 25.916 1.423e+01
2003-12-20 04:07:40 210.59.157.40 3 82.309 25.916 -3.770e+02
2003-12-21 18:37:37 210.59.157.40 3 82.309 25.916 1.116e+02
2003-12-26 23:14:12 210.59.157.40 3 88.828 20.341 -1.754e+02
2003-12-26 23:18:20 210.59.157.40 3 88.828 20.341 1.817e+02
2003-12-29 23:50:25 210.59.157.40 3 116.783 107.828 -7.396e+01
2004-01-01 18:54:04 210.59.157.40 3 116.783 107.828 7.898e+01
2004-01-04 23:49:30 210.59.157.40 4 116.783 107.828 -6.812e+01
2004-01-07 15:54:46 210.59.157.40 3 116.783 107.828 7.474e+01
As you see, chrony gets some wacky idea, which is then corrected next call.
Also, I notice nine whole minutes of waste[?]:
2004-01-07 15:47:57 0.0.0.0 0 116.783 107.828 0.000e+00
2004-01-07 15:47:59 0.0.0.0 0 116.783 107.828 0.000e+00
2004-01-07 15:48:01 0.0.0.0 0 116.783 107.828 0.000e+00...
where it just connects to 0.0.0.0, during the first nine minutes of my call.
Also note that my usual modem calls are about nine minutes long, as
another coin drops at 10 minutes here... maybe chrony didn't expect
short calls so that is what sometimes messes it up.
offline, chrony does great. Problems start when maybe it gets wrong
ideas during intensive downloads on my 56K line, connecting for nine
minutes, two times, every three days, which is my recent lifestyle
this week...
Apparently me staying on for longer during the last call helped.
Maybe chrony should detect when time is getting distorted by big
.PDF's hogging the line?
I cannot find any troubleshooting FAQ.
--- End Message ---
--- Begin Message ---
No response from submitter after four years, unreproducible.
Probably due to a very low quality server.
--
John Hasler
--- End Message ---
