Common errors found in service.log
Sample log messages are included below to illustrate how some common issues appear in the logs.
- Move all the above files (MyApp.app, MyApp-dSYM.dSYM and MyApp-Crash-log.crash) into a Folder with a convenient name wherever you can go using Terminal easily. For me, Desktop is the most easily reachable place;) So, I have moved these three files into a folder MyApp at Desktop.
- This article describes a known issue which prevents you from accessing CrashPlan app log files after upgrading to the following Mac OS versions: OS X 10.11; MacOS 10.13; To correct this problem, follow the steps below to use the chmod Terminal command to change the permissions of the Code42 app log.
Unable to connect to the backup engine
![Logs Logs](https://screenshots.macupdate.com/JPG/50698/50698_scr_uc1.jpg)
When an app crashes on your Mac, it automatically generates a crash report. You’ll see this appear after the crash with a warning dialog saying “App has quit unexpectedly.” That crash report is available to read immediately in that window by clicking the “Report ” button. The crash report can also be found in the Console app.
If you see an 'Unable to connect to the backup engine' message when you try to open the Code42 app, and the below error appears in service.log on Windows:
- Open services.msc.
- Open the CrashPlan Backup Service's properties pane.
- Set the 'Startup Type' to 'Automatic (delayed start)'.
Fix Windows Vista App Crash
For more details, see Cannot connect to background service.
Out of memory error
One extremely common reason for the 'unable to connect to the backup engine' messages is that the backup engine is running out of memory. This is visible in the service.log ('OutOfMemoryError') as shown below. See Code42 app does not run for complete details.
Client cache issues
Client cache issues can manifest themselves in a few different ways, including: some or all files missing from the Restore tab, stopped backups, incorrect reports, and incorrect file selection size.
Real-time file watching problems
Real-time file watching can have issues that manifest slightly differently on Mac and Linux. For more information, see Understand and troubleshoot backup issues with Mac file watching services and Linux real-time file watching errors.
Mac:
- (Code42 app version 6.9.2 and earlier) Spotlight file watcher:
- (Code42 app version 6.9.4 and later) File System Events file watcher:
![Mac app crash logs 2019 Mac app crash logs 2019](https://www.maketecheasier.com/assets/uploads/2018/02/how-to-read-crash-reports-2.png)
Mac App Crash Log
Linux:
I was using iTunes and I was also testing speakers for my desktop PC. After I connected my computer speakers I opened iTunes to test the speakers for sound quality. I went into my computer's settings for the sound. I clicked on 'disable speakers' and then iTunes automatically quit and a folder was created onto my desktop named 'iTunes Crash Logs' so I re-enabled my computer speakers and then re-opened iTunes and iTunes opened so I played a few songs from my playlist and they played.
null-OTHER, Windows 7
Posted on