CrashPlan updated to 4.3.0, now will not connect

Status
Not open for further replies.

gaszto

Dabbler
Joined
Feb 26, 2014
Messages
16
Guys,
I've installed crashplan plugin. I've tried the following steps
  1. pkg update
  2. pkg install bash
  3. ln -siv /usr/local/bin/bash /bin/bash
Bash has been successfully installed, but I still have the old version 3.6.3 version of crashplan.
I've restarted the crashplan service, and the jail also without any success.
I havn't .ui_info in /var/lib/crashplan/

How can I force the update?
 

unhipglint

Cadet
Joined
Oct 10, 2015
Messages
1
Guys,
I've installed crashplan plugin. I've tried the following steps
  1. pkg update
  2. pkg install bash
  3. ln -siv /usr/local/bin/bash /bin/bash
Bash has been successfully installed, but I still have the old version 3.6.3 version of crashplan.
I've restarted the crashplan service, and the jail also without any success.
I havn't .ui_info in /var/lib/crashplan/

How can I force the update?

Restart the service and check your log (/usr/pbi/crashplan-amd64/share/crashplan/log/service.log.0) to see if there are any other issues. Shortly after the service starts there should be some INFO entries saying it has detected an update and it is downloading the files/attempting to patch. This all happens on service start, so a restart is all that should be needed to "force" the update. If it isn't happening something is going wrong.

I was having similar issues and the logs indicated it still couldn't find bash - I had forgot to create the link.
 

Xelas

Explorer
Joined
Sep 10, 2013
Messages
97
OK - I'm getting REALLY fed up with this.
Crashplan UI stopped connecting to server. Went through updating the .ui.conf rigmarole, but now have a new problem, with crashplan unable to update due to missing bash (it upgraded fine for the last year? Why now?!)
pkg update / pkg install bash fails, with:
Code:
pkg: http://pkg.FreeBSD.org/freebsd:9:x86:64/latest/All/bash-4.3.18_2.txz: Not Found

Well, that's right - that file really does not exist - browsing to the repo manually shows that 4.3.42 is the latest version.
Well, Fine.
Code:
root@Crashplan:/# pkg add http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/bash-4.3.42.txz
bash-4.3.42.txz                                                                                                                                                                                  100% 1249KB   1.2MB/s   1.2MB/s   00:00
Installing bash-4.3.42...pkg: Missing dependency matching Origin: 'print/indexinfo' Version: '0.2.3'

Failed to install the following 1 package(s): http://pkg.freebsd.org/freebsd:9:x86:64/latest/All/bash-4.3.42.txz

Well, damn.
Then I find out that
Code:
 pkg -v
1.2.7_2

pkg upgrade tells me "nothing to do".
What now?!

EDIT - is the plugin immune to this BS? Any advantage to running in a jail vs plugin?

EDIT #2 - broke this out into it's own thread, as it's not really the same problem. Sorry for the noise.
 
Last edited:

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
The recent FreeNAS update ( to FreeNAS-9.3-STABLE-201509220011) broke access to the headless CrashPlan server again. As before, I used Liriel's concise recipe above to try to fix things:

For anyone else with problems similar to me, here are the steps I used to get it working:
1. Stop crashplan plugin in GUI
2. Stop crashplan jail in GUI
3. Replace value <jail path>/var/lib/crashplan/.ui_info with .ui_info from client computer
4. Make following changes to <jail path>/usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml
i) Change xxxx in <location>0.0.0.0:xxxx</location> to match value in same file on client computer
ii) Change xxxx in <servicePort>xxxx</servicePort> to match value in same file on client computer
5. Start crashplan jail in GUI
6. Start crashplan plugin in GUI


It still didn't work (client was just hanging on the splash screen, never even got to the point where it says it can't connect to server). I went back and checked the .ui_info on the server, and it was being overwritten with the same port, but then a different key, and then (this is new) a 0.0.0.0. For example, it looked like this:

4243,7e5fdffd-fb9f-4244-b8eb-86b1aa032cfd,0.0.0.0

The .ui_info on the client did not have the trailing ,0.0.0.0 (and it never did in the past either, at least not on my system). So instead of copying the client .ui_info to the server, I tried copying the server .ui_info to the client. That did the trick. Hope this helps someone else.


4. i) what file is that saved in on the local computer? I just started having this issue with the trailing 0.0.0.0 in the .ui_info file. but the steps above didn't work for me, but I wasn't sure where the Location value on the client computer was. I was accustom to looking in the ui.properties file.
 

Xelas

Explorer
Joined
Sep 10, 2013
Messages
97
4. i) what file is that saved in on the local computer? I just started having this issue with the trailing 0.0.0.0 in the .ui_info file. but the steps above didn't work for me, but I wasn't sure where the Location value on the client computer was. I was accustom to looking in the ui.properties file.

The "location" is the IP address of the jail that the crashplan server application is running in.
On the server itself, you want to set the "location" IP to 0.0.0.0 to, presumably, essentially tell it that it's running headless.
The location port (the xxxx after the IP) should be the port that the server is listening on. By default, I think it's 4243 (but mine has been something else for a couple of years now).

