Looks like limiters+pfsync
https://redmine.pfsense.org/issues/4310

Seeing bug 7116 again with squid.  Cannot place squid into any kind of shaper with match or pass rules.

pfSense 2.4.0.r.20170927.1221

squid 0.4.39

@Napsterbater:

This seems to have been corrected in 2.4.1/FreeBSD 11.1, At Least after testing immediately after reboot from upgrade.

Confirmed.

Thanks for the tip about changing that line to reduce Log Spam.

yup this was the change i guess done at that time

It's running for a few hours now.
No crash since the reboot, so this looks promising.

this got fixed on the apu2 so im assuming it works on sg-1000 as well coz both run the exact same config and both gave same symptoms

If you are going to test and contribute to closing remaining bugs, I would say the more often the better.  If you just want to use it, and everything is working I wouldn't touch a thing till a bit after release. New features as not often released this close to release, and if everything is working, why bother?

Configure "User Authentication Settings" user+pass of the openvpn client config.?

Strange.. I cannot force this to error again after saving RA as disabled, even though it was already showing disabled.

Mark it solved.. 8)

The problem is still unresolved,I have to make a video record to reflect the problem  ???

https://youtu.be/UH3D8c1TtTI

Looks somewhat familiar, might be https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903

That isn't officially marked as fixed, though if you see that crash frequently you may want to move up to 2.4.1 snapshots and see if it's stable on a FreeBSD 11.1 base

i downloaded the 2.4 on the 20th (19th 23:00 release) and i had it running for about 3 hours before it too did a dump and rebooted. how ever i didnt think to grab the files. i was using mestick install and the device it was on is Qbox nT-A3350 9 if it helps…

@doktornotor:

@chrcoluk:

The problem with UFS is that its journaling is sort of bolted on, natively UFS never had journaling, so hence its unreliability.

The problem is that UFS SU+J is turned by default and nowhere documented to be a piece of buggy junk. (This is not pfSense-specific, this is generic FreeBSD issue.)

Look for a post by chrcol on the FreeBSD forums, where I got caught out by this.  UFS+J was first set as default in FreeBSD 9.0, I installed a server using those defaults and had massive database corruption issues which vanished when I reverted the server to 8.3 on the same hardware on standard UFS without journaling.  It turns out there was a nasty bug that caused my issue, that bug got fixed but like you said there is other issues.  One of the few times I was guilty of deploying a x.0 release on production servers as well.

here it is, searched so you dont have to. :)

https://forums.freebsd.org/threads/32999/#post-183469

You don't want to use the actual glabel labels because they use metadata storage that can be problematic on some installations. GPT labels would be preferred if possible over anything but not everything works with GPT partitioned disks.

Its a non issue agreed, kind of like the zfs warning.  I personally do not recall ever seeing it though.  The zfs I have seen, but not this intel one - I will keep an eye out for it next boot..

I just looked at output of dmesg, didnt see anything of the sort.

GIGO is clearly at work here.. I would also use the term BORKED to describe his setup..

http://etherealmind.com/network-dictionary-borked/

http://www.urbandictionary.com/define.php?term=borked

I would personally recommend not touching unbound, i.e. the "DNS Resolver" at the moment with a barge pole - if you have a dynamic IP address on your WAN.
On my SG-1000 it borked frequently whenever the IP address changed.
High load average and strange behaviour, it looks like it can't handle the WAN IP changing.
I've switched to using the forwarder and it's rock solid - for awhile I thought it was the ISP.
It wasn't in my case