Slow consumption of CPU
-
Check this out:
I'm running PFSense on a Firebox x700; its been working pretty well as of lately. It sits in a managed environment where there is battery back up and all of this great stuff, so I can get some pretty high up-times. ;D
Because of this I do notice memory leaks and things of this nature a bit more with my monitoring software using SNMP. Take a look at this CPU graph over time. It appears that the PFSense firewall eats up more and more CPU. Its not been rebooted since the last time I had upgraded. Once its configured I don't really do anything with it. No config changes, I don't even really log into the web interface.
Version: 1.2.1 - built on Thu Dec 25 15:18:24 EST 2008 Uptime: 9:26AM up 191 days, 12:36, 2 users, load averages: 0.43, 0.41, 0.41
-
I've also noticed this:
TOP Output: last pid: 29597; load averages: 1.11, 0.66, 0.50 up 193+12:36:18 09:26:18 78 processes: 2 running, 61 sleeping, 2 zombie, 13 waiting CPU states: 0.0% user, 0.4% nice, 0.0% system, 0.0% interrupt, 99.6% idle Mem: 61M Active, 27M Inact, 35M Wired, 72K Cache, 25M Buf, 119M Free Swap: PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 10 root 1 171 ki31 0K 8K RUN 4227.1 61.96% idle 29596 root 1 8 20 1380K 540K nanslp 0:00 9.96% sleep 10829 root 1 8 20 20892K 18824K wait 95.8H 8.98% shAnd also noticed the "ping" program running once as well. Not sure why ping was being executed ???
Anyone have any thoughts?
-
Just disabled the RRD Graphing back end as I don't need it with a centrally managed and monitored environment. CPU is now happy without restarting :)
Hope someone else finds this info useful or a developer can check the rrd graphing code.
-
What version are you running?
-
It's in the first post; Version: 1.2.1 - built on Thu Dec 25 15:18:24 EST 2008
-
Here's an updated graph after I turned off RRD Graphing. I'll keep an eye on it over the coming month and see what happens.
-
You know that you're running an old version of pfSense and that the problem you're describing has been fixed in more recent versions, right?
-
I thought this was the latest stable version, but I've just re-checked and noticed there is a newer version available. I'll have to spend some time and upgrade it within the next couple months. Thanks for pointing out my out-of-date version, although I'm glad to hear that its fixed in the next stable release.