Skip to main content
Participant
August 24, 2017
Answered

Huge coresync log file in Sierra

  • August 24, 2017
  • 5 replies
  • 7277 views

My mac has been crashing and telling me that there is no more storage or memory to run programs since a couple of days ago.

I tracked down the problem to the CoreSync log file. The CoreSync-2017-08-23.log file is 72.42 GB. The CoreSync-2017-08-24.log file is up to 5.12 GB as of now, we are not at noon yet in this time zone. There are a few other files that are above 1.5 GB. Why are these so big?

I tried reinstalling Adobe CC, but the files regenerated with the same size. I tried to erase the files manually but then Adobe CC wont sync the files, which is my best bet now.

Im on macOS Sierra 10.12.6.

Thanks.

This topic has been closed for replies.
Correct answer ixialberto

I waited one day for coresync to generate a new log file for the day. Then I erase the huge log files from yesterday and everything seems ok now.

5 replies

Participant
June 26, 2018

Dear all,

I'm experiencing the very same pb. I erased yesterday 4 or 5 files for a total of more dans 150Gb... And today, A new file of 89Gb appeared... I keep on deleting this files, but from time to time it's completely blocking my disk. Any idea ?

And as you can see on the second picture, the sync keeps on going on even if everything seems to be fully sync....

benjaminm99412409
Participant
March 1, 2018

Update: I've received a new computer at work, installed all my Adobe CC applications, and the issue has stopped.  Standard CoreSync files are created each day, but only reach a few KB in size.

However, file syncing to the cloud isn't working.  It's turned on, but there is no note of syncing progress on the Creative Cloud menu, and the green icons on the files in my Creative Cloud folder do not appear.

Participant
March 1, 2018

Same issue here on Mac os Sierra 10.13 !

Adobe Employee
May 14, 2018

Hi,

Are you still facing the issue. If yes, can you please share your Coresync version specified in the Creative Cloud files tab in the Preferences.

Thanks,

Puneet Aggarwal

Participant
June 20, 2018

Having a similar problem. Running

Getting log files with sizes approaching 26GB

Is it safe to delete this stuff?

Participating Frequently
December 14, 2017

Just deployed Adobe DC

New Windows 10 1709 build

First day on machine 204GB CoreSync single file on system

What is this?

benjaminm99412409
Participant
December 18, 2017

I have multiple computers maxing out C hard Drive space by creating Huge Coresync files. Windows 8.1 and windows 10

David__B
Adobe Employee
Adobe Employee
December 20, 2017

I've reported this issue to engineering and we are in the process of collecting more information to understand the cause.

A few related questions
- Do you have the latest version of the Creative Cloud app installed? 4.3.0.256

- Are you seeing several or just one oversized log files?

- Are you using file sync on the systems where the issue is occurring?

- Are you seeing similar entries in the logs like was described by the earlier poster -

20171023-114055.325: t=33ec: Empty/incomplete journal on sync start

20171023-114055.325: t=33ec: Empty/incomplete journal on sync start

20171023-114055.326: t=33ec: Empty/incomplete journal on sync start

20171023-114055.326: t=33ec: Empty/incomplete journal on sync start

Thanks.

- Dave

ixialbertoAuthorCorrect answer
Participant
August 25, 2017

I waited one day for coresync to generate a new log file for the day. Then I erase the huge log files from yesterday and everything seems ok now.

David__B
Adobe Employee
Adobe Employee
August 25, 2017

Thanks for the update. If for some reason it starts happening again, please reply back on the thread and we can pursue it further.

Thanks,

- David

Participant
October 24, 2017

I am running into the same problem on windows 8.1. The logfile is 56 gb and full of entries like this. I noticed this after coresync.exe was consuming 100% cpu.  I killed the task, which stopped the logfile bloat but am worried the issue will recur next time coresync runs.

C:\Users\zyx\AppData\Local\Temp\CreativeCloud\CoreSync\CoreSync-2017-10-23.log

20171023-114055.325: t=33ec: Empty/incomplete journal on sync start

20171023-114055.325: t=33ec: Empty/incomplete journal on sync start

20171023-114055.326: t=33ec: Empty/incomplete journal on sync start

20171023-114055.326: t=33ec: Empty/incomplete journal on sync start