12

After a clean install (wiped HD before USB install) of 10.11 (El Capitan), I noticed the following error in /var/log/system.log:

Oct 21 09:06:35 computer airportd[57]: SecTaskLoadEntitlements failed error=22
Oct 21 09:07:05 --- last message repeated 5 times ---

It seems to be constantly repeating. Any ideas on how to find the issue or source process?

Thanks

  • it has something to do with the wi-fi, as disabling that stopped that message; however, now i see this a lot of this: networkd[211]: -[NETClientConnection effectiveBundleID] using process name apsd as bundle ID (this is expected for daemons without bundle ID – Saad Dec 20 '15 at 9:46
  • it happens every 14 seconds, and twice for me at the moment – Saad Dec 20 '15 at 10:11
  • code for SecTaskLoadEntitlements is here: opensource.apple.com/source/libsecurity_codesigning/…. From that, we can possibly determine what error 22 is. – Saad Dec 20 '15 at 10:26
  • Thanks for the info @SaSha, I'll do some more digging. Btw - I haven't seen any "[NETClientConnection effectiveBundleID]" in my system logs. – Tom Baker Dec 27 '15 at 19:35
  • Same issue here (together with regular WiFi outages). Any news on this one? – qqilihq Apr 18 '16 at 10:30
1

To answer your question, here's an introduction to what SecTaskLoadEntitlements really is/does:

An application (.app) in OS X is really a folder containing a number of files, including the actual program, resources (graphics, sounds, etc) as well as system files such as plist files.

One of these plist files contains a descriptions of the application's entitlements. An entitlement is either that the application "can do" a certain thing, or that it has permission to do a certain thing.

Examples on OS X would be for an app to have the permission to get read-only access to your Music folder, or that it is allowed to interact with Bluetooth devices, record from your microphone, etc.

Application on the OS X App Store are required to use entitlements in so that that they're required to be sandboxed, which is an entitlement in itself.

In order to make sure that entitlements cannot be changed or unrightfully gained, the entitlements are "signed". This means that the developer of the application uses a specific cryptographic key to "sign" the entitlements.

OS X checks the signature when loading in new applications, and only if it is signed correctly will it load the entitlements and apply them to the program.

Your error message means that the "airportd" program tried to load in the entitlements for an application, but it failed with error number 22. The number 22 means that an invalid argument (parameter) was given.

Airportd manages the wireless interfaces (WiFi) on your Mac.

So to sum up: The source process is "airportd", and the issue is an invalid argument given for loading entitlements.

However, this does not mean that you'll experience any user-facing errors. If you're not having any problems with the WiFi interfaces, then you can just ignore the log messages.

0

There seems to be some problems with wifi drivers on El Captain. I got some huge airportd crashes with that error message. Try to update to the last version of OS X (10.11.2), it seems to be a bit better.

  • 1
    Thanks @tourdetour, although I have upgraded to 10.11.2 and I am still getting the same frequency of messages. – Tom Baker Dec 27 '15 at 19:36
  • It seems to be a global problem with airport, I indeed have the same errors on my own syslog. – tourdetour Dec 30 '15 at 14:17

You must log in to answer this question.

protected by Community Aug 3 '16 at 19:49

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged .