02-04-2013 12:37 PM
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
02-05-2013 09:34 AM
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
02-05-2013 07:19 PM
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
02-06-2013 02:40 AM
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
02-06-2013 05:47 AM
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.
02-06-2013 07:29 AM
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
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!