General NAS-Central Forums

Welcome to the NAS community
It is currently Mon Oct 23, 2017 6:20 am

All times are UTC




Post new topic Reply to topic  [ 113 posts ]  Go to page Previous  1 ... 3, 4, 5, 6, 7, 8  Next
Author Message
PostPosted: Mon Oct 27, 2014 8:34 pm 
Offline

Joined: Thu Jan 30, 2014 11:38 am
Posts: 35
Thank you, normsland! I noticed today that Crashplan wasn't running anymore and found the "suspicious" upgrade folder.
With your upgrade-steps it worked and Crashplan is running again! :)


Top
 Profile  
 
PostPosted: Fri Oct 31, 2014 10:12 pm 
Offline

Joined: Thu Aug 14, 2014 7:02 am
Posts: 6
Hi,

I've got an issue also after trying to upgrade.
For all I know this is my own fault, as I hadn't read the full text of your post before executing it.
This meant that when I got several of the BusyBox/ps errors I "paniced" and terminated the execution.

Then, after reading the entire post I tried following the described steps a second time.
This of cource failed (due to my not very good linux knowledge) since I also did the "sed" steps a second time.
The error messages I then got caused me to correct a few lines in the upgrade script where I now had commands starting with /ffp/ffp that I changed back to one "ffp".

But when running it again crashplan don't work. It still gives error messages about "could not find JAR file..." which is the same as before trying to upgrade.

When looking in the upgrade.log (I also saw this when running the upgrade script) there is a lot of error messages regarding the "mv" command, stating "mv: invalid option -- 'v'.
The command in the upgrade.sh script is "MV="/ffp/bin/mv -fv"

Any suggestions on how to proceed?
Should I trash the installation, and start from scratch (if so - any tips on how to remove/uninstall?)
Or is there any tips that can help me correct my current installation?

Thanks,
Øystein


Top
 Profile  
 
PostPosted: Mon Nov 03, 2014 10:03 pm 
Offline

Joined: Thu Aug 14, 2014 7:02 am
Posts: 6
Hi again,

I looked further in the upgrade log, and in the last part I believe I found the real issue for my problems.
"Could not find JAR file /ffp/crashplan/bin/../lib/com.backup42.desktop.jar"

And after reading through the posts from the last crashplan upgrade in this tread I expect that I've found the reason for my problems, namely that I panicked the first time I ran the upgrade script, and when I ran it the second time I deleted several critical files.

From what I understand I'm now best off by uninstalling and reinstalling from scratch.
And I found also a link to the uninstall & reinstall procedures at Code42's website.

So - next time I hope I'll read the whole text before starting the upgrade.

Øystein :-)


Top
 Profile  
 
PostPosted: Sun Jan 11, 2015 2:07 pm 
Offline

Joined: Sun Mar 31, 2013 10:07 am
Posts: 68
Looks like Crashplan have updated to version 3.7.0. Please follow the update procedure in post #2 to get you back up and running :)


Top
 Profile  
 
PostPosted: Mon Jan 12, 2015 12:00 pm 
Offline

Joined: Mon Jan 12, 2015 11:26 am
Posts: 1
Thank you for your quick updates and continuous help, normsland !

I followed the steps in your second post and it worked great. The update itself took around 3:30 min and then there was high cpu usage from java for another about 2 minutes.

The first time I tried to connect, it wouldn't work. Then I realized that maybe I have to update the app on my desktop too. After updating to version 3.7.0 on my desktop, it connected right away. I just thought to mention this, so that others will keep it in mind.


Top
 Profile  
 
PostPosted: Sun May 17, 2015 9:32 am 
Offline

Joined: Sun Mar 31, 2013 10:07 am
Posts: 68
Crashplan upgrade to version 4.2.0. Please follow the update procedure in post #2 to get you back up and running :)

Also noticed in version 4.2.0 that the .identity file had changed and they'd added a line for offlinePasswordHash. So I've added a step to copy across the identity file after upgrade because I had to rekey in my password after reboot. Let me know how you get along.


Top
 Profile  
 
PostPosted: Fri Jun 26, 2015 2:01 pm 
Offline

