SOLVED Backups to FreeNAS Stopped Working: Can NOT Connect to CrashPlan

[nello]

Suddenly my desktop reports that it can not connect to CrashPlan running in a FreeNAS Jail. The symptoms are reminiscent of an old problem that ended up being caused by a new version of CrashPlan:

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

Symptoms now are these kernel log messages:

OctoberGroupNAS.local kernel log messages:
> linux: pid 40143 (java): syscall epoll_create not implemented
> linux: pid 40228 (java): syscall epoll_create not implemented
> linux: pid 40280 (java): syscall epoll_create not implemented
> linux: pid 40424 (java): syscall epoll_create not implemented
> linux: pid 40473 (java): syscall epoll_create not implemented
> linux: pid 40608 (java): syscall epoll_create not implemented
> linux: pid 40809 (java): syscall epoll_create not implemented
> linux: pid 40854 (java): syscall epoll_create not implemented

-- End of security output --

​

CrashPlan is not listening on port 4242 as it should be:

root@crashplan_1:/ # sockstat -4
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root python2.7 11290 3 tcp4 10.10.49.11:12346 *:*
root sshd 11061 5 tcp4 *:22 *:*
root syslogd 10931 7 udp4 *:514 *:*
root@crashplan_1:/ #​

Here's the CrashPlan Engine Log:

root@crashplan_1:/ # cat /var/log/crashplan/engine_output.log
Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - find_vma failed
[01.16.15 10:40:14.554 INFO main root ] Locale changed to English
[01.16.15 10:40:14.555 INFO main root ] **************************************
***********************
[01.16.15 10:40:14.555 INFO main root ] **************************************
***********************
[01.16.15 10:40:14.555 INFO main root ] STARTED CrashPlanService
[01.16.15 10:40:14.557 INFO main root ] CPVERSION = 3.7.0 - 1388728800370 (201
4-01-03T06:00:00:370+0000)
[01.16.15 10:40:14.557 INFO main root ] LOCALE = English
[01.16.15 10:40:14.558 INFO main root ] ARGS = [ ]
[01.16.15 10:40:14.558 INFO main root ] **************************************
***********************
[01.16.15 10:40:14.697 INFO main root ] Adding shutdown hook.
[01.16.15 10:40:14.705 INFO main root ] BEGIN Loading Configuration
[01.16.15 10:40:14.756 INFO main root ] BEGIN Copy Custom
[01.16.15 10:40:14.757 INFO main root ] Directories: [.Custom, custom, /usr/
pbi/crashplan-amd64/share/crashplan/conf/.Custom, /usr/pbi/crashplan-amd64/share/crashplan/conf/custom]
[01.16.15 10:40:14.757 INFO main root ] NOT waiting for custom skin to appea
r
[01.16.15 10:40:14.757 INFO main root ] NO customizations found.
[01.16.15 10:40:14.757 INFO main root ] END Copy Custom
[01.16.15 10:40:14.762 INFO main root ] Loading from default: /usr/pbi/crash
plan-amd64/share/crashplan/conf/default.service.xml
[01.16.15 10:40:14.870 INFO main root ] Loading from my xml file=conf/my.ser
vice.xml
[01.16.15 10:40:15.028 INFO main root ] Loading ServiceConfig, newInstall=fa
lse, version=6, configDateMs=1418655269476, installVersion=1388556100363
[01.16.15 10:40:15.029 INFO main root ] OS = Linux
[01.16.15 10:40:15.316 INFO main root ] AuthorityLocation@18420548[ location
=central.crashplan.com:443, hideAddress=false ]
[01.16.15 10:40:15.317 INFO main root ] Checking Java memory heap max.
[01.16.15 10:40:15.320 INFO main root ] Previous Java memory max heap size
was 1024
[01.16.15 10:40:15.322 INFO main root ] END Loading Configuration
jtux Loaded.
Exiting!!! java.lang.RuntimeException: Unexpected IO Exception constructing selector engine - e=java.io.IOException: Function not im
plemented
[01.16.15 10:40:16.256 INFO main root ] ***** STOPPING *****
[01.16.15 10:40:16.257 INFO Thread-0 root ] Stopping service...
[01.16.15 10:40:16.282 INFO Thread-0 root ] DownloadManager stopped.
[01.16.15 10:40:16.285 INFO Thread-0 root ] SystemWatcher stopped.
[01.16.15 10:40:16.286 INFO Thread-0 root ] Service stopped
root@crashplan_1:/ # ​

CrashPlan used to be running at version 3.6.4 but the log seems to indicate that it updated to 3.7.0

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

Is anyone else having CrashPlan connection issues?

 

[nello]

As before, editing this file fixed the problem:

/usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf​

Follow these instructions:

https://forums.freenas.org/index.php?threads/crashplan-3-6-3.18416/#post-101205

 

[nello]

Here are the release notes for CrashPlan ver 3.7.0:

https://support.code42.com/Release_Notes/CrashPlan_For_Home/3.7.0

 

[nello]

Apparently Code42 will continue to overwrite the run.conf file when it pushes out future upgrades.

Joshua B (CODE42 Support)

Jan 22, 4:45 PM

Hello Nello,

Thank you for contacting Code42 Support.

The change you're making to CrashPlan's run.conf file is not supported by Code 42. We would not be in a position to assure that this file will not be updated. In the instance of the 3.7 release, there were changes made to the run.conf as part of the update. Any unauthorized changes may not have been saved and may not be saved in future releases. This helps ensure that CrashPlan runs as expected in supported (non-headless) environments.

Regards,
Joshua
Tier 1 Customer Champion
Code42 Software






Nello xxxxxxx

Jan 20, 11:40 AM

I run a home FreeNAS server and use CrashPlan on it to backup several personal computers for me and my extended family.

The last three versions of CrashPlan (3.6.3, 3.6.4, and now 3.7.0) that Code42 pushed out to headless servers, the updates stop working because they overwrote the configuration file:

/usr/pbi/crashplan-amd64/share/crashplan/bin/run.conf

For a full description of the problem, see:

https://forums.freenas.org/index.php?threads/can-not-connect-to-crashplan-in-jail.26782/


Can you tell me whom to notify of this ongoing problem? Can Code42 stop overwriting run.conf please?