AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Crashplan crashing2/24/2023 ![]() ![]() I actually thought ls crashed.)Įach and every file seems to have been created when the CrashPlan Engine restarts. (I’m not kidding, I started a new SSH session to kill ls the first time I tried to list the directory because it was Taking. In the configuration directory, I found a bunch of restart.log files while hunting for the file which defined the memory limits. I raised the memory limit to 1.5GB, and Java’s only using 932MB, so there’s some headroom for growth if necessary. OutOfMemoryError occurred.RESTARTING! message=OutOfMemoryError in BackupQueue!īecause the file set changes very irregularly, once it starts crashing, it’ll continue to crash until you intervene and manually raise the memory limit. It seems that beyond a certain number of files, Java hits the hard memory limit and dies: I’d periodically go in via VNC and check up, and the desktop interface reported everything was just fine.Įxcept it wasn’t. I quite enjoyed this because my media server is headless, so set-it-up-and-forget-it backups were awesome. ![]() I’ve been getting weekly reports on my backups since I installed it. However, the hard limit led me to another problem: 2. I’m not the only guy who’s noticed this: One guy has it hitting 1.5GB of RAM. It’d regularly hit the max, but it didn’t seem to have problems, so I chalked it up to the use of Java and left it at that. I have it running on my media server, which has been specced with 1GB of RAM. This is a hard limit imposed on the Java VM when it runs. Ridiculously so.īy default it’s setup to use a maximum of 256MB of RAM. ![]() I went looking for what could cause it to start & stop with such regularly, and found the first problem: 1. I've also since upgraded to a significantly bigger NAS, so the workaround won't work anymore.Spoiler: It was dying and being restarted by a watchdog of some sort. With Windows, I had mirrored an older NAS onto my main computer's hard drive, which worked well enough, but it was always a workaround for what I really wanted to do, i.e. I switched CrashPlan to Mac in order to implement a cleaner solution for backing up my NAS. I am decently proficient with the Mac from a number of years working in an all-Mac office, but I left that company during the Mountain Lion era, and don't use Mac at home otherwise, so it's been a while since I've regularly used a Mac. I know my way around CrashPlan pretty well, having used it for nearly ten years on Windows. I've googled around on this, and I'm not finding any solution to this issue. the dock icon is not lit up, and the menu bar icon is gone. ![]() I'll start the service, it will run for a while, and then when I come back a few hours later to check on it, the service is completely closed, i.e. I got it all set up, and already got over a problem that required that I clear the cache in order to get it to actually read the files.īeing past that, my current problem is that CrashPlan keeps on crashing while trying to do its thing, in this case, scanning my backup selection. I bought the Mac Mini as a refurbished item on Amazon for $200 specifically to run backups, and I administer it by remote. I use CrashPlan on a Mac Mini (MGEN2LL/A) in order to back up a Western Digital NAS. ![]()
0 Comments
Read More
Leave a Reply. |