Skip to main content
Contact Support

This article applies to Code42 for Enterprise version 4.

Code42 Support

Configure CrashPlan engine to start on boot (OpenSUSE 12.3)

  1. Last updated
  2. Save as PDF

This article applies to Code42 for Enterprise version 4.

Overview

After you install the CrashPlan app on OpenSUSE 12.3, the backup engine will run successfully until you reboot the system. After rebooting, the backup engine is not running. This causes the CrashPlan app to fail at launch and displays an "Unable to Connect to Backup Engine" error. Retrying the connection will not succeed unless you manually start the process:

$ sudo /etc/init.d/crashplan start

This article will help you configure the CrashPlan app to start automatically at system boot.

Affects

All CrashPlan apps installed on OpenSUSE 12.3

Considerations

  • This solution has been tested with OpenSUSE, version 12.3. This solution may not be applicable to other versions of OpenSUSE, or to other Linux distributions.
  • CrashPlan installs its runlevel init links in /etc/rc5.d by default, but OpenSUSE 12.3 does not recognize this placement, and therefore does not run the startup script automatically.

Recommended solution

Already installed the CrashPlan app?

Fix this problem via this command in a terminal window:

$ sudo insserv /etc/init.d/crashplan

On subsequent reboots, the backup engine will start.

Haven't installed the CrashPlan app?

Solve this problem at installation by changing the runlevel init link location. When running the CrashPlan app's install script, look for this line:

What directory contains your runlevel init links? [/etc/rc5.d]

Change the value to: /etc/init.d/rc5.d

What directory contains your runlevel init links? [/etc/rc5.d] /etc/init.d/rc5.d

The CrashPlan backup engine will automatically start on boot.