Joined: Fri Jun 26, 2015 1:52 pm
Posts: 5
If anyone else is having problems with Crashplan not updating automatically the 4.2.0 update can be downloaded from
here.
Then just unzip the .jar file and follow normslands instructions in post #2.


Top
 Profile  
 
PostPosted: Thu Jul 09, 2015 6:57 pm 
Offline

Joined: Sun Mar 31, 2013 10:07 am
Posts: 68
Unfortunately with version 4.30 Crashplan have added more steps and made it more complicated to run in headless mode. If you are upgrading you need to follow the steps in post #2. Once this has upgraded and you have checked /ffp/crashplan/log/history.log.0
Code:
I 07/09/15 06:03PM Backup scheduled to always run
I 07/09/15 06:29PM CrashPlan started, version 4.3.0, GUID <SOME NUMBER>

On your NAS you will need to copy .ui_info to /ffp/crashplan/
Code:
cp -p /var/lib/crashplan/.ui_info /ffp/crashplan/

To make sure that this is persistent after a reboot we need to edit
Code:
nano -w  /ffp/crashplan/bin/CrashPlanEngine


and add:
Code:
cp -p /ffp/crashplan/.ui_info /var/lib/crashplan/


after:
Code:
echo "Using standard startup"
cd $TARGETDIR
mkdir -p /var/lib/crashplan

Now copy the output of the following on a notepad somewhere
Code:
cat /var/lib/crashplan/.ui_info  ; echo

The command will output a line similar to the following (everyone’s will be different):
4243,13d436c0-230a-4242-b258-574e60e62a9f

Then download the Windows client from https://www.code42.com/crashplan/thankyou/. Install the Windows client as normal. Once installed change C:\Program Files\CrashPlan\conf\ui.properties to point to your NAS as per normal. An additional step is to go in to a command prompt Start menu->Enter cmd in to the search box.
Code:
del C:\ProgramData\CrashPlan\.ui_info

Now grab that copied text from notepad.
Code:
C:\>echo 4243,some-GUID > C:\ProgramData\CrashPlan\.ui_info

eg
Code:
echo 4243,13d436c0-230a-4242-b258-574e60e62a9f > C:\ProgramData\CrashPlan\.ui_info

The Windows Crashplan UI should now connect without a problem.


Last edited by normsland on Fri Jul 10, 2015 11:47 am, edited 2 times in total.

Top
 Profile  
 
PostPosted: Fri Jul 10, 2015 10:49 am 
Offline

Joined: Sat Jun 20, 2015 4:58 pm
Posts: 22
I'm downloading now, Thanks a lot :mrgreen:


Top
 Profile  
 
PostPosted: Thu Sep 24, 2015 8:01 pm 
Offline

Joined: Thu Jan 30, 2014 11:38 am
Posts: 35
Which steps have to be done for fixing the September update (it came to my NAS on September 10th)?
The same like in July?

-- edit --
It was sufficient to do the steps from the second post only.


Top
 Profile  
 
PostPosted: Sat Sep 26, 2015 10:12 am 
Offline

Joined: Sun Mar 31, 2013 10:07 am
Posts: 68
Unfortunately with version 4.4.1 the Crashplan update breaks our ffp installation. Crashplan have also tweaked the security to run in headless mode. If you are upgrading you need to follow the steps in post #2.
Now you need to replace jna.jar in /ffp/crashplan/lib/
Code:
#cd /ffp/crashplan/lib/
#mv jna.jar jna.jar.bak
#wget http://dl.dropbox.com/u/50398581/crashplan%20on%20NAS/jna-3.2.5.jar
#ln -s jna-3.2.5.jar jna.jar

Start crashplan service
Code:
# /ffp/start/crashplan.sh start

Check that it has started.
Code:
# /ffp/start/crashplan.sh status
CrashPlan Engine (pid 27620) is running.

Copy across the new updated .ui_info file
Code:
cp -p /var/lib/crashplan/.ui_info /ffp/crashplan/

Now copy the output of the following on a notepad somewhere
Code:
cat /var/lib/crashplan/.ui_info  ; echo

The command will output a line similar to the following (everyone’s will be different):
4243,13d436c0-230a-4242-b258-574e60e62a9f,0.0.0.0

