out of swap space ??
-
@johnpoz Its done it twice with NTOPNG Disabled this is a config moved maybe 3 months ago off a machine with 8gig ram never an issue on it its recent issue maybe july seems it kills unbound pfblockerdev and ntopng if ntops not running it kills pfblocker and unbound
-
@grandrivers so what is swapping that uses up all your swap space? did you run the top command?
-
@johnpoz said in out of swap space ??:
so what is swapping that uses up all your swap space?
out of swap space ??
The question is now well defined
@grandrivers when you reply here, please add the answer.
-
@gertjan I have to catch it again was using swap but not using all the ram according to gui have to fire putty up and watch . I did delete packages and install them again
-
@grandrivers said in out of swap space ??:
I did delete packages and install them again
Packages can't be broken, as such a situation would take the system down fast.
The issue is nearly always : the (your) settings. -
@gertjan I have determined that its pfblockerng-devel and dnsbl and also unbound I have not made anychanges to those that were running on 8gig of ram just fine so have to dig into those
-
@grandrivers said in out of swap space ??:
I have not made anychanges to those
No changes to "pfblockerng-deve" means : it does nothing.
You'll be seeing this :
Actually, it does something : occupying disk space.
About unbound : See here.
-
I was NOT CLEAR this is NOT a new install this is a config I have been running for years and was working. I moved that config file via the builtin automatic backup to new hard ware MONTHS ago and it run fine till somewhere in the early part of July only changes have been too upgrade pfsense development version I have not made changes to working setting of pfblockerng-devel
-
@grandrivers said in out of swap space ??:
upgrade pfsense development version
Yeah, right - oops - I didn't saw you posted in the "2.7.0" forum.
My comment is meaningless.
Can't help you much with 2.7.0 as it is bleeding edge technology.
And ones in a while the latest build is a bummer, and forces you to take the next nightly build, with could be fine, or have some issues else where. -
Check the Status > Monitoring graphs for RAM usage over time. You may be hitting a memory leak.
Steve
