Systems Crash & Reboot on my server running 2.3.4

mrhieu

I have 2 Server IBM System x3530 M4 for production.
All of them are running on PFsense ver 2.3.4.
this week, we have received 2 unexpected reboot on these server.
I have summited a crash report from ip address: 113.161.71.186 (2017 May 22, ~ 10:00 PM GMT+7)

I've also attached the lastest crash report below
Is there anyone who could take a look at the crash report and let me know the reason for this issue.
Thanks

bug_unexpected_reboot_master.txt
bug_unexpected_reboot_slave.txt

mrhieu

please help me

jimp

The crash is in dummynet. You can't use limiters with pfsync (part of HA).

https://redmine.pfsense.org/issues/4310

You'll have to remove limiters, and things that also use limiters such as captive portal per-user bandwidth limits. Either that or disable pfsync on both nodes.

mrhieu

Hi Jimp.
I appreciate your support.

https://redmine.pfsense.org/issues/4310. I knew this bug 2 year ago from your redmine. I always follow it everyday and every pfsense version that is released. To know if it has been fixed or not
So, I'm definitely sure that I don't enable pfsync when I use limiters (part of HA).

I decided to downgrade my server to PF v2.3.3 and let them run standalone yesterday. Hopefully, everything will be fine.
I hope you can check the crash report once again. let me know whether it has other any issues or not.
We have used pfsense for 5 years. It's very stable and flexible. I always trust in your production. But I have never encountered similar problems like this when upgrading to new version.

HA_Slave.PNG_thumb

HA_Master.PNG_thumb

mrhieu

@jimp:

The crash is in dummynet. You can't use limiters with pfsync (part of HA).

https://redmine.pfsense.org/issues/4310

You'll have to remove limiters, and things that also use limiters such as captive portal per-user bandwidth limits. Either that or disable pfsync on both nodes.

Hi Jimp.

I need some help, please