Then download the Windows client from https://www.code42.com/crashplan/thankyou/. Install the Windows client as normal. Once installed change C:\Program Files\CrashPlan\conf\ui.properties to point to your NAS as per normal. An additional step is to go in to a command prompt Start menu->Enter cmd in to the search box.
Code:
del C:\ProgramData\CrashPlan\.ui_info

Now grab that copied text from notepad. Replace 0.0.0.0 with the IP-OF-YOUR-CP-SERVER
Code:
C:\>echo 4243,some-GUID,IP-OF-YOUR-CP-SERVER > C:\ProgramData\CrashPlan\.ui_info

eg
Code:
echo 4243,13d436c0-230a-4242-b258-574e60e62a9f,192.168.0.2 > C:\ProgramData\CrashPlan\.ui_info

The Windows Crashplan UI should now connect without a problem.


Last edited by normsland on Sat Nov 07, 2015 3:31 pm, edited 2 times in total.

Top
 Profile  
 
PostPosted: Mon Oct 05, 2015 5:03 am 
Offline

Joined: Mon Oct 05, 2015 4:56 am
Posts: 1
I have tried these directions...

as well as some referenced here: http://vincesoft.blogspot.ca/2011/11/ho ... omega.html

To try and get crashplan running headless on my ix2-dl.

The service starts...but I can not find .ui_info

/var/lib/crashplan/ only contains .identity (priv-key)

I am going bonkers...any suggestions?


Top
 Profile  
 
PostPosted: Mon Dec 07, 2015 7:55 pm 
Offline

Joined: Thu Jan 30, 2014 11:38 am
Posts: 35
Today I got an e-mail from Crashplan, excerpt:
Quote:
[...] Linux kernel version:

CrashPlan app version 4.5.x or later: 2.6.32 or newer and glibc 2.9+
CrashPlan app version 4.4.1 or earlier: 2.6.13 or newer and glibc 2.4+

If you have a Linux device running kernel 2.6.31 or older and are still on CrashPlan version 4.4.1, CrashPlan on this device will not upgrade to version 4.5.0. If your device is on kernel 2.6.31 or older and has already upgraded to CrashPlan version 4.5.0, CrashPlan has likely stopped working.

[...] An alternate solution to resolve this is to Uninstall CrashPlan 4.5.0, and install CrashPlan version 4.4.1, which can be found in this direct link:

https://download.crashplan.com/installs ... _Linux.tgz

Please Note: Computer-to-computer backups require both devices be on the same version of the CrashPlan app.

We've created a Support Article that explains more about this change, here:

https://support.code42.com/CrashPlan/4/ ... ot_Back_Up


Will we face some problems with our FFP installation soon?
Hopefully not!


Top
 Profile  
 
PostPosted: Mon Dec 07, 2015 9:58 pm 
Offline

Joined: Fri Jun 26, 2015 1:52 pm
Posts: 5
uname -r returns 2.6.31.8 on latest firmware V4.80(AALS.0)C0

If i understand right we won't be able to upgrade to 4.5 because of old kernel version.
Crashplan knows this and won't upgrade automatically.
Is there any way to prevent upgrades on Windows clients?


Top
 Profile  
 
PostPosted: Wed Dec 09, 2015 3:48 pm 
Offline

Joined: Thu Jan 30, 2014 11:38 am
Posts: 35
hi!

I found this workaround for preventing automatic upgrades on linux machines:
Editing the path of the upgrade directory (<upgradePath>upgrade</upgradePath> to <upgradePath>/dev/null</upgradePath>) in my.services.xml.
Source: http://nerdagentur.de/wie-die-autoupdat ... iert-wird/

But I'm not sure, whether it's also working on the windows clients (I know e.g. copy blub.doc > NUL, but what's a real /dev/null under Windows???) ... and it has to be considered that the logfiles will be full with error messages about not working upgrade.

Idea: Another workaround could perhaps be to make the upgrade directory read only (also for system user).


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 113 posts ]  Go to page Previous  1 ... 3, 4, 5, 6, 7, 8  Next

All times are UTC


Who is online

Users browsing this forum: Baidu [Spider], Bing [Bot] and 49 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group