On the server:
/var/lib/crashplan/.ui_info should have the correct port number, GUID, and then 0.0.0.0
/usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml
should have
<location>0.0.0.0:xxxx</location>
and
<serviceHost>0.0.0.0</serviceHost>
<servicePort>xxxx</servicePort>

On the client:
You only need to modify .ui_info. It is different from the one on the server, because it ends with the IP address that the crashplan jail has.

For example:
on server:
4243,5ef12818-7bf4-4432-b296-3d116d35d7f0,0.0.0.0

on client:
4243,5ef12818-7bf4-4432-b296-3d116d35d7f0,192.168.1.87

based on these examples, the "xxxx" in the my.service.xml file would be 4243, but your case may be different!

To find .ui_info file on the client, consult:
http://support.code42.com/CrashPlan..._On_A_Headless_Computer#Locations_Of_.ui_info
For Windows, it is typically (but not always!) C:\ProgramData\CrashPlan

P.S. - it's best to stop the server and the client before making changes, or your edits won't "stick". Instead of forcing the jail to stop, you can also just stop the crashplan service. Open shell, use "jls" to find the ID of the crashplan jail (JID), then "jexec x csh" where x=JID (for example, "jexec 3 csh"), then type "service crashplan stop" and "service crashplan start" as needed.
 
Last edited:

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
The "location" is the IP address of the jail that the crashplan server application is running in.
On the server itself, you want to set the "location" IP to 0.0.0.0 to, presumably, essentially tell it that it's running headless.
The location port (the xxxx after the IP) should be the port that the server is listening on. By default, I think it's 4243 (but mine has been something else for a couple of years now).

On the server:
/var/lib/crashplan/.ui_info should have the correct port number, GUID, and then 0.0.0.0
/usr/pbi/crashplan-amd64/share/crashplan/conf/my.service.xml
should have
<location>0.0.0.0:xxxx</location>
and
<serviceHost>0.0.0.0</serviceHost>
<servicePort>xxxx</servicePort>

On the client:
You only need to modify .ui_info. It is different from the one on the server, because it ends with the IP address that the crashplan jail has.

For example:
on server:
4243,5ef12818-7bf4-4432-b296-3d116d35d7f0,0.0.0.0

on client:
4243,5ef12818-7bf4-4432-b296-3d116d35d7f0,192.168.1.87

based on these examples, the "xxxx" in the my.service.xml file would be 4243, but your case may be different!

To find .ui_info file on the client, consult:
http://support.code42.com/CrashPlan/Latest/Configuring/Using_CrashPlan_On_A_Headless_Computer#Locations_Of_.ui_info
For Windows, it is typically (but not always!) C:\ProgramData\CrashPlan

P.S. - it's best to stop the server and the client before making changes, or your edits won't "stick". Instead of forcing the jail to stop, you can also just stop the crashplan service. Open shell, use "jls" to find the ID of the crashplan jail (JID), then "jexec x csh" where x=JID (for example, "jexec 3 csh"), then type "service crashplan stop" and "service crashplan start" as needed.

So I can't seem to get the changes to stick. I always stop crashplan before making the edits but when I start it back up the the .ui_info and the my.service.xml always change.

I have noticed that the my.service.xml the service port and location are always different (even though per the instructions above I save them as the same 4243). Also, they seem to be just one number different, i.e. this last time
Location stayed at 0.0.0.0:4243
ServicePort changed to 4244

So I changed the Location to 4242 and the Service Port to 4243

Stopped and restarted the service and the Location and Serviceport in both the .ui_info file and the my.service.xml stayed the same, but the key in the .ui_info file changed every time (I did it three times see below). So my guess is that the key is generated every time the service is stopped.

4243,8ec1b9bd-3d74-4c0a-85ac-d1028d2c61f6,0.0.0.0
4243,ad423edd-c8d3-4634-aadf-c0367fb15b10,0.0.0.0
4243,179de57e-c391-463a-8a40-f336d51b4959,0.0.0.0

So basically I have "assumed" that the above setup will work and then again tried on the client side.

But now I can't seem to get the .ui_info file to stay the same. Even though I changed the file to (for example)
4243,179de57e-c391-463a-8a40-f336d51b4959,192.168.1.2

when I restart the GUI on the client side it doesn't connect then when I check the .ui_info file it has been changed (for example the last time it changed from above to: 4201,18190ac4-a6e1-44c9-b621-5f8cf8888997,127.0.0.1)

I have tried different combinations of using the task manager to be sure all of the Crashplan services and process have been stopped and in all cases the client side .ui_info file keeps changing.

I also noticed when I changed the .ui_info file while the crashplan service was running (but application off) then tried to turn on the app I got a message "CrashPlan has been disconnected from the backup engine"

But every time I start the CrashPlanService it changes the .ui_info file back to something like "4201,18190ac4-a6e1-44c9-b621-5f8cf8888997,127.0.0.1". Finally, when I try to just start the App without the service running I get the "CrashPlan has been disconnected from the backup engine" message but the .ui_info file remains the same.

