Re: [Ntop] High CPU on FreeBSD with uprade to v4

[Muenz, Michael]

Hi Luca,

Thanks for your prompt reply, hope you're all well.
Family in Ferrara now finally enjoying usual activities.
As we want to be as close as possible to the underlying OS we are running:
https://github.com/opnsense/ports/blob/master/net/ntopng/Makefile#L42

Not sure if this release tag already includes your fixes, but I can wait 
for upstream.

Best,
Michael

Am 28.05.2020 um 14:07 schrieb Luca Deri:
Hi Michael
did you take the github package code or the github clone code? In the latter we 
have made a fix that should address this issue. Please let me know

If you want you can join https://tinyurl.com/r7w37nr for promptly replies

Regards Luca

On 28 May 2020, at 12:31, Muenz, Michael <m.mu...@spam-fetish.org> wrote:

Hi,

I'm maintaining the OPNsense plugin for ntopng and have several reports that 
with update from 3.8 to 4.0 the CPU grows from around 5% to 100% (one core). 
I'm not sure if FreeBSD in general is affected since OPNsense relies on 
HardenedBSD, but maybe you can try to help out finding the problem.

The error is easy reproducable sind you can hop from v4 to v3 and always see 
the spike when going to v4.
In the beginning the FreeBSD port had some errors for file permions which was 
fixed already.
Now we are in a stable state and ntopng.log is clear.

I checked the process with truss (BSD variant to strace) and compared to 3.8.
There are tons of:


select(1,{ },0x0,0x0,{ 0.1904051 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1903830 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1903608 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1903392 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1903176 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1902955 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1902732 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1902516 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1902294 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1902072 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1901856 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1901639 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1901423 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1901207 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1900967 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1900749 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1900533 })              ERR#22 'Invalid argument'
select(1,{ },0x0,0x0,{ 0.1900316 })              ERR#22 'Invalid argument'

Not sure if these are responsible for the high CPU, but I have no other idea 
where to look for.


Best,

Michael

_______________________________________________
Ntop mailing list
Ntop@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop
_______________________________________________
Ntop mailing list
Ntop@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop


--
www.muenz-it.de
- Cisco, Linux, Networks

_______________________________________________
Ntop mailing list
Ntop@listgateway.unipi.it
http://listgateway.unipi.it/mailman/listinfo/ntop