Discovered and fixed a huge CrashPlan log file | Dafacto

The personal website of Matt Henderson.

Discovered and fixed a huge CrashPlan log file

02 July 2013

A couple of days ago, I discovered that my CrashPlan log (in /Library/Logs/CrashPlan/engine_output.log) had gotten huge—over 60GB. Googling, I found this article that describes how to increase CrashPlan's memory. In cases where you have CrashPlan backing up millions of files, it can be necessary. After increasing the app's memory, and deleting the log file, it has since remained at a more reasonable 1.5GB.

Here are the steps:

  1. Launch a terminal window

  2. Shutdown the crash plan daemon. You will be asked for your admin password. Go ahead and enter it here.

sudo launchctl unload /library/launchdaemons/com.crashplan.engine.plist

  1. Edit the plist file with BBEdit:

bbedit /library/launchdaemons/com.crashplan.engine.plist

  1. Find Xmx512m and change it to Xmx1024m. This will allocate 1024mb of memory instead of the default 512mb

  2. Save the file and quit BBEdit

  3. Relaunch the Crashplan daemon (corrected Apr 19th 2012)

sudo launchctl load /library/launchdaemons/com.crashplan.engine.plist

Enjoy this article? — You can find similar content via the category and tag links below.

Questions or comments? — Feel free to email me using the contact form below, or reach out on Twitter.