[SOLVED] The agent (pma_agent_ui process) takes high CPU.

B

BenjaminF3

Junior Member
Hello,
I'm the Apple Specialist of a University, and we have a lot of Mac Computers.
Some of the Mac computers have the latest OS (10.15 Catalina), most of them have the previous OS (10.14 Mojave).
Since the version 8.0.0.94 of the Agent, the Process "Parallels Mac Management for Microsoft SCCM" takes more than 95% of CPU, no matter the version of the OS.
We ask Parallels for support and they answer this :
Following up on the (tangentially-related) issue of the CPU-hogging process that reappears when killed, the heavy-handed way to make the problem go away is
sudo chmod a-x /Library/Parallels/pma_agent.app/Contents/MacOS/pma_agent_ui
then kill the process. Parallels still works after this change, and Parallels Application Portal _appears_ to work as well, although I Have not tried to install anything with it after the change. However, since the rogue process appears to be part of the Application Portal, I would not be too sure that this would work ...
Original permissions for the executable are -rwxr-xr-x 1 root wheel 5565760 26 Sep 02:07 /Library/Parallels/pma_agent.app/Contents/MacOS/pma_agent_ui

It seems to work, but we have around 1000 Mac end-user !
So I created a package to push the command line on all the Mac computers. But when it update the agent, the problem comes back.

Yesterday, we updated SCCM to the 1906 version. I hoped that having a new agent will fix the issue.... But no.
The Agent version is now 8.1.0.14 and it still takes more than 95% of the CPU usage, which implies that the fans turn noisily.
Nothing found on google search..

Do you have similar issue ? do you find a better solution ?
thanks
 
pma_agent_ui.log :


