CrashPlan Will NOT Start

Status
Not open for further replies.

nello

Patron
Joined
Dec 30, 2012
Messages
351
Update 2016.07.17
This isn't a permissions problem ... skip down.


CrashPlan won't start on either a Jail restart or a system reboot.

Apparently, there is a permissions problem:
Code:
crashPlan@crashplan_1:~ % service crashplan onestart
install: chmod 755 /var/log/crashplan: Operation not permitted
ps: cmd: keyword not found
Starting CrashPlan Engine ... Using standard startup
/usr/pbi/crashplan-amd64/share/crashplan/bin/CrashPlanEngine: line 17: /usr/pbi/crashplan-amd64/share/crashplan/bin/../CrashPlanEngine.pid: Permission denied
OK
crashPlan@crashplan_1:~ % /usr/pbi/crashplan-amd64/share/crashplan/bin/CrashPlanEngine: line 14: /usr/pbi/crashplan-amd64/share/crashplan/log/engine_output.log: Permission denied
crashPlan@crashplan_1:



Unfortunately, I don't understand which file(s) (with full path) have insufficient privileges. Moreover, It's not clear to me what the permissions should be.

Would someone please point in the right direction?

Thank you.

- nello

PS: Is this a problem too?
Code:
crashPlan@crashplan_1:~ % service crashplan status

/usr/local/etc/rc.d/crashplan: WARNING: $crashplan_enable is not set properly - see rc.conf(5).
Will not 'status' crashplan because crashplan_enable is NO.
crashPlan@crashplan_1:~ % 
 
Last edited:

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
The latter issue seems to be that you haven't turned on the CrashPlan plugin. When you install a plugin, it isn't turned on by default. I think that's a poor default, but it is what it is. You'd turn it on on the Plugins -> Installed page.

As to the former issue, is there any chance that you created your jails dataset with Windows permissions?
 

nello

Patron
Joined
Dec 30, 2012
Messages
351
The latter issue seems to be that you haven't turned on the CrashPlan plugin.
Yes, you are correct; apparently it is off:
OctoberGroupNAS_-_FreeNAS-9_10-STABLE-201606270534__dd17351_.png


Unfortunately, clicking on the OFF button does not turn it on. I get the animation as if it were trying to start, but when the animation stops the button is still off, not on.


As to the former issue, is there any chance that you created your jails dataset with Windows permissions?
No. I don't use Windows.


It really puzzles me why this stopped working. I don't recall making any changes to FreeNAS in the past week. The only thing I remember is that I was having problems with my internet service; turned out that a spliced connection on the telephone pole was failing. But, I can't imagine how fiddling with the internet connection would have any impact on file permissions.

So, I think that I'm back to my original questions:
  1. What files are being flagged as having permissions errors?
  2. What permissions should these files have?

Thank you for your reply.

- nello
 

nello

Patron
Joined
Dec 30, 2012
Messages
351
I've done a bit more digging.

First off, apparently the permission errors occurred because I wasn't running the commands as root. Sorry about my original post when it was such a noob mistake on my part.

