[7.190] High CPU usage with P2P and I/M detection activated

It is an improvement over 7.180. However it seems the CPU (Sempron 1.9GHz) overnight slowly goes up until it is constantly at 100% although the system has yet to become unresponsive and the Disk LED is not constantly flashing. RAM utilisation is at about 63% (out of 1 GB).

I am running Site-to-Site VPN with just one site and have only 3 workstations behind the Astaro.

I am running Deluge Bittorrent on a machine that is on the IPS exception list for anti-portscan.

I have noted that it has detected my Skype, Bittorrent and Yahoo Messenger activities but the source IP detection is still not correct (it detects many IPs outside of my network).

I also have POP3 proxy activated without prefetch.

$_alex\$

0 _alex\ over 16 years ago

could you do a 'top' on the shell so we can see which process uses the cpu?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Flancer over 16 years ago in reply to _alex\

I have attached a screenshot of the output from top.

This is with Bittorrent Deluge Client, Yahoo messenger and skype running.

Yahoo messenger and skype is running from two clients.
- astaro7190.jpg
- View
- Hide
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 -=malte=- over 16 years ago in reply to Flancer

Hi,
i couldn't reproduce the problem. I enabled different P2P and IM progs on several clients behind my ASG and let them produce some traffic over night.

Can you send us a backup please, that we can check your configuration.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 -=malte=- over 16 years ago in reply to -=malte=-

The "pfilter-reporter problem" is a known issue and should be fixed in 7.3

The pfilter-reporter writes after 5min the entries from the packetfilter.log and afc.log into a database.
The problem occurs when the database already contains a lot of entries.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Flancer over 15 years ago in reply to -=malte=-

If this is still the cause of the high CPU usage issue, I would not recommend deploying the 7.2 firmwares to existing customers and customers who accidentally upgrade to 7.2 will be plagued by lots of frustrations.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel