PfSense 2.0.1 crashes



  • My pfSense 2.0.1 installation on a TEAK 3035-155 crashes almost once a day. This happened always in the night between 00:00 and 03:00 (Central Europe daylight saving time).

    When I open the pfSense website I see that a crash report is ready to be sent to the developers. Clicking the send button shows this message:

    Diagnostics: Crash reporter

    Processing…
    Uploading...
    Not Found

    The requested URL /crash_reporter.php was not found on this server.

    Continue and delete crash report files from local disk.

    Afterwards the crash report is deleted from the disk.

    This time I found the crash report files in /var/crash and could save them before trying to send the report (see attachments). Do you have any idea why the machine is crashing and how I can solve this problem?

    Thanks!
    info.0.txt
    textdump.tar.0.txt


  • Netgate Administrator

    It's not directly implicated here but you should try this as you have multiple em interfaces:
    http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#Intel_igb.284.29_and_em.284.29_Cards

    Steve



  • Thanks for the tip, Steve.

    The suggested NMB cluster size was already set but the number of queues cannot be set on my system:

    [2.0.1-RELEASE]: sysctl hw.em.num_queues
    sysctl: unknown oid 'hw.em.num_queues'
    [2.0.1-RELEASE]: sysctl kern.ipc.nmbclusters
    kern.ipc.nmbclusters: 131072
    

    The system keeps crashing apx. once a day.


  • Netgate Administrator

    Had you set it already? Does your system use a lot of MBUFs, in the dashboard the MBUF usage is displayed does it ever get close to 131072?

    Is this a new box?

    Steve



  • MBUF usage is far from the limit:

    netstat -m
    3269/706/3975 mbufs in use (current/cache/total)
    3262/588/3850/131072 mbuf clusters in use (current/cache/total/max)
    3261/323 mbuf+clusters out of packet secondary zone in use (current/cache)
    0/44/44/65536 4k (page size) jumbo clusters in use (current/cache/total/max)
    0/0/0/32768 9k jumbo clusters in use (current/cache/total/max)
    0/0/0/16384 16k jumbo clusters in use (current/cache/total/max)
    7341K/1528K/8869K bytes allocated to network (current/cache/total)
    0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters)
    0/0/0 requests for jumbo clusters denied (4k/9k/16k)
    0/8/4368 sfbufs in use (current/peak/max)
    0 requests for sfbufs denied
    0 requests for sfbufs delayed
    0 requests for I/O initiated by sendfile
    0 calls to protocol drain routines
    

    Current uptime is 2 days, 10:35. It crashed three times since the change. So MBUF size is probably not the reason.

    All crashes occurred during low traffic times (in the night time). This means apx. 1 kbit/s, no user in the office.

    Andreas



  • Did you find the solution?


Locked