Problems after clean 2.4 install on ESXi 5.1



  • A couple of issues, I'm not sure they're related. I've installed a new VM with the 2.4 release iso (amd64) and I'm experiencing random hangs. The Web UI becomes inaccessible in this case. Also, occasionally the VM fails to boot and I get the following error:

    https://imgur.com/a/lAvpb

    If it does manage to boot, it crashes at some random point and the Web UI becomes inaccessible, interestingly I still have internet access and such when the happens. The VM console appears dead with the words "VMware virtual machine" or something to that effect…

    Prior to that I've been using 2.3.4 (i386) without issues.

    ESXi: 5.1.0
    Pfsense VM:

    • 2 vCPU
    • 1GB of RAM
    • Open-VM-Tools (10.1.0)
    • 2 NICS using VMXNET3

    Another thing, Guest OS reports "Other 32-bit" when it is booted, rather than the configured "Freebsd 64-bit" when the VM is off?? Is there something up with open vm tools?

    Thoughts on what's going on here?



  • I think this is the known race condition. Please see replies here https://forum.pfsense.org/index.php?topic=137913.0 or upgrade to 2.4.1(or .2?)



  • I added the  kern.vty=sc option to the /boot/loader.conf.local as per the link.

    System update reports "Up to date." on the stable branch though, but if I toggle to the Dev branch and then save, then toggle back to the Stable branch, I get "2.4.1.r.20171022.1133" ?


  • LAYER 8 Global Moderator

    Why are you still running 5.1?

    Doesn't even support freebsd 10, and sure not 11..

    5.1 end of support of Aug of 2016…



  • @johnpoz:

    Why are you still running 5.1?

    Doesn't even support freebsd 10, and sure not 11..

    5.1 end of support of Aug of 2016…

    Not every organisation has the funds to pay for a new license every other year.



  • @joelones:

    A couple of issues, I'm not sure they're related. I've installed a new VM with the 2.4 release iso (amd64) and I'm experiencing random hangs. The Web UI becomes inaccessible in this case. Also, occasionally the VM fails to boot and I get the following error:

    https://imgur.com/a/lAvpb

    If it does manage to boot, it crashes at some random point and the Web UI becomes inaccessible, interestingly I still have internet access and such when the happens. The VM console appears dead with the words "VMware virtual machine" or something to that effect…

    Prior to that I've been using 2.3.4 (i386) without issues.

    ESXi: 5.1.0
    Pfsense VM:

    • 2 vCPU
    • 1GB of RAM
    • Open-VM-Tools (10.1.0)
    • 2 NICS using VMXNET3

    Another thing, Guest OS reports "Other 32-bit" when it is booted, rather than the configured "Freebsd 64-bit" when the VM is off?? Is there something up with open vm tools?

    Thoughts on what's going on here?

    I have here running no issues PFSense 2.4 on ESXI 5.1.0.
    I have installes VM Tools and this was a upgrade from a previous version.

    IMHO ESXI 5.1.0 is still fine to use, stable enough. Newer FreeBSD versions doesn't mean that the older ESXI won't support it…. Only VMWARE like to see you moving to a new version.
    Downside, from 5.5 you need a VCenter (resource hog) server to manage is properly, although it seems this has been resolved with 6.5 (not entirely sure).


  • LAYER 8 Global Moderator

    "Not every organisation has the funds to pay for a new license every other year. "

    Esxi is FREE!!  So you don't have to pay for anything if you don't want to..

    Who said anything about every year… 5.1 came out in 2012...  So its been 5 years..  And you don't have to pay for new license to update.. You just have to have a active support contract.. So if you paid for a license.. So you could use the fancy stuff like vcenter and vmotion, etc.

    If you don't need that fancy stuff or can live without it... Ie like a org that has no money, then could just run FREE version..

    And you never needed the vcenter -- resouce hog... Ever!  esxi has never need the vcenter server.  You could just use the client to manage it.  Or now in newer version just use the embedded web ui.  All Free for those cheaper orgs that can not even afford to pay for a support contract so they could keep their production stuff current..



  • You might hate this, but have you tried removing any and all of the USB controllers? I had to, because I was getting the same issue after installing brand new on 2.4, on my esx 6.5 box. I remember reading about a reason somewhere, while I was researching setup types for openvpn.



  • @vivithemage:

    You might hate this, but have you tried removing any and all of the USB controllers? I had to, because I was getting the same issue after installing brand new on 2.4, on my esx 6.5 box. I remember reading about a reason somewhere, while I was researching setup types for openvpn.

    What do you mean by removing the usb controllers? You mean disabling on the host or vm?



  • I might have ome further insight. I have seen this crash at 2 different systems.
    Both systems are on esxi 6.5 with a hardware version of 11.
    Those systems have 2 vcpus. Systems with one vcpu does not seem to
    have this issue.

    I was able to resolve it by using reboot and the systems came back up
    flawlessly.

    If someone need more infomration, just ask.



  • I have since upgraded ESXi to 6.5 from 5.1 and have set 1 vCPU for pfsense. I'm still on 2.4 with the kern.vty=sc option. Let's see how this goes, so far I haven't noticed the crash.



  • So I have noticed mine crashing too, and then vmware thinks its down, but its kind of up? This is with a new install too, and if I power off via esxi gui, and then unregister it and re register it, and remove the SATA host in the edit options, it seems fine…for a bit. I gave it 4 cpu, and 4gb memory.... still happened a few times before I gave up. This was all in one night :s.

    Heeeey, this is related: https://forum.pfsense.org/index.php?topic=137628.15
    TLDR: 2.4.1 fixes it.


Log in to reply