Check_reload_status: reloading filter
-
I seem to have some troubles with my pfsense box.. (2.0-ALPHA-ALPHA, built on Mon Apr 13 15:35:05 EDT 2009, FreeBSD 7.1-RELEASE-p4)
The System log is being spammed with messages like this:Apr 15 15:20:30 check_reload_status: reloading filter Apr 15 15:20:26 apinger: alarm canceled: wan(88.66.xx.xx) *** delay *** Apr 15 15:20:15 apinger: ALARM: wan(88.66.xx.xx) *** delay *** Apr 15 15:20:15 check_reload_status: reloading filter Apr 15 15:20:04 apinger: alarm canceled: wan(88.66.xx.xx) *** delay *** Apr 15 15:20:00 check_reload_status: reloading filter Apr 15 15:19:49 apinger: ALARM: wan(88.66.xx.xx) *** delay *** Apr 15 15:19:10 check_reload_status: reloading filter Apr 15 15:18:56 apinger: alarm canceled: wan(88.66.xx.xx) *** delay *** Apr 15 15:18:50 check_reload_status: reloading filter Apr 15 15:18:37 apinger: ALARM: wan(88.66.xx.xx) *** delay *** Apr 15 15:18:30 check_reload_status: reloading filter Apr 15 15:18:18 apinger: alarm canceled: wan(88.66.xx.xx) *** delay *** Apr 15 15:18:10 check_reload_status: reloading filter Apr 15 15:17:55 apinger: ALARM: wan(88.66.xx.xx) *** delay ***It also seems to increase my CPU load alot, even when there's nearly no activity on my WAN.
I have to mention though that I've played around with a bunch of not-officially supported packages some time ago, which could probably be the source of the problem!
That's what is installed currently, according to pkg_info:bsdinstaller-2.0.2009.0317 BSD Installer mega-package gettext-0.17_1 GNU gettext package grub-0.97_3 GRand Unified Bootloader libiconv-1.11_1 A character set conversion library pcre-7.8 Perl Compatible Regular Expressions library perl-5.8.9_2 Practical Extraction and Report Language pkg-config-0.23_1 A utility to retrieve information about installed libraries znc-0.066 An advanced IRC bouncerI can't really remember if the problems occured after an update or fooling around with the packages :(
So.. is the reloading filter a current bug, or did I mess up something inside my box?
I just wanted to make sure that it's probably the latter before I start to DELETE FUCKING EVERYTHING and set up a clean install :pOh, and sorry if I missed any crucial information, I'm by far no expert when it comes to any OS other than MS Windows :'(
-
The apinger warnings were caused by a typo in the code which accidentally set the latency low watermark to 10 ms, which should have been 10% packet loss.
That's been fixed.