Soagent mac os что это

Question: Q: Problems with callservicesd and soagent

I am currently running the last Yosemite public beta version.

On both my desktop and laptop I frequently see on activity manager that the processes callservicesd and soagent are racing along using 100% of CPU each. Messages which I think is related to these processes often shows the same behavior.

I kill the processes but within half an hour they are back and racing along.

Is anyone else having this problem? Is this something which might be fixed by upgrading from the public beta to the release Yosemite?

Mac Pro (Early 2009), OS X Mountain Lion (10.8.3)

Posted on Oct 27, 2014 10:03 AM

Helpful answers

I had the same issue with soagent and callerservicesd eating up all CPU.

The problem is related to a contact syncing issue with iCloud.

Open the console and filter for messages from «MCContactsManager». In the details of the message, you can find a reference to the contact causing the issue. Export this contact to a VCF file. Delete the contact and check that there are no more messages from «MCContactsManager».

Watch out for soagent and callerservicesd to relax (should use much less CPU now).

Now you can import the saved VCF into contacts again and everything should be back to normal.

Open the Contacts App.

Go to the Preferences > Accounts.

Make sure it is only using one Account to sync with.

If it is using iCloud, Google, Yahoo and more it will delay the opening of Messages as Messages links to the Contacts app and lists all the contacts.

It is best to use only one account.

9:53 pm Wednesday; July 8, 2015

soagent is a support part of Messages. I am not sure about the other one.

In the Finder hold down the ALT key whilst using the Go Menu.

Select the Library that has appeared.

Navigate to Containers/com.apple.soagent/Data/Library/Preferences and delete (Drag to Trash) the com.apple.soagent.plist and then Restart the computer.

9:52 PM Tuesday; December 2, 2014

There’s more to the conversation

Loading page content

Page content loaded

You should update to the release version, whether it solves the problem or not.

Oct 27, 2014 10:43 AM

OK so I took it upon myself to do some research because I was not getting the response I required quick enough. I personally have protools on my computer. So I followed the instructions on going to the library and updating the plug ins.

go to your computer

see what kind of Plug-In you have, mine was DigiDesign

remove plug-in and reinstall

This stopped my issue with the coreaudiod, callservicesd, & identityservicesd. I have not seen these stop responding in the past 3 days.

However I am still having some issues with slow response going between functions on my computer. Which I do not understand because I have 45GB open on my hard drive. But it is no where near as bad as it was before. Over the next week or so I will be removing a lot of pictures, video and music onto external hard drives. Cleaning my desktop, and getting rid of programs I don’t use.

I hope this helps because it was really frustrating for me.

soagent is a support part of Messages. I am not sure about the other one.

In the Finder hold down the ALT key whilst using the Go Menu.

Select the Library that has appeared.

Navigate to Containers/com.apple.soagent/Data/Library/Preferences and delete (Drag to Trash) the com.apple.soagent.plist and then Restart the computer.

9:52 PM Tuesday; December 2, 2014

I had the same issue with soagent and callerservicesd eating up all CPU.

The problem is related to a contact syncing issue with iCloud.

Open the console and filter for messages from «MCContactsManager». In the details of the message, you can find a reference to the contact causing the issue. Export this contact to a VCF file. Delete the contact and check that there are no more messages from «MCContactsManager».

Watch out for soagent and callerservicesd to relax (should use much less CPU now).

Now you can import the saved VCF into contacts again and everything should be back to normal.

I noticed that the processes started to use up more CPU resources than they should again later. Most people just kill them. They will recover and behave nicely again (for some time).

If there is a process behaving like that, you can also auto-kill and restart them. The easiest way to achieve that is to use LaunchControl: http://www.soma-zone.com/LaunchControl/

LaunchControl can be used to «nice» daemons or to kill them after a period of time (e.g. every 30 min or so).

Add «ExitTimeOut» to the process in question.

Feb 2, 2015 10:55 AM

In this case, disable iCloud contact sync and re-enable it.

Mar 28, 2015 5:15 AM

I just found out what the issue was caused by in my case.

It was a strange story, because I noticed that cannot sync all my contacts with my Parrot MKi9200 in my car.

