[pfSense] pfSense 2.0.1 crashes (Alix 2d13)

Ernst den Broeder ernst at denbroeder.ca
Mon May 7 10:54:56 EDT 2012


On 4/24/2012 12:15 PM, Ernst den Broeder wrote:
>>> On 23 apr. 2012, at 19:28, Ernst den Broeder wrote:
>>>> Hi All. I am trying to work through a kernel crash I keep having 
>>>> with pfSense 2.0.1 on Alix 2d13 hardware (my home router). This has 
>>>> been going on for about 3-4 weeks now. The crash happens about 
>>>> every 2 days, but it varies. Some times it is up 4 days without 
>>>> crashing, other days it is up only 24 hrs. Today, it happened 3 
>>>> times so far... Some of the things I have tried: - swapped Alix 
>>>> 2d13 hardware with known stable unit (I transferred only the CF 
>>>> card over) - deleted config and rebuilt it The kernel crash (I've 
>>>> pasted today's crashes below) seems to originate from the vr0 
>>>> interface (LAN side). I am wondering if anyone here has any ideas 
>>>> that I can try or suggestions to go about finding what the cause 
>>>> might be. This pfSense installation was stable until this started 
>>>> happening.
>
> I think I have a clue here now since I setup syslog to a remote 
> machine.  I now suspect a bug in /etc/rc.filter_configure_sync
>
> Apr 23 19:58:58 router ntpd[1537]: adjusting local clock by 0.165581s
> Apr 23 20:00:00 router /usr/sbin/cron[52449]: (root) CMD 
> (/etc/rc.filter_configure_sync)
> Apr 23 20:00:00 router /usr/sbin/cron[52795]: (root) CMD 
> (/usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 virusprot)
> Apr 23 20:00:00 router /usr/sbin/cron[52839]: (root) CMD 
> (/usr/bin/nice -n20 /usr/local/sbin/expiretable -v -t 3600 sshlockout)
> Apr 23 20:00:00 router /usr/sbin/cron[52867]: (root) CMD 
> (/usr/bin/nice -n20 newsyslog)
> Apr 23 20:00:37 router pf: 00:02:15.881301 rule 1/0(match): block in 
> on pppoe0: (tos 0x0, ttl 233, id 32851, offset 0, flags [DF], proto 
> TCP (6), length 40)
> Apr 23 20:00:37 router pf:     46.137.194.104.52442 > 
> 69.196.165.91.27977: Flags [S], cksum 0x8671 (correct), seq 4412, win 
> 512, length 0
> Apr 23 20:02:25 router syslogd: restart
> Apr 23 20:02:25 router syslogd: kernel boot file is /boot/kernel/kernel
> Apr 23 20:02:25 router kernel: Copyright (c) 1992-2010 The FreeBSD 
> Project.
> Apr 23 20:02:25 router kernel: Copyright (c) 1979, 1980, 1983, 1986, 
> 1988, 1989, 1991, 1992, 1993, 1994
> Apr 23 20:02:25 router kernel: The Regents of the University of 
> California. All rights reserved.
> Apr 23 20:02:25 router kernel: FreeBSD is a registered trademark of 
> The FreeBSD Foundation.
> Apr 23 20:02:25 router kernel: FreeBSD 8.1-RELEASE-p6 #0: Mon Dec 12 
> 18:59:41 EST 2011
> Apr 23 20:02:25 router kernel: 
> root at FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 
> i386
>
> Apr 24 11:30:00 router /usr/sbin/cron[10527]: (root) CMD 
> (/etc/rc.filter_configure_sync)
> Apr 24 11:32:48 router syslogd: restart
> Apr 24 11:32:48 router syslogd: kernel boot file is /boot/kernel/kernel
> Apr 24 11:32:48 router kernel: Copyright (c) 1992-2010 The FreeBSD 
> Project.
> Apr 24 11:32:48 router kernel: Copyright (c) 1979, 1980, 1983, 1986, 
> 1988, 1989, 1991, 1992, 1993, 1994
> Apr 24 11:32:48 router kernel: The Regents of the University of 
> California. All rights reserved.
> Apr 24 11:32:48 router kernel: FreeBSD is a registered trademark of 
> The FreeBSD Foundation.
> Apr 24 11:32:48 router kernel: FreeBSD 8.1-RELEASE-p6 #0: Mon Dec 12 
> 18:59:41 EST 2011
> Apr 24 11:32:48 router kernel: 
> root at FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_wrap.8.i386 
> i386
>
For anyone that is still interested in this, the problem is in the 
Schedules feature.  I disabled it and have been running crash free for 
over 8 days now.

Does anyone here use the Schedule feature?

-Ernst


More information about the List mailing list