Frequent crash and reboots (VMware 6.0.2 U2)



  • Hi all,

    I'm at the end of my rope here… my pfSense (2.3.2) runs like a dream for days, then all of a sudden it starts getting the BSOD and rebooting itself. Last time it actually hung without rebooting.

    Could a dev please look at the report generated to see what I can do to fix?

    Another crash report: http://pastebin.com/LUh0K6XA



  • Anyone in the pfSense team can please look at this?

    I can go days without a crash, and then, boom, 3 in 4 hours.

    @Jimp? Someone? Please?



  • the crashreport is not complete. either attach it to the post or put it on something like pastebin



  • @heper:

    the crashreport is not complete. either attach it to the post or put it on something like pastebin

    I apologize for the oversight… here it is in all its crashy glory: http://pastebin.com/aiJK8pti

    Any help greatly appreciated!



  • Hi guys,

    Could someone please look into these? ALL my pfSense installs in VMware are exhibiting the same crashes. The boss is screaming at me to get it fixed.

    Thanks a bunch!



  • You DID pay for pfsense support, given that you have it in production….right?

    I am going to predict that it is not a pfsense issue given that:

    • This was working.
    • Many, many people have pfsense running in ESXi 5 and 6 without any issues (incl. myself).

    It is possible that an edge case is causing this, but you as the admin, would know if there were any changes
    on these pfsense boxes, right?  (restore an older config and see if it still crashes).

    Either way, it bother me to see seemingly competent people like you, asking for urgent help in a forum.

    I don't pay for support, but then again, I take pride in being able to solve, test, rule-out, troubleshoot and figure things out on my own. It is not that hard. Change 1 variable at the time and find the problem...

    @Pistolero:

    Hi guys,

    Could someone please look into these? ALL my pfSense installs in VMware are exhibiting the same crashes. The boss is screaming at me to get it fixed.

    Thanks a bunch!



  • Thanks for the advice. I hadn't thought about troubleshooting the issue myself. I will follow your example.

    In the meantime, could someone please look at the crash dumps? Someone who actually has helpful advice?

    @pppfsense:

    You DID pay for pfsense support, given that you have it in production….right?

    I am going to predict that it is not a pfsense issue given that:

    • This was working.
    • Many, many people have pfsense running in ESXi 5 and 6 without any issues (incl. myself).

    It is possible that an edge case is causing this, but you as the admin, would know if there were any changes
    on these pfsense boxes, right?  (restore an older config and see if it still crashes).

    Either way, it bother me to see seemingly competent people like you, asking for urgent help in a forum.

    I don't pay for support, but then again, I take pride in being able to solve, test, rule-out, troubleshoot and figure things out on my own. It is not that hard. Change 1 variable at the time and find the problem...

    @Pistolero:

    Hi guys,

    Could someone please look into these? ALL my pfSense installs in VMware are exhibiting the same crashes. The boss is screaming at me to get it fixed.

    Thanks a bunch!



  • This page has been removed!
    This page is no longer available. It has either expired, been removed by its creator, or removed by one of the Pastebin staff.


  • LAYER 8 Global Moderator

    Maybe your issues is related to you using some version from the future?  Or gotten from some unknown location - there is no 6.0.2 u2, there is a 6.0 u2 is that what your on?  Have you upgraded to 6.0 patch 3 which is the current build that was released back in early Aug.  And is 2nd patch since update 2.



  • When without those latest patches, you know just as well as I do that it runs perfectly and this is not an issue specifically with VMware.  I've been running pfSense on ESXi since 4.1 and you've likely been running it for even longer.  If this guy has constant problems when I would guess he has some type of hardware issue.

    Not many people here know how to effectively read a FreeBSD crash dump, myself included, so if this is really important then he should seriously consider purchasing support.  It's not expensive.


  • LAYER 8 Global Moderator

    Oh not saying pfsense should not run on 6.0 u2, but I did have some oddness with a vm hanging up.  I could not shut it down, could not reboot esxi, etc.  I didn't have any issues with pfsense per se, even when the other vm was hung and esxi could not be shutdown pfsense vm was still routing traffic and firewalling, running current build not having any issues with any vm at all.

    I was more making fun at the fact that someone that is so keen on getting help can not even accurately post what they are running.  There is no such thing at 6.0.2 u2 ;)

    And I agree with you completely, if your using pfsense in "production" you should have a support contract with them.  They are really ramping up their support to be 24/7 and bringing on staff even.. I am quite sure with the correct information given them they could figure out what the OP problem is.  But such level of debug sure shouldn't be expected to get for free in the forums, and for sure not going to happen on your time schedule.  Someone might love debugging crash reports and find this thread and point out an issue - but wouldn't hold my breath ;) heheeh

    I have been running pfsense as vm for many many years and have had no issues of any real concern at all, atleast none that I could couldn't figure out or work through on my own.


  • Rebel Alliance Developer Netgate

    The pastebin pages were removed so I can't see what it said. I run over a dozen VMs in ESX and none ever crash, and I know customers using it in production with no issues as well.

    It could be a hardware issue, a driver issue or OS issue triggered by some combination of options in use. Hard to say, but it isn't a widespread issue.


Log in to reply