Update crashplan to 3.7.0?

[jonandermb]

Hi!
New to plugins, starting to play around with them.
I have a question:
How come people are talking about crashplan plugin 3.7.0 and I still am on 3.6.3?
I have the latest freenas updates installed.
I ask this because I have problems starting crashplan and people say updating to 3.7.0 solves those.
Thanks.

 

[fracai]

Crashplan updates itself. If you can resolve your startup problems, you'll probably be updated immediately to 3.7 and then have to fix run.conf again.

 

[Pasquale61]

Just to add to this, I don't think the FreeNAS Plugin GUI ever shows that the plugin is updated, even though it is. The way I figured out which version is actually running is by going to the terminal on the CrashPlan jail and looking in the following file:

/usr/pbi/crashplan-amd64/share/crashplan/log/app.log

Near the top you'll see the version:

CPVERSION = 3.7.0 - 1388728800370 (2014-01-03T06:00:00:370+0000)

There may be an easier way to check, but this worked for me. I think the headless client only shows the client version, but I'm not sure.

 

[fracai]

From the Crashplan GUI you should be able to double click the "house icon" to bring up a console window. I think one of the commands is "version" and will list the version. I'm assuming that this is the version of the server. Though, reports seem to indicate that different version of the client and server can't communicate, so maybe it doesn't matter.

 

[jonandermb]

Ok, I have been reading the posts over here and found this: https://forums.freenas.org/index.php?threads/crashplan-plugin-wont-start.24243/#post-149005

