SolutionĪllocate more memory to CrashPlan. When the CrashPlan engine is running out of memory it crashes. The CrashPlan engine won’t use more memory than that, even if the CrashPlan engine needs more working memory and the computer has memory available. The CrashPlan engine by default is limited to 512MB of main memory. In one of the CrashPlan service.log.# log files will appear "OutOfMemoryError" messages, like: ERROR QPub-BackupMgr ] OutOfMemoryError occurred.RESTARTING! message=OutOfMemoryError in BackupQueue! ERROR QPub-BackupMgr ] OutOfMemoryError occurred.RESTARTING! oomStack=: Java heap space Cause In the Windows System Event Viewer you may see this message repeatedly: Event Type: Informationĭescription: The CrashPlan Backup Service service entered the stopped state. When starting and stopping in the CrashPlan application its History tab, you may repeatedly see CrashPlan stopped and started: CrashPlan log file service.log.0 will show: : Unable to load library 'cpnative64': The specified module could not be found. When the UI is crashing no error message will show up in the Windows event log. After launching the Crashplan GUI, itwill run for a little bit, hang and then finally crash. Or the main CrashPlan program will run for about 30 seconds then close down with no error message. You may also see the CrashPlan version 2010 application and System Tray icon disappearing in the middle of a backup. This can be noticed by continuous stopping and starting. In some cases a large file selection (>1TiB or 1 million files) can cause CrashPlan to crash.
0 Comments
Leave a Reply. |