PFsense Crashed! Please help me identify the culprit
This is the crash log. Im using 2.1.5-RELEASE (i386) by the way. I installed a ddr1 512mb pc2700 ram together with the existing ddr1 512mb pc3200. I dunno what happen, it was working fine this morning but tonight it already crashed twice.
anyone please help me.. im a total noob on pfsense.
marvosa last edited by
Any time I've ever had an issue with PFsense it's been hardware related. For me it was a bad hard drive, but considering you're running 10 year old hardware (P4-2.66GHz) it could be any one of multiple things. I would test your HDD and Ram for starters.
I've never seen this log before, but there are some failures noted that may or may not be related to your crash:
Trying to mount root from ufs:/dev/ad0s1a
WARNING: / was not properly dismounted
<118>Configuring crash dumps…
<118>Using /dev/ad0s1b for dump device.
ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable,
add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
Consider tuning vm.kmem_size and vm.kmem_size_max
ZFS filesystem version 5
ZFS storage pool version 28
<118>/dev/ad0s1a R/W mount of / denied. Filesystem is not clean - run fsck.
<118>Operation not permitted
panic: vm_fault: fault on nofault entry, addr: c2403000
cpuid = 0
KDB: enter: panic
0xc5fa9648: tag ufs, type VREG
usecount 1, writecount 1, refcount 701 mountedhere 0
v_object 0xc5f7c330 ref 0 pages 2794
lock type ufs: EXCL by thread 0xc5237000 (pid 65682)
ino 400901, on dev ad0s1a
panic.txt0600006012447265100 7135 ustarrootwheelvm_fault: fault on nofault entry, addr: c2403000version.txt06000021612447265100 7613 ustarrootwheelFreeBSD 8.3-RELEASE-p16 #0: Mon Aug 25 08:25:41 EDT 2014
I think you may have a point, ive also experienced slow bandwidth output from rl1 interface. Could that be related to old hardware? Im thinking about changing my server(hardware), but i just want to make sure that its hardware's fault.
Update: Its been running for 4 hours and not yet crashed. I'm not sure if its hardware issue.
Cyberloard last edited by
I think you may have the same problem I have. I think it's because apinger can't resolve an address. This fills up the log and consequently this fills up your memory and causes a crash,but I'm not one hundred percent sure on that.
Im also thinking that its because apinger has failed, for some reason my cable modem keeps on dropping.