I realize that there are already many postings on these (and many similar) issues, but some are pretty old and deal with outdated versions of FreeNAS and CrashPlan, so I thought I would post this again a) to help anyone who comes up the same problems and b) as a reminder that many problems previously described as fixed are actually still with us.
This is written as of 5/15/2015, with FreeNAS 9.3 and the current CrashPlan plugin (distributed as version 3.6.3 and currently at 4.2.0).
--I was unable to get the CrashPlan plugin to update - it remained "stuck" at 3.6.3. I tried pretty much everything, and eventually ripped it out and reinstalled (which got it moving). If anyone could provide some insight as to how the plugin actually updates itself, that would be great (e.g., does it update itself directly, or "through" the interface application that you're running on another box? Do any specific ports need to be open and forwarded on your firewall in order to permit the update to occur?)
--Upon re-installation, the CrashPlan log (the "History" viewer on the CrashPlan interface) showed that updating occurred immediately - right after startup, the log says "Upgrades available at central.crashplan.com:443"). Three updates (for versions 3.6.4, 3.7.0, and 4.2.0) were then downloaded in rapid succession. If you don't see this in the log, you may (like me) have big trouble in getting it to update ever, at all.
--It then proceeds to install the first update, and the service then rapidly starts and stops (2 or 3 times per minute) for about 10 minutes. The second update then installs, and the service once again starts and stops (in my case, for another 15 minutes). The third update then installs, and after that the service turns off. You can try to turn the service back on manually, but it will always shut itself off again within a few seconds.
--You shell into the jail and take a look at the file
usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf
and you see that the option
-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider
has been stripped out of the beginning of both the SRV_JAVA_OPTS and GUI_JAVA_OPTS option lines. See this thread for the earliest description (I believe) of this:
https://forums.freenas.org/index.php?threads/crashplan-3-6-3.18416/#post-101205
--You put that option back at the beginning of both lines of the run.conf file, save it, and then immediately reboot FreeNAS. (At first I just tried to restart the Crashplan plugin. All that did was wipe out my changes. Others have reported success by editing run.conf from outside of the jail.)
--After that, all is well (fingers crossed).
CrashPlan seems like an excellent backup tool, so I hope to use it and rely on it, but unfortunately the plugin is not yet easy to use like the rest of FreeNAS.
This is written as of 5/15/2015, with FreeNAS 9.3 and the current CrashPlan plugin (distributed as version 3.6.3 and currently at 4.2.0).
--I was unable to get the CrashPlan plugin to update - it remained "stuck" at 3.6.3. I tried pretty much everything, and eventually ripped it out and reinstalled (which got it moving). If anyone could provide some insight as to how the plugin actually updates itself, that would be great (e.g., does it update itself directly, or "through" the interface application that you're running on another box? Do any specific ports need to be open and forwarded on your firewall in order to permit the update to occur?)
--Upon re-installation, the CrashPlan log (the "History" viewer on the CrashPlan interface) showed that updating occurred immediately - right after startup, the log says "Upgrades available at central.crashplan.com:443"). Three updates (for versions 3.6.4, 3.7.0, and 4.2.0) were then downloaded in rapid succession. If you don't see this in the log, you may (like me) have big trouble in getting it to update ever, at all.
--It then proceeds to install the first update, and the service then rapidly starts and stops (2 or 3 times per minute) for about 10 minutes. The second update then installs, and the service once again starts and stops (in my case, for another 15 minutes). The third update then installs, and after that the service turns off. You can try to turn the service back on manually, but it will always shut itself off again within a few seconds.
--You shell into the jail and take a look at the file
usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf
and you see that the option
-Djava.nio.channels.spi.SelectorProvider=sun.nio.ch.PollSelectorProvider
has been stripped out of the beginning of both the SRV_JAVA_OPTS and GUI_JAVA_OPTS option lines. See this thread for the earliest description (I believe) of this:
https://forums.freenas.org/index.php?threads/crashplan-3-6-3.18416/#post-101205
--You put that option back at the beginning of both lines of the run.conf file, save it, and then immediately reboot FreeNAS. (At first I just tried to restart the Crashplan plugin. All that did was wipe out my changes. Others have reported success by editing run.conf from outside of the jail.)
--After that, all is well (fingers crossed).
CrashPlan seems like an excellent backup tool, so I hope to use it and rely on it, but unfortunately the plugin is not yet easy to use like the rest of FreeNAS.