Then I checked on my iPhone, how many contacts do I have at all. I don’t know what the limit of the Parrot is, but I’m sure I was way behind it. There were more than 24000 contacts in my iCloud account. On my MBP Messages and FaceTime was starting also slow, they were bouncing 10-12 times before start, while normally they do it like 1-2-3 times.

This was the result of dragging and dropping contacts from Outlook-»Contacts to Finder (exporting my Office 365 contacts) and then importing them into iCloud.

So what I did was that I removed all my contacts from iCloud. I exported my O365 contacts from within the Contacts app on the MBP. Then I imported them into Contacts, while I disabled the contact sync with the O365 account.

Now all is quiet, because soagent and callservicesd do not throttling the CPU at all. They consume 0 CPU time, while Messages and FaceTime are running.

With O365 contacts sync enabled these two start much slower, but they still bounce 6-7 times, which is acceptable.

I have not been able to check, if my Parrot is ok, but tomorrow I’ll let you know.

One thing is for sure: if someone had more than a few thousand contacts, that will throttle the CPU with several services, like the ones mentioned. Apple needs to fix that. I don’t know, where the other thing is rooted, but it looks like O365 accounts can only be relatively slowly accessed by the Contacts, Messages, FaceTime apps on the Mac. This results in relatively slow startup of these.

Источник

Question: Q: Why is a process called «soagent» eating up my CPU?

Yesterday I noticed that the fan on my MacBook Pro was going non-stop, making a ton of noise, and my machine’s performance had slowed to a crawl. I opened up Activity Monitor to find that a process called «soagent» was using about 106% of my Mac’s CPU resources, like in this screen shot.

I’ve force quit the process several times, but it always comes back to life and grabs those processor resources, even when I have all apps closed.

Anybody have any idea what this «soagent» is related to, or what it is used for? I’m having difficulty troubleshooting.

MacBook Pro with Retina display, OS X Yosemite (10.10.1), 1 TB, 16 GB, 2.8 GHz i7, Iris Pro

Posted on Jan 15, 2016 6:00 AM

Helpful answers

I don’t have time to do a lot of research, but ‘ll add my two cents if it helps.

So it is likely being exercised by a process that accesses data (synch, get whatever) from the web via APIs. It could be a callendar, contacts, mail (OWA is web services) etc.

for the record, mine is loaded but using 0.0% CPU

Jan 16, 2016 8:34 AM

As I noted above, once I resolved a problem with my Google account sync, the soagent problem disappeared. But, thank you. Your link to the macinside thread was very helpful.

Jan 16, 2016 8:35 AM

There’s more to the conversation

Loading page content

Page content loaded

Jan 15, 2016 6:15 AM

That refers to beta software.

Jan 15, 2016 6:21 AM

You might start here.

I’ve never seen such an agent take up any significant % of CPU

Jan 15, 2016 6:23 AM

It’s not beta software. This is a fresh El Capitane install from about 2 weeks ago. It’s a production machine, so I don’t install anything beta on it.

Jan 15, 2016 6:25 AM

I was having the same problem (though with Yosemite). The referenced thread suggested the problem might be with syncing Google contacts. I think, at least in my case, that was correct. I’d changed to two-factor authentication for Google a while back and had never updated my account on my Mac. Updated everything and the soagent problem seems to have gone away (fingers crossed!).

Jan 15, 2016 7:43 AM

I don’t have time to do a lot of research, but ‘ll add my two cents if it helps.

So it is likely being exercised by a process that accesses data (synch, get whatever) from the web via APIs. It could be a callendar, contacts, mail (OWA is web services) etc.

for the record, mine is loaded but using 0.0% CPU

Jan 16, 2016 8:34 AM

As I noted above, once I resolved a problem with my Google account sync, the soagent problem disappeared. But, thank you. Your link to the macinside thread was very helpful.

Jan 16, 2016 8:35 AM

Do you use iCloud Contacts, or do you synchronize your contacts with any other network service, such as Google?

Jan 15, 2016 9:39 AM

Thanks, everyone, for the tremendously helpful input.

Indeed, this problem is related to a Google Apps account. I don’t use two-factor authentication, though.

It seemed, at first, related to the address book. I had a look and, despite all the CPU over-use, there was no syncing going on. The contacts in my Contacts app on my Mac and the contacts in the Google App interface were completely different. So I exported the contacts out of my Contacts app on my Mac, then deleted the Google Apps account from my Mac.

