Michael_P

Yes, tried that too

Output attached Docker.txt

Yes, I even tried creating it on directly on the array instead of the cache drive

Still pulling my hair out over this, it's the last step for this server build and it just isn't working [CrashPlanEngine] starting... [CrashPlanEngine] starting... [CrashPlanEngine] starting... [CrashPlanEngine] starting... [CrashPlanEngine] starting... [CrashPlanEngine] starting... [CrashPlanEngine] starting... [CrashPlanEngine] starting...

I removed the container, deleted the entire appdata share, re-created the appdata share, re-installed the container, same issue. It's cursed.

I didn't send them any files, just described the issue in the trouble ticket (only mentioned the errors, and that it was a Linux OS). He said his "tools" show the device is running unraid and they don't support it. I've tried removing and re-installing the container, deleting the CrashPlanPRO folder in appdata before re-installing the container. I've tried changing the password in CrashPlan just to make sure it wasn't a weird character. I've tried the defaults, i've tried allocating more memory (32G at one point), i've tried different network settings. No matter what i've tried, it won't start again if it stop the container. The log mentions a 000005.ldb file it can't find, is that significant as the only ldb file I can find is a 000003.ldb? Do you think it's permissions related?

Well they weren't able to help, their "tool" already knew I was running it under unraid so their suggestion is to use a supported OS..

I've tried everything I can think of and I just can't make it run again after restarting the container.

If I attempt to take over an existing device (the old container's backups), it asks me to re-enter my credentials, which fails to the unable to sign in unknown error message. If I restart the container it loops crashplan engine starting and the webui says unable to connect to engine. If i delete the appdata CrashPlanPRO folder, it will start and ask to setup again - if I choose to add a new device, it completes the backup and is OK until the container is restarted which loops the crashplan engine starting message in the log and the unable to connect to engine in the UI

Same result, attempting to take over another device ends up with the second login prompt which ends in "unable to sign in unknown error" - restarting the container just loops the crashplan engine starting

Yes, the only way to get it to service start is to remove it, delete the CrashPlanPRO folder in appdata then re-install. Then, if the container is stopped and re-started it gets stuck in the loop again.

Here's the logs Service Logs.zip

Hello! I've gone and mucked something up and I hope you can help. I originally had a WHS 2011 box backed up with CrashPlan Home, I've since built a new server using Unraid and migrated to CrashPlan Pro via the docker app and adopted the WHS 2011 backup successfully. It was working fine for a month, no troubles. However, in building my VM to host the WHS 2011 server so my windows clients can continue to backup to it, I had to move some of the vdisks around to better make use of my cache drive. To do that, I needed to bring down the array and thus the dockers - I moved the vdisks successfully and re-started the array, however the CrashPlan docker container did not come back up. I monkeyed with it a bit, and decided it was best to just delete the container and re-install. This worked and the webgui came to life and asked for my user id and password, then mentioned that it was a new device (because I deleted the files in the appdirectory) and if I'd like to replace a device, which I did. However, after skipping the file transfer portion of the process it begins to transfer settings at which point it asks for the user credentials again - that part fails with the message "Unable to sign in. Unknown error." If I try to restart the container, the service will no longer start and just sits in a crashplan service starting loop (according to the log). I do notice that Cod42 has mentioned changes on their website, so it may be on their end and I'm chasing my tail, but any help is appreciated!