This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

FQDN Host group rule causing high 100% CPU XG Hom

I was attempting to allow only specific devices to bypass https scanning by using the FQDN host group method for Netflix.com as the destination. My CPU on the box shortly following adding the new rule hit 100% and stayed. I know we only have one Roku streaming so this was the single IP hitting the rule. Subsequently

Not sure the limits of the XG Home or if I need a better CPU to process this type of rule... I have a Pentium 4 3 GHz with 4 GB RAM 2 - 1 GB NICs..

FQDN Hosts group

*.netflix.com
*.nflxext.com
*.nflximg.net
*.nflxso.net
*.nflxvideo.net

Thanks

This thread was automatically locked due to age.

Parents

0 LuCar Toni over 6 years ago

Could be related to an "old" issue in most of network products.

Check the atop of the XG while using this to be sure about it.

Saw this on UTM as well, some services uses AWS Loadbalancer and switches the IP every 3 second (which will cause a huge load on the System).
Cancel
Vote Up 0 Vote Down

Cancel
0 Rick Dunn over 6 years ago in reply to LuCar Toni

I would like to try this however with the CPU pegged the system is almost unresponsive during this scenario... Is there a console command to do the atop without the need of the web interface?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Rick Dunn over 6 years ago in reply to LuCar Toni

I would like to try this however with the CPU pegged the system is almost unresponsive during this scenario... Is there a console command to do the atop without the need of the web interface?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 LuCar Toni over 6 years ago in reply to Rick Dunn

Atop is a CLI Command.

https://linux.die.net/man/1/atop

https://community.sophos.com/kb/en-us/127740
Cancel
Vote Up 0 Vote Down

Cancel
0 Rick Dunn over 6 years ago in reply to LuCar Toni

Took me a bit to find the Advanced Shell under Device Management under system console menu... I ran a test with and without the FQDN group applied to the ROKU rule and did not see the CPU spike I did previously and so am now attributing this as a general system lockup.

Thanks for the help
Cancel
Vote Up 0 Vote Down

Cancel
0 Rick Dunn over 6 years ago in reply to Rick Dunn

One again I found the system cpu pegged fan running high speed web interface barely responsive however this time I was able to get into the advanced shell.

atop revealed the process "avd" avg 150% and greater ... 1st attempt I used the kill -9 [avd process ID] and the system calmed down for a bit but avd process was restarted by the system and it crawled back up to use 100++% of the cpu again which after I rebooted the system.

So what is the avd process?

How can I better manage it to prevent the cpu spiking by avd?

Are there settings to look for to help better manage the system where avd will not hog the system???

Thanks again.
Cancel
Vote Up 0 Vote Down

Cancel