Management CPU still an issue

[darren_g]

Yes, it's that time again.

I'm still seeing issues with the management CPU spiking despite my recent upgrade to the 5.x stream of software.

The image below shows the last 24 hours of the Management CPU on my active PA2020

Notice the regular spikes to roughly 60% utilisation - sure, the *average* is low (ignore the 80% spike - I upgraded to 5.0.6 this morning, and that was what caused that) - but this regular spiking to 60% worries me a bit.

Anyone else seeing it? Anyone from PA got an explanation? Should I shutup and not worry (which I would do if it was irregular, but these spikes are almost metronomic in their frequency, which is why I am concerned).

Cheers.

[HULK]

Hi,

Is there any scheduled updates or any scheduled activities set on this firewall at that time. Have you observed any specific daemon taking too much of CPU... ?

Thanks

SG

[HULK]

Please follow below mentioned discussion on the same topic.

https://live.paloaltonetworks.com/message/29691#29691

Thanks

SG

[darren_g]

Nope - apart from the 80% spike when I updated to 5.0.6 this morning, there are no scheduled updates throughout most of this.

It's the indexing process which is doing it - again - vis-a-vis

12577 root

30  10  3896 1312 1092 S   50  0.1   0:51.32 /bin/bash /usr/local/bin/genindex.sh 1:12:45:01

Runs like that for a few minutes, then drops back down to 10% CPU or so, then back to nothing for a while before spiking again.

And, according to the comment above, I'm not the only one still seeing it.

[HULK]

This script does the indexing of  log databases, please open a case with support so that we can look into it to see why it causing the cpu to hike.

[darren_g · Accepted solution]

For reference of anyone who searches this out, this is officially a bug, bug ID 56014, and is under investigation.

Estimated mitigation is with the 5.0.8 release.