Second, based on the file dates, it appears that CrashPlan updated itself on July 14, the day the problems started
Code:
crashPlan@crashplan_1:~ % ls -Al /usr/pbi/crashplan-amd64/share/crashplan
total 100243
-rw-r--r--    1 root  wheel         5 Jul 17 09:47 CrashPlanEngine.pid
-rw-rw-r--    1 root  wheel   7641919 Jul 14 00:08 app.asar
drwxrwxr-x    2 root  wheel        11 Jul 17 09:42 bin
drwxrwxr-x    2 root  wheel        12 Oct 22  2014 conf
drwxrwxr-x    2 root  wheel         6 Jul 14 00:08 doc
-rw-r--r--    1 root  wheel       457 Jul 14 00:08 install.vars
drwxr-xr-x    6 2013  4200         13 May 19  2015 jre
-rw-r--r--    1 root  wheel  48547492 Jul 29  2015 jre-7-linux-i586.tgz
drwxrwxr-x    2 root  wheel        19 Jul 14 00:08 lang
drwxrwxr-x    2 root  wheel        71 Jul 14 00:08 lib
-rw-rw-r--    1 root  wheel     11854 Jul 14 00:08 libc42archive.so
-rw-rw-r--    1 root  wheel     13060 Jul 14 00:08 libc42archive64.so
-rw-rw-r--    1 root  wheel   2481278 Jul 14 00:08 libc42core.so
-rw-rw-r--    1 root  wheel     24756 Jul 14 00:08 libjniwrap.so
-rw-rw-r--    1 root  wheel     48344 Jul 14 00:08 libjniwrap64.so
-rw-rw-r--    1 root  wheel    257693 Jul 14 00:08 libjtux.so
-rw-rw-r--    1 root  wheel    287934 Jul 14 00:08 libjtux64.so
-rw-rw-r--    1 root  wheel    403970 Jul 14 00:08 libleveldb.so
-rw-rw-r--    1 root  wheel    427599 Jul 14 00:08 libleveldb64.so
-rw-rw-r--    1 root  wheel      7346 Jul 14 00:08 libmd5.so
-rw-rw-r--    1 root  wheel      8417 Jul 14 00:08 libmd564.so
drwxrwxrwx    2 root  wheel        15 Jul 14 00:08 log
drwxrwxr-x    3 root  wheel        12 Jul 14 00:08 skin
drwxr-xr-x  389 root  wheel       399 Jul 14 00:08 upgrade
-rw-r--r--    1 root  wheel  47474227 Jul 14 00:07 upgrade.cpi
crashPlan@crashplan_1:~ %



Based on the log at /usr/pbi/crashplan-amd64/share/crashplan/log/upgrade.1435813200470_344.1468472873812.log apparently CrashPlan decided that I needed to update my Java Runtime Environment, which it downloaded from:

https://download1.code42.com/installs/proserver/jre/jre-7-linux-i586.tgz


Third, apparently the reason that CrashPlan can't start is that it can't find libjli.so, a file that it thinks it needs:
Code:
crashPlan@crashplan_1:~ % cat /usr/pbi/crashplan-amd64/share/crashplan/log/engine_error.log
/usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory
crashPlan@crashplan_1:~ %



Fourth, I found this thread regarding the same error message:

https://forums.freenas.org/index.php?threads/crashplan-update-failing-due-to-old-java-version.42300/

A reply toward the bottom suggests re-installing CrashPlan. I'll give that a try.


Update 2016.07.16 11:00 CDT
Reinstalling CrashPlan 4.7 hasn't had any effect:
Code:
root@crashplan_1:/ # service crashplan start
ps: cmd: keyword not found
Starting CrashPlan Engine ... Using standard startup
OK
...
root@crashplan_1:/ # ls -Al /usr/pbi/crashplan-amd64/share/crashplan/log/engine_error.log
-rw-r--r--  1 root  wheel  162 Jul 17 10:56 /usr/pbi/crashplan-amd64/share/crashplan/log/engine_error.log
root@crashplan_1:/ # cat /usr/pbi/crashplan-amd64/share/crashplan/log/engine_error.log
/usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory
root@crashplan_1:/ #


I need to find the ps command that's being executed and figure out what's wrong with it.


Update 2016.07.16 11:30 CDT
I think the script that is throwing this error is /usr/pbi/crashplan-amd64/share/crashplan/bin/CrashPlanEngine and that this is the line using ps
Code:
_findpid() {
    /bin/ps -eo 'pid,cmd'| grep 'app=CrashPlanService' | grep -v grep | awk '{ print $1 }'
}



FreeBSD's ps command does not support the keyword cmd; it uses comm instead. So, I changed this function to:
Code:
_findpid() {
        /bin/ps -eo 'pid,comm'| grep 'app=CrashPlanService' | grep -v grep | awk '{ print $1 }'
}



