Michael_P

It is an odd issue, for sure. It's running fine now in the new folder, so thank you for your help!

Using appdata does not work, but using my new "app" folder does. There must be a permissions problem with my appdata folder. I'm happy to leave it run in the new folder since it's working there but if you know which permissions should be assigned to appdata manually, I would appreciate the knowledge

As far as I know. One of my troubleshooting steps was to delete and re-create the appdata share

OK, following your lead - I tried to re-create the folder in appdata a few times, without success - service wouldn't restart. SO, I created a new share to stuff the container into, and it works - so something is wrong with my appdata folder.

OK, I've done that - added a new device and stopped and started the container and it restarts properly

How do I do that?

No disk errors noted (just a random IRQ 16 nobody cares that I haven't gotten around to addressing) - I have Fix Common Problems installed, only lists the IRQ16 problem

Well that's a downer, what do you suggest?

Looks like you have found the solution! I removed the config directory, applied the setting which automatically restarted the container - I logged in, created a new device, set the destination and restarted the container - the service started normally. Hooray! I will now try to take over the old device or just re-upload the data and report back the results. Thank you very much for your assistance!

Output in order: CP_1.txt CP_2.txt CP_3.txt CP_4.txt

Here's the output Docker_Find.txt

I'm running version 6.5.1 and installing via the Community Application plugin There is no crashplan folder in /usr/local - only: bin/ emhttp/ etc/ lib/ lib64/ sbin/ src/

This error keeps showing up in the logs, probably why it's failing: 2018/05/23-12:31:05.285880 14e5665f8700 Level-0 table #5: 247 bytes IO error: /usr/local/crashplan/conf/udb/000005.ldb: No such device SEVERE: Service UniversalStorageService [FAILED] has failed in the STARTING state. java.io.IOException: IO error: /usr/local/crashplan/conf/udb/000005.ldb: No such device

Yes, I set up the "new" device but did not add any files to the backup set - then I restart the container and the service fails to start until appdata is deleted again Tried a new account, same issue

yes, tried that too - if I stop the container, it will not start the service again, I have to delete appdata to get it to run again. Similar to francrouge's problem and my logs show the same error:

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