CoreTelephony trace file error suddenly pops up

I'm using iMac (Retina 4K, 21.5-inch, Late 2015)

Processor: 3.1 GHz Intel Core i5

Memory: 8 GB 1867 MHz DDR3

OS X El Capitan (10.11.3)


When I turned on my computer this morning a message box appears:

"CoreTelephony Trace File error"

A file operation for CoreTelephony tracing has failed, you may be out of disk space. Details 'Error opening file /tm/ct.shutdown,err = Operation not permitted'


Then I just ignored it but when I opened Xcode and run my program the simulator is unable to boot. I do not change Xcode or something. It think it was affected by that error.


Please help me. Thanks in advance

iMac, OS X El Capitan (10.11.3)

Posted on Oct 4, 2016 1:45 AM

Reply
5 replies
Sort By: 

Oct 4, 2016 1:30 PM in response to papa_dong

I'm getting the same error message out of the blue for no good reason

my specs:

MacBook Air (13-inch, Early 2015)

2.2 GHz Intel Core i7

8 GB 1600 MHz DDR3

Intel HD Graphics 6000 1536 MB

I've tried a google search and don't find any solution that seems to work

I don't know if it's my Sophos antivirus or another app causing this

I even installed the latest update and have current version 10.11.6 (15G31)

Any help please?

Reply

Oct 4, 2016 3:19 PM in response to papa_dong

I am having a similar problem. System specs:


iMac (Retina 5K, 27-inch, Late 2015)

Processor 4Ghz Intel Core i7

Memory 32GB 1867 Mhz DDR3

Graphics AMD Raderon R9 M395X 4096 MB

OSX El Capitan (10.11.6)


I get the same error on startup. Can't open certain applications, namely the Bitnami Wildfly Manager client, and our companies VPN Client. Nothing happens when I click them or attempt to open from terminal. All of this just started this morning.

Reply

Oct 5, 2016 9:31 AM in response to papa_dong

I had this exact problem too yesterday on my MacBook Pro. This caused Parallels to stop working. I've had to disable System Integrity Protection to make Parallels work again as it couldn't write to /tmp


I made no changes whatsoever the problem just happened yesterday morning when I switched on.

Reply

Oct 5, 2016 7:39 PM in response to papa_dong

This reddit discussion contained the solution I was looking for: https://www.reddit.com/r/mac/comments/55s9yg/getting_an_error_message_on_startup _coretelephony/



Two comments in particular. This:

I found solution! This is permission problem with var catalog '/tmp'. If You try to change permission this catalog, OS X do not let this change because, in system there is 'System Integrity Protection'. This SIP must be disabled before You change permission.

Try this:

  1. Reboot your Mac into Recovery Mode by restarting your computer and holding down Command+R until the Apple logo appears on your screen.
  2. Click Utilities > Terminal.
  3. In the Terminal window, type in 'csrutil disable' and press Enter.
  4. Restart your Mac.
  5. After restart Mac, try to change manual ( command: 'sudo chmod 1777 /tmp' ) or download app: ( I recommended this utility app to do this: OnyX 3.1.8 for OS X 10.11 El Capitan - download link: http://joel.barriere.pagesperso-orange.fr/download/1011/OnyX.dmg ) 5.1 In the app, select Maintenance -> Permissions, and hit Execute. This fixes all permission problems ( including changes permission '/tmp' to correct ).
  6. When the process is over ( OnyX app ) or command 'sudo chmod 1777 /tmp' works , just reboot Mac.

Now, when You changed permission, need to Enable 'System Integrity Protection'. Do this like step 1 to 4, with change: 'csrutil enable'

  1. Reboot your Mac and holding down Command+R until the Apple logo appears on your screen.
  2. Click Utilities > Terminal.
  3. In the Terminal window, type in 'csrutil enable' and press Enter.
  4. Restart your Mac. It's done :-) It will be work :-)

I hope it will help! Sorry for my English, I'm still learning ;-)

and this:

I was in a similar situation and I noticed that the files inside /private/tmp had the restrict flag. Wikipedia says that only the symbolic link /tmp itself should be restricted. So running "sudo chflags -R norestricted /private/tmp/" with SIP disabled solved it for me (don't forget to enable it back after you're done).

Per the first comment, boot into recovery mode and disable System Integrity Protection. Then restart and run the command listed. Then run the command in the second comment. Restart again into recovery mode, and then re-enable System Integrity Protection.


At least, this is what worked for me.

Reply

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.

CoreTelephony trace file error suddenly pops up

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