Snort GUI slows down after a while - 2.6.0.2.1 and previous version
-
I cannot reproduce this.
Please provide a ps awwux | grep php output during this time.
-
I cannot reproduce this.
Please provide a ps awwux | grep php output during this time.
I've un-checked all new features. Had to hard-reboot FW some hours ago because i could'nt connect to the console anymore.
This took about 5-10 seconds earlier.
llast pid: 15186; load averages: 3.08, 2.78, 1.68 up 0+03:53:09 23:45:33
62 processes: 3 running, 57 sleeping, 2 stopped
CPU states: 95.7% user, 0.0% nice, 2.7% system, 1.6% interrupt, 0.0% idle
Mem: 146M Active, 12M Inact, 34M Wired, 432K Cache, 34M Buf, 51M Free
Swap: 512M Total, 512M FreePID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND
14440 root 1 128 0 49452K 23120K RUN 6:44 47.17% php
10664 root 1 128 0 46852K 20492K RUN 4:30 46.29% php
642 proxy 1 96 0 8456K 6936K select 1:13 0.05% squid
1775 root 1 4 0 1140K 1048K kqread 0:29 0.00% snort2c
1772 root 1 -58 0 84180K 83572K bpf 0:21 0.00% snortroot 14440 46.4 9.4 50172 23844 ?? R 11:33PM 6:59.80 /usr/local/bin/php
root 10664 46.0 8.2 47044 20684 ?? R 10:33PM 4:45.06 /usr/local/bin/php
root 362 0.0 1.8 36632 4512 ?? Is 7:53PM 0:00.07 /usr/local/bin/php
root 367 0.0 1.8 36632 4512 ?? Is 7:53PM 0:00.08 /usr/local/bin/php
root 14470 0.0 1.8 36632 4620 ?? I 11:33PM 0:00.00 /usr/local/bin/php
root 14471 0.0 1.8 36632 4620 ?? I 11:33PM 0:00.00 /usr/local/bin/php
root 15229 0.0 0.4 1512 992 p0 S+ 11:46PM 0:00.01 grep php -
You are running out of ram. Insert more ram?
-
Snort has some performance settings. Did you try low mem already?
-
Snort has some performance settings. Did you try low mem already?
So RAM is the culprit. Didn't understand that.
Dont' know much about ..nix i'm afraid.
Just looked at System Overview that shows about 62% Memory usage.Yes, i'm running Performance: lowmem.
Have no more RAM i'm afraid. MB only has 2 slots. Already equipped with 2x128MB and i don't have any 256MB's.
I'll disable some snort rules and maybe uninstall Squid.Thanks for your help and sorry to have taken up your time with such an stupid issue! My bad.
I promise i'll learn all about FreeBSD memory management and status after a short nights sleep, which starts right now (1:30 am) … -
maybe remove just one of the "memoryhogs". squid and snort both can take some fair amount of ram.
-
I am having the same issue with PHP using ~100% of CPU cycles while having lots of blocked IP addresses. I am running a P3 533MHz w/ 512MB of RAM. When clicking the snort link within the GUI, CPU usage goes to 100% and stays until the page is loaded.
ps awwux | grep php: root 513 0.0 0.9 36612 4588 ?? Is 8:32AM 0:00.09 /usr/local/bin/php root 518 0.0 0.9 36612 4588 ?? Is 8:32AM 0:00.18 /usr/local/bin/php root 22772 0.0 0.9 36612 4696 ?? I 1:31PM 0:00.00 /usr/local/bin/php root 22906 0.0 0.9 36612 4696 ?? I 1:32PM 0:00.00 /usr/local/bin/php root 22923 0.0 0.9 36612 4696 ?? I 1:32PM 0:00.00 /usr/local/bin/php root 22963 0.0 0.9 36612 4696 ?? I 1:32PM 0:00.00 /usr/local/bin/phplast pid: 23346; load averages: 1.19, 0.50, 0.29 up 0+05:05:53 13:37:20 35 processes: 3 running, 32 sleeping CPU states: 94.6% user, 0.4% nice, 4.3% system, 0.8% interrupt, 0.0% idle Mem: 133M Active, 10M Inact, 28M Wired, 19M Buf, 322M Free Swap: 1024M Total, 1024M Free -
If it returns a result after some time that's normal. I tries to use the available cpu power to run the commands to build the pages as fast as it can. Isn't it normal that cpu goes up when the cpu is working? ::) At least it is normal when it returns a result after some time (depending on your systempower sooner or later). It's not normal if the process keeps at 100% cpu without returning anything after some time but it doesn't sound like you have that kind of issue, right?
-
It is normal. If you dont want it to associate the blocked alert text with the ip address then disable this feature in the settings page.
-
Woops. This just happened to me! I've hopefully fixed the problem.
Sorry about this!!