Project

General

Profile

Bug #3375

CrashPlan engine does not start within jail

Added by Richard Grech over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
No priority
Assignee:
William Grzybowski
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Looks like this is a problem and I don't think it's formally documented anywhere.

The crashplan engine needs to be manually started all the time from within the jail. Both directly after installing the plugin and on each restart of the system.

jexec crashplan_1 /bin/tcsh
cpuset -l 0 /usr/local/share/crashplan/bin/CrashPlanEngine start

History

#1 Updated by William Grzybowski over 5 years ago

  • Status changed from Unscreened to Screened
  • Priority changed from Important to No priority

Manually started? It can be started from Plugins-> CrashPlan -> ON.

That doesn't work for you?

#2 Updated by Richard Grech over 5 years ago

That "works" in the sense that the switch flips, but it doesn't actually start the engine inside of the jail.

This forum post documents the problems that others have had
http://forums.freenas.org/threads/crashplan-plugin.15366/page-2

#3 Updated by Anonymous over 5 years ago

Richard is right, maybe some problem with specific CPU architecture.

With me, also only "cpuset -l 0" makes crashplan work OK.

#4 Updated by William Grzybowski over 5 years ago

  • Assignee set to William Grzybowski

#5 Updated by Jens Andersson over 5 years ago

IT autostarts if you create a /etc/rc.local inside the jail.
Make sure to set rc.local executable, "chmod 775 rc.local"
and then add
cpuset -l 0 /usr/local/share/crashplan/bin/CrashPlanEngine start
to the file.
maybe this could be added to the plugin.

#6 Updated by William Grzybowski over 5 years ago

  • Status changed from Screened to Fix In Progress

cpuset -l 0 has been added to the plguin, it needs to be rebuilt and uploaded to the repo.

#7 Updated by Jens Andersson over 5 years ago

Seems that starting from rc.local does not work.
but logging into the jail and starting manual with "cpuset -l 0 /usr/local/share/crashplan/bin/CrashPlanEngine start"
stil works.

#8 Updated by Kal Bhatt over 5 years ago

I had the same issue. I used the cpuset command listed here to start the engine. I also had to manually create '/var/log/crashplan'.

#9 Updated by William Grzybowski about 5 years ago

  • Status changed from Fix In Progress to Resolved
  • Target version set to 9.2.1.5-RELEASE

Also available in: Atom PDF