NTPD issue on latest 64bit build

Gloom

I can't decide if this is something that has gone wrong in the upgrade or a regression in the 2.0-RC1 (amd64) built on Sat Mar 26 00:18:39 EDT 2011 build but ever since the upgrade it has failed to sync it's time with the external time servers and consequently no longer acts as a time server on the network.
The older 1.2.3 firewall is still doing the job nicely syncing with the same public time servers.

The output of ntpq -p

localhost: timed out, nothing received
***Request timed out

states show
udp 91.220.52.2:18623 -> 194.35.252.7:123 SINGLE:NO_TRAFFIC
udp 91.220.52.2:59774 -> 81.168.77.149:123 SINGLE:NO_TRAFFIC

so the outgoing request is being made but it seems to be getting nothing back.

Ideas anyone?

AhnHEL

A temporary workaround until someone notices it and figures how to fix it.

http://forum.pfsense.org/index.php/topic,34668.msg181193.html#msg181193

Gloom

sadly that workaround does not produce a working NTP server on my system
31 Mar 13:12:54 ntpdate[41324]: no server suitable for synchronization found

AhnHEL

Did you give it an hour or two? Same rules apply as before.

http://doc.pfsense.org/index.php/NTP_Server_%28OpenNTPD%29

Gloom

It's never needed hours to sync in the past after an upgrade and after leaving it over night it's still no better.

Yes the hardware clock is set. It was syncing fine until I updated to the March 26th 64 bit build and when it came back up ntpd has failed.
Guess I'll just wait and see if it gets fixed in the next release.

AhnHEL

What snap were you on before you upgraded, its been broken for some time now, March 2nd or so IIRC.

Gloom

It was on a build from Feb 23 as that seemed to be a nice stable snap and I wanted to get some decent snort logs built up before I upgraded and lost the block list.

Fortunately I've a couple of functioning 1.2.3 firewalls that are also acting as time servers so no panic.

AhnHEL

Have you seen this post yet?

http://forum.pfsense.org/index.php/topic,34668.msg182131.html#msg182131