Webgui keeps dying



  • I am running pfsense inside of hyper-v.  The issue i am seeing is the webgui keeps dying.  the only way to get it working is to restart the vm.  I have tried restarting the webconfigurator via shell menu with no joy.  The host is server 2012 r2 and i have dedicated 4 gigs of ram to the vm.  memory usage is showing 50%.  I do have ntopng running along with suricata.  Any ideas?



  • Now that i have restarted the VM.  here are my system stats:

    2.3.4-RELEASE-p1 (amd64)
    built on Fri Jul 14 14:52:43 CDT 2017
    FreeBSD 10.3-RELEASE-p19

    2.3.4-RELEASE-p1 (amd64)
    built on Fri Jul 14 14:52:43 CDT 2017
    FreeBSD 10.3-RELEASE-p19

    4 gigs of ram.



  • @hescominsoon:

    ….

    2.3.4-RELEASE-p1 (amd64)
    built on Fri Jul 14 14:52:43 CDT 2017
    FreeBSD 10.3-RELEASE-p19

    4 gigs of ram.

    Everybody has this version  ;)
    But only a few have actually 4 Gbytes memory.
    I have this

    10% of 2003 MiB

    and only 10 % is used ….

    With 50 % memory usage your telling us that you're not telling everything. Sorry, we can't come over checking your setup - start detailing it.



  • what more do you want?  There is zero swap being used…cpu usage is below 25% on average.  The system runs fine when the web gui dies.  There's no spike in usage or anything else.  If the swap file was being touched I would double the ram...but shutdown takes forever and 5 years with 8 gigs due to it needing to flush flush all of that ram..so I dropped it to 4 gigs. Disk activity is normal(aka it is not getting pegged either).

    here's the host mahcine setup:
    Dell R610: 1U, 2 X L5640 2.27 GHZ HC + HT, 48 GB DDR3 ECC, 4 x 1 GB Interfaces, 2 x 10GE Fiber Interfaces, DRAC(Dedicated interface), 6 x 2.5" HotSwap trays, H200 Controller, 2 x 250 GB SSD RAID 1(Boot). 2 x 1 TB HDD RAID 1 7.2k RPM(VM Array), 2 x 2 TB HDD 7.2k RPM (DATA Array) ReFS Formatted)

    Name firewall.etc.local
    Version 2.3.4-RELEASE-p1 (amd64)
    built on Fri Jul 14 14:52:43 CDT 2017
    FreeBSD 10.3-RELEASE-p19

    The system is on the latest version.
    CPU Type Intel(R) Xeon(R) CPU L5640 @ 2.27GHz
    4 CPUs: 1 package(s) x 4 core(s)
    Hardware crypto AES-CBC,AES-XTS,AES-GCM,AES-ICM
    Current date/time
    Sun Sep 3 16:06:22 EDT 2017
    State table size
    0% (354/406000) Show states
    MBUF Usage
    1% (1780/252994)
    Load average
    0.43, 0.44, 0.40
    CPU usage
    5%
    Memory usage
    24% of 4061 MiB
    SWAP usage
    0% of 16383 MiB
    Disk usage ( / )
    3% of 108GiB - ufs
    Disk usage ( /var/run )
    4% of 3.4MiB - ufs in RAM

    There's the full skinny on the vm and the host.



  • here's even more detail:

    https://community.spiceworks.com/people/etcmaryland/projects/my-business-networking-upgrade

    ![pfsense detail.jpg](/public/imported_attachments/1/pfsense detail.jpg)
    ![pfsense detail.jpg_thumb](/public/imported_attachments/1/pfsense detail.jpg_thumb)


  • Netgate

    Next time try console option 16 then option 11 to see if that works before rebooting.



  • I had tried both of those..no dice…:)


  • Netgate

    Then you are seeing something unique to what anyone else is seeing.

    Perhaps something happening outside the firewall?

    You could do something like curl –insecure https://lan.ip.add.ress/ from the shell prompt and see if the web server is actually responding locally.

    If so you might need to get creative with tcpdump while attempting connections and see if the traffic is even arriving.



  • @Derelict:

    Then you are seeing something unique to what anyone else is seeing.

    Perhaps something happening outside the firewall?

    You could do something like curl –insecure https://lan.ip.add.ress/ from the shell prompt and see if the web server is actually responding locally.

    If so you might need to get creative with tcpdump while attempting connections and see if the traffic is even arriving.

    The firewall itself continues to function fine it is the webgui that dies.  when/if it does it again i
    ll try those commands.



  • Run also this

    ps ax | grep 'nginx'
    

    ones, when it works,
    and when it stops responding.



  • MY problem( just ahead of yours in list) shows nothing when 'ps ax|
    grep nginx' !  Et tu?