Why are trustd, nsurlsessiond, syslogd causing high CPU on Mac?

The syslogd high CPU I am pretty sure is a result of the excess logging coming from trustd and nsurlsessiond.

In console I am getting the same 3 messages logged constantly:

error	11:38:11.053373-0700	nsurlsessiond	Failed to obtain user-directory, errno: 5
error 11:38:11.053484-0700 nsurlsessiond Process with bundleID <private> [pid 222] does not have a bundle path, rejecting connection
error 11:38:11.053661-0700 trustd obliterateAllSessionsWithReply error handler called with error Error Domain=NSCocoaErrorDomain Code=4097 UserInfo={NSDebugDescription=<private>}
error 11:38:11.054331-0700 nsurlsessiond Failed to obtain user-directory, errno: 5


This reoccurs every millisecond or so and has been occurring since Catalina was installed. Originally after a reinstall I was running Mountain Lion and then did a bridging upgrade to Mavericks to get to Catalina. I also thought this might be due to not having iCloud setup so I logged it in but didn't change the problem.




[Re-Titled by Moderator]

Posted on Apr 8, 2020 11:42 AM

Reply
Question marked as Top-ranking reply

Posted on Jun 30, 2020 9:27 AM

Hi flipflips, I followed Jeremy's instructions, and now the issue is solved. So let me explain how to do this in more detail.


But before taking off: beware that tinkering with the Mac system using the Terminal is risky business. I had a long conversation with Apple Care, who took me through a lot of steps, and they in general advise to NOT use Terminal.

So, make sure to have a backup of all your files, and check the contents of the log-files to check that your issue is caused by exactly the same issue that Jeremy reported. That is how I did it, and it worked for me.


And if your system gets unstable, you can always go back to factory defaults, and start over from there :)


Now, first we will check the log files.

To do this, start Spotlight (the looking-glass symbol in the upper righthand corner of the screen) and type:


/var/log/asl


This brings up a Finder window with the folder with the log-files.

Those log-files have a name like:


2020.06.30.xxx.asl


You can open the log-file with the program Console (that is the default program, or you can use Open with...)


Check this log-file for lines as:


libcoreservices: __makeDirectory: 405: mkdir: path=/var/folders/zz/[randomized name]/0/ mode=0755: Operation not permitted.


The [randomize name] part is a long string like zyxvpxvq6csfxvn_n00000y800007k


This string is important: it is the name of a system subdirectory that is used by the nsurlsessiond process. Nsurlsessiond tries to write to this directory, but gets no permission, and repeats and repeats and repeats and repeats. That's why nsurlsessiond stays in the top of your list of processes, eating up to 50-60% of your CPU capacity, draining your battery, and heating your MacBook.


So check if you see these lines in your log file, to make sure your issue is the same.


To solve the issue you have to do 2 things:

  1. Kill the trustd process
  2. Delete the blocked directory, so that the OS can create a new one.


These things are done using the Terminal. You can find this program in the Launchpad, or find it using Spotlight.


First, find the name of the subdirectory (the string mentioned above). Copy it from the log-file, or find it using the Terminal.


Start the Terminal program. The Terminal window opens. After the prompt, type:


ls -la /var/folders/zz | grep nsurlsessiond


You will get an output like:


drwxr-xr-x@  5 _nsurlsessiond    _nsurlsessiond     160  9 jun 13:45 zyxvpxvq6csfxvn_n00000y800007k


The part that I made bold is the name of the subdirectory we need to delete, so copy this to your Clipboard.


Now, take a look again at the Activity monitor, and look for the trustd process, that is one of the top 3 or 4 processes in the list. It has a unique process id, the PID number (for example 219).


In Terminal, kill the trustd process, by typing:


sudo kill -9 [trustd PID]


So if the PID is 219, you type:


sudo kill -9 219


After killing this process, you will see the CPU usage drop immediately.


Now we delete the subdirectory. Again in Terminal, type


sudo rm -fr /var/folders/zz/[randomized name]


Again, replace [randomized name] with the string you copied before.


Congratulations, you are done!


Keep following your system performance for several days in the Activity Monitor.


Success!




Similar questions

125 replies

