Crashplan refuses to start

[DanPrs]

I've had a similar issue a few months ago after updating. Then I followed the recommendation found here:

https://forums.freenas.org/index.php?threads/crashplan-plugin-wont-start.24243/#post-149189

Though those lines were missing again, adding them this time around did not resole the issue. Not sure where to go from here.

 

[SweetAndLow]

You need to give more info. Hardware spec, did you change permissions on anything and what error message are you seeing.

 

[DanPrs]

Ah yes sorry about that.

This happened since I updated to 9.3 about a month ago. No other change to the system besides the firmware.
Jail installed via PBI.

E3-1220 v3
16GB ECC
3x3T HDD

 

[SweetAndLow]

error message? if there isn't an error message how do you know there is something wrong?

 

[DanPrs]

There's no error message. I go to the plug ins page, hit the on button and it goes to the on position. And it stays there. However if I navigate away from the this page and return, the button is in the off position. This happens if I instantly navigate away and return to the "installed plug ins" page.

 

[SweetAndLow]

Nothing in/var/log/messages

 

[DanPrs]

Code:

Jan  1 00:00:00 crashplan_1 newsyslog[7397]: logfile turned over
Jan  8 13:39:31 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 15 00:56:32 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 21 02:41:04 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 21 11:34:37 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 13:10:12 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 13:27:34 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 13:35:58 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 13:36:12 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 13:37:44 crashplan_1 syslogd: exiting on signal 15
Jan 22 13:38:00 crashplan_1 syslogd: kernel boot file is /boot/kernel/kernel
Jan 22 13:38:00 crashplan_1 root: /etc/rc: WARNING: $crashplan_enable is not set properly - see rc.conf(5).
Jan 22 13:42:33 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 14:01:04 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 22 14:03:34 crashplan_1 syslogd: exiting on signal 15
Jan 22 14:06:46 crashplan_1 syslogd: kernel boot file is /boot/kernel/kernel
Jan 22 14:45:19 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 26 13:44:05 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Jan 26 14:13:01 crashplan_1 syslogd: exiting on signal 15
Jan 26 14:19:11 crashplan_1 syslogd: kernel boot file is /boot/kernel/kernel
Jan 26 17:19:47 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Feb  9 17:18:16 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset
Feb  9 19:12:03 crashplan_1 root: /usr/local/etc/rc.d/crashplan: WARNING: no shebang line in /usr/bin/cpuset

Well that's interesting. How do I go about this?

 

[SweetAndLow]

1. Jan 22 13:38:00 crashplan_1 root: /etc/rc: WARNING: $crashplan_enable is not set properly - see rc.conf(5).

This is probably the interesting one. Did you accept the terms of service? Also check what value you have in /etc/rc.conf

 

[DanPrs]

Not sure how to access /etc/rc.conf, access is denied.

 

[dlavigne]

Not sure how to access /etc/rc.conf, access is denied.

Click the shell icon for the jail and type vi /etc/rc.conf to open it in the vi editor.