SOLVED CrashPlan Plugin Won't Start

[SweetAndLow]

You link refers to changing the memory allocation on the client, not the server.

Derek, can you expand a bit on whether you are backing to or from FreeNAS? And, did you change the memory allocation to the FreeNAS plugin or to another computer?

Thank you.

- nello

So that link he posted is actually changing the server memory size.

In the crashplan jail if you go to /usr/loca/share/crashplan/bin/ and look at the run.conf file you will see SRV_JAVA_OPTS and in that line there is a -Xmx1024 flag, if you make the modification from the link(crashplan documentation) that number is going to change. In the same file there is also GUI_JAVA_OPTS which are the options for the gui, you can ignore that because you don't use the gui in freenas.

 

[joerawr]

I received a notice email from Crashplan that my freenas was not backing up, and sure enough, the run.conf changed again a few days ago. version 3.6.3_1. Re-Applied the fix. BTW, I only had to restart the crashplan jail.

Derek,

It would be helpful to know how big is your target backup set? It'd be nice to know roughly when the default 1024 is too small. Thanks for following up on the thread.

 

[nello]

So that link he posted is actually changing the server memory size.

Yes. And changing the FreeNAS (server) memory size is relevant only if you are backing up from FreeNAS to another device. For people (like me) who are backing up computers to FreeNAS (server), it is not relevant.

 

[Derek Dysart]

It would be helpful to know how big is your target backup set? It'd be nice to know roughly when the default 1024 is too small. Thanks for following up on the thread.

Mine just completed at 1.2TB

 

[Allan_Guy]

Hi Nello, I think I have crashplan fully working on the nas plugin. I did not put in 0.0.0.0 as some recommended, it is still on 127.0.0.1. I'm having trouble connecting windows after modifying the in the UI file to connect to it. I think I need to setup a tunnel. How'd you set yours up?

Thanks,
Allan

 

[nello]

Hi Nello, I think I have crashplan fully working on the nas plugin. I did not put in 0.0.0.0 as some recommended, it is still on 127.0.0.1. I'm having trouble connecting windows after modifying the in the UI file to connect to it. I think I need to setup a tunnel. How'd you set yours up?

Thanks,
Allan

I'm sorry, but I don't understand your question.

I followed the Code42 Tutorial. What are you using as a guide?

 

[Allan_Guy]

I read somewhere about editing /usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml and changing service host from 127.0.0.1 to 0.0.0.0. Wondering if you had to do this or not? Sorry to be so vague the first time? I tried it both ways and I still get the error in Windows Crashplan software "Unable to connect, check your network" I'm at the end of my rope on this software! I've read and googled and read for 3 days to no avail... The software and Jail on the NAS side seems to be giving me all the same results that others have when it is working. I just cannot get passed the Windows software side to connect. I've done ssh enable, port forward, -Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider, and /usr/bin/cpuset -l 0 /usr/local/share/crashplan/bin/CrashPlanEngine restart

ee /usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<config id="service" modified="2015-03-06T13:44:15:846-0800" version="6">
<configDateMs nil="true"/>
<installVersion>1388556100363</installVersion>
<logPropertiesFile>conf/my.log.properties</logPropertiesFile>
<serviceLog>
<fileHandler append="true" count="2" level="ALL" limit="26214400" pattern="log/service.log"/>
</serviceLog>
<serviceErrorInterval>3600000</serviceErrorInterval>
<historyLog>
<fileHandler append="true" count="10" level="ALL" limit="512000" pattern="/usr/pbi/crashplan-amd64/share/crashplan/log/history.l
</historyLog>
<userIdleDelay>900000</userIdleDelay>
<orgType>CONSUMER</orgType>
<systrayOnStartup>true</systrayOnStartup>
<location>0.0.0.0:4242</location>
<helpNovice>STILL_RUNNING</helpNovice>
<userHome>C:\Users\Al</userHome>
<windowsPriorityClass>NORMAL</windowsPriorityClass>
<windowsPriorityBoost>false</windowsPriorityBoost>
<macIOPriority>IOPOL_THROTTLE</macIOPriority>
<javaMemoryHeapMax>1024m</javaMemoryHeapMax>
<serviceUIConfig>
<serviceHost>0.0.0.0</serviceHost>
<servicePort>4243</servicePort>
<connectCheck>0</connectCheck>
<showFullFilePath>false</showFullFilePath>
<autoLoginPasswordHash nil="true"/>
<autoLogin>true</autoLogin>
<locale nil="true"/>
</serviceUIConfig>
<servicePeerConfig>
<authority address="central.crashplan.com:443" hideAddress="false"/>
<lastKnownVersion>1388728800370</lastKnownVersion>
<upgradeVersion nil="true"/>
<upgradePath>upgrade</upgradePath>
<upgradeDelay>15000</upgradeDelay>
<inboundWorkers>4</inboundWorkers>
<securityProviderWorkers>1</securityProviderWorkers>
<securityProviderCipherId>0</securityProviderCipherId>
<socketSendBufferSize>-1</socketSendBufferSize>
<socketReceiveBufferSize>-1</socketReceiveBufferSize>
<inboundMessageBufferSize>2097152</inboundMessageBufferSize>

 

[nello]

Sorry to be so vague the first time?

No, I did NOT update any XML files.

I recommend that you delete your Jail and start over.

 

[Allan_Guy]

Thanks Nello,

I gave up and just created a batch file to map the drive and used an at login task to run as system so the mapped drive shows up in crashplan. I have seen my torrents hit almost 10Mbps uploading, crashplan runs between 2.5 - 4Mbps. It is going to take a month or so to get my backups done! :) What do you want for near free I guess... Now with mythtv, is it worth getting it to work on the NAS or should I use an older quad AMD with 8gb ram to run mythbuntu? The Mythtv package is just the backend right? How is it working for you, do you have a ceton or an hdhomerun or something else? I have the ceton 6 turner eth, I'm running it in a non-pooled non-beta drivers and it drops out of media center on win7 about every couple days. I'm going to try the beta drivers and pooled mode and see if it works more consistently.

Thanks again,
Allan

 

[nello]

Now with mythtv …

This thread is about CrashPlan.

If you want to talk about MythTV, please find another thread or start a new topic.

 

[Allan_Guy]

https://forums.freenas.org/index.php?threads/mythtv-vs-mythbuntu.28262/

 

[nello]

I would also like to add this has been fixed with the most recent version of the port. So whenever the PBI gets updated with the latest port this issue shouldn't happen with future Crashplan updates.

Has this bug fix has been incorporated into the plugin. In other words, if I start from scratch, removing the plugin and then re-installing it, will the plugin automatically update itself? Through what version? (The current version on my client is 4.5.2)

I'm asking because CrashPlan on my FreeNAS is stuck at 4.3.3 and Code42 tech support recommends that I "
… try uninstalling and reinstalling with the latest version? In a standard uninstall, CrashPlan retains a small amount of information (including your computer's identity) so CrashPlan can “remember” your computer."

 

[diskdiddler]

This crashplan thing has become a mess. I stopped trying to fix it, waiting for someone else to writeup a definitive guide.
Installing a copy of crashplan 4.3.3, hoping to quickly connect to my server, which will prompt it to upgrade (apparently) was a nightmare, because the local windows client auto updated far too quickly.

As it stands, I can't manipulate the data I've selected to backup, but I fortunately had a fairly reasonable default root selection on my drive to backup, so it's still working but I literally can't change what's backed up. It's pretty poor