Pfsync kernel panic after 2.1.5 to 2.2 to Upgrade - pfsync_undefer_state
-
Two CARP upgraded (each one with two server), the first yesterday, the last one today. Works without problems: low CPU, CARP without error and log spam, and the back CARP with limiter on bandwidth. I don't know why, but 2.2.2 really works. :)
-
In 2.2.2 there is still a problem i found in 2.2.1, as i said before: on limited rules, i need to unchek the flag "State Type" to "NO pfsync". If i don't, CARP Slave randomly crash.
As i said before, in my CARP configuration limited rules are only HTTP and HTTPS: the state is not really important for me. However, 2.2.2 it is much better than 2.2.1. :) -
Fixed all my issues! I made my limiter rules, set them to 10Mbps, applied the firewall and did a test :)
[omitted@omitted ~]# wget cachefly.cachefly.net/100mb.test
–2015-04-16 14:02:53-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: “100mb.test.7”100%[======================================>] 104,857,600 1.18M/s in 89s
2015-04-16 14:04:21 (1.13 MB/s) - “100mb.test.7” saved [104857600/104857600]
I tested it a few times :)
THANK YOU!!
-
Please is there any progress? I am also still having problems with this bug.
Thanks -
Have you tried a 2.2.3 snapshot, if you are able to?
There have been fixes gone in to address this though it seems not all cases have been resolved. Some here have reported success.Steve
-
I sent a couple crash logs for this yesterday. This is on version 2.2.4.
-
Interesting to find this thread. We didn't have this issue until upgrading from 2.2.6 to 2.3.1_5. It does look like it is logged during a nightly copy that triggers a limiter, ending when the traffic stops.
-
In 2.3.1 there is a checkbox "No pfSync" on the rule, but checking that doesn't avoid the error message. Nor does setting "State type" to None.
I can duplicate by simply using "rsync –dry-run" so it's not like it needs a lot of traffic.
-
I upgrade to 2.3.3 and kermel entry "pfsync_undefer_state: unable to find deferred state" in log persist. Any existing or planned solutions?
-
No direct cause has yet been found as far as I know.
Obviously we would like to resolve it as soon as possible.
https://redmine.pfsense.org/issues/4310
Steve
