guygg

I'm getting the exact same notifications over and over every time the cron runs. Doesn't matter if syslog is on or off in the plug-in settings. I've scoured through all the settings I can find and so far haven't found anything relevant. Any luck figuring out how to get these to stop sending over and over?

If you're referring to auto fan control, same problem for me. Was working fine on 6.13 builds, but fans are just running at full at all times with v7 RC2.

Working well for me. Thanks for the update and the work on the container.

Gizmotoy how do you go back to history? I have two tower destinations which are marked as "offline" in the restore tab in the new crashplan container. I have had to start backups all over in the past.I do not want to do it a third time.I can see my backup destination files on the tower. What config is crashplan looking for? If I restore my old v5.5 unraid flash on a vm,can I restore my crashplan plugin config?What should the path be? It sounds like you started a new device previously rather than using the "adopt" option. If you adopt, it should not create another device. If the paths to the data being backed up hasn't changed, it should just go through a process where it compares block information and looks like it's backing up stuff again but is really just flying through all the comparisons at an extremely higher rate. As such, all the previous version stuff would be retained and things would continue on. IF the paths to the data being backed up is different, the one key thing to note is that you want to leave the previous paths (that will be noted as "Missing" in the backup area of the UI) if you wish to retain the old versions of stuff. So, you would have the old path marked as missing and the new path that shows the active amount of stuff being backed up. It'll still do the block-level comparing and only re-upload all the changes, so it won't be re-backing up everything again. Incidentally, the proper time to do the adopt step is when you first sign into the app after re-install. At the top, it should have an option to click to adopt a previous computer backup. Just pick the previous instance and you're good.

Yeah, I stopped using the RDP client, as the version conflict was causing very undesirable issues. Since the engine had auto-updated to 4.2, I continued using the also-4.2 application on my Windows machine to connect to the Docker-based engine just as I had done back when running Crashplan headless in the v5-and-earlier days. Crashplan apparently does NOT play well with version mismatches between engine and application. It would be mighty nice if the devs at Code 42 would have some version intelligence between the two components so that in instances where they are NOT in sync, it wouldn't just go ahead and happily do things that break everything... So, what's the upshot of the Docker modules at this point? Are both the engine and application now up to 4.2? Will both of them forcibly prevent in-app updates? Or are we gonna get hit by the same problem again? Not trying to sound like a complainer. I know this kinda thing is tough on people trying to get these nifty new Docker modules operational. A bit of a teething period to go through.

Well, supposed to or not, my CrashPlan engine Docker managed to get itself up to 4.2 somehow... DateTime = Thu Jun 18 17:16:34 CDT 2015 OS = Linux (4.0.4-unRAID, amd64) JVM = Java SE Runtime Environment (1.7.0_72-b14, 64-bit) Locale = English, America/Chicago User = root, /root Application = CrashPlan CPVERSION = 4.2.0 - 1425276000420 (2015-03-02T06:00:00:420+0000) - Build: 61

Any resolution to this. I just upgraded from unRAID v5 to a clean unRAID v6. I had CrashPlan running headless on it previously (using the SSH tunnel from a Windows machine to manage). I installed the Crashplan service and GUI Dockers. I went in and adopted my machine and let it start comparing and resynching and ran into the same Cryptography errors making it start to re-upload everything again (not even sure if it's successfully even doing that). CrashPlan support told me to check for a version mismatch between the service and GUI, which is the most common cause for that. Sure enough, the GUI is on 3.7 and the services is on 4.2. Competely screws up the functionality, and I didn't change or update anything other than install the two Docker modules. Being a bit new to the whole Docker approach, how in the world does the updating of the CrashPlan engine and GUI apps work in these things? Clearly, they're not updating at the same time, and that's causing a real headache. I'm not sure what to do at this point, as CrashPlan's suggestion is to uninstall and reinstall and make sure the Engine and GUI are on the 4.2 version. I'm not even sure how I'm supposed to accomplish that now... Thanks