pfsense 2.5.2 slowly leaking memory
-
Yes, the pcscd process is the most likely suspect. Start by disabling it:
https://redmine.pfsense.org/issues/11933#note-7Steve
-
I think explaining the graph I posted in the beginning will help.
The big mountains you see there are from the time when I didn't have pcscd fix. I would reboot pfsense and pcscd would eventually eat away my free memory. Like I mentioned in my first post, I have the full pcscd fix, so it doesn't start on boot anymore. You can see the positive effect it had on memory. I haven't rebooted pfsense for 7 days now. But it seems something else is chipping away at the memory.
@psp you most likely have a mem leak problem as well. Not sure if it's same root cause.
My services are below.
I wonder if it's haproxy or vmware guest services. Perhaps it's wpa_supplicant (i do att bypass).
-
Is it actually still growing steadily? Hard to say from that graph.
Doesn't look like it's wired memory so what's using it? Check
ps -auxwwd.Also if it never actually exhausts it that may not be a problem. Unused RAM helps nothing.
Steve
-
I would have expected a better response from Netgate: "If it never exhausts it that may not be a problem" is a frankly irresponsible way to categorize memory issues for a company that sells hardware that is supposed to run on devices with limited cpu and memory 24/7. Perhaps this kind of attitude allowed to slip a terrible memory leak like pcscd into production.
Also what is the expectation here? Am I supposed to wait until all my memory is exhausted so my router goes down and suffer the consequences? I would rather be proactive than to be reactive.
Sorry if this sounds too harsh, but please take this as constructive criticism as I really am not trying to troll you or Netgate.
-
@netnerdy
I'm just a user of Netgate products but since the dawn of embedded devices there have been arguments around unused RAM.
One school is RAM should be 100% used the other is basically "you should always have 20% free RAM just in case".If you have unused RAM you are not near capacity.
Is this device using ZFS or standard UFS? That makes a difference.One also needs to understand the different types of memory: wired is basically kernel owned can't really be freed quickly. Cache and Free are self explanatory, Inactive is typically "was used but isn't now and should be freed next".
The position "if it never exhausts it may not be a problem" is technically accurate. Think garbage collection or lazy releasing of memory; so "it's allocated right now but in secs it's freed".
-
-
@netnerdy said in pfsense 2.5.2 slowly leaking memory:
Also what is the expectation here? Am I supposed to wait until all my memory is exhausted so my router goes down and suffer the consequences? I would rather be proactive than to be reactive.
I'm asking if it's actually a leak or just something using memory because your graph in the first screenshot looks to be leveling off at ~30% which generally wouldn't worry me.
The actual used memory value will vary wildly with how much RAM you have installed and what packages you're running. 30% of 64GB with no packages would be unexpected.
If it is a linear usage rise that characterises a memory leak then that's obviously a problem.
In which case check what is using the memory.Steve
-
Sorry if misunderstood, thx for the clarification. Unfortunately, I had to reboot my router for another reason so I'll need to wait a week to answer your question.
I started paying attention to mem usage just because of the pcscd leak. When I saw the second drop I was worried. I would be totally content with the explanation of "this kind of mem usage trend is by design", which seems to be case. I'll revive this if I see anything fishy. thx!
-
Mmm, hard to say without more data. If is is still leaking somewhere it's small. It could also be something that simply doesn't free memory unless it has to and since you still have >30% free it doesn't.
Keep monitoring it. Check the process list.Steve
-
There is definitely a memory leak in 2.5.2. Have to reboot about once a week, otherwise system just crash, because it runs out of memory (have 8GB) and swap.
-
@netnerdy said in pfsense 2.5.2 slowly leaking memory:
when you do a monthly view with 1 hour resolution?
Here is my sg4860 running 21.05.1, been up 46 days. Graph 1 month, 1 hour resolution
-
This post is deleted! -
Turns out the biggest memory hog was pfblocker unbound mode. When I switched to python mode I see significant memory savings.
-
Huge difference in systems all running the same config.
-
@murzik I agree, 2.5.2 is acting weird.
On a system with 4GB of ram and 2GB of swap, after 70 days, I notice unusual behavior.
Ram and swap usage is at 60%, however, I have never ever seen swap usage before, even after months of uptime.
My setup is really basic, no ressource hungry addons of any kind.
-
@cool_corona you say "same config"; is it same hardware, same set of packages, same functionality in your network?
Just curious because your graphs are "interesting" -
@mer Exactly the same.
-
Just for one day
After reboot
-
@murzik And just to be clear, you've patched for the pcscd issue and/or that service is stopped (Status/Services)? We do have one 2.5.2 and its graphs are literally flat today except at 6:30 this morning when free memory increased 1%. That's when Suricata updates.
Do you have pfBlocker's DNSBL active, or any other packages?
-
You can see exactly when I turned off pcscd a couple of days ago.. I thought I had stopped it, but it was running again..
