Code42 agent does not restart after Linux reboots or upgrades


If your Code42 agent does not restart when its Linux machine reboots or upgrades, follow these instructions to determine whether a new or revised restart script will solve the problem. If so, follow the instructions to create a Code42 agent restart script in /lib/systemd/system/ or to modify the existing script at /etc/init.d/.


Code42 agents installed on Linux for all users (the default). When Linux reboots, the Code42 agent fails to restart. Or a Linux upgrade process reports an error.

Unsupported process
The information presented here is intended to offer information to advanced users. However, Code42 does not design or test products for the use described here. This information is presented because of user requests.

Our Technical Support Engineers cannot assist you with unsupported processes, so you assume all risk of unintended behavior.


The Code42 agent writes its restart script to a file in /etc/init.d, a long-time standard for Linux systems. Two Linux variations require a new or revised script:

Missing systemd script

Some Linux systems (see the list below) look for restart scripts in /lib/systemd rather than /etc/init.d. To make those systems restart the Code42 agent when they reboot, you need to create a restart script at: 

Linux distributions that implement systemd:

  • Supported by Code42
    • Red Hat Enterprise Linux (RHEL)
    • Ubuntu 
  • Unsupported by Code42
    • CentOS 
    • Debian
    • Fedora
    • openSUSE
    • SUSE Linux Enterprise Server

For details, see Wikipedia's article on systemd.

Non-compliant init.d script

In addition, some Linux systems that use init.d scripts, or both systemd and init.d, require compliance with a standard called Linux Standard Base (LSB). To meet that standard, you need to add some header information to the file:

Failed upgrade due to non-LSB compliance of systemd
If you have only a systemd script, then upgrades may fail because the upgrade process cannot run the init.d script to stop the Code42 agent before proceeding. Therefore, if you have a failed upgrade, try making the /etc/init.d/code42 or /etc/init.d/crashplan file LSB-compliant.
Users have reported LSB problems on these Linux distributions:

  • Supported by Code42
    • Red Hat Enterprise Linux (RHEL)
    • Ubuntu
  • Unsupported by Code42
    • CentOS 
    • Debian 

Diagnose and fix

The Code42 agent may fail to restart after its Linux machine reboots for either or both of the causes described above. Follow the instructions in the order presented below to:

  1. Determine whether your Linux machine uses systemd.
    If it does, install the systemd script, then reboot the machine.
    If the Code42 agent restarts, the problem is solved. You are finished.
  2. Determine whether your Linux distribution requires LSB compliance.
    If it does, edit the init.d script.

Note that an LSB problem may not show up until after a systemd problem is solved and the system rebooted.

Verify and use systemd

Determine whether your Linux machine uses systemd

At the Linux command line, enter the command:

sudo stat /proc/1/exe | head -1

If the command returns a reference to a systemd directory, as in the example below, then your Linux distribution does use systemd to manage services. Proceed with Install the systemd script, immediately below.

>$ sudo stat /proc/1/exe | head -1
>$ File: '/proc/1/exe' -> '/usr/lib/systemd/systemd'

If your Linux distribution does not use systemd, skip ahead to Diagnose and implement LSB compliance.

Install the systemd script

  1. Copy the script below into a new file /lib/systemd/system/code42.service

    Description=Code42 app
    ExecStart=/usr/local/crashplan/bin/Code42Service start
    ExecStop=/usr/local/crashplan/bin/Code42Service stop
  2. Edit the file paths in the script, if necessary.
    The script below points to the default paths. Only a nonstandard installation needs changes to the script.
  3. At the Linux command line, enter two commands:
    sudo systemctl daemon-reload
    sudo systemctl enable code42.service
  4. Verify that the second command returns results that report creating the symlink:
    Created symlink from /etc/systemd/system/ to /lib/systemd/system/code42.service
    Do not create the symlink manually; that may lead to problems of ownership and privileges.
  5. Restart the Code42 agent with the new code42.service script. The command is:
    sudo systemctl restart code42
  6. Reboot your machine with this command:
    sudo shutdown -r now
  7. Verify that the Code42 agent restarted with this command:
    sudo systemctl status code42.service
    If the Code42 agent restarts, the problem is solved. Your work is done.
    If the Code42 agent does not restart, proceed with Diagnose and implement LSB compliance.

Diagnose and implement LSB compliance

Determine whether your Linux machine requires LSB compliance

Search through your system logs using a command like the following:

sudo grep -r Code42Service /var/log/*

Look for a message like this one:

insserv: warning: script 'Code42Service' missing LSB tags and overrides

If you find such a message, edit the existing init.d script to comply with the LSB standard.

Edit init.d script to comply with LSB

  1. Open /etc/init.d/code42 with a text editor.
  2. Copy the following 13 lines to the top of the file.

    # Linux Standard Base comments
    # Provides: Code42Service
    # Required-Start: $local_fs $network $remote_fs
    # Required-Stop: $local_fs $network $remote_fs
    # Should-Start:
    # Should-Stop:
    # Default-Start: 2 3 4 5
    # Default-Stop: 0 1 6
    # Short-Description: Code42 Service
    # Description: Code42 data security service

  3. Reboot your machine with this command:
    sudo shutdown -r now
  4. Verify that the Code42 agent restarted by by reopening the Code42 agent, or with a command like the following:
    service --status-all
    If the Code42 agent does not restart, contact our Technical Support Engineers​.