CrashPlan Plugin Issues

[JMaciak87]

I'm trying to install the CrashPlan plugin (3.6.3_1) and I'm getting errors post-install. I'm on FreeNAS-9.10.2-U5 (561f0d7a1).

The main error is:

Code:

Aug 11 11:02:44 redgiant manage.py: [plugins.utils:91] Couldn't retrieve http://10.8.12.9/plugins/crashplan/1/_s/status: HTTP Error 503: OK

That occurs at the end of the install and also when I try to view the "Installed" plugins.

During the install, these errors come up:

Code:

Aug 11 11:00:45 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 11:00:45 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 11:00:45 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 11:00:45 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 11:00:51 redgiant manage.py: [freeadmin.navtree:577] Couldn't retrieve http://10.8.12.9/plugins/crashplan/1/_s/treemenu: timed out

I've checked the jail, it has an IP address on the same network and I can ping the GW. Initially it had issues with DHCP, so I manually set an IP.

Still getting this error:

Code:

Aug 11 11:39:18 redgiant manage.py: [plugins.utils:91] Couldn't retrieve http://10.8.12.9/plugins/crashplan/1/_s/status: HTTP Error 503: OK

Ideas?

 

[joeschmuck]

Do you have the Gateway setup on FreeNAS? If you were having DHCP issues and changed over to a static IP, you may have forgot to setup the gateway address.

 

[JMaciak87]

Do you have the Gateway setup on FreeNAS? If you were having DHCP issues and changed over to a static IP, you may have forgot to setup the gateway address.

I did not have a gateway set in Network > Global Config. I set it accordingly...

I'm still getting this error:

Code:

Aug 11 13:37:54 redgiant manage.py: [plugins.utils:91] Couldn't retrieve http://10.8.12.9/plugins/crashplan/1/_s/status: HTTP Error 503: OK

When I restart the Crashplan jail I get this:

Code:

Aug 11 13:40:27 redgiant kernel: epair1a: link state changed to DOWN
Aug 11 13:40:27 redgiant kernel: epair1a: link state changed to DOWN
Aug 11 13:40:27 redgiant kernel: epair1b: link state changed to DOWN
Aug 11 13:40:27 redgiant kernel: epair1b: link state changed to DOWN
Aug 11 13:40:28 redgiant kernel: ifa_del_loopback_route: deletion failed: 48
Aug 11 13:40:28 redgiant Freed UMA keg (udp_inpcb) was not empty (120 items).  Lost 12 pages of memory.
Aug 11 13:40:28 redgiant Freed UMA keg (udpcb) was not empty (1169 items).  Lost 7 pages of memory.
Aug 11 13:40:28 redgiant Freed UMA keg (ripcb) was not empty (30 items).  Lost 3 pages of memory.
Aug 11 13:40:28 redgiant hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Aug 11 13:40:28 redgiant hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Aug 11 13:40:29 redgiant epair1a: Ethernet address: 02:ff:20:00:08:0a
Aug 11 13:40:29 redgiant epair1b: Ethernet address: 02:ff:70:00:09:0b
Aug 11 13:40:29 redgiant kernel: epair1a: link state changed to UP
Aug 11 13:40:29 redgiant kernel: epair1a: link state changed to UP
Aug 11 13:40:29 redgiant kernel: epair1b: link state changed to UP
Aug 11 13:40:29 redgiant kernel: epair1b: link state changed to UP
Aug 11 13:40:29 redgiant kernel: epair1a: promiscuous mode enabled
Aug 11 13:40:29 redgiant kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Aug 11 13:40:29 redgiant kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Aug 11 13:40:32 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 13:40:32 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 13:40:32 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 13:40:32 redgiant manage.py: [freeadmin.tree.tree:98] Failed to get item order
Traceback (most recent call last):
  File "/usr/local/www/freenasUI/../freenasUI/freeadmin/tree/tree.py", line 95, in __lt__
  return self.gname.lower() < other.gname.lower()
AttributeError: 'int' object has no attribute 'lower'
Aug 11 13:40:38 redgiant manage.py: [freeadmin.navtree:577] Couldn't retrieve http://10.8.12.9/plugins/crashplan/1/_s/treemenu: timed out

It does get an IP now via DHCP, though.

 

[Jailer]

If you search the forums you'll see a plethora of problems with the crashplan plugin. IMHO you would be better off running it in a linux VM.

 

[JMaciak87]

I did see a lot of problems, with no solutions....

That's unfortunate. I was hoping to have everything in once place. Oh well.

 

[scrappy]

I agree with @Jailer. If possible, run Crashplan in a Linux VM and your Crashplan plugin headaches will immediately disappear. Crashplan was never intended to run inside a FreeBSD jail and many times Crashplan updates break the plugin from what I've seen from other users on these forums. I personally use a CentOS VM for Crashplan. It has yum-cron setup for fully automatic updates so I never even worry about keeping it patched.

 

[danb35]

Crashplan was never intended to run inside a FreeBSD jail

More accurately, it was never intended to run on FreeBSD at all (in a jail or otherwise). It's also a very resource-intensive and fragile Java app, which causes its own problems even under a supported environment.