Unfortunately, I still get the same error saying that
libjli.so is missing from /usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java:
Code:
root@crashplan_1:/usr/pbi/crashplan-amd64/share/crashplan/bin # cd /
root@crashplan_1:/ # cat /usr/pbi/crashplan-amd64/share/crashplan/log/engine_error.log
/usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory
 
Last edited:

nello

Patron
Joined
Dec 30, 2012
Messages
351
From the log at /usr/pbi/crashplan-amd64/share/crashplan/log/upgrade.1435813200470_344.1468472873812.log, it appears that
jre-7-linux-i586.tgz was unpacked to /usr/pbi/crashplan-amd64/share/crashplan/jre and I found libjli.so in a subdirectory:
Code:
crashPlan@crashplan_1:~ % ls -lA /usr/pbi/crashplan-amd64/share/crashplan/jre/lib/i386/jli
total 65
-rwxr-xr-x  1 2013  4200  88513 Apr 10  2015 libjli.so
crashPlan@crashplan_1:~ % 



Unfortunately, JAVACOMMON in /usr/pbi/crashplan-amd64/share/crashplan/install.vars is not pointing to the directory where libjli.so is located:
Code:
root@crashplan_1:/ # cat /usr/pbi/crashplan-amd64/share/crashplan/install.vars
TARGETDIR=/usr/pbi/crashplan-amd64/share/crashplan
BINSDIR=/usr/pbi/crashplan-amd64/share/crashplan/bin
JAVACOMMON=/usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java
APP_BASENAME=CrashPlan
DIR_BASENAME=crashplan
JRE_X64_DOWNLOAD_URL=http://download.code42.com/installs/proserver/jre/jre-7u45-linux-x64.tgz
JRE_I586_DOWNLOAD_URL=http://download.code42.com/installs/proserver/jre/jre-7u45-linux-i586.tgz
TARGETDIR=/usr/pbi/crashplan-amd64/share/crashplan
root@crashplan_1:/ #



Following a post by @Eric Blau ...

I added
export LD_LIBRARY_PATH=/usr/pbi/crashplan-amd64/share/crashplan/jre/lib/i386/jli/ right after the shebang in /usr/pbi/crashplan-amd64/share/crashplan/bin/
CrashPlanEngine
and started it up with no errors.
Code:
root@crashplan_1:/ # service crashplan onestart
Starting CrashPlan Engine ... Using standard startup
OK
root@crashplan_1:/ # ps
  PID TT  STAT    TIME COMMAND
8636  0  IJ   0:00.01 su
8639  0  SJ   0:00.20 _su (csh)
35325  0  SNJ  0:05.09 /usr/pbi/crashplan-amd64/share/crashplan/jre/bin/java -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=
35329  0  R+J  0:00.00 ps
root@crashplan_1:/ # 



Curiously, even after restarting the Jail, I can't start CrashPlan from the GUI.
OctoberGroupNAS_-_FreeNAS-9_10-STABLE-201606270534__dd17351_.png
 
Last edited:

smalahove

Cadet
Joined
Aug 5, 2016
Messages
2
I had the same problem, and your export-line enabled crashplan to start running again. Good job!
 

dsfew32

Dabbler
Joined
May 9, 2015
Messages
12
Thanks so much for your work nello. It is absurd this plugin keeps breaking and seems to get harder and harder to manage. But your export line fixed things. Just waiting for the next update to break things again :(
 

Kulasir

Cadet
Joined
May 23, 2015
Messages
4
A new update last night (Sept 28) from Crashplan broke the system again. Fortunately, the fix described here worked again.
 

t3hG04T

Cadet
Joined
Jan 26, 2015
Messages
7
Yup, thank you for the great solution, fixed the non-starting 4.8 for me as well :).
 
Status
Not open for further replies.
Top