Apr 17, 2020 9:00 AM in response to biofed

Open the "Activity Monitor" app.

Locate the "trustd" process in the left column.

Find its PID in the "PID" column, it should be an integer.


Open the "Terminal" app.

Copy the following command, replacing "[trustd PID]" with the PID you just found:

sudo kill -9 [trustd PID]

and run it (press "Return")


Still in "Terminal", copy and run the following command:

ls -la /var/folders/zz | grep nsurlsessiond

The name in the last column is the name you need to replace "[randomized name]" with in the next and last command to run:

sudo rm -fr /var/folders/zz/[randomized name]


That's it, you're done!

May 13, 2020 5:09 AM in response to MrPablo14

You can do this two different ways.... you can navigate to the /var/log/asl folder via Terminal, and then run remove file commands on the appropriate files. In theory there files don't matter since they're just logs, but make sure you know what you're doing before removing anything you might need. An even easier way is to just navigate to the /var/log/asl folder from Finder, and then move these files to the trash. I was finding the nsurlsessiond process was creating 25MB log files every 1-2 minutes, and it was hijacking my computer's storage. Not only that, the process itself was draining my battery. Once I followed the info mathieu105 posted, I was able to stop these logs from accruing.

Jul 4, 2020 2:22 AM in response to Warrennj31

No, nothing will be disabled. We only delete a dictionary witch nsurlsession wants to change. Sience it has no rights to do that it tries over and over again what causes the high CPU usage.


The only thing what we do is to delete this dictionary with the logs in it, the logs are not needed anymore. Nsurlsession creates automatically a new dictionary after that.

Apr 26, 2020 11:54 AM in response to PabloGonCasal

Open the "Activity Monitor" app.

Locate the "trustd" process in the left column.

Find its PID in the "PID" column, it should be an integer.


Open the "Terminal" app.

Copy the following command, replacing "[trustd PID]" with the PID you just found:

sudo kill -9 [trustd PID]

and run it (press "Return")


Still in "Terminal", copy and run the following command:

ls -la /var/folders/zz | grep nsurlsessiond

The name in the last column is the name you need to replace "[randomized name]" with in the next and last command to run:

sudo rm -fr /var/folders/zz/[randomized name]


That's it, you're done!

Jul 8, 2020 8:49 AM in response to jeremywohl

Thank you so much. It wasn't clear to me whether the steps were doing anything until I tried:

# ls -la /var/folders/zz | grep nsurlsessiond

and plugged in that result.

# sudo rm -fr /var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k

Suddenly, the CPU load dropped from ~60% to 8%.

The memory pressure plot turned from yellow to green.

The energy impact plot has a dropoff like one side of the Mariana Trench.

Amazing. Thank you.

Jun 23, 2020 11:00 PM in response to elle0405

I killed the trustd process, and that has taken care of nsurlsessiond as well. It's been a few weeks now.


There is a comment, where you are walked step by step through the process. I don't have a link at the moment, but it should be this, because I'm getting the notifications. I usually don't touch Terminal, but it worked very well.


Thanks again to everyone taking time and effort to help!

Jun 8, 2020 12:31 PM in response to jpaussa

Same issue solved here in Denmark with the recipe above, on my girlfriend's eight year old Macbook Air after updated it to "Catalina". The folder name was exactly the same, so doesn't seem to be that random. After reboot the folder was re-created, but this time as a symbolic link - that's what the "@" in the 'ls' output means - to a directory under mountpoint /System/Volumes:

$ ls -ldi /var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k
 12885475075 drwxr-xr-x@ 5 _nsurlsessiond _nsurlsessiond 160 7 Jun 09:16 /var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k
$ find / -inum 12885475075 -ls 2>/dev/null
 12885475075 0 drwxr-xr-x 5 _nsurlsessiond _nsurlsessiond 160 7 Jun 09:16 /System/Volumes/Data/private/var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k
 12885475075 0 drwxr-xr-x 5 _nsurlsessiond_nsurlsessiond 160 7 Jun 09:16 /private/var/folders/zz/zyxvpxvq6csfxvn_n00000y800007k

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Why are trustd, nsurlsessiond, syslogd causing high CPU on Mac?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.