NTP clock sync
-
Can you try the same thing with a i386 32bit version? Clean install and restore settings.
Works. At least it have started properly following 4 reboots, which have never happened with my 64 bit VM.
This could also be a virtualization issue.
Possible but I would imagine more than me today run pfSense in VirtualBox…
-
I had a similar failure under ESXi but my mind was not focusing on the NTP issue because the AMD64 version was also breaking my interfaces under ESXi…
I would have thought of this earlier, but I wasn't tipsy earlier ;D
-
No, not without someone providing the core dumps at least.
I wasn't aware that someone wanted it.
In addition to that, I am not at all familiar with the procedure so I will need some guidance… :-\
-
Is it broken again? ???
-
32 bit VM survived 5 reboots which is good.
64 bit VM is as broken as it have always been for me. -
Cool - Then with any luck you will have a shortage of core dumps to provide.
Maybe you can boot into the 64bit version just to provide a core dump so the devs can improve product.
-
I will try if they want it and explain what I need to do.
-
http://www.freebsd.org/doc/en/books/developers-handbook/debugging.html
I'm sure someone knows a better way :P
-
After having tried this on my production hardware also I have unfortunately concluded that is isn't limited to virtualized instances of pfSense. My now live physical firewall does the same thing (ntp service crashes) when having it's ntp server peers on two different interfaces (WAN and LAN). :'(
Only using external ntp servers on the WAN interface have been stable for a few days now so that is the workaround I 'll have to settle with until the bug is resolved. Only connecting to the internal ntp server on the LAN interface is not an option for me for redundancy reasons, so I haven't tried that but my guess is that it would also work.
Maybe it isn't very common to have ntp server peers on multiple interfaces and maybe that is the reason this haven't been discovered in beta testing?