In the web interface I imported the contacts into Google Apps, then went through them and sorted out some problems.

Then I re-added the Google Apps account to my Mac. Of course, the initial sync took some time and a lot of computer resources. The original «soagent» problem has been reduced (it will only peak, along with another process, «callservicesd» to 75% or so from time to time, so you were right, Grant, there was another culprit at play). But that’s still not okay. The new problem now is that when Mail is open, it constantly utilizes 175% of my CPU. This slows the machine and kills the battery nearly instantly.

So the new problem is: how do I get this Google Apps account to play nice with my Mac?

But that’s a problem for an entirely new threat, methinks. Thanks for your help, everyone.

Jan 16, 2016 8:43 AM

Jan 16, 2016 1:30 PM

So, about soagent and callservicesd, finally I solved doing what has been suggested here Re: Problems with callservicesd and soagent thanks to alecthomas.

when you do it, you lose all your messages from your mac mail app, so save them to a local folder you can create in mail before to proceed with the account deletion. Same thing if you are syncing your contacts: export/save all your contacts before proceed, otherwise you might lose them.

I also found someone who said to go in (home)/Library/Preferences/. and delete some xxx.plist files there, but I didn’t need to touch anything there.

After I recreated my internet account to sync my personal gmail account, the first sync with google needed to download thousands of emails from there, so I think is more than expected that it will consume time, band (internet connection) and CPU resources, but now all the problems with soagent and callservicesd has gone and I’m happy again with my MBA.

About you current problem with the OSX Mail app, I solved other problems I started experiencing after updating to 10.11.2, by disabling the SIP protection which has been introduced by 10.11.2. I don’t know, but you may try it. If you don’t solve the problem you can re-enable SIP protection on OSX. Currently I disabled SIP and I’m waiting for 10.11.3 to see if I can enable it without problems, but I will wait at least one month before applying any new update to my MBA monitoring the community to see if there are any new issues with them.

Hoping to help everyone who suffered like me after 10.11.2 😉

Источник

Профилактика OS X: возвращаем системе производительность

Продолжаем приводить Mac в порядок. На прошлой неделе мы устроили профилактику накопителю, а сегодня возьмемся непосредственно за операционную систему.

Итак, OS X. Причин снижения производительности, появления различных неполадок в работе и других проблем может быть огромное множество, поэтому рассмотреть их все в рамках одного материала просто не представляется возможным. Поступим проще.

Мы предлагаем вам 6 советов, которые гарантированно не навредят системе и с высокой степенью вероятности повысят производительность компьютера, а также предотвратят возникновение проблем в будущем. Ничего сложного — просто несколько полезных трюков. Поехали!

Совет 1. Проверка списка автозагрузки

Начнем с банального — автозагрузки. Открываем «Системные настройки» и выбираем пункт «Пользователи и группы». Переходим на вторую вкладку под названием «Объекты входа» и внимательно изучаем список приложений, которые запускаются вместе с системой. Если заметили что-то откровенно лишнее, то смело выделяем эту программу и нажимаем на минус внизу. Снятие или установка галочки эффекта не дадут — это всего лишь средство скрыть окно программы после ее автозагрузки при запуске системы.

Очевидно, что Final Cut Pro X при запуске системы – не лучшая идея

Совет 2. Обнуление PRAM

Далее еще один известный, но от этого не менее полезный совет — сбросить PRAM. Эта процедура описана даже на сайте Apple:

PRAM — это небольшой раздел памяти компьютера, где хранится ряд значений параметров, к которым система OS X может быстро получить доступ.

Соответственно, периодический сброс данного раздела позволит «взбодрить систему». Для этого делаем следующее:

После того как система все-таки загрузится, вы можете заметить, что некоторые параметры сбились. Их придется настроить заново в «Системных настройках».

Совет 3. Использование Терминала

В «Терминале» OS X можно вводить команды, которые позволят внепланово запустить процедуры обслуживания системы. Для этого запускаем «Терминал» и копируем туда следующее:

sudo periodic daily
sudo periodic weekly
sudo periodic monthly