The problem is the file I'm suppose to edit, already has the changes suggested on the post above!
I'm stuck with this issue. I can't make crashplan start even once :(

 

[Pasquale61]

The problem is the file I'm suppose to edit, already has the changes suggested on the post above!

First, I'm assuming that this was working until a couple of weeks ago when the 3.7.0 update came out. If not, you may just need to start over with the plugin.

If run.conf already has the suggested first two entries and you did not recently did not add them, then you probably did not take the 3.7.0 update, because the update is what wipes them out. That would mean you have something else going on. Look for "CPVERSION" in this file to see which version is installed on your server: /usr/pbi/crashplan-amd64/share/crashplan/log/app.log.

Here is my run.conf for comparison if it helps:

SRV_JAVA_OPTS="-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.encoding=UTF-8 -Dapp=CrashPlanService -DappBaseName=CrashPlan -Xms20m -Xmx1024m -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false"
GUI_JAVA_OPTS="-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider -Dfile.encoding=UTF-8 -Dapp=CrashPlanDesktop -DappBaseName=CrashPlan -Xms20m -Xmx512m -Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=300 -Dnetworkaddress.cache.ttl=300 -Dsun.net.inetaddr.negative.ttl=0 -Dnetworkaddress.cache.negative.ttl=0 -Dc42.native.md5.enabled=false"

Also, many of us had to reboot the entire FreeNAS for the plugin to correctly show that it is running. Just restarting the jail doesn't always work for some reason.

 

[jonandermb]

Code:

Jan 26 16:58:03 NAS kernel: bce0: link state changed to UP
Jan 26 16:58:03 NAS kernel: bce0: link state changed to UP
Jan 26 16:58:03 NAS Gigabit link up!
Jan 26 16:58:04 NAS ctld[1672]: invalid target name "nasr:crashplan"; should start with either ".iqn", "eui.", or "naa."
Jan 26 16:58:04 NAS ctld[1672]: auth-group "ag4tg_1" not assigned to any target
Jan 26 16:58:06 NAS root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jan 26 16:58:06 NAS vboxdrv: fAsync=0 offMin=0x41a offMax=0xdad2
Jan 26 16:58:11 NAS ntpd[1897]: ntpd 4.2.4p5-a (1)
Jan 26 16:58:11 NAS WARNING: 192.168.1.4 (iqn.1991-05.com.microsoft:servidor3.dom.lan): no ping reply (NOP-Out) after 5 seconds; dropping connection
Jan 26 16:58:15 NAS ntpd[1898]: time reset -0.888124 s
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint,name
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpW6FjSw -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Jan 26 16:58:20 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -L
Jan 26 16:58:20 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net sam rights grant root SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege
Jan 26 16:58:20 NAS nmbd[2157]: [2015/01/26 16:58:20.794762,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 26 16:58:20 NAS winbindd[2163]: [2015/01/26 16:58:20.993035,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Jan 26 16:58:20 NAS winbindd[2163]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jan 26 16:58:21 NAS winbindd[2163]: [2015/01/26 16:58:21.011405,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 26 16:58:21 NAS smbd[2160]: [2015/01/26 16:58:21.311706,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 26 16:58:21 NAS smbd[2160]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Jan 26 16:58:37 NAS bridge0: Ethernet address: 02:52:d6:6a:72:00
Jan 26 16:58:37 NAS kernel: bce1: promiscuous mode enabled
Jan 26 16:58:37 NAS kernel: bridge0: link state changed to UP
Jan 26 16:58:37 NAS kernel: bridge0: link state changed to UP
Jan 26 16:58:37 NAS kernel: bce0: promiscuous mode enabled
Jan 26 16:58:37 NAS kernel: lagg0: promiscuous mode enabled
Jan 26 16:58:37 NAS epair0a: Ethernet address: 02:31:e3:00:0c:0a
Jan 26 16:58:37 NAS epair0b: Ethernet address: 02:31:e3:00:0d:0b
Jan 26 16:58:37 NAS kernel: epair0a: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0a: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0b: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0b: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0a: promiscuous mode enabled
Jan 26 16:58:37 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 26 16:58:37 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 26 16:58:47 NAS manage.py: [freeadmin.navtree:550] Couldn't retrieve https://192.168.1.15/plugins/crashplan/1/_s/treemenu: timed out

This appears in the log when starting, idk if it might shed some light on the problem

It's a fresh install: I'm starting to use crashplan on freenas for backup purposes.
I just installed the plugin: I don't get it to launch even once.
I have no log folder under /mnt/STORAGE/jails/crashplan_1/usr/pbi/crashplan-amd64/share/crashplan/

A mmoment ago, I tried removing the jail completely, rebooting, reinstalling, rebooting, and still the same effect.

EDIT:
I found what might be the problem: The ip of the jail. I had it set to a static IP i decided, but after changing to DHCP, the app seems to start.
The run.conf file has changed now, and I have a log folder.... Now I have where to start from.... I'll report later my advances

 

[SweetAndLow]

Code:

Jan 26 16:58:03 NAS kernel: bce0: link state changed to UP
Jan 26 16:58:03 NAS kernel: bce0: link state changed to UP
Jan 26 16:58:03 NAS Gigabit link up!
Jan 26 16:58:04 NAS ctld[1672]: invalid target name "nasr:crashplan"; should start with either ".iqn", "eui.", or "naa."
Jan 26 16:58:04 NAS ctld[1672]: auth-group "ag4tg_1" not assigned to any target
Jan 26 16:58:06 NAS root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jan 26 16:58:06 NAS vboxdrv: fAsync=0 offMin=0x41a offMax=0xdad2
Jan 26 16:58:11 NAS ntpd[1897]: ntpd 4.2.4p5-a (1)
Jan 26 16:58:11 NAS WARNING: 192.168.1.4 (iqn.1991-05.com.microsoft:servidor3.dom.lan): no ping reply (NOP-Out) after 5 seconds; dropping connection
Jan 26 16:58:15 NAS ntpd[1898]: time reset -0.888124 s
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint,name
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: zfs list -H -o mountpoint
Jan 26 16:58:18 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmpW6FjSw -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Jan 26 16:58:20 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -L
Jan 26 16:58:20 NAS generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net sam rights grant root SeTakeOwnershipPrivilege SeBackupPrivilege SeRestorePrivilege
Jan 26 16:58:20 NAS nmbd[2157]: [2015/01/26 16:58:20.794762,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 26 16:58:20 NAS winbindd[2163]: [2015/01/26 16:58:20.993035,  0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Jan 26 16:58:20 NAS winbindd[2163]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jan 26 16:58:21 NAS winbindd[2163]: [2015/01/26 16:58:21.011405,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 26 16:58:21 NAS smbd[2160]: [2015/01/26 16:58:21.311706,  0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 26 16:58:21 NAS smbd[2160]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Jan 26 16:58:37 NAS bridge0: Ethernet address: 02:52:d6:6a:72:00
Jan 26 16:58:37 NAS kernel: bce1: promiscuous mode enabled
Jan 26 16:58:37 NAS kernel: bridge0: link state changed to UP
Jan 26 16:58:37 NAS kernel: bridge0: link state changed to UP
Jan 26 16:58:37 NAS kernel: bce0: promiscuous mode enabled
Jan 26 16:58:37 NAS kernel: lagg0: promiscuous mode enabled
Jan 26 16:58:37 NAS epair0a: Ethernet address: 02:31:e3:00:0c:0a
Jan 26 16:58:37 NAS epair0b: Ethernet address: 02:31:e3:00:0d:0b
Jan 26 16:58:37 NAS kernel: epair0a: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0a: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0b: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0b: link state changed to UP
Jan 26 16:58:37 NAS kernel: epair0a: promiscuous mode enabled
Jan 26 16:58:37 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 26 16:58:37 NAS kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 26 16:58:47 NAS manage.py: [freeadmin.navtree:550] Couldn't retrieve https://192.168.1.15/plugins/crashplan/1/_s/treemenu: timed out

This appears in the log when starting, idk if it might shed some light on the problem

It's a fresh install: I'm starting to use crashplan on freenas for backup purposes.
I just installed the plugin: I don't get it to launch even once.
I have no log folder under /mnt/STORAGE/jails/crashplan_1/usr/pbi/crashplan-amd64/share/crashplan/

A mmoment ago, I tried removing the jail completely, rebooting, reinstalling, rebooting, and still the same effect.

Make a new thread, your issues has nothing to do what is being discussed in this thread. You have a networking or hardware issues.

 

[Jailer]

Ok, I have been reading the posts over here and found this: https://forums.freenas.org/index.php?threads/crashplan-plugin-wont-start.24243/#post-149005

The problem is the file I'm suppose to edit, already has the changes suggested on the post above!
I'm stuck with this issue. I can't make crashplan start even once :(

Did you accept the EULA from the plugins menu in the left pane of the freenas GUI?

If you're still having trouble follow this install guide to get it going and then fix it with the link you posted earlier describing the update fix.

 

[jonandermb]

OK, Someone close the thread. I'll follow the guide and start over.
Thanks

 

[Jailer]

Don't close the thread, report back and let us know if you got it going and what you did to fix it. Others may find your experience useful.

 

[jonandermb]

Will do in the next days.

Thanks :)

 

[jonandermb]

OK, The plugin updated to 3.7.0, as per what the log says.
Now I face some other problem: The jail does not start.
I'm kind of lost here. I don't really know where to start from: Where can I see the logs to find out why the jail is failing to start?

 

[jonandermb]

Ok, the jail starts and updates whenever it wants to.
I wanted to start from scratch, so I deleted the jails folder, now I have some leftover files here and there...... I kind of messed up.
I'll try rebooting later, since the machine is in production and I can't now.-

 

[subzer011]

my crashplan 3.7 also kept crashing. i re-did the install from scratch, following the instructions from the link Jailer posted,

http://techflow.io/blog/crashplan-plugin-for-freenas

But I also had to go in through SSH and apply the following two fixes as well,

https://forums.freenas.org/index.php?threads/crashplan-3-6-3.18416/#post-101205
https://forums.freenas.org/index.php?threads/crashplan-plugin-wont-start.24243/#post-167989

Keep in mind, when CrashPlan updates, it resets run.conf back to defaults. So you gotta keep applying the fixes until it stops updating. For me, installing from the FreeNAS plugin screen went from 3.6.3 to 3.6.4 to 3.7.0. I had to reapply the fixes after each update. It's now been running for a week without crashing.

 

[raidflex]

What user does the Crashplan plugin run as? I cannot seem to find this info. I prefer not to run anything as root if possible, and it seems like that is what the Crashplan plugin is using.

 

[raidflex]

Bump. Anyone have some insight on the user that is used?

 

[SweetAndLow]

I have this user:

Code:

cat /etc/passwd | grep crash
crashplan:*:1001:1001:CrashPlan:/home/crashplan:/bin/sh

The java process that are running are owned by root.

 

[raidflex]

I have this user:

Code:

cat /etc/passwd | grep crash
crashplan:*:1001:1001:CrashPlan:/home/crashplan:/bin/sh

The java process that are running are owned by root.

Okay, thanks. I just need to know which permissions to give to the Dataset for the incoming backups folder, this is why I was asking.

 

[SweetAndLow]

just give "other" write permissions for simplicity