Setup pfSync causes an instant crash pfsense 2.7
-
Has anyone had any issues getting ha setup, I have tried to follow the steps detailed in the documentation and the second it click save to apply pfsync pfsense crashes.
This the latest version of pfsense running in a KVM based virtual machine.
-
@cwager990 2.7.2 is the latest.
https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshootingDefine "crash"? What do the logs show at that time?
-
@SteveITS I'll have to clone it and do it again to get the log.
By crash I mean exactly that a hard crash box crashed reboots and then shows a notice saying a crash occurred.
-
@SteveITSG Here is a text file with the crash info in it any ideas would be great. crashinfo.txt
-
@cwager990 Does that happen consistently?
The backtrace shows we're panicing trying to export a state and we dereference a NULL pointer. Very early on in the export function in fact.
That might happen if the state has been unlinked and its keys have been removed. There may be race conditions that allow that to happen, but that'd be very very rare occurrences, not consistent panics.So: does this happen every time you turn on pfsync, and is the backtrace and register dump always the same?
-
@kprovost Hi, yes this happens every single time without fail it blows up the same way every single time. Both nodes are KVM/QEMU Virtual machines hosts are identical in every respect I have even tried with both Virtual Machines on the same host. Same result every single time.
-
@cwager990 And presumably the backtrace is identical every time?
Can you post or otherwise share the state table?
Thepfctl -ss -vvv
output is what I'm after.While you're gather information include /tmp/rules.debug too.
There has to be something very odd with at least one of your states, but I don't have any idea how that could be happening, especially so consistently.
-
@kprovost Hi, I have attached both the requested files. rules.debug.txt states.txt
Thanks
-
@kprovost I have now got this working, I have no idea what I did differently but on two newly built virtual machines I have it working.