После этого потребуется ввести пароль администратора. Обратите внимание, что набираемые символы в «Терминале» не видны. Нажимаем Enter и ждем выполнения всех процедур.

Также из «Терминала» можно перестроить кэш dyld. Нередко его повреждение приводит к «задумчивости» компьютера, когда появляется индикатор загрузки и то или иное приложение становится временно недоступным для работы.

Потребуется ввести пароль, а затем желательно перезагрузить компьютер.

Совет 4. Очистка кэша приложений

Для выполнения этого совета придется завершить все запущенные приложения. Затем открываем Finder и нажимаем комбинацию клавиш Shift-Cmd-G. В появившемся поле вводим адрес

/Library/Caches и попадаем в указанную папку. Отсюда абсолютно все отправляем в корзину.

Все это смело отправляем в корзину

Вновь открываем Finder и нажимаем Shift-Cmd-G. Теперь в поле вводим уже /Library/Caches (отличие в тильде) и опять удаляем все файлы и папки. Очищаем корзину, перезагружаем компьютер.

Этот совет будет полезен, если какое-то приложение стало работать слишком медленно или даже перестало запускаться. После очистки кэша и последующего запуска программы он будет создан заново, но уже лишен проблем.

Совет 5. Заглядывайте в Мониторинг системы

У пользователей Windows есть «Диспетчер задач», а у владельцев компьютеров Mac «Мониторинг системы». Его можно найти среди других системных утилит в Launchpad. После запуска нас интересуют первые две вкладки: ЦП и Память.

Если какой-то процесс отъедает неожиданно много ресурсов процессора, то его необходимо закрыть. Простое правило, позволяющее зачастую определить программу, тормозящую работу всей системы.

На вкладке «Память» тоже стоит обратить внимание на программы, использующее чересчур много оперативной памяти. Например, этим иногда страдает Safari — браузер вроде бы завис, а на деле не может справиться с огромным куском ОЗУ, который отхватил себе у других программ. Если не хотите ждать несколько минут, пока система разберется сама, то лучше помочь Safari завершить работу принудительно.

Совет 6. Используйте специальный софт для профилактики OS X

Проще всего ухаживать за системой при помощи специального программного обеспечения. Такого для OS X в избытке, но самая популярная и, пожалуй, мощная — CleanMyMac 3. Кроме перечисленных выше операций, она обладает массой других возможностей, которые могут оказаться полезными именно вам. Разумеется, утилита платная.

Зачастую любую проблему в OS X можно победить даже без переустановки системы. Перечисленные выше советы — верный шаг к восстановлению прежней работоспособности компьютера. Главное, что следовать им достаточно просто и совершенно безопасно.

Источник

Процесс soagent грузит процессор

Когда Mac начинает без видимой причины увеличивать обороты вентиляторов системы охлаждения, есть повод задуматься о причинах.

Процесс soagent грузит процессор Mac os X

Что это за процесс soagent

Вспоминая, что по сути своей Mac osX является UNIX, soagent может быть только агентом UNIX, который управляет SOA — процессами сервис-ориентированной архитектуры — в основном обработчиком веб-сервисов (SOAP / rest). Таким образом, он, вероятно, может быть вызван процессом, который получает доступ к данным (синхронизирует, получает что угодно) из Интернета через API. Это может быть звонок, контакты, почта (OWA — веб-сервисы) и тому подобное. Поскольку What’sApp, Telegram и им сочувствующие были закрыты, а процесс soagent продолжал нагружать процессор, пришлось искать дальше.

Завершить процесс soagent

Простое завершение процесса не приносит желаемого результата — процесс запускается вновь и продолжает отжирать ресурсы. Подсказка уже есть — при загрузке ноутбука автоматически открывается браузер и все вкладки. Ищем дальше.

Кто вызывает soagent

На скриншоте видно, что soagent вызван не системным запросом. Подумав, кто ещё может синхронизировать большой поток данных, пришлось прибить Google Drive. Оказалось, что это был не он, поскольку нагрузка на процессор не снизилась. Перезагрузка тоже не помогла — нагрузка от процесса soagent не изменилась.

Решение проблемы

Как подсказывает логика, виновником будет процесс, который потребляет примерно те же значения процессорного времени.

