2.4.1 is killing me

rscrub

Ever since I updated, it crashes almost every day and will not shutdown/startup. I keep getting this message

There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy - The line in question reads [0]: @ 2017-11-07 07:02:41

and…

PF was wedged/busy and has been reset. @ 2017-11-07 07:02:36

I can't figure out what is going on. Please help!!!

kejianshi

For me, that just means I'm on pfsense. I see those two every day and it dosn't cause me any crashes or hangs that I've noticed.

We are talking for years.

Ever since I updated, it crashes almost every day and will not shutdown/startup. I keep getting this message

If 2.4.1 is not a must be, I would roll back to 2.4.0 or an earlier version where you was not getting any problems in, and
if the version 2.4.2 is out you could try it again! So if you are not pressed to use this version perhaps better to wait
until 2.4.2 is out.

Some VLAN labeling problems were there and the VLANs on the WAN interface using PPP is also broken. as
I am informed right.

Birke

regarding that DIOCXCOMMIT-errormessage a quick google-search offered me this possible solution:
@https://detlev.bluelf.me/2015/06/14/pfsense-error-pfctl-diocxcommit/:

There were error(s) loading the rules: pfctl: DIOCXCOMMIT: Device busy – The line in question reads [ 0 ]

Here’s what worked for me:
Rather than allowing your NICs to autoselect speed, duplex and flow control, I locked these in on each interface to the highest possible setting and configured the firewall to be the master controller of these settings.

In my case that’s 1000baseT full-duplex,flowcontrol,master

C’est tout.
=)D

have you tried that already?

I get the second message on my pf too, but it never crashed. The only thing is, that the gui is unavailable for some seconds.

rscrub

@BlueKobold:

Ever since I updated, it crashes almost every day and will not shutdown/startup. I keep getting this message

If 2.4.1 is not a must be, I would roll back to 2.4.0 or an earlier version where you was not getting any problems in, and
if the version 2.4.2 is out you could try it again! So if you are not pressed to use this version perhaps better to wait
until 2.4.2 is out.

Some VLAN labeling problems were there and the VLANs on the WAN interface using PPP is also broken. as
I am informed right.

I cant figure out how to roll back?

Derelict

You reinstall the old version and restore the configuration backup you took before you upgraded.