On 2015-08-24 11:33, Volker Kuhlmann wrote:
On Fri 26 Jun 2015 14:54:38 NZST +1200, Brian Caouette wrote:
Anyone else notice the clock is broke on 2.2.3? Anything time related
is seriously off.
Agreed. It's broken in 2.2.4 too.
At least the upgrade to 2.2.4 did not change the time zone
(Pacific/Auckland) for me. I can no longer tell for the upgrade to
2.2.3.
Time synchronisation does not happen. I configured 2 time servers, both
reachable, and the system time is wrong.
pfsense # ntpdate -qu 0.pfsense.pool.ntp.org time.paradise.net.nz
server 130.217.226.50, stratum 1, offset -11.124288, delay 0.05031
server 103.239.8.22, stratum 1, offset -11.124315, delay 0.03931
server 203.96.152.12, stratum 3, offset -11.120111, delay 0.04111
24 Aug 12:13:24 ntpdate[95005]: step time server 103.239.8.22 offset
-11.124315 sec
11 seconds difference does not happen if NTP is working.
uptime 23 days.
Hardware is PCEngines APU1.
Volker
No issues here (also Pacific/Auckland) with any 2.2 release.
I have about a dozen 2.2.x systems (plus some older ones that I really
must get upgraded) that are a mixture of physical and virtual, none of
which have any time problems that I am aware of. I have just logged
into all of them and checked to make sure. The physical ones are mostly
current model pfSense store hardware. All the virtuals are KVM.
This is off a 2.2.4 that is a KVM guest and the one with the largest
offset.
# ntpdate -qu 0.pfsense.pool.ntp.org time.paradise.net.nz
server 103.242.68.68, stratum 2, offset -0.003817, delay 0.05771
server 103.242.68.69, stratum 2, offset -0.003988, delay 0.05685
server 203.96.152.12, stratum 0, offset 0.000000, delay 0.00000
24 Aug 11:53:45 ntpdate[9217]: adjust time server 103.242.68.69 offset
-0.003988 sec
Regards
Mike
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