Оказалось, что процесс Google Chrome Helper постоянно обновляет данные во вкладке с новой Youtube Studio, будь она неладна. Со старой версией такой проблемы, ясно дело, не наблюдалось. После закрытия вкладки процесс soagent заснул и перестал грузить процессор.

Процесс soagent с нормальным потреблением ресурсов

Источник

Question: Q: OS X process ‘soagent’

Anyone know what the OS X process ‘soagent’ is?

It seems to be chewing up a fair amount of processor time.

iMac, OS X Mountain Lion (10.8.3), 6GB RAM, Time Capsule 500GB

Posted on Jun 18, 2013 9:49 PM

Not true. I have this framework on my machines, and it’s running:

Posted on Jun 20, 2013 9:30 AM

Helpful answers

What is the parent process shown in Activity Monitor? What user is it running as?

Jun 19, 2013 6:02 PM

That whole framework should not be there. You may have installed the expired beta of Messages. Back up all data, then reinstall the OS. Even that may not get rid of it. In that case, you’ll have to erase, install, and restore your data from a backup.

Jun 19, 2013 8:27 PM

There’s more to the conversation

Loading page content

Page content loaded

Jun 19, 2013 1:35 PM

What is the parent process shown in Activity Monitor? What user is it running as?

Jun 19, 2013 6:02 PM

Process: soagent [358]

Path: /System/Library/PrivateFrameworks/MessagesKit.framework/Versions/A/Resources/so agent.app/Contents/MacOS/soagent

Load Address: 0x103372000

Parent Process: launchd [253]

The user is my user account.

Jun 19, 2013 7:20 PM

Well, it’s something in the MessagesKit framework 😉

I don’t know specifically what it does, but I have it running on my machine, and it’s built into an OS X framework. I figure if you kill it, then Messages may stop working or something.

Jun 19, 2013 8:02 PM

That whole framework should not be there. You may have installed the expired beta of Messages. Back up all data, then reinstall the OS. Even that may not get rid of it. In that case, you’ll have to erase, install, and restore your data from a backup.

Jun 19, 2013 8:27 PM

Thanks William & Linc,

Yes Linc you are correct I did install the expired iMessages Beta.

This may also be linked to another problem I have been having, again for which you were assisting.

(This has incidentally become a problem again, and I will respond to that as suggested.)

A sample of the process reveals references to the AddressBook, etc processes.

It seems as though an erase, install and restore is almost inevitable

Jun 20, 2013 7:55 AM

Not true. I have this framework on my machines, and it’s running:

Jun 20, 2013 9:30 AM

I really don’t want to go through the fresh install of Mavericks and restore from Time Machine process, we’re not using Windows after all.

I should be able to go into the depths of the files and remove what needs removing no? Any guidance on a solution?

Nov 22, 2013 5:52 AM

An upgrade to Mavericks solved this problem for me. While I eventually did a fresh reinstall for other reasons, the Mavericks upgrade had already eliminated this bug.

Apologies but I don’t have the technical knowledge to assist with your idea to remove / reinstall the associated files. I’d recommend against this path, unless you can find someone out there with the in depth knowledge to achieve this without «breaking» anything else.

Nov 22, 2013 5:16 PM

And an upgrade to Mavericks *created* this problem for me. :-/

Dec 24, 2013 4:53 PM

I’ve just recently had this problem with soagnet and it not responding. We’ve also had some issues with malware. Do you think they are or may be related?

Feb 17, 2014 7:05 PM

I am having the same problem. Not sure what this is. Upgrade to Mavericks caused the problem.

Feb 28, 2014 10:04 AM

Thanks for your help.

Feb 28, 2014 5:50 PM

A misbehaving soagent is frequently caused by a conflicting contact that cannot be synchronized with iCloud.

See my solution here:

Feb 2, 2015 10:57 AM

I saw this issue appear when I added a new mail account to my mac mail.

I had an email address setup under outlook.com. I migrated this email over to Gmail. I then installed Gmail before deleting the outlook account. This is when I saw these processes use a tremendous amount of CPU usage.

This would only happen when I would try to open the iMessage app.

To fix this, I simply deleted one of the accounts from Mac Mail, Contacts, iMessage, Calendars. and my computer went back to normal!

I know this may not be the same issue for all. but was how I was able to fix this issue.

Источник