So, what am I missing?
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
Have you changed the ui.properties file on the client computer?

Uncomment the IP address line, and make sure it points to the jail IP.
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
Have you changed the ui.properties file on the client computer?

Uncomment the IP address line, and make sure it points to the jail IP.

I did. My ui.properties file is as follows:

#Fri Dec 09 09:50:22 CST 2005
serviceHost=192.168.1.2
servicePort=4243
#pollerPeriod=1000
# 1 second
#connectRetryDelay=10000
# 10 seconds
#connectRetryAttempts=3
#showWelcome=true
#font.small=
#font.default=
#font.title=
#font.message.header=
#font.message.body=
#font.tab=
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
What version of the CrashPlan client are you using? Make sure the client is at least the same version as the FreeNAS plugin.
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
What version of the CrashPlan client are you using? Make sure the client is at least the same version as the FreeNAS plugin.

CrashPalan client says it is version 4.4.1 (1435726800441)
CrashPlan Plugin says it is version 3.5.3_1 (and there isn't an upgrade button next to it)
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
Where are you seeing an upgrade button? We're talking about the version of CrashPlan, not the version of the CrashPlan plugin.

To figure out the version of CrashPlan, run:

Code:
cat /var/log/crashplan/engine_output.log | grep CPVER 
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
Thank you for the clarification. I was not sure what was meant. The version on the server is different see below. So how do I go about getting that updated?

CPVERSION = 4.3.3 - 1430802000433 (2015-05-05T05:00:00:433+0000) - Build: 3
 
Last edited:

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
Version 4.4 changed a whole bunch of stuff. You need a version 4.3.x client to work with any version 4.3.x version of the server or older, and a version 4.4.x version of the client to work with any version 4.4 or newer.

Also, Crashplan changed their update scheme in version 4.4 to require bash. There are a lot of articles around here that deal with installing bash to upgrade crashplan.

HOWEVER, you do not need to upgrade if you don't want to. Version 4.3.x will work just fine (at least for now; CrashPlan hasn't made a habit of breaking support with earlier versions).

Since, I assume, you haven't ever got this working, I would recommend going through with the upgrade. Better to figure it out now, when there's nothing to break.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
HOWEVER, you do not need to upgrade if you don't want to. Version 4.3.x will work just fine (at least for now; CrashPlan hasn't made a habit of breaking support with earlier versions).
FWIW, I wasn't able to get the version 4.4.1 client on my Mac to connect to a 4.3.x backend. Once the backend updated to 4.4.1, it connected without a problem (until one of them restarts and changes the UUID again).
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
So I think I installed bash (not sure how to check that) then I did the pkg install pkg and the following happened. So I am still missing something:

Code:
root@crashplan_1:/ # pkg install pkg
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
Updating database digests format: 100%
New version of pkg detected; it needs to be installed first.
The following 1 packages will be affected (of 0 checked):

Installed packages to be UPGRADED:
  pkg: 1.4.12 -> 1.6.1

The process will require 453 KiB more space.
2 MiB to be downloaded.

Proceed with this action? [y/N]: y
[crashplan_1] Fetching pkg-1.6.1.txz: 100%  2 MiB  2.1MB/s  00:01
Checking integrity...pkg: Skipping unknown key 'messages'
done (0 conflicting)
pkg: Skipping unknown key 'messages'
[crashplan_1] [1/1] Upgrading pkg from 1.4.12 to 1.6.1...
[crashplan_1] [1/1] Extracting pkg-1.6.1: 100%
Updating FreeBSD repository catalogue...
pkg: Unable to upgrade "FreeBSD" repo schema version 2010 (target version 2012) -- change not found
pkg: need to re-create repo FreeBSD to upgrade schema version
[crashplan_1] Fetching meta.txz: 100%  968 B  1.0kB/s  00:01
[crashplan_1] Fetching packagesite.txz: 100%  5 MiB  2.8MB/s  00:02
Processing entries: 100%
FreeBSD repository update completed. 24460 packages processed.
Checking integrity... done (0 conflicting)
The most recent version of packages are already installed
root@crashplan_1:/ #[code/]
 

Andrew076

Patron
Joined
Apr 5, 2015
Messages
206
By the way when is stop the crashplan service I get the following noticed:

Code:
/usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Not sure if that is causing me any of the problems.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
No, the lack of the shebang isn't causing a problem. How do you think you installed bash? What's the output of 'which bash'? What's the output of 'ls -l /bin/bash'?
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
FWIW, I wasn't able to get the version 4.4.1 client on my Mac to connect to a 4.3.x backend. Once the backend updated to 4.4.1, it connected without a problem (until one of them restarts and changes the UUID again).

Yup, that's why I said:

Version 4.4 changed a whole bunch of stuff. You need a version 4.3.x client to work with any version 4.3.x version of the server or older, and a version 4.4.x version of the client to work with any version 4.4 or newer.
 

Nick2253

Wizard
Joined
Apr 21, 2014
Messages
1,633
If the only thing you did was "pkg install pkg", all you did was update pkg. If you want to install bash, you need to do "pkg install bash".
 
Status
Not open for further replies.
Top