PA2020 High CPU utilization "useridd" 100% management plane

cancel
Showing results for 
Search instead for 
Did you mean: 

PA2020 High CPU utilization "useridd" 100% management plane

L3 Networker

Dears,

My PA2020 has 2 agent working identifying my AD users... but the mgnt plane is running 100% all day long...

Any suggestion ?

pls find below the show resources output....

PA2020 running OS 5.0.2

top - 18:26:05 up 6 days,  1:33,  1 user, load average: 10.26, 11.02, 12.17  <<<<<<<<<<<<<<<< !!!!!

Tasks: 100 total,   2 running,  98 sleeping,   0 stopped,   0 zombie

Cpu(s): 51.9%us, 46.0%sy,  2.1%ni,  0.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st

Mem:    995872k total,   901792k used,    94080k free,     5996k buffers

Swap:  2212876k total,   647316k used,  1565560k free,   179620k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

2373 root      20   0  209m  72m  63m S  140  7.5  10861:51 useridd<<<<<<<<<<<<<<<<< 140% CPU !!!!

21021 nobody    20   0  429m  51m 4808 S   37  5.3 329:34.26 appweb3

2042 root      30  10  4468  964  792 R    4  0.1   0:00.12 top

2371 root      20   0  651m 210m 4076 S    4 21.6 118:50.34 mgmtsrvr

1720 admin     20   0  4532 1164  912 R    1  0.1   0:02.64 top

2405 root      20   0  355m  89m 2192 S    1  9.2  48:59.31 logrcvr

2142 root      15  -5 39636 2920 1240 S    1  0.3 106:28.41 sysd

2151 root      30  10 40568 3644 1692 S    0  0.4  21:50.38 python

2408 root      20   0  247m 2480 1628 S    0  0.2   5:39.85 varrcvr

2415 root      20   0  141m 2640 1760 S    0  0.3   1:17.82 routed

    1 root      20   0  1836  560  536 S    0  0.1   0:02.30 init

55 REPLIES 55

Using both agentless userid and agent server here.

Support suggested a few steps to try if using agentless.

First disable agentless configuration... Commit... debug software restart user-id... Wait 5-10 min... Enable agentless configuration and then commit.

Did seem to fix the problem for now on our PA-2050.

Jo Christian

/Jo Christian

L4 Transporter

I have a case open on this as well.  PA is aware of it and is actively coding a fix.  The timeline is unknown at this point, "will definitely be in 5.0.3" but and could be "weeks away".  According to the folks I spoke with it is a serious enough issue there may be some sort of hotfix issued, but he could not state that for sure.

It has been causing quite a bit of issues on or PA500:  Captive portal timeouts, problems with UserID mappings etc.

Given the lack of a timeline I rolled back to 5.0.1 which fixed it immediately.

Hope that helps,

Bob

Hello,

We are also seeing the same issue on an PA-5050 installation using 5.0.2.

Seems like this is a 5.0.2 issue then.

Jo Christian

/Jo Christian

L1 Bithead

We are also seeing this on our PA-500 with 5.0.2. We have attempted to upgrade the agent although this has made no difference.

L1 Bithead

Same here... since 5.0.2 with PA-2050

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

2317 root      20   0  197m  73m  63m S  101  7.5   3047:40 useridd

22375 root      30  10 90500  49m 4148 S   13  5.1   0:00.41 pan_logdb_index

2106 root      15  -5 40572 3688 1116 S    7  0.4  85:24.78 sysd

8931 root      30  10  3996 1380 1112 S    6  0.1   1:55.05 genindex.sh

22376 root      30  10 26984 1316  924 R    3  0.1   0:00.09 sdb

  167 root      20   0     0    0    0 S    1  0.0  13:09.53 kswapd0

L2 Linker

We've had a great number of problems (other than just Mgmt CPU) with 5.0.2 on our PA-500's. It seems to me that 5.0.2 has a number of issues, but that they manifest most dramatically (based on the other posts in this thread) on the PA-500 appliances (CPU and Memory capacity would be my guess).

We're rolling back to 4.1.10 tonight on the 500's and 5.0.1 on the VM-100 appliance.

L1 Bithead

Same problem with 5.0.2 and 3020.

Case opened.

Actually 5.0.0 seemed fine as far as the CPU issue goes. Unfortunately the DHCP server was borked. It would simply stop granting leases.

5.0.2 is perfect w.r.t. the DHCP ;_)

Not applicable

Same issue here PA2050 Running 5.0.2

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND
2331   20   0  244m  75m  64m S  124  7.8   7094:50 useridd
2329   20   0  624m 258m 5668 S   13 26.6 406:35.06 mgmtsrvr
3672   30  10  4468  992  792 R8  0.1   0:00.18 top
3647   30  10 46936 1980 1672 R7  0.2   0:00.18 pan_logdb_index
3686   20   0  4468 1064  800 R7  0.1   0:00.10 top
3696   20   0 12440 1996 1720 S7  0.2   0:00.05 wmic

L3 Networker

Dears,

Yesterday we have moved back to 5.0.1 and everything is OK now.... unless the real time QoS graphical which is not OK... but that is a known bug for this version....

PA confirmed PANOS 5.0.2 has a bug for useridd process and there is no estimated time of correction... so I did that .. and I also suggest everyone to do the same.

Thanks in advance!!

View solution in original post

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!