Jump to content

Crashplan GUI worked once, now will not launch


wisem2540

Recommended Posts

Posted

Ive posted about this before, and i apologize in advance for posting again but crashplan is about to drive me INSANE.  Magically, after many uninstalls, CP GUI finally launched.  I adpoted unraid and allowed it to start syncing. 

 

I then shut off the VM and waited.  After deciding to check it, I powered up the VM and crashplan will not launch...AGAIN.  Now I have no idea whats going on with my 5TB backup.  Im hoping someone knows what to do.

Posted

Here are 2 entries in the CP Desktop log

 

 

sed: can't read /var/lib/crashplan/.ui_info: No such file or directory

cp: cannot stat ‘/root/wallpapers/*’: No such file or directory

Posted

I apologize, yes I am using the docker.  I have had problems getting the CP GUI to launch since the beginning.  It will literally just do nothing.  No error, no nothing.  Magically, it started to work, so I configured CP and adopted the unraid box.  Then it stopped again.

Posted

So you have the CrashPlan Desktop container and the CrashPlan container installed on your server and it just don’t work any longer but it has been not too long ago?

 

First I would check that the configuration files for the CrashPlan container still are located where they should be. My mappings for these are /mnt/user/appdata/Crashplan (also see the pic). Yours might be different depending on what you have set on your system depending on if you have the files on a cache drive or on the array. Have a look on next pic to see how it would look like. You can also have a look on the history.log file in the log folder (and take the one with latest modified date) to see if the if the backup is running or when it stopped.

 

If the files that should have been in the CrashPlan folder isn’t there it might be that you are using a cache drive and haven’t set the appdata share to Use cache disk: Only. Then they have been moved to the array.

 

If the above looks ok, go to the Docker tab (in the unRAID GUI), switch to Advanced View and click on force update for the CrashPlan container. Wait a minute and do the same for the CrashPlan Desktop Container. This should make sure that both containers are updated to latest version.

 

Try to connect with Remote Desktop to CrashPlan Desktop Container and see if it works or not.

 

If not, edit the CrashPlan container so you can see the settings and enable Advanced View, take a screen shot from the row with Name: CrashPlan down to the top of Additional fields. Do the same with CrashPlan Desktop Container and post the result.

CrashPlan_mappings.png.d0aaaed391afc1224254b6e388deda26.png

appdata.png.4a23eb8b721afa7712bdf822b5023603.png

Posted

Let me try to be a bit more clear.  I had been trying to get this docker working for sometime, and I could not.  So I abandoned it.  Last night, out of nowhere, the GUI finally opened for me and I adopted unraid.  I shut down CP GUI and turned it back on a few hours later, and I am back in the same situation.  Now I have no control over my backup.

unraid.jpg.df6aa8ce48279875a920fdaaf4993a7d.jpg

Posted

Ok thanks. So how far does it get? Does the CrashPlan splash screen open at all or does it open and tells you it can’t connect?

BTW, when you say Ubuntu VM most people here assumes that you have a VM with a full Ubuntu desktop installed, not a Docker container (at least I do that since that is what I have...)

Posted

Understand.  Sorry for the confusion.  No, the crashplan app does not launch at all.  Except of course the one random time that it decided to work.  I have removed the container several times and reloaded it with no success.  I do see the 2 errors in the log that I posted earlier.

 

sed: can't read /var/lib/crashplan/.ui_info: No such file or directory

cp: cannot stat ‘/root/wallpapers/*’: No such file or directory

 

These are in the Crashplan-Desktop Log

 

 

Posted

Don’t worry about the wallpaper stuff, has nothing to do with CrashPlan.

 

Check that your CrashPlan Desktop settings are as the enclosed pic, especially the Extra Parameters.

CrashPlan_Desktop_settings.png.456c157b188270f8cdf292b401903e62.png

Posted

holy crap...out of habit, I had a /config directory mapped for CP-Desktop.  I removed that  and the app launched.  But now its telling me that it cannot connect to the backup engine....  So we are getting somewhere.

Posted

I thought for a second that maybe CP was out of memory.  I remember having to increase it when I used it on windows.  But, I cannot find the log for proof, and I restarted Crashplan, and it shouldnt run out of memory immediately.  So, Im not sure that is it.

Posted

Nope, don’t think it’s the memory but can’t be sure! Have you changed the memory settings or is it as standard?

 

I have had memory problems in the past but that usually happens when CrashPlan does it maintenance and rescan every file, during normal backup nothing happen.

 

We could try to play with it? How much data do you have in your backup set?

 

The file

run.conf 

with the memory settings is located in the

bin 

folder. Use a Linux text editor like NotePad++ or similar (not Windows Note Pad) and edit the first line that looks like this:

SRV_JAVA_OPTS="-Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m [b]-Xmx1024m[/b] -Dsun.net.inetaddr.ttl=300 –D

……

[b]-Xmx1024m[/b] 

is 1 GByte (the default) and should be enough for around 1 TByte of data, I believe that I changed my settings to

[b]-Xmx6144m[/b]

(enough for 6 TByte data).

 

Save the changes and restart the CrashPlan Container.

Posted

So the CP log was pretty clear that it was out of memory.  I changed it to 6GB, since I have close to a 5TB dataset.  Its definitely happier now, based on the log, but the CP GUI still says unable to connect.

Posted

I finally started from scratch, combining everything I learned here.  Its finally working as expected, I think.  Truthfully, I think, in the end, I may have neglected to restart CP Desktop after making the config file changes.  Either way, all is well, and I owe you a beer.  Let me know where to send :)

 

On a side note, with this same backup set running on a windows box, it ran fine with 1.5GB allocated to memory.  Now its using a TON.  I will definitely have to invest in a memory upgrade now.

Posted

Happy to hear you got it going again! I am working on a new version on my setup guide so this little exercise will be used to improve the trouble shooting section.

 

The memory settings it just there to limit the max usage, CrashPlan only allocates more memory when it needs but it’s for sure a good excuse to get some more  ;)

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...