1-12 08:35:58.180 D /PmaBreakpad:765:307/ Crash reporter path: '/Library/Parallels/pma_agent.app/Contents/MacOS/pma_report_tool'
11-12 08:35:58.194 D /PmaBreakpad:765:307/ Is about to create breakpad::ExceptionHandler.
11-12 08:35:58.194 D /PmaBreakpad:765:307/ minidump_calback = 0x100a98b30.
11-12 08:35:58.194 D /PmaBreakpad:765:307/ breakpad::ExceptionHandler is in in-proc mode.
11-12 08:35:59.145 I /logrotate:765:307/ Log rotator started
11-12 08:35:59.146 D /pma_agent_ui:765:307/ Console user: **************
11-12 08:35:59.147 D /pma_agent_ui:765:307/ Window server user: **************
11-12 08:35:59.147 D /CepClientItf:765:307/ Starting cep event server client...
11-12 08:35:59.156 D /CepClientItf:765:307/ Cep event server client has been started
11-12 08:35:59.156 D /AskRestartAgent:765:307/ Starting AskRestartAgent
11-12 08:35:59.157 D /MacAgentUI_Libraries_MdmApproval:765:307/ Starting NotificationAgent
11-12 08:35:59.157 D /pma_agent_ui:765:307/ PdConfig agent has started. (0x0x7ff825212400))
11-12 08:35:59.157 D /pma_agent_ui:765:307/ VmConfig agent has started. (0x0x7ff824657400))
11-12 08:35:59.240 D /Profiles:765:307/ Will open journal db @ /Users/**************/Library/Application Support/Parallels/PMA_Agent/dcm/subagent/macConfigAgent/profile_ext_info.db
11-12 08:35:59.341 D /MacConfigAgent:765:307/ Will open journal db @ /Users/**************/Library/Application Support/Parallels/PMA_Agent/dcm/subagent/macConfigAgent/inst_journal.db
11-12 08:35:59.418 I /MacConfigAgent:765:307/ MacConfigAgentImpl::ctor() : Configuration profile application timeout = 3600000 ms
11-12 08:35:59.419 D /pma_agent_ui:765:307/ MacConfig agent has started. (0x0x7ff82513ce90))
11-12 08:35:59.419 D /FileVaultAgentUI:765:307/ Timer stopped and reset to 300 sec
11-12 08:35:59.419 D /pma_agent_ui:765:307/ direct:FileVaultAgent agent has started. (0x0x7ff825214b70))
11-12 08:35:59.419 D /pma_agent_ui:765:307/ direct:RegistrationAgent agent has started. (0x0x7ff825217f00))
11-12 08:35:59.419 D /pma_agent_ui:765:307/ direct:UserCredentials agent has started. (0x0x7ff825218510))
11-12 08:35:59.419 I /PmaUtils:765:307/ UserSessionMonitor started
11-12 08:35:59.427 D /PdVmManager:765:307/ PdVmManager constructed @ 0x7ff824554bf0
11-12 08:35:59.484 W /PdVmManager:765:307/ Unable to initialize SDK library
11-12 08:35:59.484 D /SmsVmManager:765:307/ SmsVmManager started
11-12 08:35:59.484 D /DcmManager:765:307/ Starting DCM manager...
11-12 08:35:59.558 D /DcmManager:765:307/ DCM manager started
11-12 08:35:59.558 D /PackageInstallAgent:765:307/ PackageInstallAgent started
11-12 08:35:59.565 D /LocalIpc:765:307/ Client 'cep_client_{825f48df-35c3-45a8-b25c-6126419df3c9}' connected to server '/var/run/pmm_cep_client.socket'
11-12 08:35:59.567 D /pma_agent_ui:765:307/ Client ************** connected to server with code : 0
11-12 08:35:59.567 D /FileVaultAgentUI:765:307/ Connected to daemon
11-12 08:35:59.567 D /FileVaultAgentUI:765:307/ Reset FileVaultAgentUI state
11-12 08:35:59.567 D /FileVaultAgentUI:765:307/ Timer stopped and reset to 300 sec
11-12 08:35:59.571 D /SmsVmManager:765:307/ Network configuration changed, op id = {d919aeef-790c-496a-9118-08fa254333db}
11-12 08:36:06.635 D /LocalIpc:765:307/ LocalIpcConnectionImpl::onError() : 1 (QLocalSocket: Remote closed)
11-12 08:36:06.635 D /LocalIpc:765:307/ LocalIpcConnectionImpl::onDisconnected()
11-12 08:36:06.635 D /LocalIpc:765:307/ Client ************** disconnected from server.
11-12 08:36:06.635 D /pma_agent_ui:765:307/ Client ************** disconnected from server
11-12 08:36:06.635 D /FileVaultAgentUI:765:307/ Disconnected from daemon
11-12 08:36:06.635 D /FileVaultAgentUI:765:307/ Reset FileVaultAgentUI state
11-12 08:36:06.635 D /FileVaultAgentUI:765:307/ Timer stopped and reset to 300 sec
11-12 08:36:16.783 D /pma_agent_ui:765:307/ Client ************** connected to server with code : 0
11-12 08:36:16.783 D /FileVaultAgentUI:765:307/ Connected to daemon
11-12 08:36:16.783 D /FileVaultAgentUI:765:307/ Reset FileVaultAgentUI state
11-12 08:36:16.783 D /FileVaultAgentUI:765:307/ Timer stopped and reset to 300 sec
11-12 08:36:16.804 D /SmsScheduler:765:307/ Schedule [policy id = {FE6AD13D-FD68-403B-B7BF-00F9D03DDCC5}, schedule id = {78534645-c47f-482c-83dc-1f2ef3b90b5c}, message id = {FE6AD13D-FD68-403B-B7BF-00F9D03DDCC5}, target endpoint = 'direct:DCMAgent_impl'], has history, last trigger time = 20191112065935.780000+000
11-12 08:36:16.804 D /SmsScheduler:765:307/ No messages for [policy id = {FE6AD13D-FD68-403B-B7BF-00F9D03DDCC5}, schedule id = {78534645-c47f-482c-83dc-1f2ef3b90b5c}, message id = {FE6AD13D-FD68-403B-B7BF-00F9D03DDCC5}, target endpoint = 'direct:DCMAgent_impl'] can be scheduled on '2019-11-12T08:36:16'
11-12 08:36:16.804 D /SmsScheduler:765:307/ Scheduled message {
PolicyID: {FE6AD13D-FD68-403B-B7BF-00F9D03DDCC5}
ScheduleID: {78534645-c47f-482c-83dc-1f2ef3b90b5c}
TargetEndpoint: direct:DCMAgent_impl
Trigger schedule: RecurNone: { Token = 4dab6c4000080001, StartDate = 2019-06-11T13:19:00Z (UTC = 1), Duration = { Days = 0, Hours = 0, Minutes = 0, AllInSeconds = 0 } }
Message name: Undefined
Message:
} has no active schedules
11-12 08:36:16.805 D /SmsScheduler:765:307/ Schedule [policy id = DEP-SIU2007C-ScopeId_90B82680-9A1D-4E01-A83F-CD49688A1BB6/Application_28029e0a-9c72-4dcc-98f3-840ebde27728, schedule id = {35f2268f-d4cf-4fe7-9086-b106f898b707}, message id = DEP-SIU2007C-ScopeId_90B82680-9A1D-4E01-A83F-CD49688A1BB6/Application_28029e0a-9c72-4dcc-98f3-840ebde27728, target endpoint = 'direct:DCMAgent_impl'], has no history
11-12 08:36:16.805 D /SmsScheduler:765:307/ Next message for [policy id = DEP-SIU2007C-ScopeId_90B82680-9A1D-4E01-A83F-CD49688A1BB6/Application_28029e0a-9c72-4dcc-98f3-840ebde27728, schedule id = {35f2268f-d4cf-4fe7-9086-b106f898b707}, message id = DEP-SIU2007C-ScopeId_90B82680-9A1D-4E01-A83F-CD49688A1BB6/Application_28029e0a-9c72-4dcc-98f3-840ebde27728, target endpoint = 'direct:DCMAgent_impl'] is 'TriggerMessage' @ '2033-04-10T06:35:00' in 423176324 seconds
11-12 08:36:16.805 D /SmsScheduler:765:307/ Scheduling 'TriggerMessage' for [policy id = DEP-SIU2007C-ScopeId_90B82680-9A1D-4E01-A83F-CD49688A1BB6/Application_28029e0a-9c72-4dcc-98f3-840ebde27728, schedule id = {35f2268f-d4cf-4fe7-9086-b106f898b707}, message id = DEP-SIU2007C-ScopeId_90B82680-9A1D-4E01-A83F-CD49688A1BB6/Application_28029e0a-9c72-4dcc-98f3-840ebde27728, target endpoint = 'direct:DCMAgent_impl'] in 423176324 seconds @ '2033-04-10T06:35:00'
11-12 08:36:16.805 D /SmsScheduler:765:307/ Schedule [policy id = {81DCE1E8-70D6-4EFE-A616-AA7634DCBE51}, schedule id = {d0ac0fc8-d545-439e-9ef6-3b9c9488bdc6}, message id = {81DCE1E8-70D6-4EFE-A616-AA7634DCBE51}, target endpoint = 'direct:DCMAgent_impl'], has history, last trigger time = 20180925061047.719000+120
11-12 08:36:16.805 D /SmsScheduler:765:307/ No messages for [policy id = {81DCE1E8-70D6-4EFE-A616-AA7634DCBE51}, schedule id = {d0ac0fc8-d545-439e-9ef6-3b9c9488bdc6}, message id = {81DCE1E8-70D6-4EFE-A616-AA7634DCBE51}, target endpoint = 'direct:DCMAgent_impl'] can be scheduled on '2019-11-12T08:36:16'
11-12 08:36:16.805 D /SmsScheduler:765:307/ Scheduled message {
PolicyID: {81DCE1E8-70D6-4EFE-A616-AA7634DCBE51}
ScheduleID: {d0ac0fc8-d545-439e-9ef6-3b9c9488bdc6}
TargetEndpoint: direct:DCMAgent_impl
Trigger schedule: RecurNone: { Token = a54c2c0000080001, StartDate = 2018-02-12T10:41:00Z (UTC = 1), Duration = { Days = 0, Hours = 0, Minutes = 0, AllInSeconds = 0 } }
Message name: Undefined
Message:
} has no active schedules
 
Hello,
It's hard to say right now why pma agents take 95% CPU on macs. It will be better to investigate this behavior within a support request.
Please submit a ticket and attach your previous ticket number.
 
Timur Skorlov said:
Hello,
It's hard to say right now why pma agents take 95% CPU on macs. It will be better to investigate this behavior within a support request.
Please submit a ticket and attach your previous ticket number.
Click to expand...
It seems it has been fixed with the new version of the agent 8.1.0.14. Thanks
 
You must log in or register to reply here.
Back
Top