Been prompted to update the crash plan docker container today. Is this safe too do so? Will it remove the ability too run CP as it's running headless?

Updated to the new Docker 2.0 version with the 6.6.0 Crashplan

- Required my email/pass to login

- Worked smooth, continued on backing up

- GUI is all new... and terrible.  But that's Crashplan's fault, not Djoss's! 

 

5 minutes ago, benswinney said:

Been prompted to update the crash plan docker container today. Is this safe too do so? Will it remove the ability too run CP as it's running headless?

 

Don't worry, the headless thing Code42 is talking about is the one described here:

https://support.code42.com/CrashPlan/4/Configuring/Use_CrashPlan_on_a_headless_computer

 

Inside the container, from CP point of view, it's running like on a standard desktop.

 I got upgraded to the new crashplan container, and now it tells me that I am unable to sign in due to an unknown error.   I am able to sign into my account on the crashplan site.  Any recommendations?

Did you try multiple times ? I know that when you start from scratch, you got an error. But just sign in again and it’s working.

8 minutes ago, Djoss said:

Did you try multiple times ? I know that when you start from scratch, you got an error. But just sign in again and it’s working.

I've been trying it repeatedly.  Also restarted the docker a few times.

When you said that you upgraded, were you running the same image before or a different one?

Just now, Djoss said:

When you said that you upgraded, were you running the same image before or a different one?

The crashplan pro docker was updated by my autoupdate.  I did not install a new container, it just updated the one already installed.

Does it takes a long time before showing up the error message?

Can you provide service.log.0, located in /config/log/?  I can check if there is anything obvious.

8 minutes ago, Djoss said:

Does it takes a long time before showing up the error message?

Can you provide service.log.0, located in /config/log/?  I can check if there is anything obvious.

It takes 5-10 seconds after clicking login before it gives the error

service.log.zip

Well, the docker auto-updated itself. The new CrashPlan version looks like a really bad cross between a poor website and a local app.

 

I found the "History", and this line is in it:

"12/09/17 12:22 AM    CrashPlan for Small Business started, version 6.6.0, GUID <snip>"

so I guess I'm on the latest version, and it seems to be running.

 

Going to take a bit of time to figure out the new interface design, but my first reaction is... meh.

1 hour ago, lordbob75 said:

It takes 5-10 seconds after clicking login before it gives the error

service.log.zip

 

I didn't find anything useful

If you want, you can try to open a support ticket with Code42.  When creating the ticket, upload your logs at the same time: shit+ctrl+c and then run the command "getlogs".  You will get the path to the compressed logs.

The other option is to start with an empty app data folder.  You should be able to sign in without problem.  When you sign in, select the option to replace a device and then skip the file transfert.  You should be able to be up and running again without having to re-upload your data.

2 hours ago, Djoss said:

 

I didn't find anything useful

If you want, you can try to open a support ticket with Code42.  When creating the ticket, upload your logs at the same time: shit+ctrl+c and then run the command "getlogs".  You will get the path to the compressed logs.

The other option is to start with an empty app data folder.  You should be able to sign in without problem.  When you sign in, select the option to replace a device and then skip the file transfert.  You should be able to be up and running again without having to re-upload your data.

I appreciate the look anyways.  I'll try clearing the appdata (after I back it up) and then if that doesn't work I'll contact code42.

 

Thanks!

Good, let me know how it went!

Just now, Djoss said:

Good, let me know how it went!

Hey forgot to reply earlier.  I deleted the appdata folder for crashplan in appdata and restarted it.  Works fine now, although it's still syncing up so I haven't actually been able to continue yet.

I updated the docker without any issues today, just had to sign it and away it went. The new interface is terrible...but so far it's working. 

I updated to newest version of this docker and after updating I am getting a can`t login error after 15 seconds. I have attempted to login repeatedly with same error. 

 

UPDATE:  I stopped the Crashplan Pro docker and then started it again. After that I was able to login without an issue. Just an FYI for anyone experiencing the same issue. 

Updated- first log in attempt seemed to hang. So I stopped and restarted the docker.

 

2nd, 3rd, and 4th attempts gave me a blank white screen with a "could not connect to server error."

 

Retarted this time and got the login prompt again. Logged in and the program began syncing the files again. Hopefully everything will go well without a need to reupload.

 

Posting this just to doc my experiences, will update if there are any issues

 

 

 

 

EDIT - So after it synced the files the total size was significantly less than previously. I had no compression selected before, so Im wondering if they are forcing compression now on their side of things? It seems like all of my folders are still correctly selected, so I'm not sure what might have changed (1.7TB ->.5TB)

 

EDIT2 - I may have missed it, but looking deeper into the options it would seem that we no longer have the option to change the compression size of our backups. 

Edited December 12, 20178 yr by ryoko227

@Djoss another legacy Crashplan docker user, now on Pro Docker due to the autoupdating into a black screen.  No problems updating nor adding in the memory.  Thanks!

Edited December 16, 20178 yr by landS

Today I'm unable to vnc into the crashplan container.  Getting a "Server Disconnected: Code 1006" error.  Restarting has no effect.  Will be attempting a server reboot, but that's not something I want to have to do to fix this.

 

Edit: Reboot did not help.  Will be rebuilding the flash drive tomorrow, perhaps that will fix it.

Edited December 16, 20178 yr by lordbob75

Oh boy... woke up this morning, all directories still selected, but now web ui says files are missing and zero size... and crashplan's website also indicates zero files available for backup.  bummer

 

my docker's storage location is /mnt/user and i have a few share's selected in crashplan for backup.  it just... isn't recognizing any subfolders/files in these shares. 

 

Given that all the files disappeared from backup from the online portal, I deleted the appdata, restarted fresh.  Still, no joy. 

 

FYI, the online portal restore/'show deleted' indicates the paths in light grey for yesterday and today... but they are not backing up.  grr

Edited December 16, 20178 yr by landS

9 hours ago, lordbob75 said:

Today I'm unable to vnc into the crashplan container.  Getting a "Server Disconnected: Code 1006" error.  Restarting has no effect.  Will be attempting a server reboot, but that's not something I want to have to do to fix this.

 

Edit: Reboot did not help.  Will be rebuilding the flash drive tomorrow, perhaps that will fix it.

 

Can you provide  the container's log?

3 hours ago, landS said:

Oh boy... woke up this morning, all directories still selected, but now web ui says files are missing and zero size... and crashplan's website also indicates zero files available for backup.  bummer

 

my docker's storage location is /mnt/user and i have a few share's selected in crashplan for backup.  it just... isn't recognizing any subfolders/files in these shares. 

 

Given that all the files disappeared from backup from the online portal, I deleted the appdata, restarted fresh.  Still, no joy. 

 

FYI, the online portal restore/'show deleted' indicates the paths in light grey for yesterday and today... but they are not backing up.  grr

If your files are marked as "missing", it's basically because their location is not the same between the 2 containers.  Just re-select your files, they are under /storage.

Because of de-duplication, they should not be re-uploaded.

2 minutes ago, Djoss said:

 

Can you provide  the container's log?

How do I get those?  If I still have them I will post, but working on rebuilding the usb drive right now.

On the docker page, there is an icon at the right of each container, under the “log” column.